> host -t txt example.com
> "v=spf1 redirect=_spf.example.com -all"
> host -t _spf.example.com
> "v=spf1 +all"
Redirect makes it a replacement for the record, so +all
> host -t txt example.net
> "v=spf1 -include=_spf.example.net +all"
> host -t _spf.example.net
> "v=spf1 ~all"
-include is not a thing. So it would be an invalid record. Even if -include was
a thing, ~all would not be taken into account for an include.
I didn't look at the RFC, but these seemed pretty easy to me. If you were
implementing SPF you would actually be looking at the RFC, and it would be even
easier. I do think that of all the things, SPF is pretty easy to implement. If
you even need to implement it, that is. Seeing how old it is now and how it's
already implemented everywhere.
Groetjes,
Louis
Op zaterdag 12 oktober 2024 om 11:11, schreef Gellner, Oliver via mailop
<[email protected]>:
> > On 11.10.2024 at 23:02 Mark E. Mallett via mailop <[email protected]
> [[email protected]]> wrote:
> >
> > On Fri, Oct 11, 2024 at 04:20:23PM +0000, Dave Crocker via mailop wrote:
> >>> On 10/11/2024 12:49 AM, Matus UHLAR - fantomas via mailop wrote:
> >>> Yes, SPF has drawbacks. But it is still trivial to implement and makes
> >>> DMARC easier to implement as well.
> >> Actually it isn't.
> >
> > That was my initial reaction(*) too, about "trivial to implement." The
> > macro handling, for example, is a bit touchy. And some special
> > considerations based on context. And other things that I've probably
> > forgotten.
>
> Yeah, for example do the following SPF records deny everything, allow
> everything, or are they invalid and produce no results?
>
> > host -t txt example.com
> > "v=spf1 redirect=_spf.example.com -all"
> > host -t _spf.example.com
> > "v=spf1 +all"
>
> > host -t txt example.net
> > "v=spf1 -include=_spf.example.net +all"
> > host -t _spf.example.net
> > "v=spf1 ~all"
>
> If you happen to be an author of the SPF RFC you know the answer, but at least
> I have to read up on it.
>
> —
> BR Oliver
> ________________________________
>
> dmTECH GmbH
> Am dm-Platz 1, 76227 Karlsruhe * Postfach 10 02 34, 76232 Karlsruhe
> Telefon 0721 5592-2500 Telefax 0721 5592-2777
> [email protected] [[email protected]]<mailto:[email protected] [[email protected]]> *
> www.dmTECH.de [https://www.dmtech.de/]<http://www.dmtech.de
> [http://www.dmtech.de/]>
> GmbH: Sitz Karlsruhe, Registergericht Mannheim, HRB 104927
> Geschäftsführer: Christoph Werner, Martin Dallmeier, Roman Melcher
> ________________________________
> Datenschutzrechtliche Informationen
> Wenn Sie mit uns in Kontakt treten, beispielsweise wenn Sie an unser
> ServiceCenter Fragen haben, bei uns einkaufen oder unser dialogicum in
> Karlsruhe besuchen, mit uns in einer geschäftlichen Verbindung stehen oder
> sich bei uns bewerben, verarbeiten wir personenbezogene Daten. Informationen
> unter anderem zu den konkreten Datenverarbeitungen, Löschfristen, Ihren
> Rechten sowie die Kontaktdaten unserer Datenschutzbeauftragten finden Sie
> hier<https://www.dm.de/datenschutzerklaerung-kommunikation-mit-externen-493832
> [https://www.dm.de/datenschutzerklaerung-kommunikation-mit-externen-493832]>.
> _______________________________________________
> mailop mailing list
> [email protected] [[email protected]]
> https://list.mailop.org/listinfo/mailop
> [https://list.mailop.org/listinfo/mailop]
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
