Re: [vox-tech] sendmail+spamassassin
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [vox-tech] sendmail+spamassassin
Thanks a lot for the response and links, i finally got my sendmail +
mailfilter + spamassassin + f-prot works!
it works like SPAM feature of yahoo.com , finally.
----- Original Message -----
From: "ME" <email@example.com>
Sent: Thursday, May 27, 2004 3:34 PM
Subject: Re: [vox-tech] sendmail+spamassassin
> Milver S. Nisay said:
> > hello there.
> > anybody can guide me to useful link on settiup up sendmail +
> > my sendmail works fine. my spamassassin installed successfully.
> > my problem is it seems that sendmail does not know that spamassassin is
> > existing therefore
> > spamassassin is not working together with sendmail. anyone?
> > i have RH9, sendmail-8.12.8-9.90, sendmail-cf-8.12.8-9.90 .
> Pete gave you a link, and I'll comment with a description of where you
> should be looking in the process.
> SpamAssassin will only *mark* mail as being spam-like or non-spam-like
> based on criteria you give it through configuration (simplest would be the
> score threshold where by which a message is marked as spam or not.) It is
> possible that spamassassin and sendmail are working fine on your system,
> but you have not enabled a 3rd program to actually filter your messages
> based on their status as marked by SpamAssassin.
> It is a common misconception that SpamAssassin would pre-locate messages
> marked as spam in "greymail" or "spam" folders for you. SpamAssassin (SA)
> only marks messages. It is up to you to use a mail client's filtering , or
> something like procmail to control how messages marked as spam should be
> saved, and in what "folders."
> To see if SA is working, look through your messages' extended header
> information and see if you can find any reference to "spam"
> An example header of message tagged as spam:
> Received: from localhost by hoch.passwall.com
> with SpamAssassin (2.62 2004-01-11);
> Thu, 27 May 2004 05:15:03 -0700
> From: "========= ========" <=.======@==========.==>
> To: firstname.lastname@example.org
> Subject: ============================
> Date: Thu, 27 May 2004 12:16:47 +0000
> Message-Id: <88e801c443e4$bb6837d8$47b38be8@mbefzrbj>
> X-Spam-Flag: YES
> X-Spam-Checker-Version: SpamAssassin 2.62 (2004-01-11) on
> X-Spam-Level: ********
> X-Spam-Status: Yes, hits=8.7 required=5.0 tests=BAYES_99,HTML_MESSAGE,
> RCVD_IN_DSBL,RCVD_IN_NJABL autolearn=no version=2.62
> MIME-Version: 1.0
> Content-Type: multipart/mixed; boundary="----------=_40B5DBC7.31699B1D"
> In my case, I have procmail search the header of messages for
> "X-Spam-Flag: YES" and then drop the message in my "spam" folder. Search
> your spam-like messages... maybe they are being marked, but not handled by
> the 3rd part of the picture, a procmail or client filter which uses this
> header information.
> If none of your messages are being marked, then it is a matter of having
> sendmail process incoming messages. Just how you have sendmail do this
> depends on your SA setup. If you have global SA settings (no single user
> settings) then you can have sendmail "call" SA to scan in one way, while
> if you want each user to have separate configs for SA, then you can use
> spamd and have spamc help with this and call spamc in another way.
> So your job is to find out which case is true. If the first case it true,
> then work on procmail or another filtering to use the header data to
> determin where messages should be places. If the second one is true,
> research the integration aspects of having sendmail "call" spamassassin or
> spamc when spamd is running.
> vox-tech mailing list
vox-tech mailing list