From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, John Barham <jbarham@gmail.com>
Subject: Re: [9fans] acme mail on unix
Date: Fri, 20 Jan 2006 08:50:38 -0500 [thread overview]
Message-ID: <20060120135038.04867B095F@conchobor.berzerked.org> (raw)
In-Reply-To: <4f34febc0601192204u4787baa6w92c16b49834e1709@mail.gmail.com>
the standard for the top level is $home/.maildir or $home/Maildir (cyrus).
you can get away with only working with $MAILDIR/new if you don't
have a need for maildir-style folders (which start with a "." and get utf-7-
encoded).
there is disagreement about the format of the unique.file.name. the cyrus
maildir man page says this:
A new unique filename is created using one of two possible forms:
``time.MusecPpid.host'', or ``time.MusecPpid_unique.host''. ``time''
and ``usec'' is the current system time, obtained from gettimeofday(2).
``pid'' is the process number of the process that is delivering this
message to the maildir. ``host'' is the name of the machine where the
mail is being delivered.
their maildir files look like this
1136731697.M580106P15382V0000000000000303I0009030C_0.conchobor.berzerked.org,S=2872
(the S=2872 is the file size. i'm not sure why stat is so expensive on their machine.)
but postfix gives you this:
1137764424.Vfe04I16e1M435392.dexter-peak.quanstro.net
and fetchmail gives you this
1125641448.1984_0.dexter-peak
i don't use djb's stuff, but i'm sure he disagrees with all of these formats. ;-)
i see the important part of the file format to be time "." unique-extension.
i wrote a set of programs for reading mail in maildirs (from, mcat, mimedesc,
e.g.). they get buy by not paying any attention to the file names.
- erik
John Barham <jbarham@gmail.com> writes
|
| > Maildir uses the structure folder/{tmp,cur,new}/unique.file.name.
| > The files are required to be uniquely named, and there is a convention for
| > the intermediate directories. djb has a brief but detailed specification
| > under cr.yp.to somewhere, if you want to google for it.
|
| http://cr.yp.to/proto/maildir.html
next prev parent reply other threads:[~2006-01-20 13:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 16:46 Russ Cox
2006-01-18 17:56 ` Tim Wiess
2006-01-18 18:08 ` Tim Wiess
2006-01-18 19:10 ` Russ Cox
2006-01-19 16:17 ` Aaron Griffin
2006-01-19 16:24 ` Russ Cox
2006-01-19 21:28 ` Dan Cross
2006-01-19 21:58 ` Russ Cox
2006-01-20 2:38 ` geoff
2006-01-20 5:31 ` Scott Schwartz
2006-01-20 6:04 ` John Barham
2006-01-20 13:50 ` erik quanstrom [this message]
2006-01-20 23:01 ` Dave Eckhardt
2006-01-21 0:06 ` erik quanstrom
2006-01-20 13:58 ` erik quanstrom
2006-01-20 20:02 ` erik quanstrom
2006-01-20 20:12 ` uriel
2006-01-20 20:18 ` erik quanstrom
2006-01-20 20:41 ` uriel
2006-01-20 20:59 ` erik quanstrom
2006-01-20 22:58 Russ Cox
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=20060120135038.04867B095F@conchobor.berzerked.org \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=jbarham@gmail.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).