OPENDKIM: DKIM does not match in the domain UI

[stephdl]

Steps to reproduce

• Record a domain in the mail domain UI
• Most of time the DKIM test is ok (If correctly recorded)
• In some case the DKIM mismatches even if it is correctly set

Expected behavior

I expect if the DKIM is correctly set in the DNS registar the UI output that DKIM is correctly set

Actual behavior

A sysadmin has a DNS provider who output the key a bit differently as usual

 [root@prometheus ~]# echo '{"action":"network-checks","domain":"domain.com"}'| /usr/libexec/nethserver/api/nethserver-mail/domains/read
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnDHXY9axEEi2mNiPJarErUkCdnuCIo3pLidherVt+6z6NHrB/Fwc2BWwK97qH9APzbo4cBhm/wtbXAiRnNlcTBMkG4P4lm09a/dR6spVsJ72QMrr+V5M04sLQ+76Ru4K6Pj4iyHJmBlAvORS3v4tpoZgXipi4o9qmbPvcT7JzXucICZ6q5gSKuyQRrKlZKL55TR7GWTCJ6VVLhbis74HlMNWfwjhJmcz3z1zMnNKHsDSaQfLplDBi5c3gZFG8hJ7mBVA1fGZHD4SeDv5mSYQrBgFT5Hgij67eSmYtZ5GcMPyn7q3aobCDXHvWVTFQD1x5SNIJohYTBuPQ7SfRNs17QIDAQAB
v=DKIM1; k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw0LJtESK0G5LJ3euhIpLRyXlJyVOrw7exuztpOurn+/CYIYrpKVyBEdYBwlU2fOpSITJotK6dL2oOuhVnfCt6DhtSrTlA+jAvbHFsAraOm50dONtA9UllyKqjBPjYUP3VgPfTrHdC0r6oz1VcHb8JEuY9aDMb5EG8p155ZUpsrPYLn/m2Fq6nf5w/0g1/liPF3zFdLY8N61Vfgj3oX1dIhGGKVECPapA4Nh2tP+tznVaD6saMpH9POjHAmOPZ56ZaCrbdyChPKXh6ntwscb75QILhjuvLnmkfKsanO3bjJrIRl9tR25RhOEGnxwzAzqrxGvh+wj+bd2tDvVsLYcmiQIDAQAB
{"port-25":{"response":"ok","status":"success","message":""},"dkim-record":{"response":"mismatch","status":"success","message":""},"mx-record":{"response":"ok","status":"success","message":"mail.domain.com"},"status":"success","iprev-check":{"response":"ok","status":"success","message":""}}

we can see

default key
v=DKIM1; k=rsa; p=MIIBIjAN
dig output
v=DKIM1; k=rsa;p=MIIBIjAN

we need to remove all spaces to compare exactly the string

Components

nethserver-mail-common-2.29.8-1.ns7.noarch

See also

https://community.nethserver.org/t/dkim-records-not-matching/18078

---

Thank Elleni

[stephdl]

After rpm testing upgrade

• Go to domain panel of the email software and check on an already configured DKIM setting that your DKIM matches the DKIM from DNS (in the domain list check the domain popover)

[nethbot]

in 7.9.2009/testing:

• nethserver-mail-common-2.29.8-1.2.gab03262.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-disclaimer-2.29.8-1.2.gab03262.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-filter-2.29.8-1.2.gab03262.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-getmail-2.29.8-1.2.gab03262.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-imapsync-2.29.8-1.2.gab03262.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-ipaccess-2.29.8-1.2.gab03262.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-p3scan-2.29.8-1.2.gab03262.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-quarantine-2.29.8-1.2.gab03262.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-server-2.29.8-1.2.gab03262.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-smarthost-2.29.8-1.2.gab03262.ns7.noarch.rpm x86_64 armhfp aarch64

[gsanchietti]

I've tested it on a machine where the check was already ok: no regression found.

[gsanchietti]

Tested also by Elleni, verified.

[nethbot]

in 7.9.2009/updates:

• nethserver-mail-common-2.29.9-1.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-disclaimer-2.29.9-1.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-filter-2.29.9-1.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-getmail-2.29.9-1.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-imapsync-2.29.9-1.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-ipaccess-2.29.9-1.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-p3scan-2.29.9-1.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-quarantine-2.29.9-1.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-server-2.29.9-1.ns7.noarch.rpm x86_64 armhfp aarch64
• nethserver-mail-smarthost-2.29.9-1.ns7.noarch.rpm x86_64 armhfp aarch64