[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mail bypass spamassassin



On Thu, Apr 11, 2002 at 06:52:10PM -0400, christophe barbé wrote:
> I got a mail with sample.exe (2.4MB) attachment. This mail has not been
> scanned by spamassassin. I don't understand why. I use a procmail rule
> as below :
> 
> # ==== SPAMASSASSIN ====
> :0fw
> | spamc -f

Could it be that spamd was overloaded or spamc otherwise couldn't talk
to it, and so spamc just passed the message through unscanned?

       -f  Cause spamc to safe-failover if it can't connect to
           spamd -- what this means is that in case spamc fails
           to connect to spamd, it will not return with an exit­
           code set, it will instead dump the original message to
           stdout, allowing the message to be delivered, albeit
           unscanned for spam.  Without this flag, connection
           failures to spamd will cause message delivery fail­
           ures.  Even with this flag set however, if spamc con­
           nects successfully, and then encounters an error at a
           later stage of communication, it will still return an
           exitcode.  This now defaults to on, and can't be
           turned off.  This flag is accepted though for back­
           wards-compatibility.

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]


-- 
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: