Dom> It all depends on whether you mean "shared mail queue" or "shared Dom> maildrops"... Sharing the mail queue is a big nono, really. Dom> None of the existing MTA's support doing this, and it will cause Dom> you slow mail delivery and general havoc.
Shared maildrops and home directories is what I'm looking for. I'm planning to leave the mail queues on the individual machines, though a combined view of everything would be nice. (Actually storing each machine's queue (separately) on the filer might be nice for reliability and management reasons. I'm not sure about performance.)
Dom> Shared maildrops are a different issue. If you use something Dom> like qmail[1], OTOH, there are simply no locking issues Dom> whatsoever (and easy POP3 support, but no IMAP).
I'll have another look at qmail, but we're pretty firmly entrenched in the sendmail camp at the moment, for a variety of reasons.
Dom> Don't forget to set up a directory hashing scheme, though as Dom> 100,000 files in a directory will also cause you performance Dom> problems. :-)
I'll probably do this anyway while switching over. We don't have enough files now to be much of an issue on a WAFL file system, but we might as well put in the scalability now. -- Alan
+--- In our lifetime, Alan Judge Alan.Judge@indigo.ie wrote: | | I'll have another look at qmail, but we're pretty firmly entrenched in | the sendmail camp at the moment, for a variety of reasons.
sendmail and the delivery agent have nothing to do with each other. What makes the qmail concept so cool is that there is no mbox format file. Every piece of mail is a separate file.
You can achieve the same goal by hacking the local delivery agent do the same. And you can stick with sendmail, if that is what you like.
Of course, you could have a setup that has boxes running sendmail for queue runs as well as setup as MX's. Then your sendmail box simply passes the email that is slated for local delivery to a qmail machine(s). And frankly, BSDI boxes make for amazing mail machines (very cheap!). Then you can run a hacked qpopper, the qmail-qpopper, or hack your own. This setup becomes quite fault tolerant (no single piece breaks the whole; save for the filer), scaleable (adding more boxes to do dedicated tasks is a trivial issue) and reliable (boxes doing single tasks rarely fail; in my experience (except for solaris, of course...)).
Alexei