is DkimSigner development dead?

[DependableUser]

Does anyone know if it has this been abandoned?
Longstanding issue has not been fixed and some users don't get answers to their questions so I'm wondering...

TIA for any info

[PacsoT]

The 3.4.0 verison's relase notes declare that there is no real need for further updates, unless there is some new issue comes up.
So I think it's not dead. Its complete :)

[DependableUser]

I would consider it finished if this: #368 got fixed but I guess it is what it is.... :(

[Deckard99]

I wouldn't say it's complete, but as said above "it is what it is".
There are still problems with signing OOF or NDRs, there is still missing an option for Ed25519-SHA256 algorithm aso.

[rvanmill22]

Is this still valid for existing exchange 2019 - CU14 just installed - need to ensure support before using this. Still active dev on this?

[DependableUser]

Is this still valid for existing exchange 2019 - CU14 just installed - need to ensure support before using this. Still active dev on this?

I upgraded from CU13 to CU14 and it still works fine, the error keeps registering in the event viewer but it can be ignored

[BruceFeuillette]

I wouldn't say it's complete, but as said above "it is what it is". There are still problems with signing OOF or NDRs, there is still missing an option for Ed25519-SHA256 algorithm aso.

I agree, the NDR problem just came to the surface for us. And it's really annoying. I guess I'll go for a Postfix/Linux solution as a workaround.