Hey there all,

I am one of the people who has maintainer access to OpenDKIM and OpenDMARC.  I 
use both regularly, but I’m also a novice as a C-coder.  (Sysadmin, not 
developer).  As mentioned in another thread, I don’t have access to the web 
hosting stuff or the list management stuff, though I’m tempted to just put up a 
temp site on AWS and ask the person who DOES have access to put in an HTTP 
redirect for both of those.

This is not my day job.  My day job is in DNS operations, and it can be 
insanely busy, but also has lulls.  I’ve also had a family situation that 
derails me at times.  Without breaking confidences or saying too much, brains 
suck sometimes.  (If you know, you know).

=====

Anyway,

Here’s a list of the things I’m trying to do, soonish:

1) Get the current “develop” branch of OpenDKIM cut into a release branch that 
includes recent enough SSL that it works on recent version, works with a modern 
autoconf, and works with the key types people are presently using.

2) Get some of the critical patches that are being used in some of the mainline 
OSes into base.

THIS IS HARD.  People jump in and say “Wait, I use GNUTLS, so I need that 
too!”.  People say “Wait, this ancient solaris box I have in the corner running 
mail still uses openSSL 0.9.6, don’t break it on me!”.  People complain about 
the lack of progress which honestly, doesn’t help.  I know.

This is also hard because there’s been a history of community patches breaking 
things on some other OS, or causing vague stability issues.

3) Get testing infrastructure spun up (on AWS or local VMware or somewhre that 
I can spin up for more OSes).  Running unit tests on Slackware (via something 
like Jenkins, or manually) is not as simple as it sounds.

As an example, someone posts a vague bug that says “this breaks for me on 
slackware 15”.  Well, to respond to that, I need to replicate the problem on a 
Slackware 15 box.  Slackware is NOT a friendly OS to just install and get 
running”.  Same for OpenBSD.  Same for Arch Linux.  Same for Alpine Linux.  
Same for….etc.  

Each OS is a special snowflake with regard to how to get a BASE system able to 
configure a network stack and services without the system installing everything 
from X to Cups, maybe some firewall rules so we’re not running an 
open-to-the-world thing, install enough packages to build and keep up to date, 
and get cron running.

I don’t think this project is unsalvageable, and I feel like forking it would 
do more harm than good.  I want something better out the door, too.

I may re-post this to mailop, but if you’re the kind of person that feels able 
to help with some of this, I’ll get (pending boss permission) a new mailing 
list spun up on dayjob’s existing infra that we can use to get going TODAY.  
Please contact me privately.



_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

Reply via email to