Dear Allori,
Finally i finished installing openprotect on my servers ad it works:
Internet----router----SMTP with openprotect ----- IMAPserver
Now i have started testing it to see how it works meaning how much spam can control and tag with the {Spam?} tag.
It works on some spam but it is not very high (a lot of spam passes).. where can i download rulesets? how can i improve my bayesian filters?
thank you very much,
If you want those spam mails to be caught as spam, you can train them using SpamAssassins Bayes Filter and sa-learn feature.
If you want to teach it when it gets it wrong, you can have it run the "sa-learn" script to learn about particular messages. Set up 2 addresses here, "spam" and "notspam" in your server.
People can just redirect wrongly-classified messages to one of the addresses. Then once an hour the script below is run by cron to teach the bayes engine about the messages it got wrong. sa-learn --no-rebuild --spam /path/to/spam/folder sa-learn --no-rebuild --ham /path/to/ham/folder
You should also run a nightly cron job that does a "sa-learn --rebuild" as well, to do all the time consuming housekeeping the Bayes engine requires.
The problem of having the wrong headers added when the mail is forwarded from a MUA can be resolved using IMAP accounts.
Simply create two different IMAP accessible mailboxes (Spam and
Notspam) and have users copy the message in there, i.e. all your users should have access to spam and notspam IMAP accounts and they should move false-positives to notspam account in their MUA and false negatives to spam account in their MUA. This needs your users to reconfigure their MUA and also to judiciously forward the wrongly classified mails.
A less painful, but not so elegant approach is do nothing about the forwarded headers, and whitelist your users in the file /etc/MailScanner/rules/spam.whitelist.rules:
From: yourdomain.com1 yes From: yourdomain.com2 yes
You can also blacklist new spam IP's or domains as new spam is received in the blacklist.
Set "Is Definitely Spam = /etc/MailScanner/etc/rules/blacklist.rules". Set addresses to be blacklisted using rules such as From: [EMAIL PROTECTED] yes From: [EMAIL PROTECTED] yes
in the file /etc/MailScanner/etc/rules/blacklist.rules. But, this is painful.
Let me know how well it goes for you.
cheers, Karthikeyan, S. -- S.Karthikeyan | Ph: +91 (0) 44 52166646 Fax: +91 (0) 44 52079957 Opencomputing Technologies | http://opencompt.com Server Side E-Mail Protection.
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Opencomputing-openprotect mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opencomputing-openprotect