From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Skip intermediate mbox file in mail-sources?
Date: Wed, 28 May 2003 14:55:03 -0400 [thread overview]
Message-ID: <4n7k8aewag.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87d6i43wgs.fsf@cag.lcs.mit.edu> (David Z. Maze's message of "Tue, 27 May 2003 17:34:27 -0400")
On Tue, 27 May 2003, dmaze@MIT.EDU wrote:
> Is there a reason the intermediate mbox file is necessary? (I could
> entirely believe that, once upon a time, GNUS only grokked mbox
> format, and "translate anything to mbox" was the easiest way to add
> more mail sources.) With formats like directory, pop, maildir, and
> imap, where you can readily fetch a message at a time, this adds an
> unnecessary layer of indirection.
I think it makes sense to have a uniform format for incoming mail. I
don't think mbox is it, but there should be just one format. How
about a message digest with MIME attachments? Gnus already has the
functionality to parse those, so the backend modifications should be
fairly simple.
Fetching a message at a time may be inconvenient or unfeasible, so I
think a format like digests that allows 1 to N attachments with
minimal overhead and no quoting issues is nice.
> This also results in side effects: From at the start of the line
> gets the ugly mbox quoting, which really shouldn't be necessary
> unless the backend is also in mbox format.
MIME attachments would avoid this problem and most others with the
mbox format, I think.
Ted
next prev parent reply other threads:[~2003-05-28 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 21:34 David Z Maze
2003-05-28 9:05 ` Kai Großjohann
2003-05-28 18:55 ` Ted Zlatanov [this message]
2003-05-29 8:40 ` Kai Großjohann
2003-10-18 12:59 ` Lars Magne Ingebrigtsen
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=4n7k8aewag.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).