-
Notifications
You must be signed in to change notification settings - Fork 144
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
DKIM not working with FQDN (ie. mail.domain.com) #111
Comments
Further investigation shows that DKIM signing does work when using a TLD as an allowed sender (i.e.: domain.com), but does not work when using a FQDN (i.e.: mail.domain.com). |
Thank you for this report. I will have a look at it. |
Can you share the whole set of parameters you used to start the image? |
Of course.
With the above configuration DKIM fails. My limited knowledge of opendkim suggests that mail._domainkeys.mail.mydomain.com as
Notice the only change for DKIM to work was to remove mail. from mail.mydomain.com and to change the key filenames the same way. |
I have same problem, but also for some reason when
|
At first I thought it was my own incompetence not unlike this fellow: #109
But even when using the autogenerated keys function of the image, DKIM validators still report that the message is not DKIM signed.
When using
docker start -a postfix
to see the STDOUT it looks like the key files are found by the script. There must be a single step missing for opendkim to actually sign with them.Also, not sure if relevant or not, but it seems that the KeyTable, SigningTable, and TrustedHosts files are missing from
/etc/opendkim/
.All this using
boky/postfix:latest
, that is, the Alpine version. Not tested using the Ubuntu one.The text was updated successfully, but these errors were encountered: