RFC 5451 is obsoleted

[AndreyMZ]

Problem description

authres_status/README.md

Line 3 in 9a6718e

This plugin checks the Authentication-Results headers that were added by your MTA and displays an icon to show the verification status. Parsing of the Authentication-Results headers is more or less done according to [RFC5451](https://tools.ietf.org/html/rfc5451) which supports DKIM, DomainKeys, SPF, Sender-ID, iprev and SMTP AUTH result values.

Parsing of the Authentication-Results headers is more or less done according to RFC5451

But RFC 5451 (April 2009) is obsoleted by RFC 7001 (September 2013) which is obsoleted by RFC 7601 (August 2015) which is obsoleted by RFC 8601 (May 2019).

Possible solution

Check if this plugin is compliant with RFC 8601. If yes, then just update the references in README and the project description and topics on GitHub. If no, then fix the parsing of the Authentication-Results header to conform with the actual RFC 8601.

[pimlie]

Thanks for the info but the way you communicate it is not really constructive and it seems you are missing the major point of open-source software ;)

[AndreyMZ]

Unfortunately, no one has communicated this issue better than me...

Could you please clarify what you don't like about my description of the issue so I can fix it? It is quite concise but it contains problem statement and possible solution. Why not to fix the description instead of closing an unfixed valid issue as "completed"?

[pimlie]

The idea behind open source (or at least it is for me) is that we all have the possibility to work together on the same software and make it better. Maybe I misunderstood you, but the last paragraph of your message just sounded a bit demanding. Like why won't you be the one who checks compliance with RFC 8601? That's the real power of open source! 😃

[AndreyMZ]

OK, I have updated the description. I hope it is not so demanding now. Thank you!

[pimlie]

Awesome, really appreciate the detailed chain of RFC's! I will see if I can find some time to read these RFC's and check what needs changing.

Between you and me, I actually searched for follow-up RFC's for 5451 many years back (i think around 2017) cause I found it strange that 5451 was never updated since 2009. But I guess my search skillz weren't what they needed to be cause I didn't find anything at the time 😞