Florian Weimer wrote:
no charset is defined for the explanation string
There's also no kind of language handshake.
It's used in the SMTP error message (reject) and integrated
into a bounce message by a 3rd party (the client MTA).
There's also no kind of language handshake.
Any Accept-Language negotiation would be a part of HTTP if
the exp= explanation is an URL (or if it contains an URL).
These days, this is unacceptable for a message which should
be presented to end users.
For SMTP error messages "i-default" is better than guesswork.
What if a Chinese MTA talks to a Korean server with a German
gmx.de MAIL FROM used by an employee of the Mongolian embassy ?
The bounce is sent by the Chinese MTA to the gmx.de address.
Bye, Frank