On Wed, 26 Feb 2020 08:13:42 +0100 Bengt Gördén <bengan@bag.org> wrote:
On 2020-02-25 21:20, Dave Howorth wrote:
And some recipient's mailservers (presumably my ISP?) who bother to check for such things consequently discard it as from the wrong source?
That's the whole point of Sender Policy Framework (spf)
If so, surely the list server should remove the SPF record before forwarding the message, and perhaps add one of its own?
You got it all wrong. It's not included in the mail. It's part of DNS, and the mail server software (sendmail, postfix etc.) looks at it.
If you look at he's (Pauls) mx domain you get mail.swabian.net.
A check of the spf record gives:
$ dig +short mail.swabian.net. TXT "v=spf1 a -all"
The records are interpreted from left to right.
v = version a = allow sending mail from the DNS a-record -all = reject all mail coming from hosts other than the a-record.
$ dig +short mail.swabian.net. 80.152.201.148
A starting point to read is Wikipedia. https://en.wikipedia.org/wiki/Sender_Policy_Framework
Thanks for the explanation. As I said I don't understand SPF. The wikipedia article just looks like gobbledygook to me. So is there anything that either Paul, or the list mailserver, or for that matter my ISP's mailserver is doing 'wrong' somehow that could be improved to prevent Paul's mails getting bounced? Or is it just a poorly designed protection scheme? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org