Bug 7246 - unparseable header, [ip.address:port]
Summary: unparseable header, [ip.address:port]
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: 3.4.0
Hardware: PC Linux
: P2 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-15 14:57 UTC by Frank Ch. Eigler
Modified: 2018-08-24 01:55 UTC (History)
2 users (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 Frank Ch. Eigler 2015-09-15 14:57:04 UTC 
Recent spam false-negative, bypassing DNSBL due to unparseable line.
Running on older version on Fedora 21 (sorry):

Received: from 85.105.56.217.static.ttnet.com.tr ([85.105.56.217:48526]
        helo=85.105.56.217.static.ttnet.com.tr)
        by yxt.85.105.56.217.static.ttnet.com.tr (envelope-from <Petty5835b@ttnet.com.tr>)
        (ecelerity 3.3.2.44647 r(44647)) with ESMTP
        id 44/38-17613-E55FA926; Tue, 15 Sep 2015 17:47:07 +0300

=>

Sep 15 10:55:16.657 [1833] dbg: received-header: unparseable: from 85.105.56.217.static.ttnet.com.tr [...]
Comment 1 RW 2015-09-16 11:14:11 UTC 
This shouldn't have any effect, except possibly breaking the ALL_TRUSTED rule for ham. What makes you think it caused an FP?
Comment 2 RW 2015-09-16 11:16:00 UTC 
(In reply to RW from comment #1)
> What makes you think it caused an FP?

I meant FN
Comment 3 Kevin A. McGrail 2018-08-24 01:55:28 UTC 
No input from reporter