As a user of your MD plugin since it's Beta release, it has worked perfectly. SA can have problems with completely unrelated rules / tests should there be a syntax error in any one of SA's CF files.

I'd suggest using ONLY the default SA installation rules to test, and/or running all CF rules via the --lint option to verify all rules are good. (See http://wiki.apache.org/spamassassin/WritingRules)

 

-----Original Message-----
From: Message Sniffer Community [mailto:[EMAIL PROTECTED] On Behalf Of Pete McNeil
Sent: Saturday, September 30, 2006 9:39 AM
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.

Reply via email to