> -----Original Message-----
> From: exim-users-bounces+msk=cloudmark.com@??? [mailto:exim-users-bounces+msk=cloudmark.com@exim.org] On Behalf Of Pedro Mansilla
> Sent: Sunday, September 11, 2011 1:59 PM
> To: exim-users@???
> Subject: Re: [exim] Is DomainsKeys (DK not DKIM) disabled since v4.70-4.71?
>
> Hi Phil, thanks for the answers.
>
> Ok, so lets say that I need both. What was the last version that supported
> both as Experimental. I mean the SRC. And what should I do or need to
> compile it and have both working and signing out messages.
>
> Is any other way to have DK, DKIM and SPF signing out messages. Something
> like DKIMProxy which I recently saw?
DKIMproxy will sign or verify mail, but only with DKIM. It doesn't do DomainKeys.
As others have said, DomainKeys is obsolete. In fact the only reason any of the big mailbox providers are still checking it is because there's only one big sending company still using it, and that's only because it takes a long time to change over a large infrastructure. All of them have said they will be dropping it as soon as possible. So, the requirement to sign with DomainKeys doesn't really provide any value. Legislation that says so probably needs to be changed. I realize that doesn't help you much, but that is why you're not likely to find much help retrofitting exim to meet this requirement.
I think you also mentioned Sender-ID, which by most accounts is also largely dead.
You don't "sign" with SPF, and so you don't need any software changes in exim to support it outbound. I believe it already has inbound support.
-MSK
