Welcome to the mailbox user forum

New Topic

mailbox user forum Topic Problem E-mail: Setup

Category E-mail: Setup

Tags bug

You're failing GMail DKIM as "No valid DKIM" in Authentication-Results header

k234525 shared this problem ago

Published

Apparently in an attempt to address this https://userforum-en.mailbox.org/topic/2301-inconsistent-authentication-results-of-mailbox-servers-seems-potentially-risky you're now failing GMail/Google Mail via an "No Valid DKIM" line in Authentication-Results despite DKIM being present. Furthermore, there is no dkim=... entry at all in the Authentication-Results header anymore, only a dmarc=... entry. For a missing DKIM there should be dkim=none or similar. This seems like quite a mess. Also, it says "incoming_mbo" instead of a proper "something.mailbox.org" server name clients can trust.

I hope this can be fixed timely, it makes filtering malicious e-mail almost impossible based on this header.

The same problem 0

Replies (6)

k234525 ●

It would be nice if this didn't take weeks to fix. Do you have a beta program where such issues can be reported early?

Reply URL

Peter ●

Is this still happening?

Reply URL

k234525 ●

Sadly yes, I now forwarded an e-mail example to support@mailbox.org that is affected. Hopefully it will shed some light on what the problem is. Before the recent changes, the verification worked fine, so this is some new behavior of the mailbox servers that is suddenly causing trouble. Other senders than gmail also work fine.

URL

k234525 ●

DKIM has been broken for a month now...

Reply URL

5422682 ●

But just yesterday they won an award for security with a DKIM criterion!

URL

k234525 ●

It's still not working properly. Some forwarded e-mails in particular will fail when they shouldn't (and I don't mean the kind where the signed headers were modified), the dkim= header part is randomly missing, and there is no proper identifying hostname in the Authentication-Results header.

It used to work fine, but then they changed something in July 2025 ish.

URL

mailbox.org Support ●

Hi,

thank you very much for your feedback. You are right, we are still experiencing some issues with DKIM. We are very sorry, and we are working on a solution, but we still have to ask for a little more patience. We will of course keep you updated and write here as soon as we have fixed the issue.

With kind regards
Your mailbox.org team

URL

k234525 ●

Thank you for the acknowledgment. Until now I wasn't quite sure if it was recognized as a problem.

URL

k234525 ●

I've had some interactions where despite my multiple explanations, there seems to have been quite some confusion about what even the problem is, with some suggestions contradicting some information already exchanged before. I'm not sure why that is, perhaps I communicated it poorly.

But whatever causes this situation to be ongoing, at this point I think I might be forced to start looking for a different e-mail provider.

URL

Ginger Soap ●

Is this fixed by now?

Reply URL

k234525 ●

I received the last mail that seems to be broken this way on the 26th and haven't heard about any changes since, so my guess is that it hasn't.

URL

k234525 ●

As of 2025-10-30, this is still ongoing.

URL

k234525 ●

It seems like, there's now a more detailed reason given:

reject ("cannot verify 2 of 2 signatures: {[1] = sig:google.com:invalid dkim param: fh}")

It seems like, there's now a more detailed reason given:

reject ("cannot verify 2 of 2 signatures: {[1] = sig:google.com:invalid dkim param: fh}")

URL

Andreas Weiß ●

I've started a similar thread in the German forum. However, my problem has been ongoing since June 2025.

https://userforum.mailbox.org/topic/12271-mails-mit-eigener-domain-sehr-haufig-ohne-dkim-signatur

Reply URL

k234525 ●

The problem here concerns purely incoming mail so I'm not sure how much it is related.

URL

Andreas Weiß ●

Oh, sorry, then there is probable no dependency between the two problems.

Reply URL