You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@spamassassin.apache.org on 2020/04/06 02:44:36 UTC

[Bug 7805] New: Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

            Bug ID: 7805
           Summary: Mail::SpamAssassin::Plugin::SPF passes the wrong
                    <Received> headers to MAIL::SPF when helo is initially
                    invoked at external relay.
           Product: Spamassassin
           Version: 3.4.4
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Plugins
          Assignee: dev@spamassassin.apache.org
          Reporter: support@handynetworks.com
  Target Milestone: Undefined

Created attachment 5691
  --> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5691&action=edit
Example email with local server, recipient and bounce-address redactions. 
Still reproduces issue with SPF plugin with and without redactions on 3.4.4.

With certain websites such as wetransfer.com, the Received headers show that
the email is first sent to a third party mail sending service (sendgrid, for
example), before eventually being sent to the recipient mail server.

Headers will therefore look something like this (redacted example excerpt):

===
Return-Path:
<bo...@em9713.email.wetransfer.com>
Delivered-To: [redacted]
Received: from [local server, redacted]
        by [same local server, redacted] with LMTP
        id EIsRK0oghl7LDjkAsPOUtg
        (envelope-from
<bo...@em9713.email.wetransfer.com>)
        for <redacted>; Thu, 02 Apr 2020 17:26:34 +0000
Return-path: <redacted>
Envelope-to: redacted
Delivery-date: Thu, 02 Apr 2020 17:26:34 +0000
Received: from o2.email.wetransfer.com ([192.254.118.54]:28541)
        by redacted with esmtps  (TLS1.2) tls
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
        (Exim 4.93)
        (envelope-from
<bo...@em9713.email.wetransfer.com>)
        id 1jK3bs-00FhdM-HC
        for redacted; Thu, 02 Apr 2020 17:26:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 
        d=email.wetransfer.com; 
       
h=from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; 
        s=s1; bh=1p2PYxSXvi6qePAWGFMzuI6trBOd/BJScAE9vMJg5Fk=; b=q/za1KA
        pfOKpTIJV+zmTrGhUiKQXFolNCVst2/dU/4PjhyTZ2HJ47+f8SJNZo0q9usAir5K
        poTPN7NV+DkvIQ5q0BDAe5K7j62oVbTC30xPf4lhktEojZcXa08V5BFfg/XYgLKD
        9/RxI0EPQpGfizjVEggsimvmDlAIxgVuZtTA=
Received: by filter1969p1mdw1.sendgrid.net with SMTP id
filter1969p1mdw1-26204-5E86201A-1A
        2020-04-02 17:25:46.597663144 +0000 UTC m=+66385.574505142
Received: from ba695f3d37e6 (unknown)
        by ismtpd0004p1lon1.sendgrid.net (SG) with ESMTP id
NOaf64uIQHK7kDPqITWP7g
        for <redacted>; Thu, 02 Apr 2020 17:25:46.417 +0000 (UTC)
Received: from [10.30.65.95] (helo=wetransfer.com)
        by ba695f3d37e6 with esmtp (Exim 4.86_2)
        (envelope-from <no...@wetransfer.com>)
        id 1jK3b8-0001QE-8R
        for redacted; Thu, 02 Apr 2020 17:25:46 +0000
Date: Thu, 02 Apr 2020 17:25:46 +0000 (UTC)
From: WeTransfer <no...@wetransfer.com>
Reply-To: redacted
To: redacted
Message-ID: <wt...@wetransfer.com>
===

The helo is input to sendgrid's mailservers by the webserver for
wetransfer.com, and sendgrid does not provide a helo of its own when sending
mail inbound to our local server.

This seems a little unusual, but not so much that it should through SPF
checking for a loop and get it to try and check the private IP.

Here are the results of testing the message in question, with or without
redactions:

===
Content analysis details:   (16.3 points, 10.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was
                            blocked.  See
                           
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                             for more information.
                            [URIs: wetransfer.com]
-0.5 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0000]
 0.1 TO_MALFORMED           To: has a malformed address
 1.0 SURBL_BLOCKED          ADMINISTRATOR NOTICE: The query to SURBL was
                            blocked.  See
                           
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                             for more information.
                            [URIs: wetransfer.com]
 8.0 SPF_FAIL               SPF: sender does not match SPF record (fail)
