I have discourse installed on VPS I have directadmin installed on a different managed VPS running exim smtp In discourse I used SMTP server details on the directadmin VPS I checked emails with isnotspam.com Sending email using thunderbird with directadmin SMTP Result: pass ID(s) verified: [header.From=discourse@example.com](mailto: header.From=discourse@example.com) Selector=x domain=example.com DomainKeys DNS Record=x._domainkey.example.com BUT if I send it out using discourse the result passes, but no selector Result: pass ID(s) verified: [header.From=discourse@example.com](mailto :header.From=discourse@example.com) Selector= domain= DomainKeys DNS Record=._domainkey. Any ideas?

My SMTP server should. However when emails are sent from discourse it’s not getting signed the same. I’m wondering if it has to do with the helo forum.example.com

You gave the answer yourself :sunglasses: Discourse acts as an smtp client and the dkim signing must be provided by the smtp server receiving the mails from Discourse.

[image] Thommie Rother: Discourse acts as an smtp client Yes correct. So the different signing results when checked with isnotspam was confusing me. Anyway , I re ran the test today and now it passes – ---------------------------------------------------------- DKIM check details: ---------------------------------------------------------- Result: pass ID(s) verified: header.From=discourse@example.com Selector=x domain=example.com DomainKeys DNS Record=x._domainkey.example.com Not sure what happened, but I did have to update my DNS txt key inside cloudflare, as well as update the rDNS for the mail server. Maybe it just required time for everything to propagate or clear some cache?

[image] o o: Anyway , I re ran the test today and now it passes In the previous test: Result: pass ID(s) verified: [header.From=discourse@example.com](mailto :header.From=discourse@example.com) Selector= domain= DomainKeys DNS Record=._domainkey. there was no DKIM record, so it wasn’t signed. [image] o o: Maybe it just required time for everything to propagate or clear some cache? DNS doesn’t propagate, remember. Regardless, now the mail is signed so you should be good?

Yep its signs on checking, so something needed cache updating

Emails not getting signed by DKIM when sent using discourse

Product Support Self-hosting

supermathie (Michael Brown) May 4, 2024, 10:49pm 2

Which component are you expecting to be doing the DKIM signing?

Topic		Replies	Views
Why are e-mails sending from @discoursemail.com? Product Support	2	4527	April 16, 2019
DKIM - Body hash does not verify - on email sent from Discourse Product Support	4	263	September 19, 2024
Email failure after install Self-hosting	7	1278	March 25, 2020
DKIM key was provided incorrect Product Support	10	4089	January 17, 2015
E-Mail not working after moving to self-hosting and adding DKIM record Self-hosting	4	1653	December 6, 2021

Emails not getting signed by DKIM when sent using discourse

Related topics