11/18 Can someone recommend a good place to get started on procmail and
SpamAssassin? I forward my soda mail to another account, which avoids
the (very effective) blacklists on that machine. I'd like to send it
through SpamAssassin before it gets forwarded. -John
\_ motd log or what I do:
:0fw
| /usr/local/bin/spamc
X-Spam-Status: Yes
gets set if the message is spam. you can then do something like:
:0 hw:
* ^X-Spam-Status: Yes
spamassassin
\_ The spamassassin docs say how to do set it up with procmail.
\_ Just curious, anyone tried using both ifile and spamassassin?
\_ Yes, but it was hard to get it through both filters. If you run
ifile first, SpamAssassin will overwrite the X-Ifile spam header
and make the message an attachment. If you do SpamAssassin
first, ifile will "learn" from SA's X-Spam-Status header, which
is bad.
and make the message an attachment. If you do SpamAssassin first,
\_ Can you get ifile is ignore that header? --sa user
\_ Possibly, but then you're still running ifile on a post-SA
piece of spam-- SA removes all headers except for To, From,
Date, & Subject, then attach-ifies the rest (last time I
\_ isn't that a SA option? (user_prefs)
\_ indeedy do. Thanks.
checked), so ifile will start to pick up on that sort of
pattern. OTOH, since ifile is only looking for words and
ifile will "learn" from SA's X-Spam-Status header, which is bad.
\_ Can you get ifile is ignore that header? --sa user
\_ man spam
not format, this might not be a huge issue.
\_ anyone have a local install of spamassassin 2.60?
\_ Yeah in ~abuser/trojans/hehehe/spamassassin/bin/
\_ man spam |
http://csua.com/feed/