>
> Date: Mon, 16 Nov 2015 10:43:22 -0500
> From: David T Darnell <[log in to unmask]>
> Subject: Administrivia: Yahoo refused to distribute posted message
>
> I successfully posted on the message board website, but Yahoo is
> sending me a message that the email distribution of it was denied on
> policy. The explanation is that the email needs to be submitted
> through a Yahoo or other trusted email server. I believe this to be an
> issue between the utc.edu environment and Yahoo.
>
The message headers of the message I received from utc.edu contains this:
Received-SPF: Softfail (domain owner discourages use of this host)
identity=mailfrom; client-ip=150.182.136.7; helo=raven.utc.edu;
[log in to unmask];
[log in to unmask]
Received: from raven.utc.edu (raven.utc.edu [150.182.136.7])
by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP
for <[log in to unmask]>; Tue, 17 Nov 2015 00:01:29 -0500 (EST)
Looking at the Sender Policy Framework (SPF) records for utc.edu we see:
dig RAVEN.UTC.EDU txt
; <<>> DiG 9.8.3-P1 <<>> RAVEN.UTC.EDU txt
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12106
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;RAVEN.UTC.EDU. IN TXT
;; ANSWER SECTION:
raven.utc.edu. 60 IN TXT "v=spf1 include:spf.protection.outlook.com
~all"
. . .
dig spf.protection.outlook.com TXT
; <<>> DiG 9.8.3-P1 <<>> spf.protection.outlook.com TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6324
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 8
;; QUESTION SECTION:
;spf.protection.outlook.com. IN TXT
;; ANSWER SECTION:
spf.protection.outlook.com. 600 IN TXT "v=spf1 ip4:207.46.101.128/26
ip4:207.46.108.0/25 ip4:207.46.100.0/24 ip4:207.46.163.0/24
ip4:65.55.169.0/24 ip4:157.55.133.0/25 ip4:157.56.110.0/23
ip4:157.55.234.0/24 ip4:213.199.154.0/24 ip4:213.199.180.0/24
include:spfa.protection.outlook.com -all"
. . .
In April of 2014 AOL, GOOGLE, and YAHOO, among others free email
providers, began enforcing SPF with "DomainKeys Identified Mail"
(DKIM) and “Domain-based Message Authentication, Reporting, and
Conformance" (DMARC) to reduce the use of their address space in email
PHISHING scams. YAHOO in particular have decided to enforce SPF
without regard to the preferences of the sender domain, the so-called
SOFTFAIL option.
Basically, if a domain has an SPF and someone sends messages from that
domain through a mail reflector, like a mailing list manager, that
re-transmits their message using the original FROM address but through
a host belonging to a different domain then that is going to trigger
an SPF failure.
In this case however, it appears the problem is that raven.utc.com
does not list itself as a permitted sender address for its own
messages. IPv4:150.182.136.7 is not listed among the authorised
addresses for raven.utc.edu. To avoid the SPF failure raven's DNS TXT
Resource Record should probably contain the +a tag and look like this:
raven.utc.edu. 60 IN TXT "v=spf1 +a
include:spf.protection.outlook.com ~all"
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
James B. Byrne mailto:[log in to unmask]
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
