Bug 3972 - Hotmail forged header error
Summary: Hotmail forged header error
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: PC All
: P5 minor
Target Milestone: Future
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-17 01:47 UTC by John Devine
Modified: 2019-06-19 16:01 UTC (History)
2 users (show)



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description John Devine 2004-11-17 01:47:42 UTC
I run MDaemon mail server with SA3.0.1 and one of my domains is 
truehotmail.com, all email leaving my server is given this SA report

 Mon 2004-11-15 11:29:21: Start SpamAssassin results Mon 2004-11-15
>11:29:21: 2.2 points, 5.0 required; Mon 2004-11-15 11:29:21: *  0.1 
>FORGED_RCVD_HELO Received: contains a forged HELO Mon 2004-11-15
>11:29:21: *  2.1 FORGED_HOTMAIL_RCVD Forged hotmail.com 'Received:' 
>header found Mon 2004-11-15 11:29:21: End SpamAssassin results Mon
>2004-11-15 11:29:21: ----------

So all of my email already has value of 2.2 beacuse my domain contains 
the  'hotmail' string, can this be solved please

Regards

John Devine
Comment 1 Jesse Houwing 2004-11-22 12:09:13 UTC
The domain in question helo's as: truehotmail.com 

Nothing wrong with that, except that it contains hotmail.com. Maybe the evals
coulb be changed from \S*hotmail.com to \bhotmail.com, but I guess that would
make the rules much less effective.
Comment 2 Bob Menschel 2005-04-06 23:31:13 UTC
John -- Can you attach a full email which demonstrates this problem? It should
be a minor fix, which can be quickly implemented and validated, but having an
actual email to run the test against would be very helpful for this. 

Setting milestone to future for now -- can be moved to a fixed 3.1.x milestone
once we have that email. 
Comment 3 Dave Jones 2018-02-13 19:16:08 UTC
I think this has been resolved in the past 13 years.  If we can't get a sample email that triggers FORGED_HOTMAIL_RCVD soon, this issue will be closed.
Comment 4 Henrik Krohns 2019-06-19 16:01:57 UTC
Guys just close it if it looks legacy, don't leave it lingering just in case someone replies 15 years later. And they can reopen the bug even if that's the case. JUST CLOSE IT. I'm sure I could figure out better things to do on holiday than closing bugs. :-D