----Original Message----
From: Tom Kistner [
mailto:tom@duncanthrax.net]
Sent: Tuesday, June 30, 2009 3:27 AM
To: Rick Cooper
Cc: Exim Users
Subject: Re: [exim] DKIM and DomainKeys
> Rick Cooper wrote:
>
>> Is there any work being done, or a patch available, to allow signing both
>> DKIM and DomainKeys without sending a message through exim twice?
>
> The situation right now is a bit confusing.
>
> I had added concurrent Domainkeys (via libdomainkeys) and DKIM (via
> libdkim) signing support in CVS after the 4.69 release. That code was
> never released, but some people run a snapshot of it.
>
> DKIM verification support was oddly implemented, and the library I used
> had some limitations at that time. It also brought in additional
> build-time dependencies (lstdc++, openssl).
>
> So I wrote my own DKIM implementation [1] which is dependency-free and
> portable even to non-posix platforms like Windows. Similar to how pcre
> was handled, a copy is included in the Exim source, so Exim can have
> DKIM support by default on its supported platforms (I didn't try them
> all of course ...).
>
> The code is finished and in CVS. What is missing is the documentation. I
> hope to finish it next week. Domainkeys support has been dropped. I
> don't really feel like bringing it back, since I now consider it to be a
> dead proprietary technology. If you really need to run DKIM/Domainkeys
> concurrently with Exim, your only option is to pull a CVS snapshot by
> date of April last year, or use the tarball I posted back then [2].
>
That explains why it appeared that domainkeys support was missing, even
though the respondent had stated both worked in cvs. I suppose I will just
move to just dkim but not all providers have done so and I was hoping to be
able to please all.
BTW: the current exim-doc in cvs appears to be broken and won't build. It
appears to be broken in the section you added a couple of weeks ago
referencing the DKIM support. There are a bunch of errors all pretty much
like
** Error: missing closing flag %&
Processing macro vitem
Detected near line 34296 of spec.xfpt
And since spec.xml cannot be built neither can the rest. The filter
documentation builds fine. I would try and fix it but I no nothing of the
xfpt syntax.
Rick
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
