Cedartech Administrator wrote:
I have asked before but have been unable to get a usable solution. I am
running qmail, spamassassin, clamav, etc from the qmr package on one of
our FBSD 6.2 servers. If you email via squirrelmail, your outbound email
does not get labeled spam. If you send out via a client with smtp, it
labels 95% of it as spam...so when you email someone, they get it with
:SPAM: in the subject. These days with the spammers and the ammount of
users I can not kill off spamassassin all together. I really do not want
to have to pay for a subscription to postini either. Can someone help me
stop spamassassin from scanning my users smtp sessions and only scan mail
coming in?
Cedar Springs Technologies
As Robert has already mentioned, you need to make it that your client's
SMTP connections don't feed through SpamAssassin.
The process to fix this is not truly a SA problem; it's an issue in the
SMTPD process itself.
I see you're already getting answers on the QMR list. That's properly
where it belongs, no matter what John Johnstone says.
In short, you need to use daemontools, create _two_ smtpd processes.
One is the normal SMTPD that doesn't require authentication, and
receives email for your local domains. This _should_ process through
qmail-scanner or simscan. The other should be an authenticated ONLY
(preferably SSL, of course) SMTPD on port 465 (as I recall). That one
can either receive email and not scan it at all, or you can try creating
a second scanner install that stores separately from the first, and only
calls the antivirus. (I'd suggest, at your apparent level, that you
don't try to create the second scanner to start).
Yes, they will authenticate against the same user database. They're the
same program, they're just spawned with different configurations.
BW