On Tue, Feb 05, 2002 at 12:51:12PM -0700, Michael Moncur wrote:
> Message-Id: <[EMAIL PROTECTED]>
> 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?
Ok, so the test is:
header INVALID_MSGID Message-Id !~
/^<(?:\".+\"|[^\s]+)\@(?:\[.+\]|[^\s]+)>$/ [if-unset: <NO@MSGID>]
So the regex wants one of these:
<"something"@something>
<"something"@[something]>
<something@something>
<something@[something]>
It looks like the problem above is that the Message-Id has 2 spaces at the
front. Is the parser expecting only 1 space, and then the check gets
" <message-id stuff>" ?? All leading whitespace should be stripped according
to the RFC.
As an FYI, the regex can be made a little more efficient via:
header INVALID_MSGID Message-Id !~
/^<(?:\".+\"|\S+)\@(?:\[.+\]|\S+)>$/ [if-unset: <NO@MSGID>]
basically \S instead of [^\s], they're functionally equivalent, but one's
shorter than the other. ;)
--
Randomly Generated Tagline:
"Lotus won't work, it uses a bunch of db files" (Microsoft pre-1998)
"We reorganized Exchange 2000 to scale by using multiple DB files!"
(Microsoft in 2000).
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
