agentxin
New Member
- Messages
- 19
- Reaction score
- 0
- Points
- 1
All outgoing emails from webmail are getting marked as spam because the DKIM signature fails. I have consulted several dkim-checker sites, and have found that DirectAdmin inserts tabs and newlines to break up the public key TXT record because it is too long. This shows up as follows, in several sites (\010 is newline, \009 is a tab):
[ https://www.mail-tester.com/test-kfo30 ]
>> Your public key is:
>> "(\"v=DKIM1;
>> k=rsa;
>> p=MIIBIjAN [...] Kgm5G\"\010\009\009\009\009\009\"YS8Jyq [...]
Some testing sites ignore the tabs and say that the DKIM is valid, but obviously Gmail and most other sites see these unwanted characters.
Edit: I have enabled DMARC on its lowest risk level and tried disabling DKIM altogether, but Google is not appeased and still marks as spam.
I'm fairly sure that this is a DirectAdmin issue (I have opened a thread on their forums https://forum.directadmin.com/threads/invalid-dkim-due-to-tabs-inserted.59979/ but to no effect).
If any admin is reading this, can you either:
1) directly edit the TXT record, replace the tabs and newlines separating the DKIM record lines with a single space, or
2) enable manual editing of raw DNS file in the control panel, if that exists (there is apparently a reseller-level skin option that allows this).
Thank you for all of your attention.
Happy New Year, and great job on the migration.
Another example of invalid public key (their "tip" is quite accurate):
[ https://www.mail-tester.com/test-kfo30 ]
>> Your public key is:
>> "(\"v=DKIM1;
>> k=rsa;
>> p=MIIBIjAN [...] Kgm5G\"\010\009\009\009\009\009\"YS8Jyq [...]
Some testing sites ignore the tabs and say that the DKIM is valid, but obviously Gmail and most other sites see these unwanted characters.
Edit: I have enabled DMARC on its lowest risk level and tried disabling DKIM altogether, but Google is not appeased and still marks as spam.
I'm fairly sure that this is a DirectAdmin issue (I have opened a thread on their forums https://forum.directadmin.com/threads/invalid-dkim-due-to-tabs-inserted.59979/ but to no effect).
If any admin is reading this, can you either:
1) directly edit the TXT record, replace the tabs and newlines separating the DKIM record lines with a single space, or
2) enable manual editing of raw DNS file in the control panel, if that exists (there is apparently a reseller-level skin option that allows this).
Thank you for all of your attention.
Happy New Year, and great job on the migration.
Another example of invalid public key (their "tip" is quite accurate):
Last edited: