Issue Outlook and Gmail block my clients emails! DKIM too long

[Zalvatore Dela]

Hi, I've been struggling especially with emails sent to Outlook...they get bounced right away!
I have enabled DKIM, SPF and DMARC. But the validation still reports errors.
I'm using plesk onyx on rocky linux. Here the report.
PLEASE HELP!

This message is an automatic response from Port25's authentication verifier
service at verifier.port25.com. The service allows email senders to perform
a simple check of various sender authentication mechanisms. It is provided
free of charge, in the hope that it is useful to the email community. While
it is not officially supported, we welcome any feedback you may have at
<[email protected]>.

Thank you for using the verifier,

The Port25 Solutions, Inc. team

==========================================================
Summary of Results
==========================================================
SPF check: pass
"iprev" check: fail
DKIM check: permerror

==========================================================
Details:
==========================================================

HELO hostname: contat.eu
Source IP: 195.231.22.245
mail-from: [email protected]

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result: pass
ID(s) verified: [email protected]

DNS record(s):
contat.eu. 300 IN TXT "google-site-verification=aJkr4J1CxJ_-9iHXtIE3b7yvU3tVgBYOYwiH-JWQOlU"
contat.eu. 300 IN TXT "v=spf1 +a +mx +a:contat.cloud -all"
contat.eu. 300 IN A 195.231.22.245


----------------------------------------------------------
"iprev" check details:
----------------------------------------------------------
Result: fail (no matching DNS records found)
ID(s) verified: policy.iprev=195.231.22.245

DNS record(s):
245.22.231.195.in-addr.arpa. 300 IN PTR host245-22-231-195.serverdedicati.aruba.it.
host245-22-231-195.serverdedicati.aruba.it. A (NXDOMAIN)