[SPF failed: Please see
http://www.openspf.org/Why?s=mfrom;id=noreply%40wetransfer.com;ip=10.30.65.95;r=redacted]
 0.0 SPF_HELO_FAIL          SPF: HELO does not match SPF record (fail)
[SPF failed: Please see
http://www.openspf.org/Why?s=helo;id=wetransfer.com;ip=10.30.65.95;r=redacted]
 0.1 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily
                            valid
 2.0 RDNS_NONE              Delivered to internal network by a host with no
rDNS
 2.5 UNPARSEABLE_RELAY      Informational: message has unparseable relay
                            lines
 1.0 DMARC_QUAR             No description available.
 2.0 DKIM_INVALID           DKIM or DK signature exists, but is not valid
 0.2 TXREP                  TXREP: Score normalizing based on sender's
reputation
===

You'll notice that SPF fails, and indicates it is checking the RFC1918 IP that
wetransfer.com first sends the email from, before it reaches an unknown relay,
and then a sendgrid endpoint.

Here is the debug output of this test:

===
Apr  5 19:35:10.154 [10970] dbg: rules: running head_eval tests; score so
far=-0.499
Apr  5 19:35:10.156 [10970] dbg: rules: run_eval_tests - compiling eval code:
9, priority 0
Apr  5 19:35:10.168 [10970] dbg: spf: checking to see if the message has a
Received-SPF header that we can use
Apr  5 19:35:10.204 [10970] dbg: spf: using Mail::SPF for SPF checks
Apr  5 19:35:10.204 [10970] dbg: spf: checking HELO (helo=wetransfer.com,
ip=10.30.65.95)
Apr  5 19:35:10.205 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.205 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.206 [10970] dbg: dns: providing a callback for id:
21426/IN/TXT/wetransfer.com
Apr  5 19:35:10.207 [10970] dbg: dns: bgread: received 603 bytes from dnsip
Apr  5 19:35:10.208 [10970] dbg: dns: dns reply 21426 is OK, 6 answer records
Apr  5 19:35:10.250 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.251 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.251 [10970] dbg: dns: providing a callback for id:
38194/IN/TXT/servers.mcsv.net
Apr  5 19:35:10.252 [10970] dbg: dns: bgread: received 128 bytes from dnsip
Apr  5 19:35:10.252 [10970] dbg: dns: dns reply 38194 is OK, 1 answer records
Apr  5 19:35:10.257 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.257 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.258 [10970] dbg: dns: providing a callback for id:
10004/IN/TXT/_spf.google.com
Apr  5 19:35:10.258 [10970] dbg: dns: bgread: received 160 bytes from dnsip
Apr  5 19:35:10.259 [10970] dbg: dns: dns reply 10004 is OK, 1 answer records
Apr  5 19:35:10.262 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.262 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.262 [10970] dbg: dns: providing a callback for id:
40838/IN/TXT/_netblocks.google.com
Apr  5 19:35:10.263 [10970] dbg: dns: bgread: received 286 bytes from dnsip
Apr  5 19:35:10.263 [10970] dbg: dns: dns reply 40838 is OK, 1 answer records
Apr  5 19:35:10.269 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.269 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.269 [10970] dbg: dns: providing a callback for id:
23072/IN/TXT/_netblocks2.google.com
Apr  5 19:35:10.270 [10970] dbg: dns: bgread: received 218 bytes from dnsip
Apr  5 19:35:10.270 [10970] dbg: dns: dns reply 23072 is OK, 1 answer records
Apr  5 19:35:10.276 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.276 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.277 [10970] dbg: dns: providing a callback for id:
27898/IN/TXT/_netblocks3.google.com
Apr  5 19:35:10.277 [10970] dbg: dns: bgread: received 275 bytes from dnsip
Apr  5 19:35:10.278 [10970] dbg: dns: dns reply 27898 is OK, 1 answer records
Apr  5 19:35:10.283 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.284 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.284 [10970] dbg: dns: providing a callback for id:
61590/IN/TXT/sendgrid.net
Apr  5 19:35:10.287 [10970] dbg: dns: bgread: received 348 bytes from dnsip
Apr  5 19:35:10.288 [10970] dbg: dns: dns reply 61590 is OK, 3 answer records
Apr  5 19:35:10.292 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.292 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.292 [10970] dbg: dns: providing a callback for id:
8713/IN/TXT/mail.zendesk.com
Apr  5 19:35:10.293 [10970] dbg: dns: bgread: received 190 bytes from dnsip
Apr  5 19:35:10.293 [10970] dbg: dns: dns reply 8713 is OK, 1 answer records
Apr  5 19:35:10.296 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.296 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.296 [10970] dbg: dns: providing a callback for id:
4845/IN/TXT/mailsenders.netsuite.com
Apr  5 19:35:10.342 [10970] dbg: dns: bgread: received 746 bytes from dnsip
Apr  5 19:35:10.343 [10970] dbg: dns: dns reply 4845 is OK, 1 answer records
Apr  5 19:35:10.356 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.356 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.356 [10970] dbg: dns: providing a callback for id:
20832/IN/TXT/_spf.salesforce.com
Apr  5 19:35:10.357 [10970] dbg: dns: bgread: received 108 bytes from dnsip
Apr  5 19:35:10.358 [10970] dbg: dns: dns reply 20832 is OK, 1 answer records
Apr  5 19:35:10.360 [10970] dbg: dns: bgsend, DNS servers: [dnsip]:53,
[dnsip]:53, [dnsip]:53
Apr  5 19:35:10.360 [10970] dbg: dns: attempt 1/3, trying connect/sendto to
[dnsip]:53
Apr  5 19:35:10.360 [10970] dbg: dns: providing a callback for id:
21567/IN/A/10.30.65.95._spf.mta.salesforce.com
Apr  5 19:35:10.361 [10970] dbg: dns: bgread: received 117 bytes from dnsip
Apr  5 19:35:10.362 [10970] dbg: dns: dns reply to
21567/IN/A/10.30.65.95._spf.mta.salesforce.com: NXDOMAIN
Apr  5 19:35:10.364 [10970] dbg: spf: query for /10.30.65.95/wetransfer.com:
result: fail, comment: Please see
http://www.openspf.org/Why?s=helo;id=wetransfer.com;ip=10.30.65.95;r=spamd-server,
text: Mechanism '-all' matched
===

Ideally, it would be able to tell that 192.254.118.54 is the sending IP, or at
least determine that 10.30.65.95 is an RFC1918 IP, and thus very likely part of
the sending mail servers' relay chain (and not in SPF).

I'm sure part of the problem is being caused by their own mail configuration,
and we'll be working around by whitelisting their domain (not something I like
to do), but it's possible there's other sendgrid-leveraging sites with a
similar configuration that makes your SPF plugin collapse like this.

Let me know if you require further info.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

--- Comment #13 from hnsupport <su...@handynetworks.com> ---
(In reply to RW from comment #12)
> You appear to have 192.254.118.54 in your trusted_networks, and since you
> haven't defined internal_networks explicitly, it gets copied from
> trusted_networks. Presumably you haven't added the private address ranges to
> trusted_networks which makes 10.30.65.95 look like the last-external IP
> address.
> 
> Others see the spf pass because they don't have 192.254.118.54 in
> internal_networks, and so, correctly, see that IP address as last-external.

(In reply to Kevin A. McGrail from comment #11)
> On my 2 systems, init.pre is where the SPF plugin is loaded
> 
> On my key test rig SPF passes.
> 
> What is your glue for calling spamassassin
> 
> Here's the output that matches the word SPF for your review:
> 
> Apr  6 19:54:28.295 [8453] dbg: check: tagrun - tag DKIMDOMAIN is still
> blocking action 1
> Apr  6 19:54:28.306 [8453] dbg: plugin:
> Mail::SpamAssassin::Plugin::MIMEHeader=HASH(0x94faff0) implements
> 'finish_tests', priority 0
> Apr  6 19:54:28.306 [8453] dbg: plugin:
> Mail::SpamAssassin::Plugin::Check=HASH(0x9588a90) implements 'finish_tests',
> priority 0
> Apr  6 19:54:28.444 [8453] dbg: netset: cache trusted_networks
> hits/attempts: 25/26, 96.2 %
> Press any key to continue...
> Apr  6 19:55:16.614 [8828] dbg: plugin: loading
> Mail::SpamAssassin::Plugin::SPF from @INC
> Apr  6 19:55:17.959 [8828] dbg: config: fixed relative path:
> /var/lib/spamassassin/3.004004/updates_spamassassin_org/25_spf.cf
> Apr  6 19:55:17.959 [8828] dbg: config: using
> "/var/lib/spamassassin/3.004004/updates_spamassassin_org/25_spf.cf" for
> included file
> Apr  6 19:55:17.960 [8828] dbg: config: read file
> /var/lib/spamassassin/3.004004/updates_spamassassin_org/25_spf.cf
> Apr  6 19:55:18.243 [8828] dbg: config: fixed relative path:
> /var/lib/spamassassin/3.004004/updates_spamassassin_org/60_whitelist_spf.cf
> Apr  6 19:55:18.243 [8828] dbg: config: using
> "/var/lib/spamassassin/3.004004/updates_spamassassin_org/60_whitelist_spf.
> cf" for included file
> Apr  6 19:55:18.243 [8828] dbg: config: read file
> /var/lib/spamassassin/3.004004/updates_spamassassin_org/60_whitelist_spf.cf
> Apr  6 19:55:20.552 [8828] dbg: config: warning: no description set for
> FROM_MISSP_SPF_FAIL
> Apr  6 19:55:20.597 [8828] dbg: config: warning: no description set for
> FORGED_SPF_HELO
> Apr  6 19:55:22.549 [8828] dbg: askdns: depend on tags SENDERDOMAIN, rules:
> JMQ_SPF_ALL, __PDS_SPF_ONLYALL, PDS_SPF_NONE, PDS_SPF_ALL, JMQ_SPF_NEUTRAL,
> PDS_SPF_ONLYALL 
> Apr  6 19:55:22.549 [8828] dbg: askdns: query template _SENDERDOMAIN_, type
> TXT, rules: JMQ_SPF_ALL, __PDS_SPF_ONLYALL, PDS_SPF_NONE, PDS_SPF_ALL,
> JMQ_SPF_NEUTRAL, PDS_SPF_ONLYALL
> Apr  6 19:55:23.825 [8828] dbg: spf: checking to see if the message has a
> Received-SPF header that we can use
> Apr  6 19:55:23.908 [8828] dbg: spf: using Mail::SPF for SPF checks
> Apr  6 19:55:23.909 [8828] dbg: spf: checking HELO
> (helo=o2.email.wetransfer.com, ip=192.254.118.54)
> Apr  6 19:55:23.913 [8828] dbg: dns: providing a callback for id:
> 32395/IN/SPF/o2.email.wetransfer.com
> Apr  6 19:55:23.923 [8828] dbg: spf: query for
> /192.254.118.54/o2.email.wetransfer.com: result: none, comment: , text: No
> applicable sender policy available
> Apr  6 19:55:24.093 [8828] dbg: spf: already checked for Received-SPF
> headers, proceeding with DNS based checks
> Apr  6 19:55:24.093 [8828] dbg: spf: found Envelope-From in first external
> Received header
> Apr  6 19:55:24.093 [8828] dbg: spf: checking EnvelopeFrom
> (helo=o2.email.wetransfer.com, ip=192.254.118.54,
> envfrom=bounces+922094-0e6c-juridico1=fernangonzalezabogados.es@em9713.email.
> wetransfer.com)
> Apr  6 19:55:24.097 [8828] dbg: dns: providing a callback for id:
> 9080/IN/SPF/em9713.email.wetransfer.com
> Apr  6 19:55:24.182 [8828] dbg: spf: query for
> bounces+922094-0e6c-juridico1=fernangonzalezabogados.es@em9713.email.
> wetransfer.com/192.254.118.54/o2.email.wetransfer.com: result: pass,
> comment: , text: Mechanism 'ip4:192.254.118.54' matched
> Apr  6 19:55:24.189 [8828] dbg: rules: ran eval rule SPF_PASS ======> got
> hit (1)
> Apr  6 19:55:24.227 [8828] dbg: spf: def_whitelist_from_spf:
> bounces+922094-0e6c-juridico1=fernangonzalezabogados.es@em9713.email.
> wetransfer.com is not in DEF_WHITELIST_FROM_SPF
> Apr  6 19:55:24.239 [8828] dbg: spf: whitelist_from_spf:
> bounces+922094-0e6c-juridico1=fernangonzalezabogados.es@em9713.email.
> wetransfer.com is not in user's WHITELIST_FROM_SPF
> Apr  6 19:55:27.112 [8828] dbg: auto-whitelist: sql-based get_addr_entry:
> found 1 entries for noreply@wetransfer.com|spf
> Apr  6 19:55:27.113 [8828] dbg: auto-whitelist: sql-based
> noreply@wetransfer.com|spf scores -3.56, msgcount 4
> Apr  6 19:55:27.118 [8828] dbg: auto-whitelist: sql-based add_score/insert
> root|noreply@wetransfer.com|none|1|-0.89|spf: SQL error: Duplicate entry
> 'root-noreply@wetransfer.com-spf-none' for key 'PRIMARY'
> Apr  6 19:55:27.122 [8828] dbg: auto-whitelist: sql-based add_score/update
> new msgcount: 5, new totscore: -4.45 for
> 5|-0.89|root|noreply@wetransfer.com|spf|none
> Apr  6 19:55:27.126 [8828] dbg: auto-whitelist: sql-based get_addr_entry:
> found 1 entries for wetransfer.com|spf
> Apr  6 19:55:27.126 [8828] dbg: auto-whitelist: sql-based wetransfer.com|spf
> scores -3.56, msgcount 4
> Apr  6 19:55:27.131 [8828] dbg: auto-whitelist: sql-based add_score/insert
> root|wetransfer.com|none|1|-0.89|spf: SQL error: Duplicate entry
> 'root-wetransfer.com-spf-none' for key 'PRIMARY'
> Apr  6 19:55:27.135 [8828] dbg: auto-whitelist: sql-based add_score/update
> new msgcount: 5, new totscore: -4.45 for 5|-0.89|root|wetransfer.com|spf|none
> Apr  6 19:55:27.176 [8828] dbg: check:
> tests=DKIM_INVALID,DKIM_SIGNED,HTML_MESSAGE,KAM_DMARC_STATUS,
> KAM_REALLYHUGEIMGSRC,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,
> RCVD_IN_SENDERSCORE_90_100,SPF_PASS,UNPARSEABLE_RELAY,UNWANTED_LANGUAGE_BODY
> Apr  6 19:55:27.182 [8828] dbg: timing: total 10639 ms - init: 5581 (52.5%),
> parse: 21 (0.2%), extract_message_metadata: 420 (3.9%), get_uri_detail_list:
> 31 (0.3%), tests_pri_-1000: 532 (5.0%), compile_gen: 725 (6.8%),
> compile_eval: 137 (1.3%), tests_pri_-950: 19 (0.2%), tests_pri_-900: 19
> (0.2%), tests_pri_-100: 45 (0.4%), tests_pri_-90: 17 (0.2%), tests_pri_0:
> 2820 (26.5%), check_spf: 189 (1.8%), poll_dns_idle: 9 (0.1%),
> dkim_load_modules: 77 (0.7%), check_dkim_signature: 29 (0.3%),
> check_dkim_adsp: 12 (0.1%), wait_for_pending_rules: 0.58 (0.0%),
> tests_pri_20: 323 (3.0%), check_razor2: 304 (2.9%), tests_pri_30: 18 (0.2%),
> check_pyzor: 1.04 (0.0%), tests_pri_500: 511 (4.8%), tests_pri_1000: 130
> (1.2%), total_txrep: 110 (1.0%), check_txrep_email_ip: 7 (0.1%),
> update_txrep_email_ip: 7 (0.1%), check_txrep_domain: 5 (0.0%),
> update_txrep_domain: 7 (0.1%), check_txrep_helo: 4.8 (0.0%),
> update_txrep_helo: 6 (0.1%), check_txrep_ip: 4.5 (0.0%), update_txrep_ip: 6
> (0.1%)
>         RCVD_IN_MSPIKE_H2,RCVD_IN_SENDERSCORE_90_100,SPF_PASS,
> Filter Tests:
> DKIM_INVALID,DKIM_SIGNED,HTML_MESSAGE,KAM_DMARC_STATUS,KAM_REALLYHUGEIMGSRC,
> RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,RCVD_IN_SENDERSCORE_90_100,SPF_PASS,
> UNPARSEABLE_RELAY,UNWANTED_LANGUAGE_BODY
> Content analysis details:   (1.9 points, -100.0 required)
> -0.0 SPF_PASS               SPF: sender matches SPF record
>  0.0 KAM_DMARC_STATUS       Test Rule for DKIM or SPF Failure with Strict
> Filter Tests:
> DKIM_INVALID,DKIM_SIGNED,HTML_MESSAGE,KAM_DMARC_STATUS,KAM_REALLYHUGEIMGSRC,
> RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,RCVD_IN_SENDERSCORE_90_100,SPF_PASS,
> UNPARSEABLE_RELAY,UNWANTED_LANGUAGE_BODY
> Content analysis details:   (1.9 points, -100.0 required)
> -0.0 SPF_PASS               SPF: sender matches SPF record

I'm just inputting the email to spamassassin -D to get the output I provided.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

--- Comment #8 from hnsupport <su...@handynetworks.com> ---
Created attachment 5694
  --> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5694&action=edit
original unredacted testcase debugging output

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

hnsupport <su...@handynetworks.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #15 from hnsupport <su...@handynetworks.com> ---
(In reply to hnsupport from comment #14)
> (In reply to RW from comment #12)
> > You appear to have 192.254.118.54 in your trusted_networks, and since you
> > haven't defined internal_networks explicitly, it gets copied from
> > trusted_networks. Presumably you haven't added the private address ranges to
> > trusted_networks which makes 10.30.65.95 look like the last-external IP
> > address.
> > 
> > Others see the spf pass because they don't have 192.254.118.54 in
> > internal_networks, and so, correctly, see that IP address as last-external.
> 
> Interesting: thanks RW, sounds promising!  And like an environmental issue,
> of course...
> 
> I'll re-read the documentation for those directives more carefully, and
> define internal_networks / redefine trusted_networks as appropriate.
> 
> Thanks again.

Just to follow up here: that was exactly the problem.  I've done a RADB lookup
to find all of our subnets, put them in internal_networks for an initial test,
and the proper relay is once again evauluated:

====
Content analysis details:   (8.6 points, 10.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was
                            blocked.  See
                           
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                             for more information.
                            [URIs: zendesk.com]
 3.0 BAYES_50               BODY: Bayes spam probability is 40 to 60%
                            [score: 0.4277]
-0.1 SPF_PASS               SPF: sender matches SPF record
 0.0 SPF_HELO_NONE          SPF: HELO does not publish an SPF Record
 0.1 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily
                            valid
 2.0 DKIM_INVALID           DKIM or DK signature exists, but is not valid
 3.7 TXREP                  TXREP: Score normalizing based on sender's
reputation
====

Thanks again, closing this out.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

--- Comment #7 from hnsupport <su...@handynetworks.com> ---
Created attachment 5693
  --> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5693&action=edit
original unredacted testcase

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

Giovanni Bechis <gi...@paclan.it> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |giovanni@paclan.it

--- Comment #1 from Giovanni Bechis <gi...@paclan.it> ---
I cannot reproduce it, the output of a spamassassin check for the attached
message follows:
------------------------------------------------------------------------------
Content analysis details:   (1.4 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.1 TO_MALFORMED           To: has a malformed address
 0.0 SPF_HELO_NONE          SPF: HELO does not publish an SPF Record
-0.0 SPF_PASS               SPF: sender matches SPF record
 0.0 HTML_MESSAGE           BODY: HTML included in message
 1.1 KAM_REALLYHUGEIMGSRC   RAW: Spam with image tags with ridiculously
                             huge http urls
 0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily
                            valid
 0.1 DKIM_INVALID           DKIM or DK signature exists, but is not valid
 0.0 UNPARSEABLE_RELAY      Informational: message has unparseable relay
                            lines
 0.0 KAM_DMARC_STATUS       Test Rule for DKIM or SPF Failure with Strict
                            Alignment
------------------------------------------------------------------------------
Which Mail::SPF version are you using ?
Other than that I think a there could be a dns-related problem in your setup.
Please follow
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/DnsBlocklists#dnsbl-block
to fix at least SURBL_BLOCKED warning.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

Henrik Krohns <ap...@hege.li> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |apache@hege.li

--- Comment #2 from Henrik Krohns <ap...@hege.li> ---
SPF simply uses first external header, so I suggest you debug that:

spamassassin -t -D -L < testmsg 2>&1 | grep received

Check that external etc look ok and no received-header: unparseable seen.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

RW <rw...@googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rwmaillists@googlemail.com

--- Comment #12 from RW <rw...@googlemail.com> ---
You appear to have 192.254.118.54 in your trusted_networks, and since you
haven't defined internal_networks explicitly, it gets copied from
trusted_networks. Presumably you haven't added the private address ranges to 
trusted_networks which makes 10.30.65.95 look like the last-external IP
address.

Others see the spf pass because they don't have 192.254.118.54 in
internal_networks, and so, correctly, see that IP address as last-external.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

--- Comment #9 from hnsupport <su...@handynetworks.com> ---
(In reply to hnsupport from comment #6)
> (In reply to Giovanni Bechis from comment #3)
> > Created attachment 5692 [details]
> > fix unparseable relay
> > 
> > I cannot reproduce the spf error, anyway the attached diff fixes the
> > unparseable relay for me.
> 
> I'll apply this patch and test, thanks.

Spam detection software, running on the system
"spamd-node0.wehostwebsites.com",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
monitoring@handynetworks.com for details.

Content preview:  sgarrido@bycoconstruccion.com te ha enviado archivos 1
elemento,
   40 MB en total ・ Se eliminará el 9 de Abril de 2020 Enlace de descarga:
  
https://wetransfer.com/downloads/058fc95d58f0d9a427265377a121cc5820200402172453/c6947aad5fc592c6b7b95bcfba3d17f220200402172455/943a2f


Content analysis details:   (6.3 points, 10.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was
                            blocked.  See
                           
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                             for more information.
                            [URIs: zendesk.com]
-0.5 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0000]
 6.0 SPF_FAIL               SPF: sender does not match SPF record (fail)
[SPF failed: Please see
http://www.openspf.org/Why?s=mfrom;id=noreply%40wetransfer.com;ip=10.30.65.95;r=spamd-node0.wehostwebsites.com]
 0.0 SPF_HELO_FAIL          SPF: HELO does not match SPF record (fail)
[SPF failed: Please see
http://www.openspf.org/Why?s=helo;id=wetransfer.com;ip=10.30.65.95;r=spamd-node0.wehostwebsites.com]
 0.1 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily
                            valid
 0.5 RDNS_NONE              Delivered to internal network by a host with no
rDNS
 1.0 DMARC_QUAR             No description available.
-6.0 TRUSTED_BUT_SPAMMY_DOMAINS No description available.
 2.0 DKIM_INVALID           DKIM or DK signature exists, but is not valid
 3.3 TXREP                  TXREP: Score normalizing based on sender's
reputation

Confirmed resolution of unparseable relay on my end.  SPF issue still persists.

Since none of you can reproduce it in your respective environments with the
redacted test case, I've included both an unredacted test case (the message,
post-delivery) and my own debug output with that test case for further
reference.

I provided my version of Mail::SPF and Mail::SpamAssassin, and confirmed both
are the latest stable versions, already, so it's nothing immediately obvious to
me.

If anyone else can't reproduce the issue, I'd appreciate if you could include
your full debug output for my reference.  If it's an environmental difference,
that will quantify it well.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

--- Comment #6 from hnsupport <su...@handynetworks.com> ---
(In reply to Giovanni Bechis from comment #3)
> Created attachment 5692 [details]
> fix unparseable relay
> 
> I cannot reproduce the spf error, anyway the attached diff fixes the
> unparseable relay for me.

I'll apply this patch and test, thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

--- Comment #11 from Kevin A. McGrail <km...@apache.org> ---
On my 2 systems, init.pre is where the SPF plugin is loaded

On my key test rig SPF passes.

What is your glue for calling spamassassin

Here's the output that matches the word SPF for your review:

Apr  6 19:54:28.295 [8453] dbg: check: tagrun - tag DKIMDOMAIN is still
blocking action 1
Apr  6 19:54:28.306 [8453] dbg: plugin:
Mail::SpamAssassin::Plugin::MIMEHeader=HASH(0x94faff0) implements
'finish_tests', priority 0
Apr  6 19:54:28.306 [8453] dbg: plugin:
Mail::SpamAssassin::Plugin::Check=HASH(0x9588a90) implements 'finish_tests',
priority 0
Apr  6 19:54:28.444 [8453] dbg: netset: cache trusted_networks hits/attempts:
25/26, 96.2 %
Press any key to continue...
Apr  6 19:55:16.614 [8828] dbg: plugin: loading Mail::SpamAssassin::Plugin::SPF
from @INC
Apr  6 19:55:17.959 [8828] dbg: config: fixed relative path:
/var/lib/spamassassin/3.004004/updates_spamassassin_org/25_spf.cf
Apr  6 19:55:17.959 [8828] dbg: config: using
"/var/lib/spamassassin/3.004004/updates_spamassassin_org/25_spf.cf" for
included file
Apr  6 19:55:17.960 [8828] dbg: config: read file
/var/lib/spamassassin/3.004004/updates_spamassassin_org/25_spf.cf
Apr  6 19:55:18.243 [8828] dbg: config: fixed relative path:
/var/lib/spamassassin/3.004004/updates_spamassassin_org/60_whitelist_spf.cf
Apr  6 19:55:18.243 [8828] dbg: config: using
"/var/lib/spamassassin/3.004004/updates_spamassassin_org/60_whitelist_spf.cf"
for included file
Apr  6 19:55:18.243 [8828] dbg: config: read file
/var/lib/spamassassin/3.004004/updates_spamassassin_org/60_whitelist_spf.cf
Apr  6 19:55:20.552 [8828] dbg: config: warning: no description set for
FROM_MISSP_SPF_FAIL
Apr  6 19:55:20.597 [8828] dbg: config: warning: no description set for
FORGED_SPF_HELO
Apr  6 19:55:22.549 [8828] dbg: askdns: depend on tags SENDERDOMAIN, rules:
JMQ_SPF_ALL, __PDS_SPF_ONLYALL, PDS_SPF_NONE, PDS_SPF_ALL, JMQ_SPF_NEUTRAL,
PDS_SPF_ONLYALL 
Apr  6 19:55:22.549 [8828] dbg: askdns: query template _SENDERDOMAIN_, type
TXT, rules: JMQ_SPF_ALL, __PDS_SPF_ONLYALL, PDS_SPF_NONE, PDS_SPF_ALL,
JMQ_SPF_NEUTRAL, PDS_SPF_ONLYALL
Apr  6 19:55:23.825 [8828] dbg: spf: checking to see if the message has a
Received-SPF header that we can use
Apr  6 19:55:23.908 [8828] dbg: spf: using Mail::SPF for SPF checks
Apr  6 19:55:23.909 [8828] dbg: spf: checking HELO
(helo=o2.email.wetransfer.com, ip=192.254.118.54)
Apr  6 19:55:23.913 [8828] dbg: dns: providing a callback for id:
32395/IN/SPF/o2.email.wetransfer.com
Apr  6 19:55:23.923 [8828] dbg: spf: query for
/192.254.118.54/o2.email.wetransfer.com: result: none, comment: , text: No
applicable sender policy available
Apr  6 19:55:24.093 [8828] dbg: spf: already checked for Received-SPF headers,
proceeding with DNS based checks
Apr  6 19:55:24.093 [8828] dbg: spf: found Envelope-From in first external
Received header
Apr  6 19:55:24.093 [8828] dbg: spf: checking EnvelopeFrom
(helo=o2.email.wetransfer.com, ip=192.254.118.54,
envfrom=bounces+922094-0e6c-juridico1=fernangonzalezabogados.es@em9713.email.wetransfer.com)
Apr  6 19:55:24.097 [8828] dbg: dns: providing a callback for id:
9080/IN/SPF/em9713.email.wetransfer.com
Apr  6 19:55:24.182 [8828] dbg: spf: query for
bounces+922094-0e6c-juridico1=fernangonzalezabogados.es@em9713.email.wetransfer.com/192.254.118.54/o2.email.wetransfer.com:
result: pass, comment: , text: Mechanism 'ip4:192.254.118.54' matched
Apr  6 19:55:24.189 [8828] dbg: rules: ran eval rule SPF_PASS ======> got hit
(1)
Apr  6 19:55:24.227 [8828] dbg: spf: def_whitelist_from_spf:
bounces+922094-0e6c-juridico1=fernangonzalezabogados.es@em9713.email.wetransfer.com
is not in DEF_WHITELIST_FROM_SPF
Apr  6 19:55:24.239 [8828] dbg: spf: whitelist_from_spf:
bounces+922094-0e6c-juridico1=fernangonzalezabogados.es@em9713.email.wetransfer.com
is not in user's WHITELIST_FROM_SPF
Apr  6 19:55:27.112 [8828] dbg: auto-whitelist: sql-based get_addr_entry: found
1 entries for noreply@wetransfer.com|spf
Apr  6 19:55:27.113 [8828] dbg: auto-whitelist: sql-based
noreply@wetransfer.com|spf scores -3.56, msgcount 4
Apr  6 19:55:27.118 [8828] dbg: auto-whitelist: sql-based add_score/insert
root|noreply@wetransfer.com|none|1|-0.89|spf: SQL error: Duplicate entry
'root-noreply@wetransfer.com-spf-none' for key 'PRIMARY'
Apr  6 19:55:27.122 [8828] dbg: auto-whitelist: sql-based add_score/update new
msgcount: 5, new totscore: -4.45 for
5|-0.89|root|noreply@wetransfer.com|spf|none
Apr  6 19:55:27.126 [8828] dbg: auto-whitelist: sql-based get_addr_entry: found
1 entries for wetransfer.com|spf
Apr  6 19:55:27.126 [8828] dbg: auto-whitelist: sql-based wetransfer.com|spf
scores -3.56, msgcount 4
Apr  6 19:55:27.131 [8828] dbg: auto-whitelist: sql-based add_score/insert
root|wetransfer.com|none|1|-0.89|spf: SQL error: Duplicate entry
'root-wetransfer.com-spf-none' for key 'PRIMARY'
Apr  6 19:55:27.135 [8828] dbg: auto-whitelist: sql-based add_score/update new
msgcount: 5, new totscore: -4.45 for 5|-0.89|root|wetransfer.com|spf|none
Apr  6 19:55:27.176 [8828] dbg: check:
tests=DKIM_INVALID,DKIM_SIGNED,HTML_MESSAGE,KAM_DMARC_STATUS,KAM_REALLYHUGEIMGSRC,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,RCVD_IN_SENDERSCORE_90_100,SPF_PASS,UNPARSEABLE_RELAY,UNWANTED_LANGUAGE_BODY
Apr  6 19:55:27.182 [8828] dbg: timing: total 10639 ms - init: 5581 (52.5%),
parse: 21 (0.2%), extract_message_metadata: 420 (3.9%), get_uri_detail_list: 31
(0.3%), tests_pri_-1000: 532 (5.0%), compile_gen: 725 (6.8%), compile_eval: 137
(1.3%), tests_pri_-950: 19 (0.2%), tests_pri_-900: 19 (0.2%), tests_pri_-100:
45 (0.4%), tests_pri_-90: 17 (0.2%), tests_pri_0: 2820 (26.5%), check_spf: 189
(1.8%), poll_dns_idle: 9 (0.1%), dkim_load_modules: 77 (0.7%),
check_dkim_signature: 29 (0.3%), check_dkim_adsp: 12 (0.1%),
wait_for_pending_rules: 0.58 (0.0%), tests_pri_20: 323 (3.0%), check_razor2:
304 (2.9%), tests_pri_30: 18 (0.2%), check_pyzor: 1.04 (0.0%), tests_pri_500:
511 (4.8%), tests_pri_1000: 130 (1.2%), total_txrep: 110 (1.0%),
check_txrep_email_ip: 7 (0.1%), update_txrep_email_ip: 7 (0.1%),
check_txrep_domain: 5 (0.0%), update_txrep_domain: 7 (0.1%), check_txrep_helo:
4.8 (0.0%), update_txrep_helo: 6 (0.1%), check_txrep_ip: 4.5 (0.0%),
update_txrep_ip: 6 (0.1%)
        RCVD_IN_MSPIKE_H2,RCVD_IN_SENDERSCORE_90_100,SPF_PASS,
Filter Tests:
DKIM_INVALID,DKIM_SIGNED,HTML_MESSAGE,KAM_DMARC_STATUS,KAM_REALLYHUGEIMGSRC,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,RCVD_IN_SENDERSCORE_90_100,SPF_PASS,UNPARSEABLE_RELAY,UNWANTED_LANGUAGE_BODY
Content analysis details:   (1.9 points, -100.0 required)
-0.0 SPF_PASS               SPF: sender matches SPF record
 0.0 KAM_DMARC_STATUS       Test Rule for DKIM or SPF Failure with Strict
Filter Tests:
DKIM_INVALID,DKIM_SIGNED,HTML_MESSAGE,KAM_DMARC_STATUS,KAM_REALLYHUGEIMGSRC,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,RCVD_IN_SENDERSCORE_90_100,SPF_PASS,UNPARSEABLE_RELAY,UNWANTED_LANGUAGE_BODY
Content analysis details:   (1.9 points, -100.0 required)
-0.0 SPF_PASS               SPF: sender matches SPF record

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

--- Comment #10 from hnsupport <su...@handynetworks.com> ---
One thing I have found: the SPF plugin is loaded explicitly in my init.pre...
so it may not be loaded by default.  Is this true of your test environments? 
Debug output will confirm it, if so.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

--- Comment #3 from Giovanni Bechis <gi...@paclan.it> ---
Created attachment 5692
  --> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5692&action=edit
fix unparseable relay

I cannot reproduce the spf error, anyway the attached diff fixes the
unparseable relay for me.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

hnsupport <su...@handynetworks.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |support@handynetworks.com

--- Comment #5 from hnsupport <su...@handynetworks.com> ---
(In reply to Giovanni Bechis from comment #1)
> I cannot reproduce it, the output of a spamassassin check for the attached
> message follows:
> -----------------------------------------------------------------------------
> -
> Content analysis details:   (1.4 points, 5.0 required)
> 
>  pts rule name              description
> ---- ----------------------
> --------------------------------------------------
>  0.1 TO_MALFORMED           To: has a malformed address
>  0.0 SPF_HELO_NONE          SPF: HELO does not publish an SPF Record
> -0.0 SPF_PASS               SPF: sender matches SPF record
>  0.0 HTML_MESSAGE           BODY: HTML included in message
>  1.1 KAM_REALLYHUGEIMGSRC   RAW: Spam with image tags with ridiculously
>                              huge http urls
>  0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not
> necessarily
>                             valid
>  0.1 DKIM_INVALID           DKIM or DK signature exists, but is not valid
>  0.0 UNPARSEABLE_RELAY      Informational: message has unparseable relay
>                             lines
>  0.0 KAM_DMARC_STATUS       Test Rule for DKIM or SPF Failure with Strict
>                             Alignment
> -----------------------------------------------------------------------------
> -
> Which Mail::SPF version are you using ?
> Other than that I think a there could be a dns-related problem in your setup.
> Please follow
> https://cwiki.apache.org/confluence/display/SPAMASSASSIN/DnsBlocklists#dnsbl-
> block to fix at least SURBL_BLOCKED warning.


spamassassin and spf module versions:

[root@spamd-node0 ~]# perl -MMail::SPF -e 'print $Mail::SPF::VERSION ."\n";'
v2.009
[root@spamd-node0 ~]# perl -MMail::SpamAssassin -e 'print
$Mail::SpamAssassin::VERSION ."\n";'
3.004004

I don't think the debug output I included is indicative of a DNS issue...
considering the header is selected before spamassassin called Mail::SPF to
evaluate that RFC1918 IP.

Will check out that wiki regardless.

Can you show me your debug output upon testing this message (-D flag) for my
own reference?  Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

--- Comment #14 from hnsupport <su...@handynetworks.com> ---
(In reply to RW from comment #12)
> You appear to have 192.254.118.54 in your trusted_networks, and since you
> haven't defined internal_networks explicitly, it gets copied from
> trusted_networks. Presumably you haven't added the private address ranges to
> trusted_networks which makes 10.30.65.95 look like the last-external IP
> address.
> 
> Others see the spf pass because they don't have 192.254.118.54 in
> internal_networks, and so, correctly, see that IP address as last-external.

Interesting: thanks RW, sounds promising!  And like an environmental issue, of
course...

I'll re-read the documentation for those directives more carefully, and define
internal_networks / redefine trusted_networks as appropriate.

Thanks again.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7805] Mail::SpamAssassin::Plugin::SPF passes the wrong headers to MAIL::SPF when helo is initially invoked at external relay.

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

Kevin A. McGrail <km...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kmcgrail@apache.org

--- Comment #4 from Kevin A. McGrail <km...@apache.org> ---
+1 on the patch for 3.4 and trunk though it's not relevant to this issue. 
Please close this as WORKSFORME.

-- 
You are receiving this mail because:
You are the assignee for the bug.