[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Sudden instability
From: |
SG |
Subject: |
Re: Sudden instability |
Date: |
Thu, 8 Jul 2004 15:55:51 -0400 |
> If you don't see any milter timeout messages, then something is making
> a decision to not run spamassasin on that mail. The 2 most likely
> explanations: those messages came in via a trusted sender (listed by
> the -i flag to spamass-milter) and checking was skipped, or they were
> over 250k and spamc short-circuited them right back without running
> them through spamassassin. Neither of those seem to be the case for
> you though. Try adding "-d misc" to your spamass-milter commandline
> and see whether you see an "SA Score" maillog entry for the next
> message that doesn't get marked.
>
> Dan Nelson
I put it here:
spamass_milter_flags=${spamass_milter_flags:-"-d misc -f -p
${spamass_milter_socket}"}
Seems to work... I'll keep my eyes on the maillog, when another spam
comes through.
It didn't work when I put spamass_milter_flags="-d misc" in rc.conf
Thnaks,
SG
- Re: Sudden instability, (continued)
- Re: Sudden instability, John E Hein, 2004/07/06
- Re: Sudden instability, SG, 2004/07/06
- Re: Sudden instability, Dan Nelson, 2004/07/06
- Re: Sudden instability, SG, 2004/07/07
- Re: Sudden instability, Dan Nelson, 2004/07/07
- Re: Sudden instability, Todd Lyons, 2004/07/07
- Re: Sudden instability, SG, 2004/07/08
- Re: Sudden instability, Dan Nelson, 2004/07/08
- Re: Sudden instability, SG, 2004/07/08
- Re: Sudden instability, Dan Nelson, 2004/07/08
- Re: Sudden instability,
SG <=
- Re: Sudden instability, SG, 2004/07/08
- Re: Sudden instability, Dan Nelson, 2004/07/08
- Re: Sudden instability, Chris Crowley, 2004/07/08
- Re: Sudden instability, SG, 2004/07/09
- Re: Sudden instability, Dan Nelson, 2004/07/09
- Re: Sudden instability, SG, 2004/07/08
- Re: Sudden instability, SG, 2004/07/08
Update: Re: Sudden instability, Todd Lyons, 2004/07/15