Here is the rule from 3.0 header __SANE_MSGID MESSAGEID =~ /^<[^<>\\ [EMAIL PROTECTED]<>\\ \t\n\r\x0b\x80-\xff]+>\s*$/m header __HAS_MSGID MESSAGEID =~ /\S/ header __MSGID_COMMENT MESSAGEID =~ /\(.*\)/m meta INVALID_MSGID __HAS_MSGID && !(__SANE_MSGID || __MSGID_COMMENT) describe INVALID_MSGID Message-Id is not valid, according to RFC 2822
It's a little hard to understand, basically you must have /\S/ and neither of the other two? I assume this means your msgid had some type of character not fitting the set above. I placed your MSGID in a sample message and ran it through my SA install. It did not cause that rule to hit. This leads me to believe something happened that is not reproducable with just the msgid you pasted into that message. Please send a copy of the message which is causing your issue and if something is wrong with the rule, someone will take action to get this corrected in a future release. Frederic Tarasevicius Internet Information Services, Inc. http://www.i-is.com/ 810-794-4400 mailto:[EMAIL PROTECTED] Dan Barker wrote: > SpamAssassin (default settings except a few score's) 3.0.0 sez: > > 1.1 INVALID_MSGID Message-Id is not valid, according to RFC > 2822 > > I can't for the life of me see anything wrong with: > > Message-ID: > <[EMAIL PROTECTED]>
