Hi,
On Tue, 12.12.2006 at 08:37:30 -0600, Mark Farver <mfarver@ticom.com> wrote:
> I recommend replacing qmail-smtpd with qpsmtpd. qpsmtpd is
> also written in Perl, but it is fast and a number of high
> volume sites utilize it. (Apache.com and perl.com IIRC)
>
> http://smtpd.develooper.com/
I was also thinking along these lines, but wondered if/why I should not
stick with the qmail-smtpd (from qmail-ldap, of course) + qmail-scanner
combo I've been using so far. I have to test it out (or read the code),
but I think that plugging into qmail-scanner would be just as easy,
and should yield much the same result (ie, reject the message during
the SMTP session). I'd rather not miss TLS and all the other goodies,
and don't yet know if qpsmtpd supports all of these.
Last but not least, there is the possibility of hacking some more
features into qmail-smtpd... 'helowait' comes to mind...
> I noticed a lot of our spam was arriving with "Delivered-To"
> headers already set to my user and server. qmail-local will
I also have a lot of these.
> Adding qpsmtpd, and spamassassin during smtp means I am now
> rejecting 95% of incoming mail during the SMTP transaction. My
> mail server has essentially no load processing 10,000 messages
> per day. (A light workload, I admit)
Please look at the message header lines or your protocol. I'm very
interested in the performance figures for your SpamAssassin. On servers
I tend, I see regularly about 15 CPU seconds burned _per_message_,
which I find way to high. OTOH I'm unaware of alternatives that have
comparable filtering abilities.
TIA!
Best,
--Toni++
|