On Feb 04, David T-G [[EMAIL PROTECTED]] wrote: > So tell me a bit about Maildir... When new mail arrives, it is written > to tmp/ and then atomically moved to new/, right? Does it stay in new/ > until you read it and it moves to cur/? If that's the usual behavior,
Yes.
> when you e'x'it or otherwise don't sync your changes (like changing from
> 'n'ew to read) do they stay in new/ instead of moving? I had thought
Yes. And Mutt will move them back to new/ if you toggle the N flag to true
again and sync.
> that all mail gets moved to cur/ as a final part of the delivery and that
> the MUA was not expected to find things in new/ ...
No... the MTA is responsible for getting it to new/. The MUA is
responsible for it after that.
From the maildir(5) man page:
HOW A MESSAGE IS DELIVERED
...
Files in cur are just like files in new. The big differ
ence is that files in cur are no longer new mail: they
have been seen by the user's mail-reading program.
...
HOW A MESSAGE IS READ
A mail reader operates as follows.
It looks through the new directory for new messages. Say
there is a new message, new/unique. The reader may freely
display the contents of new/unique, delete new/unique, or
rename new/unique as cur/unique:info. See
http://pobox.com/~djb/proto/maildir.html for the meaning
of info.
The reader is also expected to look through the tmp direc
tory and to clean up any old files found there. A file in
tmp may be safely removed if it has not been accessed in
36 hours.
It is a good idea for readers to skip all filenames in new
and cur starting with a dot. Other than this, readers
should not attempt to parse filenames.
msg24205/pgp00000.pgp
Description: PGP signature
