My previous setup involved a combination of procmail, spamassassin call from filtmail which is a perlscript that runs
from my .procmailrc.


I am reimplementing the lot in perl using SpamAssassin and Mail::Audit with qmail.

so far everything works quite nicely.

However, in the past I used my own whitelist which simply worked like this.

If you were on the whitelist you'd never go to spamassassin the mail would simply
be delivered. If you weren't then the mail would be checked for spam.


Secondly, I added users to the whitelist simply by Bccing myself a copy of any replies
I sent to them and my filters saw that the message came from myself but was addressed
to somebody else so it then added that person to the list.


Users could also add themselves to the list by providing a special token in the Subject
of their first message to me.


I could reimplement all of this but I'm wondering if I should just use the existing Spamassassin
APIs for it's whitelist.


Q. With the SA whitelist, will mail that contains addresses that are on the whitelist ever be checked for spam?

I noticed this comment which suggests the score might reflect the message was spam
even if the sender was in the whitelist


"Then, it combines this long-term average score for the sender with the score for the particular message being evaluated, after all other rules have been applied."



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to