Hi -
Our servers are checking mail from bounce.example.com.
It "redirect"s to example.com's SPF record, which includes an "mx" token.
I assume that since the redirect is a "macro", "mx" in this case refers
to the mx of bounce.example.com, not example.com, right?
bounce.example.com has two mx hostnames listed. One of them
(mail.example.com) has no A records.
RFC 4408, section B1, example, 3, says "no sending hosts pass since
example.org has no A records". So i take it that the behavior should be
that a verifier "permerror" these messages? What do most verifiers do,
if anyone knows (I know that's a separate question)?
The tool at kitterman.com shows:
"Results - ambiguous SPF Ambiguity Warning: No A records found for:
mail.example.com", but doesn't say what the python library's final SPF
result would be (we're not using that library, but just curious...).
Another online checker said "that sender is probably not allowed" or
something similar.
Thanks!
-c
-------------------------------------------
Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
Archives: https://www.listbox.com/member/archive/1020/=now
RSS Feed: https://www.listbox.com/member/archive/rss/1020/1311530-08394398
Modify Your Subscription: https://www.listbox.com/member/?member_id=1311530&id_secret=1311530-644bccd5
Unsubscribe Now: https://www.listbox.com/unsubscribe/?member_id=1311530&id_secret=1311530-512c0f9e&post_id=20101012212942:59E9D412-D669-11DF-9FC0-F02EA19BE261
Powered by Listbox: http://www.listbox.com
Our servers are checking mail from bounce.example.com.
It "redirect"s to example.com's SPF record, which includes an "mx" token.
I assume that since the redirect is a "macro", "mx" in this case refers
to the mx of bounce.example.com, not example.com, right?
bounce.example.com has two mx hostnames listed. One of them
(mail.example.com) has no A records.
RFC 4408, section B1, example, 3, says "no sending hosts pass since
example.org has no A records". So i take it that the behavior should be
that a verifier "permerror" these messages? What do most verifiers do,
if anyone knows (I know that's a separate question)?
The tool at kitterman.com shows:
"Results - ambiguous SPF Ambiguity Warning: No A records found for:
mail.example.com", but doesn't say what the python library's final SPF
result would be (we're not using that library, but just curious...).
Another online checker said "that sender is probably not allowed" or
something similar.
Thanks!
-c
-------------------------------------------
Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
Archives: https://www.listbox.com/member/archive/1020/=now
RSS Feed: https://www.listbox.com/member/archive/rss/1020/1311530-08394398
Modify Your Subscription: https://www.listbox.com/member/?member_id=1311530&id_secret=1311530-644bccd5
Unsubscribe Now: https://www.listbox.com/unsubscribe/?member_id=1311530&id_secret=1311530-512c0f9e&post_id=20101012212942:59E9D412-D669-11DF-9FC0-F02EA19BE261
Powered by Listbox: http://www.listbox.com