deiva shanmugam wrote:
> When the headers being signed using DKIM technology are in format:
> *Header field name<sp>:header field value*
>
> Gmail is showing hardfail as its verification status and AOL is showing
> DKIM:none as its status.
>
> Is, space between header field name and colon is not legal?
Well, the WSP between header field name and a colon used to be allowed
by RFC 822, but is treated as obsolete syntax by RFC2822 and RFC 5322,
which means that it should still be accepted, but not generated.
The Mail::DKIM seems to be in error, it does not want to sign such
header fields. If it happens to one of the DKIM-required header
fields i.e. a 'From' header field, the resulting signature does
not list the 'from' in its 'h' tag, which could be treated as a
DKIM requirement violation. In fact the dkim-milter reports:
Authentication-Results: example.com; dkim=permerror
(verification error: header list missing required entries) [...]
Mark
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
dkim-milter-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
