Hi,
On Tue, 1 Jul 2003 13:52:40 +0100 "Darren Shrubsole" <[EMAIL PROTECTED]> wrote:
> I'm still getting a BUGGY_CGI firing when using NMS FormMail.
>
> The relevant headers are:
>
> X-Mailer: NMS FormMail 3.08c1
> X-Spam-Status: No, hits=2.8 required=5.0
> tests=BUGGY_CGI
> version=2.54
>
> Should it still be firing? Or is that a bug?
Looks like a bug, provided you haven't mucked with the NMS X-Mailer:
header (which I'm guessing you haven't...)
Long answer: It seems that the NMS people removed the 'v' from their
version number in the X-Mailer header. SA is looking for that 'v' and is
failing the __NMS_CGI_NOT_BUGGY meta test which would stop the BUGGY_CGI
test from firing.
Here's a quick, temporary fix for 2.55:
1) Edit /usr/share/spamassassin/20_meta_tests.cf and change
header __NMS_CGI_NOT_BUGGY X-Mailer =~ /^NMS FormMail\.pl.*v\d/
to
header __NMS_CGI_NOT_BUGGY X-Mailer =~ /^NMS FormMail\.pl.*v?\d/
or
header __NMS_CGI_NOT_BUGGY X-Mailer =~ /^NMS FormMail\.pl.*\d/
2) Attach a test message that's flagged as a false positive to a bug report at
http://bugzilla.spamassassin.org/ . You may need to register first.
Normally you don't want to edit /usr/share/spamassassin/20_meta_tests.cf
because those changes will be lost when you next upgrade SA but if
you report this bug, it'll probably get fixed in 2.61; there's a code
freeze on for 2.60 as GA runs have just started.
hth,
-- Bob
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
