Grant, Pete, I *think* that the problem has been solved within our installation. I haven't changed anything, but SPAM messages are not coming through anymore (execept some Russian spam that SNF is not catching, but that's logical --> can I forward these messages to someone é armresearch for analysis?) .
We also had contact with mdaemon and at this moment they are analysing our logfiles, if they find something, I'll post it to this list. We are still at version 9.0.6 Regards, Sven > -----Original Message----- > From: Message Sniffer Community > [mailto:[EMAIL PROTECTED] On Behalf Of Pete McNeil > Sent: zaterdag 30 september 2006 15:39 > To: Message Sniffer Community > Subject: [sniffer] Re: Mdaemon plugin 'sleeping' > > Hello Grant, > > Saturday, September 30, 2006, 8:20:21 AM, you wrote: > > <snip/> > > > We are having the same problem. Sniffer is processing the > messages but it > > appears as if SA is not picking it up. I posted this in the MDaemon > > Discussion list yesterday and had one reply. Upgraded to > 9.07 and tried > > what the poster recommended and it is still not adding to > the spam score. > > Anyone else (Pete?) have ideas. We need to get this working. > > <snip/> > > > Link to MDaemon discussion: > > http://lists.altn.com/[EMAIL PROTECTED]@.eebd191/1 > > From what you've posted, SNF definitely did it's part - the SNF > headers are in the message. After that it's entirely up to SA (or CF). > > This leaves me to wonder what else SA might not be matching that it > should - - That is, once the message gets to SA it's just another > message and the SNF headers are just another bit of text in the > headers so there's no reason I can think of that SA would not match > that text unless SA were broken... > > Since from SA's perspective the SNF headers are just like any other > text, then I wonder what other rules in SA are also not firing when > they should and how often? Perhaps identifying those cases might tell > us something about what's going on. > > Also - why the sudden change? This has worked fine for some time. Can > anybody pinpoint when (at what event precisely) this problem showed > up? > > Those are my thoughts. > > _M > > > -- > Pete McNeil > Chief Scientist, > Arm Research Labs, LLC. > > > ############################################################# > This message is sent to you because you are subscribed to > the mailing list <[email protected]>. > To unsubscribe, E-mail to: <[EMAIL PROTECTED]> > To switch to the DIGEST mode, E-mail to > <[EMAIL PROTECTED]> > To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> > Send administrative queries to <[EMAIL PROTECTED]> > > > ############################################################# This message is sent to you because you are subscribed to the mailing list <[email protected]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
