9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: rsc@swtch.com, 9fans@9fans.net
Subject: Re: [9fans] Mail configuration
Date: Fri, 20 Feb 2009 10:59:15 -0500	[thread overview]
Message-ID: <6c3fa750d6017250cd40c1f0fc19aeb8@quanstro.net> (raw)

> 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.
[..]
> 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.

(n)upas/fs imap4 client uses the body[]<n.m> syntax
to download blocks from the message.  this technique
also works on gmail.  however, gmail lies about message
sizes so there's a bit of extra work.

> Messages saved with the Save command
> go into imap folders, not local files.

cool.  (n)upas lacks this ability, but has the framework
for adding it.  it would take a little work to figure out
how to handle defaulting to the imap server or
to another folder.  the folder selection code is
already horrible.

- erik


             reply	other threads:[~2009-02-20 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 15:59 erik quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-20 15:59 erik quanstrom
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
2009-02-20 16:04 ` 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=6c3fa750d6017250cd40c1f0fc19aeb8@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    --cc=rsc@swtch.com \
    /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).