How about A-R dkim-adsp's "header.from" value?

From: Alessandro Vesely <vesely_at_tana.it>
Date: Tue, 06 Jul 2010 20:16:03 +0200

Hi all,
the specs seem quite confusing about that field. Does it actually
/have/ to be there, or is it optional? Since A-R fields are not meant
to be shown to end users, that question is really about what do we
expect some downstream filter may do with such value.

In case the header.from value is needed, it apparently makes little
sense to strip comments but leave the display name in place, since
they can be used for the same purpose. Is that a "bug" in the ADSP
spec? A "header.from" propspec appears in RFC 5451 for domainkeys,
and in pre-rfc5451 drafts for dkim-adsp, and in both cases it is an
easily parsable value...

IMHO, for generic filtering, a "header.domain" would be the only
required datum for decisions about signatures being or being not
author domain ones, and I'd be tempted to use "x-header.domain". Is
anything planned for opendkim's filter, about this?
Received on Tue Jul 06 2010 - 18:16:14 PST