This has nothing to do with it. Dkim is only a sending issue, it should not effect incoming emails.
If its a incoming issue then the sending server is at fault.
use this format is mxtools dkim check mydomain.com:selector ie mydomain:2023
1 Like
so if I shorten the TTL it would make testing quicker and easier.
(for some reason I was thinking TXT records were instant 
)
No DNS always at the the VM provider.
But I trust Virtualmin to provide me withe the correct TXT records → which seems to be a problem here.
The problem was initiated by Thunderbird reporting to the user that an email sent on the domain (SMTP through the application - a NodeJS app) being delivered with the image posted in #1
Otherwise, I might never have been aware of it. As far as I was concerned the emails have always been sent DKIM signed - this is NOT a problem with Thunderbird sending anything. I even believe (without checking headers) that this user has Thunderbird set up to send via some other server Ionos (DR) So as my version of Thunderbird was uninstalled locally I had to reinstall it to see the image in #1 for myself. (hence suspecting a change in Thunderbird in the way it is reporting alerts on incoming mail.)
MxTools just produces the same errors reported above
You need to remove the quotes out of the TXT
IE suggested shows “v=DKIM1; k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmxNOxkiQPXinA” "SL…etc
change to
v=DKIM1; k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmxNOxkiQPXinASL…etc
remove all quotes (and spaces in the p= section)
The invalid character is the quotes (quotes and spaces in the p= section this needs to be one long strings without any spaces)
Do that and test again.
1 Like
So removing all the quotes AND the brackets out of the suggested TXT records
Solves the problem
with Thunderbird now reporting:
So I have emailed the user who should come back tomorrow with gifts 
Thank you
1 Like
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.