Quoting grarpamp <grarp...@gmail.com>:
specified out there that applications could utilize...
where n is your split width... tmp/n, new/n, cur/n.
alternate you may use mdbox
http://wiki2.dovecot.org/MailboxFormat/dbox
Both of these hold all messages in a single directory.
So sdbox would be no advantage there.
And mdbox does not support one message per file, nor
without metadata added to it, so those needing that for
other purposes would have no advantage.
[There is a per file limit specified in bytes, not count. It's
not clear what the behavior would be if a proposed new msg in
a new file would exceed a lesser byte limit. Perhaps a safe
bounce or queue.]
I do like that they are reasonably well specified, publicly
on a wiki as opposed to only in source, and have a comparison
table of support on the parent page. All of which lead to easier
review and adoption by interested parties.
It used to take me well over 2days to backup my email.
I switched to using mdbox 2.2years ago, and I have been extreemly
happy with it.
Current stats on my personal mailbox is 4.8gigs compressed, holding
8.3gigs of email.
470k emails in 300 mdbox files (exactly 300 currently), the current
mdbox file number is 850
I purge emails weekly out of my mdbox files.
So with my average mailfolder holding 10k+ emails with maildir, or 300
files in a folder for mdbox, mdbox wins for me.
I never switched to dbox, but the gains with using it are also
available for using mdbox, you can use single instance storage, and
archival storage. I think the limit is using 3 different paths to hold
your dbox/mdbox files.
