An SPF rejection message string is sent as (part of) the body of a message.
AFAIK, the RFC2047 mechanisms apply only to message headers. I can't see that
MUAs are required to decode body text which has been encoded in this way.
My proposal conformas to RFC2045.
And, just to clarify who is reading this message, it's people in the same
(sending) domain as you, so in most cases I would think the choice of language
would be clear.
Chris
----- Original Message -----
From: "william(at)elan.net" <william(_at_)elan(_dot_)net>
To: <spf-discuss(_at_)v2(_dot_)listbox(_dot_)com>
Sent: Monday, July 26, 2004 7:47 AM
Subject: Re: [spf-discuss] Support for Internationalized Explanations
Personally don't have much motivations to see internatlized explanations
(you're sending explanation to somebody else, who you dont know, nor do
you know what language they speek, better pick closest to semi-international
language there is in the world>.
But if there is serious interest to do it, I recommend doing it the same
way its been done to support multiple charsets for Subject and From
and other headers. For more info see http://www.ietf.org/rfc/rfc2047.txt
--
William Leibzon
Elan Networks
william(_at_)elan(_dot_)net
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Send us money! http://spf.pobox.com/donations.html
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com