My mail server is serving 4 domains for sending (even more for receiving). I have DKIM configured for the 4 sending domains.

A couple of years ago, before DKIM was implemented in Mercury, I added areplymod daemon from @Rolf Lindby and set the address for the auto-replies to get around the problem that gmail was requiring a non-empty from address in the envelope, using the the primary domain in the address.

Now, I'm seeing that auto-replies fail for all but the primary domain. I believe the problem is that DKIM is not applied to auto-replies. And with DMARC configured with SPF and DKIM, if the envelope header From address does not match the auto-reply From address, and the auto-reply is not DKIM signed, the auto-reply is rejected.

I haven't tried disabling Rolf's daemon, but before I do that, I thought I'd ask if anybody knows a solution for getting DKIM signing on auto-replies.

Tony

The beta test team has also reported this issue to me. After an initial inspection of the code, I can't see why it would be happening, but I am looking into it. Once I find the solution, I'll bring out a patch quickly.

Cheers!

-- David --

Hello David, Tony,

I am in the "same boat" as Tony, using Rolf's auto-reply daemon and planning to upgrade to the beta and implementing DKIM. As it will be in a few month time (winter) I just wanted to let you know that there is one more user with this auto-reply daemon.

Johannes

Just a quick note that I've worked out what's going on here, and should have a fix soon. It'll need a brief period in beta, then I'll release it as soon as we're sure it's working as intended.

Cheers!

-- David --

Hello David,

Thank you for your quick actions. Very much appreciated!

Hopefully the result will be positive, but I am sure it will. Waiting for the result.

Johannes

looking at the beta download page it still says April 2026. Just asking how far the progress is.

Johannes

This problem has been fixed and is in the final stages of testing at the moment.

I've also added support for automatic certificate reloading (no longer requires a restart), which will be useful to some of you, I suspect. Support for retrieving certificates from ACME clients is in progress, but I suspect I'll release the current state of the code as a kind of "hot-fix" for the DKIM issue, hopefully sometime in the next week.

Cheers!

-- David --