Replies: 1 comment 2 replies
-
It may refer to authenticated submission? Which is not the case over port 25 (receiving public mail from external MTAs). You may want to compare to the equivalent rspamd support which is eventually intended to become a default and replace opendkim among other services. Other mail-server projects already use rspamd. The signing tables should be configured when using the docker-mailserver/target/bin/open-dkim Lines 158 to 168 in aba218e I don't have time unfortunately to look further into that for you, but it may be the project still has some legacy assumptions on the happy path of a single mail domain shared with the DMS hostname. Our test suite only covers the two (opendkim + rspamd) DKIM generation scripts are working correctly. No networked containers with DNS records setup yet, we're rather reliant upon community contributions to improve on areas like this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am running the following configuration and all works fine until I setup DKIM.
MX records of
mydomainABC.xyzandmydomainDEF.xyzpoint tomail.mymailer.orgI created DKIM keys for all 3 domains in DMS and copied the public keys into the DNS record of each domain.
Now from the documentation it is not very clear to me what I need to change. Maybe someone has a pointer.
I am getting the following DKIM log entries
I assume this is for outgoing mail and there seems to be a problem.
And some of these log entries:
I assume this is DKIM for incoming mail and the information seems to indicate that verification is ok but what does "not authenticated" mean? It seems to come up with every incoming sender.
Beta Was this translation helpful? Give feedback.
All reactions