----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result: permerror (invalid key: error reading public key: 139927431399168:error:0D07207B:asn1 encoding routines:ASN1_get_object:header too long:crypto/asn1/asn1_lib.c:101:;139927431399168:error:0D068066:asn1 encoding routines:asn1_check_tlen:bad object header:crypto/asn1/tasn_dec.c:1118:;139927431399168:error:0D07803A:asn1 encoding routines:asn1_item_embed_d2i:nested asn1 error:crypto/asn1/tasn_dec.c:290:Type=X509_PUBKEY
ID(s) verified:

Canonicalized Headers:
to:[email protected]'0D''0A'
from:Contat'20'Digital'20'Agency'20'<[email protected]>'0D''0A'
subject:Test'20'dkim'20'sign'0D''0A'
dkim-signature:v=1;'20'a=rsa-sha256;'20'c=relaxed/relaxed;'20'd=contat.eu;'20's=default;'20't=1659644106;'20'bh=v71q/geWA20/E5J3oTyerQmA+v7dj2uyasvnbMn2s00=;'20'h=To:From:Subject;'20'b=

Canonicalized Body:
Test'20'mail'20'test'20'mail'20'test'20'mail'20'test'20'mail'20'test'20'mail'20'test'20'mail'20'test'20'mail'0D''0A'
test'20'mail'20'test'20'mail'0D''0A'


DNS record(s):
default._domainkey.contat.eu. 300 IN TXT "v=DKIM1; p=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDQBBggPO9uk2Exnnw6ZeC8txfj3+1zK98QKBog/jjhkEUYphOCk4wgO9vJjdD66eFqu6eS4lXSQbdKx6al50M422w36TtOTzYAm7fD+uVo4XKxOajgGjB0BETMKTesfSxqRkRgV+VAESxBo0JIMjtTfBINGnEeYjXZtNbewJGJUwIDAQAB;"

NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions. If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.

==============================================================
Explanation of the possible results (based on RFCs 7601, 7208)
==============================================================


DKIM Results
============

none: The message was not signed.

pass: The message was signed, the signature or signatures were
acceptable to the ADMD, and the signature(s) passed verification
tests.

fail: The message was signed and the signature or signatures were
acceptable to the ADMD, but they failed the verification test(s).

policy: The message was signed, but some aspect of the signature or
signatures was not acceptable to the ADMD.

neutral: The message was signed, but the signature or signatures
contained syntax errors or were not otherwise able to be
processed. This result is also used for other failures not
covered elsewhere in this list.

temperror: The message could not be verified due to some error that
is likely transient in nature, such as a temporary inability to
retrieve a public key. A later attempt may produce a final
result.

permerror: The message could not be verified due to some error that
is unrecoverable, such as a required header field being absent. A
later attempt is unlikely to produce a final result.


SPF Results
===========

none: Either (a) no syntactically valid DNS domain name was extracted from
the SMTP session that could be used as the one to be authorized, or
(b) no SPF records were retrieved from the DNS.

neutral: The ADMD has explicitly stated that it is not asserting whether
the IP address is authorized.

pass: An explicit statement that the client is authorized to inject mail
with the given identity.

fail: An explicit statement that the client is not authorized to use the
domain in the given identity.

softfail: A weak statement by the publishing ADMD that the host is probably
not authorized. It has not published a stronger, more definitive policy
that results in a "fail".

temperror: The SPF verifier encountered a transient (generally DNS) error
while performing the check. A later retry may succeed without further
DNS operator action.

permerror: The domain's published records could not be correctly interpreted.
This signals an error condition that definitely requires DNS operator
intervention to be resolved.


"iprev" Results
===============

pass: The DNS evaluation succeeded, i.e., the "reverse" and
"forward" lookup results were returned and were in agreement.

fail: The DNS evaluation failed. In particular, the "reverse" and
"forward" lookups each produced results, but they were not in
agreement, or the "forward" query completed but produced no
result, e.g., a DNS RCODE of 3, commonly known as NXDOMAIN, or an
RCODE of 0 (NOERROR) in a reply containing no answers, was
returned.

temperror: The DNS evaluation could not be completed due to some
error that is likely transient in nature, such as a temporary DNS
error, e.g., a DNS RCODE of 2, commonly known as SERVFAIL, or
other error condition resulted. A later attempt may produce a
final result.

permerror: The DNS evaluation could not be completed because no PTR
data are published for the connecting IP address, e.g., a DNS
RCODE of 3, commonly known as NXDOMAIN, or an RCODE of 0 (NOERROR)
in a reply containing no answers, was returned. This prevented
completion of the evaluation. A later attempt is unlikely to
produce a final result.




==========================================================
Original Email
==========================================================

Return-Path: <[email protected]>
Received: from contat.eu (195.231.22.245) by verifier.port25.com id htgkc82p2tog for <[email protected]>; Thu, 4 Aug 2022 20:15:00 +0000 (envelope-from <[email protected]>)
Authentication-Results: verifier.port25.com; spf=pass [email protected];
iprev=fail reason="no matching DNS records found" policy.iprev=195.231.22.245;
dkim=permerror reason="invalid key: error reading public key: 139927431399168:error:0D07207B:asn1 encoding routines:ASN1_get_object:header too long:crypto/asn1/asn1_lib.c:101:;139927431399168:error:0D068066:asn1 encoding routines:asn1_check_tlen:bad object header:crypto/asn1/tasn_dec.c:1118:;139927431399168:error:0D07803A:asn1 encoding routines:asn1_item_embed_d2i:nested asn1 error:crypto/asn1/tasn_dec.c:290:Type=X509_PUBKEY;"
Received: from [192.168.1.88] (host-212-171-72-122.pool212171.interbusiness.it [212.171.72.122])
by contat.cloud (Postfix) with ESMTPSA id 6133710090974
for <[email protected]>; Thu, 4 Aug 2022 20:15:06 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=contat.eu;
s=default; t=1659644106;
bh=v71q/geWA20/E5J3oTyerQmA+v7dj2uyasvnbMn2s00=; h=To:From:Subject;
b=eD8klaFi1ZRu39ZDTMdJZ2u4EeBzPvi9xnxjY095K6RPHf4/SJ0bNZ8npk8k+IzPC
XF4ul8LXySbSMIesBRYyWu5lszc+1CjQUOkJMRDWo0qBJLxCZeAf8cORyG0etGSl4B
hkKAb3cpPAfrxLaFrhztO3la4yaPuSY43BJ3a/eY=
Received-SPF: pass (contat.cloud: connection is authenticated)
Message-ID: <[email protected]>
Date: Thu, 4 Aug 2022 22:14:55 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.11.0
To: [email protected]
From: Contat Digital Agency <[email protected]>
Subject: Test dkim sign
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-PPP-Message-ID: <[email protected]>
X-PPP-Vhost: contat.eu

Test mail test mail test mail test mail test mail test mail test mail
test mail test mail

 

[Zalvatore Dela]

Here the config on Plesk

 

[Zalvatore Dela]

I tried removing the old domainkey record manually and then disabling and re-enabling DKIM spam protection system to sign outgoing email messages
the only thing changes was the key, the response is still an error!

 

[Zalvatore Dela]

Wondering if it's only me having this problem... ?

 

[Zalvatore Dela]

UP

 

[Zalvatore Dela]

UPDATE. Removing the ";" at the end of the key seems to pass the test on
[email protected] but NOT on https://mxtoolbox.com/deliverability/

 

[Zalvatore Dela]

UP yet emails are not being accepted what is the right conf?? Its just unbelievable...

 

[Maarten.]

Try some other tools, like:
- DKIM, SPF, and Spam Assassin Validator - dkimvalidator.com
- Newsletters spam test by mail-tester.com

 

[Zalvatore Dela]

Passed both test yet outlook and icloud boucing right back. Will look into blacklisting