I'm not convinced there is sufficient installed base that
should preempt making DKIM work right, the "first time."
What sort of deployed base would you consider "sufficient"? Speaking for
myself alone I've had many tens of thousands of downloads (and I assume
installs) of my software since DK/DKIM support was added. For me, that's
significant and I'm nothing compared to some of the other vendors interested
in this topic.
So early adopters, who well knew in advance that the value
of this work had no meaningful value with by-far a
non-compliant world, was incomplete and/or was plagued
with serious security issues, and only added this stuff for the
most part for marketing reasons,
I'd be careful in making assumptions like that. The last time I checked,
you weren't part of my decision making process (maybe you are for others
here). Speaking for myself, I added DK and DKIM for the same reason I added
SPF et al - because I care about the future of email which is under threat
today (and my customers do too).
--
Arvel
_______________________________________________
ietf-dkim mailing list
http://dkim.org