qmail
I’m not here to sing the death of Sendmail. Let’s just say that I’m tired of editing arcane files in order to compile even more arcane files. I’d like some closer sense of what the email server’s doing, and frankly, Sendmail and I aren’t the best of friends. We can work together, but we can’t really dance or sing.
My boss’s business hosts domains (like most do, these days), and so we have a whole bunch of pre-existing users, domains, forwards and autoresponders. We have been creating system users for each of these users, which can confuse the matter. I’ve already gotten ftp to read the database information for the users so we didn’t need shell accounts for that, and I wanted to do the same for email. Seems like a fairly simple idea; and yes, some people have walked this road before. I chose “qmail” for our system based on its speed and ease-of-configuration.
I strongly recommend the Life With Qmail site. He’s done a terrific job making it way too easy to install qmail. If you plan to incorporate qmail and mysql, however, first go through his setup. You can even patch vpopmail to use mysql. I don’t recommend patching both qmail and vpopmail; since both have hardcoded information in their configurations, it was very difficult to get them to talk to each other. I wound up receiving email ok for users in the database, but they couldn’t get their email. They could check it, but it wasn’t there. In order to keep from maintaining 3 database tables (the original hosting one, the vpopmail one and the qmail one). To simplify matters, I ripped out the qmail and started over without the mysql-patched version (but kept the mysql-patched vpopmail).
To be continued …

