Hetzner PTR Record Invalid

[matix131997]

I also confirm with myself the problem with DKIM and DMARC, which test says that “from” does not match the domain.

I did a test on the site: https://unspam.email/results/uPOw0MP1f2

[matix131997]

I did a comparison between the e-mail that was sent earlier, before version 8.2.0, and now.

Before version 8.2.0

After 8.2.0

[robi]

Can someone test toggling the DKIM setup to see if 8.2 can actually set it?
Or a new sub.domain.. might help narrow it down

[matix131997]

I had a domain that I bought accidentally with the wrong name.

Old Domain:

New Domain:

Half of the settings are gone.

Records in DNS:

[robi]

Did you set up and enable email for the new domain?

EDIT:

[matix131997]

@robi Yes

EDIT: F***, I forgot about that

[matix131997]

I enabled email. I sent email from that domain and still the same as above. And the records are like this after the launch.

[robi]

Records are fine, does the Cloudron status think they're fine?

Does the external test think the records match now?

How are the mail headers?

Let's not miss any testing steps after making changes..

[d19dotca]

The Cloudron status shows everything green in my instance. The DNS records are perfectly fine. The issue is the Haraka SMTP service in Cloudron seems to no longer be signing the messages properly so they are missing DKIM signatures.

[matix131997]

@robi Yes, all points in the status are in green. Message headers the same as above - post #15

[d19dotca]

@nebulon / @girish , I think unfortunately this is coming down to a defect in 8.2.x where the DKIM signatures are not being used to sign outgoing messages.

I'm thinking we will need a patch for that as soon as possible, please as it's having a big impact in connecting to certain mail providers (seems to mostly be Google at the moment but I'm sure others are affected to a degree too). In the meantime, I may need to switch to a different SMTP server / relay service temporarily.

If there's anything I can do to help, please let me know. I can offer SSH connection into my server if you require it too.

[andreasdueren]

@d19dotca said in Hetzner PTR Record Invalid:

@nebulon / @girish , I think unfortunately this is coming down to a defect in 8.2.x where the DKIM signatures are not being used to sign outgoing messages.

I'm thinking we will need a patch for that as soon as possible, please as it's having a big impact in connecting to certain mail providers (seems to mostly be Google at the moment but I'm sure others are affected to a degree too). In the meantime, I may need to switch to a different SMTP server / relay service temporarily.

If there's anything I can do to help, please let me know. I can offer SSH connection into my server if you require it too.

Of THAT could be the case that I'm currently getting lots of failing DKIM reports

[girish]

There is indeed a regression with DKIM signing. This is fixed now. Will get a patch release out asap.

[Kubernetes]

@girish Great, thanks and happy new year !

[d19dotca]

Hi @girish , any chance that the fix could be released today or tomorrow for those of us on 8.2.x?

Also I’m sure you already have this being tracked for the future but I wanted to at least write down my suggestion: I think if possible it may be a great time to add some more automated test cases for the email functionality in order to make sure the DKIM signature exists in messages as an example.

[girish]

@d19dotca 8.2.2 is out now and should fix the crash and the DKIM issue. The crash issue is only mildly tested since upstream has not merged it yet, but maybe you can check if that works fine?

[avatar1024]

@girish said in Hetzner PTR Record Invalid:

@d19dotca 8.2.2 is out now and should fix the crash and the DKIM issue. The crash issue is only mildly tested since upstream has not merged it yet, but maybe you can check if that works fine?

It works indeed thank you for the speedy fix!

[Kubernetes]

@girish Great work, thank you very much for the quick fix and release. I just updated and tested and the crash doesn't show up again and DKIM is also working.

Always glad to post real defects

[d19dotca]

Confirmed, it seems to be much better now. Thank you so much for the quick turnaround on that! Great job!

https://unspam.email/results/6edDuKodjB