Hi Pete, Here is my setup.
I still have SpamAssassin running, for two reasons. 1. It allows my users to submit False Positives, False Negatives, and Whitelisted address'. By using the built-in email address' that Mdaemon provides for those. I then setup rules in the Mdaemon Content Filter to then forward those to the appropriate SortMonster address'. 2. It can block obvious spam in the SMTP session before it even comes in. I also have Spam Assassin setup to use the Message Sniffer Results. As far as my updating of the Rule Base. I setup a Content Filter Rule to scan incoming mail for the Update Notification. Listed Below. [Rule007] RuleName=Update Message Sniffer Rules Enable=Yes ThisRuleCondition=All ProcessQueue=BOTH Condition01=SUBJECT|contains|AND|vXXXXXXX.snf Update| Action01=run a program|"-1,0,1","cmd.exe /C C:\MDaemon\MessageSniffer\snfupd.cmd" Action02=stop processing| The snfupd.cmd is setup pretty much like the example you include with the plugin I setup two Content Filter rules to forward the False Positive and False Negatives to Sort Monster. Listed Below [Rule001] RuleName=Forward Ham Learn to Message Sniffer Enable=Yes ThisRuleCondition=All ProcessQueue=BOTH Condition01=TO|contains|AND|[EMAIL PROTECTED]| Action01=remove header|"Subject","" Action02=add header|"Subject","False Positive Report - license vXXXXXXX" Action03=remove header|"From","" Action04=add header|"From","[EMAIL PROTECTED]" Action05=copy to|"[EMAIL PROTECTED]" Action06=stop processing| [Rule002] RuleName=Forward Spam Learn to Message Sniffer Enable=Yes ThisRuleCondition=All ProcessQueue=BOTH Condition01=TO|contains|AND|[EMAIL PROTECTED]| Action01=remove header|"From","" Action02=add header|"From","[EMAIL PROTECTED]" Action03=copy to|"[EMAIL PROTECTED]" Action04=stop processing| HTH, Daniel > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Pete McNeil > Sent: Thursday, November 10, 2005 12:36 PM > To: Peer-to-Peer (Support) > Subject: Re[4]: [sniffer] > > On Thursday, November 10, 2005, 11:45:48 AM, Peer-to-Peer wrote: > > PtPS> _M, > > PtPS> <<_M said>> will create a "default" installation that > emits headers and puts > PtPS> a .cf file in place for SA to interpret them. > > PtPS> Not sure if this is relevant to your thought process, > but we feel that SA > PtPS> (SpamAssassin) does more harm than good. Under > moderate loads it bogs-down > PtPS> MDaemon so we always have SA disabled. Sniffer is by > far superior in every > PtPS> category, (accuracy, speed, dependability etc...) so > there's no need to use > PtPS> SpamAssassin. > > PtPS> My point: Keep in mind that some of us use sniffer > independently (not tied > PtPS> to SA). We're using sniffers .cfg plug-in for MD ver 8. > PtPS> I assume you will, and I probably misunderstood your > post, but just wanted > PtPS> to mention this out-loud. > > Thanks for this! I think it's the first time I've heard it said out > loud from anyone involved with MDaemon. As a result I'm operating > under the assumption that folks who install SNF on MDaemon _most > likely_ have SA running and so that would be the simplest default > installation. > > Is that true (do you think) or is it now more likely that SA would be > disabled? > > In any case, the installer is intended for someone who just wants to > push the button and have it work. In that context, what is the best > "default install"? > > All that said, once the installation is complete, a technically savvy > person could reconfigure SNF to and MDaemon to work in any way they > prefer. We're definitely not going to do anything to make that more > difficult. > > Thanks, > > _M > > > > This E-Mail came from the Message Sniffer mailing list. For > information and (un)subscription instructions go to > http://www.sortmonster.com/MessageSniffer/Help/Help.html > This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
