9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Mathieu Lonjaret" <lejatorn@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Mail configuration
Date: Mon,  2 Mar 2009 10:40:19 +0100	[thread overview]
Message-ID: <ad38707524a718dfd30d7f7b07bd669c@ipgp.jussieu.fr> (raw)
In-Reply-To: <23496-82982@sneakemail.com>

[-- Attachment #1: Type: text/plain, Size: 290 bytes --]

factotum -g 'key=mykey proto=pass service=imap server=yourserverurl user=yourimapusername !password?'

then

mailfs yourserverurl

or, if you want tls:

mailfs -t yourserverurl

Once it has returned, you can use as a ui the Mail command in acme
for example.

Cheers,
Mathieu

[-- Attachment #2: Type: message/rfc822, Size: 5221 bytes --]

From: 6o205zd02@sneakemail.com
To: 9fans@9fans.net
Subject: Re: [9fans] Mail configuration
Date: Sun, 01 Mar 2009 23:52:12 -0800
Message-ID: <23496-82982@sneakemail.com>

On Fri, 2009-02-20 at 03:06 -0800, Russ Cox rsc-at-swtch.com |9fans|
wrote:
> I didn't bring over upas/fs.
> There is a separate program, not installed
> by default, in src/cmd/upas/nfs (n=new)
> that speaks only imap.  When installed, its
> name is mailfs.  It works with the nedmail
> and acme Mail that are in the plan9port
> distribution; the file tree is slightly different
> than the standard upas/fs (more faithful to imap).
> It downloads pieces of the message as it
> needs them, so if you have big attachments,
> they don't get downloaded until you ask for them.
> Messages saved with the Save command
> go into imap folders, not local files.
> I used this setup for a few years against a dovecot
> imap server.  It does not work against the
> gmail imap server, because gmail imap
> will not serve the full mime tree of the message;
> it only gives you the raw message bytes.
>
> Russ
>

I must be getting dumber, but while I think I successfully built and
installed src/cmd/upas/nfs as mailfs (P9P on debian/testing linux), I
have failed to figure out how to get it to talk to my dovecot server.
Can someone post an example of the command-line they use to run it
(perhaps with a short explanation of the arguments)?

	thanks,
	Peter Canning



  parent reply	other threads:[~2009-03-02  9:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20  8:38 hugo rivera
2009-02-20 11:06 ` Russ Cox
2009-03-02  7:52   ` 6o205zd02
2009-03-02  9:38     ` sqweek
2009-03-02  9:40     ` Mathieu Lonjaret [this message]
2009-02-20 16:04 ` erik quanstrom
  -- strict thread matches above, loose matches on Subject: below --
2009-02-20 15:59 erik quanstrom
2009-02-20 15:59 erik quanstrom
2007-04-02 20:24 Stefan Burtscher
2007-04-02 20:28 ` erik quanstrom
2007-04-02 20:37   ` Russ Cox
2007-04-02 20:30 ` Steve Simon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ad38707524a718dfd30d7f7b07bd669c@ipgp.jussieu.fr \
    --to=lejatorn@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).