On 2015-07-15 23:49, Matus UHLAR - fantomas wrote:
On 2015-07-15 13:53, David Jones wrote:
I have seen Microsoft Exchange servers use the header From: domain
instead of the envelope-from but this does not follow RFC 4408 spec.
On 15.07.15 15:06, Dave Warren wrote:
This is valid under Sender-ID, which was Microsoft's attempt at SPF
version 2. It has since died a (deserved) death, and such use should
be depreciated. However, if you don't have an explicit spf2.0/pra
record, Sender-ID suggested using the v=spf1 record instead (which
obviously causes issues)
If you want to avoid these tests, add this as a TXT record:
"spf2.0/pra" or "spf2.0/pra ?all"
Better not. Don't jump on dead horse. Microsoft SPF/2 is dead, let it die
and don't even try to fix things by implementing it, since may break
things
working properly.
From a receiving side, I agree completely. As a sender, I still like to
have a record telling receivers "Don't apply spf2.0/pra tests" because
otherwise there is (potential for) minor breakage if you happen to send
to a server that still performs these tests. If not, the records are
harmless TXT records.
With that being said, I only personally know of one small Exchange
server which still implements Sender ID tests, it's been running some
years without an administrator and they have no plans to hire one, so
it's likely got other issues which need attention, but aren't critical
enough to get it. And frankly, even when spf2.0/pra records don't exist
and Sender ID falls back to v=spf1 records, things work often enough.
Each to their own, but if you encounter a server that is still using
Sender-ID, it's generally so poorly maintained that it's easier to add
the record yourself than to try and get them to fix it.
--
Dave Warren
http://www.hireahit.com/
http://ca.linkedin.com/in/davejwarren
