On Sun, Mar 11, 2001 at 07:37:06PM +0000, Mark Delany wrote:
[...]
> A more sensible strategy might be to introduce a new "info" flag (say
> '3' equals POP wire size) on the filename, eg, a 10,000 byte email has
> a name something like this:
>
> Maildir/new/980195114.16740.geex:2,RS3,10000
>From reading <URL:http://cr.yp.to/proto/maildir.html>, it is not clear to me
that this would be the proper format for such an 'info' extension. I would
worry that MUAs and other software dealing with maildir (scripts!) would
expect info semantics in the 2, series to be at the end of the filenames.
> Optimally the wire-size is calculated when the mail is written to
> Maildir/tmp/ and then applied as an "info" flag when the file is moved
> to Maildir/new/.
> A possible complication with this approach is that my reading of
> Maildir infers that "info" can only be set when the file moves from
> Maildir/new/ to Maildir/cur/.
No, this is not what that document says. It says
"When you move a file from new to cur, you have to change it's name [...]"
You *have* to change the name when the file move from new/ to cur/ , but
there is no specification of other cases; in fact, lots of MUA's will change
info when the file has been in cur/ for a while: mutt, for example, moves
the file from new/ to cur/, adds :2, and only modifies that to be 2,S after
the user has read the message (it is no longer 'N'ew).
Vince.
