On Thu, 26 Sep 2013, Matus UHLAR - fantomas wrote:
On Tue, 2013-09-24 at 21:12 -0700, [email protected] wrote:
I just installed 3.3.2 on Slackware 14. I am seeing what looks like
duplicated effort in /var/log/mailog. Here is the log for a single
email. You can see the same message ID is processed first by root, then
twice as user bobo. Is this normal? I had been using SA 3.2.5 on
the decommissioned server and i never saw this:
On 26.09.13 01:17, Karsten Bräckelmann wrote:
You will have to review the entire mail processing chain on that
machine. Here's what I can tell from your logs:
The first scan appears to be by a milter -- most likely some (changed)
default configuration of Sendmail on Slackware. It is obvious this first
scan is not intended by you (Bayes DB locking fails, and missing custom
required_score conf).
Disable the unwanted milter in your Sendmail config.
Oh, no. Milter is the best way to refuse clear spam at SMTP time.
just configure it so it can use the correct user names.
Maybe using -e or -x options for spamass-milter?
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Spam = (S)tupid (P)eople's (A)dvertising (M)ethod
Thank you, Matus. It wasn't the -e or -x switches. But I was missing the
-u switch and putting it in stopped emails from being scanned as user
root, which was the first problem.
Thank you also to Kevin, John and Karsten. spamc was, in fact, being
called by sendmail, the system procmailrc and bobo's ~/.procmailrc for a
total of three calls. The procmail rc files have been fixed and
everything is working as it should.
Thanks again,
Kevin
