Simple? Well....doable. My experience with qmail in a high-spam environment, more than a million attempted deliveries per month for just one domain due to joe-job attacks, is less than adequate. I hate to say it, but Sendmail was actually working better to stop the joe-job attacks. The biggest problem I had with qmail was recipient verification--there wasn't anything available that could check against a standard user database, like /etc/passwd or vpopmail's vpasswd files. I had to use the moregootrcptto patch for this--and that requires some additional administration overhead.-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 12 January 2004 01:16, Ben Munat wrote:
Okay, that's two votes for postfix and none for qmail... and the words
"simpler to setup and manage" are music to my ear... thanks for the help.
Then I'll put my vote in for qmail.
qmail is simple to setup, and manage. More so with webmin, but still simple from the command line. Can't say I've found anything remotely difficult.
I recently started investigating Postfix and found that it has MANY /built-in/ UCE features--none of which qmail has. Which Postfix, I can reject mail at the SMTP connection level if the HELO/EHLO, MAIL FROM, or RCPT TO has an invalid domain name. I can also specify recipient maps that allow me to add users without having to update any files other than the user database.
For virtuals, well....it doesn't get any easier. One can simply create a MySQL database (or a flat file, if preferred) that contains the necassary data about the virtual users like home directory, quotas, etc.
If you want to talke about "manageability", with qmail I have 10 to 15 programs that I need for each server: qmail and patches, vpopmail, Courier-IMAP, Maildrop, checkpasswd, qmail-scanner, .SqWebmail, SpamAssassin, F-Prot, and others.
With Postfix, I need only Postfix, Courier-IMAP, Maildrop, MySQL (for virtual support), SqWebmail, SpamAssassin, and F-Prot.
Both are good MTAs. But when it comes to manageablity and UCE controls, Postfix has the heads up--for me, anyway.
I've replaced qmail-smtpd with qpsmtpd, a drop in perl replacement. It's so cool to be able to change *anything* I wish with minimal effort.This is actually a nifty idea. The only problem I'd see here is the overhead generated by Perl--using qmail-scanner (all Perl) has more than tripled the CPU/RAM overhead of my server. Most people who write these types of filters disclaim upfront that this type of overhead /will/ occur.
Want to allow one host, or mail to one user to bypass max file size? 2-3 lines of perl and your done (well, I was when I had a user needing to send a few slightly larger files than the max 5meg).
Spamassassin filtering for incoming mail only? Another line or two and the spamassassin plugin is modified to not scan mail from local users.Yeah, Postfix can do that too! ;-)
-- [EMAIL PROTECTED] mailing list
