Scott Pilz <tech(_at_)squid(_dot_)tznet(_dot_)com> writes:
We are setting up a server with Sendmail, Qpopper and Procmail.
Using Qpopper, there is a way (that is soposedly better) for storing mail..
/var/mail/a/a
/var/mail/a/b
/var/mail/a/c
...
/var/mail/z/a
/var/mail/z/b
/var/mail/z/c
So the username tech for example would be put in /var/mail/t/e/tech..
Now, Qpopper is just the pop3 server, but procmail (in place of the
old 'mail' system on our bbsd box) actually saves the mail locally..
how can we setup procmail (or can we? and if we can't, what can we
use?) to use qpoppers structure?
Grab the procmail source from
ftp://ftp.procmail.org/pub/procmail/procmail.tar.gz
Then edit either the config.h or src/authenticate.c file and insert
the line
#define MAILSPOOLHASH 2
All the options for controlling the location of the mailspool are described
at the top of the src/authenticate.c file.
Another interesting question, ... If you have, say 10,000 users on a
box, and each one has their own mail placed in /var/mail, won't that be
somewhat SLOW being so many names to be accessed in one directory?
isn't it better to do the above way?
Not necessarily: some UNIXes have file systems that can efficiently
support very large directories (IRIX's XFS comes to mind), in which
case the explicit hashing scheme that you describe will actually be
slower than a 'flat' directory. There are also backwards compatibility
issues for many sites. But yes, most 'large' sites should not store
mailboxes in a flat directory.
Philip Guenther
Procmail Maintainer
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail