trusteddomainproject organization members team needs update

[Neustradamus]

Dear @trusteddomainproject team, @mskucherawy,

We are in 2025, the trusteddomainproject projects have never been updated since a long time:

• https://github.com/trusteddomainproject/OpenDMARC
• https://github.com/trusteddomainproject/OpenDKIM
• https://github.com/trusteddomainproject/OpenARC
• https://github.com/trusteddomainproject/ARC_Community_Sealers

It is needed to update the team for a new development.

There are several PRs:

• https://github.com/trusteddomainproject/OpenDMARC/pulls
• https://github.com/trusteddomainproject/OpenDKIM/pulls
• https://github.com/trusteddomainproject/OpenARC/pulls
• https://github.com/trusteddomainproject/ARC_Community_Sealers/pulls

There are several issues/tickets:

• https://github.com/trusteddomainproject/OpenDMARC/issues
• https://github.com/trusteddomainproject/OpenDKIM/issues
• https://github.com/trusteddomainproject/OpenARC/issues
• https://github.com/trusteddomainproject/ARC_Community_Sealers/issues

Who manage the domain name?

• http://www.trusteddomain.org/

Thanks in advance.

Linked to:

• trusteddomainproject organization members team needs update #291
• trusteddomainproject organization members team needs update OpenDKIM#256
• trusteddomainproject organization members team needs update OpenARC#190
• trusteddomainproject organization members team needs update ARC_Community_Sealers#12

[JulianAtkins]

There was someone from the organization, who posted in the postfix mailing list. He said that there are no developers maintaining these projects (did not specify why) and that he still had write access to the repositories but did not know how to do anything else.

[thegushi]

That would be me. I have interest in moving these projects forward, but the basic problems are:

• There are a number of patches in a number of individual OS repos, that are only tested against those operating systems and not always written in the same style as the existing code.

• Knowing how to set up testing infrastructure for this stuff means you have to know the intricacies of those OSes. (For example, to test on OpenBSD, you have to know why it needs you to set weird ENV vars to make autoconf work.)

• There's been a history of "works for me" patches that have broken stability in other ways. (And don't get me started about just letting Copilot or Claude do this)

• There are issues in two different places (sourceforge and github). There are a collection of patches in sourceforge and github.

• Every time you fix even one thing, people start clamoring "DEAD PROJECT PLEASE JUST SAY THAT".

• People ask for things that are only relevant to their own needs and don't help the project as a whole, i.e. "Can you also make this work on Alpine Linux or Arch Linux or FooBar Linux?" or "Can you make this work with the MUSL libraries" or "Can you make this work with this other openssl-alternative".

• The main developer of the project has some time to work on individual issues. OpenDMARC is easy enough to update, because it has virtually no cryptography in it. OpenDKIM is a harder problem. Linking against newer versions of OpenSSL, on many new OSes, that are randomly doing things like ripping out SHA1 "for their own reasons", is a lot harder.

If you can help, reach out. (github@gushi.org) Suggesting that the project just needs to be killed off, I'll just close the tickets.

[Neustradamus]

@thegushi: Thanks for your answer!

I have sent you an e-mail.

Can you add you in public here:

• https://github.com/orgs/trusteddomainproject/people

If you are not OWNER, please see with current OWNERS to have rights.

About PRs, it is important to communicate with authors.

About the website, who manage it?
Currently, it is unsecure.

Thanks in advance.

[Neustradamus]

@thegushi: Have you looked my previous comment?

[thegushi]

Yes, are you offering to help fix things?