(Speaking with my Trusted Domain Project hat on). Yes, we'll take help.
I have commit access to all the Github repos, and am trying to push out a new release of OpenDKIM. I've been meaning to do this for months, but life and family stuff has been getting in the way. Here are the things I'd really like to focus on: * Making it work with a more current autoconf (we already did this for OpenDMARC) * Making it build cleanly with modern openSSLs. * Making it support the latest dkim key types (the version you can build from "devel" already does this.) * Defining a set of "what the current state of OSes we test this thing are". What I don't have the access to fix is our mailing lists, but I'm trying to get that (or at least get a list of the members and fork them off). Rather than drag this thread on *far* too long, I'd strongly suggest starting this discussion elsewhere, and this mailing list may not be the place. The chicken-and-egg problem is that there are a bunch of linuxes that I don't normally use that someone always insists are important. A lot of the submitted patches are "works for me" but break things on other platforms. And there's a bunch of stuff that, honestly, just needs to be ripped the hell out (like the GnuTLS support). If people want to get together on some chat platform and bang things out, I'd love to work with anyone who can. -Dan > On Dec 27, 2022, at 16:59, Peter <pe...@pajamian.dhs.org> wrote: > > On 28/12/22 12:12, raf wrote: >> Actually, it's been nearly five years since the last >> commit. But dead is a strong word. I expect there's >> still a lot of people using it. And there are 21 pull >> requests. I've emailed the trusted domain project to >> ask if it's dead, and if they'd accept help. If not, a >> fork might be a good idea. > > Hopefully something comes of this. Opendkim is indeed highly used throughout > the email community in both individual and commercial landscapes. It > deserves to be well maintained. > > > Peter
