> Strange -- that rule hasn't changed since Dec 17, which is before the > 2.0 release... Did you change anything else while updating SA? Can you > show us a sample message id which is being tagged?
Sure - here is a chunk of the headers from your message quoted above, which was tagged. Every message I've received since upgrading to the latest SA has been tagged. X-Mailer: Evolution/1.0.12mdk Message-Id: <[EMAIL PROTECTED]> Mime-Version: 1.0 X-Spam-Status: No, hits=-107.0 required=5.0 tests=IN_REP_TO,INVALID_MSGID,SUBJ_ENDS_IN_Q_MARK,A_FROM_IN_AUTO_WLIST,USER_IN_ WHITELIST_TO version=2.1 I haven't changed anything here besides upgrading SA... Are you sure this isn't something to do with the RFC2822 changes? Then again, INVALID_MSGID looks like a normal regex test. Is anyone else having this problem? -- michael moncur mgm at starlingtech.com http://www.starlingtech.com/ "There is no safety in numbers, or in anything else." -- James Thurber _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
