Ummm stalwart generates wrong spf ??

[lulzkiller666]

When adding a domain, stalwart gives the DNS entries to put. Specifically the SPF records

For example : v=spf1 a ra=postmaster -all

But thats not a valid spf record the " ra=postmaster " according to my knowledge, and i ran it through chatgpt also, is wrong. No such thing exists for the spf record....

[lulzkiller666]

So i guess i was wrong, and even chatgpt was wrong after i researched this more deeply. Funny enough there is very very sparse information regarding this ra=postmaster available online only a single document tells about it

[mdecimus]

See https://datatracker.ietf.org/doc/html/rfc6652

[lulzkiller666]

Yup thats the document i found. its weird why this is not more "widely" used, literally all SPF testers i used marked it as an error. There aint much info about this online

[lulzkiller666]

So, i had a short chat with powerdmarc about this issue. And according to them. This "ra=postmaster" is just a proposal, it has not yet been implemented yet, that is why their tool and mxtoolbox etc still marks it as an error

[mdecimus]

It is actually an RFC, not a draft. In any case, SPF indicates that unknown tags have to be ignored, returning an error is incorrect.