kirk at icapsolutions
Jun 3, 2011, 7:37 AM
Post #10 of 13
FYI, I've implemented the all perl solution as provided here:
Very simple setup, nicely packaged, but it's causing the server to work
entirely too hard, somewhere in the magnitude of about 10X as seen by
the CPU usage, too expensive.
I tried the all C solution from here:
This most likely would solve the CPU issues seeing as Perl is a CPU hog,
but it didn't compile.
Any chance of any other all C or sh solution that would improve, perhaps
not relying on firing up ans instance of Perl for each and every
On 6/3/2011 12:55 AM, Erwin Hoffmann wrote:
> Hi John,
> On 2 Jun 2011 16:22:58 -0000
> "John Levine"<johnl [at] iecc> wrote:
>> I've been doing my DKIM signing with a perl wrapper around
>> qmail-queue. It works well for me, was short and easy to code, and it
>> has the advantage that applications that are inclined to be helpful
>> (list managers and web mail) can pass environment variables to tell
>> the signer what identity to use in the signature.
> This sounds to fit with SMTP authentication as well.
> Though I was initially not inclined to include DKIM in my Spamcontrol patch, however I see a growing need to support DKIM as well (SPF is already on my development list).
> If you dont't mind sending me your code, I could have a look at it and perhaps provide a combined solution.
>> If people are interested I can package it up. I also have a little
>> script to generate signing keys and tinydns verification keys that
>> rotate each month. And as an evil hack, I can use wildcard selectors
>> so each message has a different selector and I can do traffic analysis
>> on the DNS queries.
>> John Levine, johnl [at] iecc, Primary Perpetrator of "The Internet for Dummies",
>> Please consider the environment before reading this e-mail. http://jl.ly