You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2007/08/16 18:53:49 UTC
[Bug 5600] New: Possible wrong detection of FORGED_MUA_OUTLOOK
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5600
Summary: Possible wrong detection of FORGED_MUA_OUTLOOK
Product: Spamassassin
Version: 3.1.7
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Rules
AssignedTo: dev@spamassassin.apache.org
ReportedBy: r.epping@meteo.nl
As far a I know the attached (stripped) message was sent with a "normal" outlook
client, but still is detected as FORGED_MUA_OUTLOOK.
Why is it tagged as FORGED_MUA_OUTLOOK?
For details on original mail ask.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5600] Possible wrong detection of FORGED_MUA_OUTLOOK
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5600
------- Additional Comments From r.epping@meteo.nl 2007-08-16 09:58 -------
(In reply to comment #0)
> As far a I know the attached (stripped) message was sent with a "normal" outlook
> client, but still is detected as FORGED_MUA_OUTLOOK.
>
> Why is it tagged as FORGED_MUA_OUTLOOK?
>
> For details on original mail ask.
Forgot to mention that this is Debian version 3.1.7~bpo1 on sarge with sa-update
to 3.001007
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5600] Possible wrong detection of FORGED_MUA_OUTLOOK
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5600
sidney@sidney.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From sidney@sidney.com 2007-08-16 15:21 -------
This is an example of bug 5571, which has to do with a new Message-ID format
introduced with Vista, and maybe also Windows 2003 Server SP2.
I checked the updated rule into the 3.1 branch sa-update channel when I closed
bug 5571, but I guess you don't get that in the 3.001007 channel.
If you upgrade SpamAssassin to 3.1.9, which is the current release in the 3.1
branch, or to the latest 3.2 release, then you will get the fix.
Can some dev let me know if there is any procedure in place for backporting rule
updates to sa-update channels for old versions like 3.1.7 that are still being
distributed with some systems? Is that something that we want to get into?
*** This bug has been marked as a duplicate of 5571 ***
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5600] Possible wrong detection of FORGED_MUA_OUTLOOK
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5600
------- Additional Comments From r.epping@meteo.nl 2007-08-16 09:56 -------
Created an attachment (id=4089)
--> (http://issues.apache.org/SpamAssassin/attachment.cgi?id=4089&action=view)
Striped mail which gets tagged.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5600] Possible wrong detection of FORGED_MUA_OUTLOOK
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5600
------- Additional Comments From r.epping@meteo.nl 2007-08-17 03:53 -------
(In reply to comment #3)
> This is an example of bug 5571, which has to do with a new Message-ID format
> introduced with Vista, and maybe also Windows 2003 Server SP2.
Verified to be from a Vista system.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.