-
-
Notifications
You must be signed in to change notification settings - Fork 266
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 is not signed #728
Comments
Hi!
|
1 - public server I am replacing the domain name so that it cannot be found in the search my dns dkim record: Wildduck api dkim: GET http://apihost:8080/dkim/66d1bbb05c9d6f1d8060d74e
I sent the message like this: POST http://apihost:8080/users/66cf5c04d9402600076a79ad/submit
|
But why does your DKIM DNS key contain another I just set up a basic wildduck server, added dkim. Sent an email to gmail and the DKIM is working. So I would first check if the dns entry is actually correct and those quotes are not included in the value but just how your provider displays the value, |
The provider says this is normal behavior, it's just that the txt record is limited to 255 characters I asked chatgpt and searched the internet - this is really a normal practice https://support.cpanel.net/hc/en-us/articles/4402114117911-Why-are-DKIM-TXT-records-split I generally do not understand what the dns record has to do with it, there is no dkim signature in the body of the letter. It will not come to checking dns records, because there is nothing to check Or am I wrong? |
Yeah it's just a split record. A lot of people don't know about them, as most dns providers show them as a single string in their panel. But it's how dns works and it's fine. |
Do you have DKIM enabled in zone-mta plugin? Under |
it was disabled. enable and restarted containers, The situation has not changed
|
Is zonemta set to use the same db as wildduck? I think it's probable that the plugin is not finding your dkim keys in the db for some reason. |
(by the way, signTransportDomain is not needed for your usecase of signing the from address domain. You'd use that to also sign with mta.example.com. So you can leave it false. Signing the from domain should happen automatically if it finds a matching key in the db.) |
I am using the standard configuration from the repository https://github.com/nodemailer/wildduck-dockerized The only thing I changed is I changed the version here to nodemailer/wildduck:1.45.0 my /wildduck-dockerized/config/zone-mta/zonemta.toml : |
I'm using the container version of wild duck
I created a dkim for the domain using the api method https://docs.wildduck.email/api/#operation/postdkim
I have activated the sign Transport Domain parameter in /config/wildduck/dkim.toml
I am sending an email from the same domain for which the signature was generated
When sending an email, it is not signed by DKIM
What did I miss?
The text was updated successfully, but these errors were encountered: