Bug 2966 - Forged mail pretended to be from MS Outlook
Summary: Forged mail pretended to be from MS Outlook
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: unspecified
Hardware: Other other
: P5 critical
Target Milestone: 2.70
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-26 04:21 UTC by Kristin Floyd
Modified: 2004-01-28 05:06 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kristin Floyd 2004-01-26 04:21:26 UTC 
When sending e-mails from my Outlook account to an e-mail account that uses 
spam assassin,  I was told my e-mail was ending up in the spam box from time 
to time.    I tested the e-mail with my version of spam assassin and found the 
following header on my e-mail.  I contacted Microsoft and they checked my 
Outlook program and then said I needed to report the problem to you:

X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcPfd4fqIO+pr/tiSl+ntPMb6DM/eA==
X-Spam-Status: Yes, hits=5.4 required=5.0 
        tests=FORGED_MUA_OUTLOOK,HTML_70_80,HTML_MESSAGE, 
              MISSING_OUTLOOK_NAME,MSG_ID_ADDED_BY_MTA_3 
        version=2.54
X-Spam-Checker-Version: SpamAssassin 2.54 (1.174.2.17-2003-05-11-exp) 
X-Spam-Report:   ---- Start SpamAssassin results 
  5.40 points, 5 required;
  *  0.5 -- BODY: Message is 70% to 80% HTML
  *  0.1 -- BODY: HTML included in message
  *  0.7 -- 'Message-Id' was added by a relay (3)
  *  3.5 -- Forged mail pretending to be from MS Outlook
  *  0.6 -- Message looks like Outlook, but isn't
  ---- End of SpamAssassin results
X-Spam-Flag: YES
Comment 1 Theo Van Dinter 2004-01-28 14:06:44 UTC 
well, a few things.

1) SpamAssassin 2.54 is ancient at this point.  It should be upgraded to 2.63 at a minimum.
2) we can't really do anything without the full message (headers + body) to see what is going on.

from your description, it looks like the Outlook 2003 thing, which should be fixed in the 2.6x 
series of SpamAssassin.  If the problem is still occuring with 2.63 or later, please attach (via the 
webpage) a full text copy of a message showing the issue, and we can reopen the ticket and look 
into the issue.