<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Yahoo DomainKeys draft specification</title>
	<link>http://L.Bukys.org/2004/05/19/yahoo-domainkeys-draft-specification/</link>
	<description>security, policy and law, software development, and more</description>
	<pubDate>Fri, 21 Nov 2008 11:55:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>

	<item>
		<title>by: Liudvikas Bukys</title>
		<link>http://L.Bukys.org/2004/05/19/yahoo-domainkeys-draft-specification/#comment-44</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://L.Bukys.org/2004/05/19/yahoo-domainkeys-draft-specification/#comment-44</guid>
					<description>Sigh, yes.
MTAs can and do prepend (e.g. Received headers) and append (e.g. almost everything else).  DK could define a robust encapsulation method -- but isn't just reinventing S/MIME?  Or it could select a subset of headers to include (e.g. only From and Subject).  Although proposed standard RFC2476 does allow leeway in changing From, having this only occur for malformed From wouldn't be too bad.
</description>
		<content:encoded><![CDATA[	<p>Sigh, yes.
MTAs can and do prepend (e.g. Received headers) and append (e.g. almost everything else).  DK could define a robust encapsulation method &#8212; but isn&#8217;t just reinventing S/MIME?  Or it could select a subset of headers to include (e.g. only From and Subject).  Although proposed standard RFC2476 does allow leeway in changing From, having this only occur for malformed From wouldn&#8217;t be too bad.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
