> If we are to stand a chance of defeating spammers, then we have to > make DKIM > easier to install and configure so mere mortals can install and use > it, and > encourage adoption. I'm sure many would like to see dkim-filter available > in rpm for various distros. Hey Andy, As an experienced sysadmin, I'm sure you're aware that the developers of a given software project rarely cater directly to a specific distribution. This software is used by many folks on many different platforms. There's heavy concentration on making sure that things are cross-platform compatible as opposed to "installable in 30 minutes on Fedora 7." After all, it's generally up to the folks who make the distribution to configure packages for their distribution, not up to the developers of the software itself.
I agree that an RPM would be nice. All it takes is a spec file and a little time, and since you've already solved the majority of the distribution-specific problems, you might be primed and ready to construct an RPM that saves the next person a lot of time. You can also lobby the developers and maintainers of Fedora to include your package in the extras/contrib yum repository for distribution to others. The man page thing can be fixed by adding define(`confMANROOT', `/usr/share/man/man') to the site.config.m4... this will put the manuals in the right place on a Fedora system (unless they've moved them... I can't keep up with a F-release every 6 months) at the ./Build install step. As opposed to relying on a mailing list email from gmail to check verification (which is broken for any number of reasons), try sending email to the sa-test --at-- sendmail.net autoresponder. It will both verify the mail you send it, and properly sign a response that you can verify when it comes back. There are also other DKIM autoresponders available if you google around a little. As far as the crash, it might be helpful to get versions of openssl and openssl-devel on your system, ensure that no stray, random versions of openssl headers exist. Being able to successfully compile, but not successfully run a piece of software can sometimes be caused by running against different versions of shared libraries than their headers, so it's a good thing to check, IMO. Output of ldd /usr/bin/dkim-filter and /usr/bin/dkim-filter -V might also be helpful. I don't run any x86_64, but I have not had stability trouble with dkim-filter on i386. I will let the other, more skilled programmers on the list provide additional suggestions, like providing gdb or strace output... which I don't know are helpful yet. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
