Bug 6194 - mis-parse of Received header token "([unix socket])"
Summary: mis-parse of Received header token "([unix socket])"
Status: RESOLVED DUPLICATE of bug 5495
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: 3.2.5
Hardware: All All
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-04 10:32 UTC by Stephen Gildea
Modified: 2009-09-07 03:49 UTC (History)
1 user (show)


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 Stephen Gildea 2009-09-04 10:32:08 UTC 
SpamAssassin can't parse the following header, because it wants an IP
address inside the ([...]), and "unix socket" confuses it.  The
confusion causes the received trust chain to be broken.

Received: from hathor.gsd.harvard.edu ([unix socket])
         by hathor (Cyrus v2.3.7) with LMTPA;
         Fri, 15 May 2009 20:32:11 -0400

Yes, the literal words "unix socket" appear in the header where you
would expect an IP address.  Replacing that text with "127.0.0.1"
would work.
Comment 1 Karsten Bräckelmann 2009-09-07 03:49:00 UTC 
Already reported.

*** This bug has been marked as a duplicate of bug 5495 ***