On Jan 19, 2006, at 11:10 PM, Graham Murray wrote:
Douglas Otis <dotis(_at_)mail-abuse(_dot_)org> writes:
Those who are hoping what _may_ be visible to the recipient is
being checked will not want conformance based upon any other
header. Of course, what is visible remains within the control of
the sender,
Surely not. What is visible is controlled by the recipient and the
recipients mailer software. For example, with the mailer I use I
can (and have) configure it to show or hide whichever headers I
choose and can also (with a single button press) display all the
headers. I admit that not all mailer software makes it that easy,
but the mailer software used is under the control of the recipient
not the sender.
What is displayed is not really under the control of the recipient.
The recipient may control which fields are displayed, such as the
display-name or the display-name and the email-address, but the
sender is still has a large number of tools at their disposal to
control what is seen by the recipient in either case. There are
encoding methods defined by the native OS that are sometimes used,
there is HTML encodings that may be recognized, there is RFC2047 that
offers two methods of encoding where character-repertoires can even
change. What appears as normal syntax may not be seen as syntax by
the email-application. The sender can often pick characters of any
language including ideograms, and glyphs. There is also RFC3490,
RFC3491, and RFC3492 that introduce the use of ACE labels within the
domain name. The email-application must then choose to display the
ACE label or the characters selected by the ACE label. A difficult
choice where neither are really acceptable.
-Doug
_______________________________________________
ietf-dkim mailing list
http://dkim.org