Re: [exim-dev] [exim-cvs] cvs commit: exim/exim-doc/doc-docb…

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Phil Pennock
Datum:  
To: Tom Kistner
CC: exim-dev
Betreff: Re: [exim-dev] [exim-cvs] cvs commit: exim/exim-doc/doc-docbook spec.xfptexim/exim-doc/doc-txt ChangeLog experimental-spec.txt
On 2009-06-11 at 15:07 +0100, Tom Kistner wrote:
> tom         2009/06/11 15:07:57 BST

>
>   Modified files:
>     exim-doc/doc-docbook spec.xfpt 
>     exim-doc/doc-txt     ChangeLog experimental-spec.txt 
>   Log:
>   DKIM docs WIP


> Index: experimental-spec.txt
> ===================================================================


> -0. DKIM support


> -1. Yahoo DomainKeys support


Does this mean that DomainKeys support disappears with 4.70?

Since in 4.69, in practice it's DomainKeys or DKIM but not both when
signing outbound mail (DKIM silently ignored) what is the migration
strategy for sites currently using DomainKeys? Do they need to get DKIM
support built in 4.69 and just stop using DomainKeys?

The issue I'm wary of is remote sites which use reputation systems for
senders that track whether a domain uses DomainKeys and how reliably it
does so; if a domain stops DomainKeys usage without first ramping up
DKIM usage to establish a history of that, this might affect
deliverability to some of the larger email providers.

For me, I'm still using DomainKeys because of all the fuss over the
standardisation of signing-policy-in-DNS preventing a useful policy for
DKIM from being published. Ie, _domainkey.spodhuis.org exists and when
I last checked there wasn't an equivalent for DKIM;
_adsp._domainkey.spodhuis.org looks like it would be the current
mechanism, but who uses that?

Until there are signing policies in DNS for DKIM and those are used in
practice, can DomainKeys be dropped?

-Phil