Bug 4399 - SpamAssassin doesn't recognize the Received header when ip starts with "@" in the Received header created by Qmail
Summary: SpamAssassin doesn't recognize the Received header when ip starts with "@" in...
Status: RESOLVED DUPLICATE of bug 4355
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 3.0.3
Hardware: All All
: P3 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-08 05:44 UTC by Arvinn Lokkebakken
Modified: 2005-06-09 17:52 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Example text/plain None Arvinn Lokkebakken [NoCLA]
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 Arvinn Lokkebakken 2005-06-08 05:44:04 UTC 
When Qmail creates a Received header and has ident information from the
smtp-client, but the ident username is blank/unwriteable, the received header
parser in SA fails to recognize it.
Comment 1 Arvinn Lokkebakken 2005-06-08 05:46:31 UTC 
Created attachment 2930 [details]
Example
Comment 2 Arvinn Lokkebakken 2005-06-08 05:48:13 UTC 
This bug leads to bug 3949.
Comment 3 Bob Menschel 2005-06-09 22:27:17 UTC 

*** This bug has been marked as a duplicate of 4355 ***
Comment 4 Daryl C. W. O'Shea 2005-06-09 22:40:42 UTC 
Subject: Re:   New: SpamAssassin doesn't recognize the Received
 header when ip starts with "@" in the Received header created by Qmail

bugzilla-daemon@bugzilla.spamassassin.org wrote:
>            Version: 3.0.4

Are you really seeing this with 3.0.4?  Are you sure it's not 3.0.3 or 
earlier?
Comment 5 Arvinn Lokkebakken 2005-06-10 01:52:28 UTC 
I am really sorry. Poor research. Version changed to 3.0.3.
Comment 6 Daryl C. W. O'Shea 2005-06-10 10:28:53 UTC 
Subject: Re:  SpamAssassin doesn't recognize the Received header
 when ip starts with "@" in the Received header created by Qmail

> ------- Additional Comments From arvinn@sandakerveien.net
> I am really sorry. Poor research. Version changed to 3.0.3.

Yeah, this was fixed in 3.0.4.  I suggest upgrading if this is an issue 
for you.