Gnus development mailing list
 help / color / mirror / Atom feed
From: patl@curl.com (Patrick J. LoPresti)
Subject: Re: Gnus and the qmail maildir format
Date: 10 Apr 1998 13:30:32 -0400	[thread overview]
Message-ID: <s5gn2dtoa87.fsf@curl.com> (raw)
In-Reply-To: Istvan Marko's message of 08 Apr 1998 17:18:36 -0400

>>>>> "imarko" == Istvan Marko <imarko@pacificnet.net> writes:

 imarko> Shouldn't the maildir handling stuff be added to movemail
 imarko> instead? The maildir is just a different kind of INBOX right?

Yes, but with important performance and robustness features that using
movemail would completely defeat.

The original purpose of movemail was to provide system-dependent
locking while accessing a file in the brain-damaged Unix mbox format.
The movemail program is a necessary concession since that brain damage
is so widespread.  Qmail maildirs, on the other hand, are architected
to require no locking at all; they can be accessed simply, directly,
and reliably by Emacs lisp.  (In fact, it is even easier than I first
thought; I just noticed that the "rename-file" function does the Right
Thing whether or not the destination is on a different filesystem than
the source.)

As you probably know, movemail was later modified to support POP.
That was a mistake.  It works by connecting to a server, dragging over
all the messages, and stuffing them into a file in mbox format.  Thus
it inflicts the brain damage of mbox (">From " quoting and *potential
mail loss*) where it isn't necessary.

Abstractions are good.  But abstractions should not be chosen based on
the need to support a stupid and fragile format, then forcing that
format (with its stupidity and fragility) onto everything in the name
of preserving the abstraction.

I agree that maildir handling should be in a library accessible by
other Emacs MUAs.  But it should be written in Emacs Lisp, so that it
will 1) automatically work portably across platforms; 2) preserve the
sanity and robustness of the maildir format; and 3) be faster.

Since nobody else has volunteered to take up this task, I guess I will
have to hack it up myself.

 - Pat

P.S.  Lars, is there any chance of your including such a thing in the
standard distribution?  If not, I do not want to waste time making it
"clean"...


  reply	other threads:[~1998-04-10 17:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3wwddekkx.fsf@toyland.sauerland.de>
     [not found] ` <x7u38e28hc.fsf@gkar.prescienttech.com>
1998-04-08 19:28   ` Patrick J. LoPresti
1998-04-08 21:18     ` Istvan Marko
1998-04-10 17:30       ` Patrick J. LoPresti [this message]
1998-04-10 18:39         ` Kai Grossjohann
     [not found]           ` <x7ra339ho5.fsf@peorth.gweep.net>
1998-04-12 16:18             ` Alan Shutko
1998-04-23 14:23         ` Carsten Leonhardt
     [not found]           ` <x77m4gnsjs.fsf@peorth.gweep.net>
1998-04-24  8:02             ` Robert Bihlmeyer
1998-04-25 16:04               ` Patrick J. LoPresti
1998-04-27 20:48                 ` Dan Christensen
1998-04-28  0:59                   ` Patrick J. LoPresti
1998-04-24 20:08         ` 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=s5gn2dtoa87.fsf@curl.com \
    --to=patl@curl.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).