Haraka does not presently support the Authentication-Results header (RFC 5451). At present, auth info is being appended to the Received header.
When I added Authentication-Results handling in QP, I found it beneficial to create a method Qpsmtpd::Plugin::store_auth_results() that auth plugins (SPF, iprev, DKIM, DMARC) called to store their results in a connection note. At the end of the SMTP session, the QP auth results and the contents of the connection note would be checked and any results would be formatted into the Authentication-Results header as performed in Qpsmtpd::SMTP::authentication_results.
It would be swell if Haraka had such a mechanism. Even if it was half-baked, with a decent structure around it, so someone less familiar with the code base and direction could come along and fill in the blanks.
baudehlo
commented
10 years ago
Haraka does not presently support the Authentication-Results header (RFC 5451). At present, auth info is being appended to the Received header.
When I added Authentication-Results handling in QP, I found it beneficial to create a method Qpsmtpd::Plugin::store_auth_results() that auth plugins (SPF, iprev, DKIM, DMARC) called to store their results in a connection note. At the end of the SMTP session, the QP auth results and the contents of the connection note would be checked and any results would be formatted into the Authentication-Results header as performed in Qpsmtpd::SMTP::authentication_results.
It would be swell if Haraka had such a mechanism. Even if it was half-baked, with a decent structure around it, so someone less familiar with the code base and direction could come along and fill in the blanks.