Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perhaps consider changing the default of AlwaysAddARHeader to enabled #242

Open
ell1e opened this issue Feb 17, 2025 · 0 comments
Open

Perhaps consider changing the default of AlwaysAddARHeader to enabled #242

ell1e opened this issue Feb 17, 2025 · 0 comments

Comments

@ell1e
Copy link

ell1e commented Feb 17, 2025

I've been part of multiple discussions now on the client-side to evaluate AuthenticationResults headers. This may be desirable for mail accounts where the SMTP server fully rejecting any DKIM failed mail or always moving it to spam is impractical, e.g. due to the many misconfigured mailing lists.

It seems this can become way more complicated with spoofed AuthenticationResults headers, if the own target MTA only sporadically inserts unspoofed ones.

See: https://bugzilla.mozilla.org/show_bug.cgi?id=265226 or this comment lieser/dkim_verifier#465 (comment)

Most providers I've tested only sporadically insert AuthenticationResults, and I suspect it might be because they run OpenDKIM with default settings.

Therefore, I wonder if the AlwaysAddARHeader default should be changed.

Of course I realize this is a huge change and I might be missing something here anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant