C) I can sell the ability to do 3rd party DKIM signing for those companies
who are described in A)
Oh, OK, so what we need is better DNS provisioning tools. Problem solved,
as far as the IETF is concerned.
R's,
John
________________________________________
From: ietf-dkim-bounces(_at_)mipassoc(_dot_)org
[ietf-dkim-bounces(_at_)mipassoc(_dot_)org] On Behalf Of John Levine
[johnl(_at_)iecc(_dot_)com]
Sent: Monday, October 05, 2009 8:38 PM
To: ietf-dkim(_at_)mipassoc(_dot_)org
Cc: MHammer(_at_)ag(_dot_)com
Subject: [ietf-dkim] The mystery of third party signatures
In light of the comments by Bill Oxley and my belief that the ability of
a domain to designate signing by a specified 3rd party is useful, ...
It would really be helpful if you two could explain WHY you think it's
useful. Given the way that DKIM works, there's only two possible
benefits from third party signatures. Say we want to have isp.com
signing for its customer a.com:
A) a.com sends its mail through isp.com's system, a.com is unable to
sign mail before it's relayed to the smarthost, and it's too hard for
isp.com to apply an a.com signature
B) Nobody's heard of a.com, so it wants to benefit from the reputation
of isp.com.
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html