J.D. Falk wrote:
> Dave CROCKER wrote:
>
>
>> Won't the Overview, as well as the Deployment, documents help?
>>
>
> I hope so.
>
>
Hmm. Overview's been around a long time...
Can you list off some bullets of what you think is missing from an ops
standpoint? A DKIM cookbook could be helpf
Dave CROCKER wrote:
> Won't the Overview, as well as the Deployment, documents help?
I hope so.
--
J.D. Falk
Return Path Inc
http://www.returnpath.net/
___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html
J.D. Falk wrote:
> Steve Atkins wrote:
>
>> but for whom the dry
>> RFC-style specification isn't as helpful as a more HOWTO set
>> of docs.
>
> That's been a big problem when talking to operationally-minded folks --
> which includes a very large percentage of likely implementers.
...
Steve Atkins wrote:
> It's a work in progress to provide operational documentation for
> typical senders who want to use DKIM, but for whom the dry
> RFC-style specification isn't as helpful as a more HOWTO set
> of docs.
That's been a big problem when talking to operationally-minded folks --
wh
On Mar 11, 2009, at 2:48 PM, Franck Martin wrote:
> http://dkimcore.org/dkimcore.pdf
>
> I just stumbled on this document, this seems strange to me. What do
> you think?
It's a work in progress to provide operational documentation for
typical senders who want to use DKIM, but for whom the dry
Suresh Ramasubramanian wrote:
> On Thu, Mar 12, 2009 at 9:17 AM, SM wrote:
>> At 15:24 11-03-2009, HLS wrote:
>>> This domain has no content, totally blind. I would not trust this
>>> dkimcore . org until they reveal themselves.
>>>
>> The person who wrote that document revealed himself/herself.
On Thu, Mar 12, 2009 at 9:17 AM, SM wrote:
> At 15:24 11-03-2009, HLS wrote:
>>This domain has no content, totally blind. I would not trust this
>>dkimcore . org until they reveal themselves.
>
> The person who wrote that document revealed himself/herself. :-)
And if people missed that, then I a
At 15:24 11-03-2009, HLS wrote:
>This domain has no content, totally blind. I would not trust this
>dkimcore . org until they reveal themselves.
The person who wrote that document revealed himself/herself. :-)
Regards,
-sm
___
NOTE WELL: This list o
Well, anonymous domains and documents should not be trusted, especially
since PDF has recently suffered with Zero-Day PDF Exploit.
Google: PDF Zero Day Exploit
Its fresh out of the press.
This domain has no content, totally blind. I would not trust this dkimcore
. org until they reveal
http://dkimcore.org/dkimcore.pdf
I just stumbled on this document, this seems strange to me. What do you think?
I find that adding a hash on the body and putting it in the DKIM record will
certainly break the DKIM spec, as it stops mailing lists to forward a DKIM
email and add a footer to the
10 matches
Mail list logo
