Robbie Garrett skrev, on 27-02-2008 15:07:
are any of you are using dspam as a daemon?
I am.
and what MTA are you using to feed
into it?
Postfix 2.5.1 with 2 smtpd listeners, MySQL 5.0 backend.
Also.. what are your processing times?
Mostly from 0.01 to 0.3 seconds per message on high-end hardware.
Im getting anywhere from 1 to 12 seconds
per message.. and sadly it's not based on message size. I'm guessing if i
run
dspam as a daemon it wil improve my message processing time.
I don't suppose running dspam as a daemon will help you get much better
times than any other method.
so dspam gets the message first.. then hands it to your smtp server for
delivery and virus scan?
Please keep replies to the list.
No, Postfix has the possibility of running multiple smtpd listeners on
different ports simultaneously, each doing its own thing.
Mail comes into LDAP-based smtpd on port 25 (or 587 or 465) which hands
on to a Perl-based content filter, amavisd-new, on port 10024 which runs
Clamav and Bitdefender for virus scanning, hands on to smtpd on port
10025 which hands inet lmtp port 24 to dspam which hands smtp to smtpd
on port 10026 which runs DKIM milter and hands onto pipe which hands off
to LDAP-based Courier maildrop as LDA.
So there is one glorified pre-queue content filter of which dspam is
just a single component. If any one of the components rejects the
message, smtpd on the incoming port (25, 587 or 465) rejects the
message with an smtp 55x before letting go of the client connection.
Best,
--Tonni
--
Tony Earnshaw
Email: tonni at hetnet dot nl
