On 27 Nov 2015 7:36 PM, Richard James Salts wrote:
>>>>>
>>>>> 1. Required initial free-form body part, this can use UTF-8
>>>>> without any need for EAI.
>>>>
>>>> Yes, part 1 is where I want the UTF-8 to go.
>>>>
>>>> I’ve not consulted the RFCs myself. Basically, I want the text after
>> Exim
>>>> shows the intended recipient address to be able to be any UTF-8
>> characters.
>>>
>>> This may well be a feature request, I don't know whether Exim
>>> supports this or not. As proof of concept (this is neither a
>>> sufficient nor implied reason to consider Postfix, just an
>>> example I happen to be familiar with):
>>>
>>
>> I think, yes, this is a feature request.
>>
>> src/deliver.c, at least, hard-codes US-ASCII as the charset for those
>> “fail” messages; the ability to customize those doesn’t seem to be in
>> evidence currently.
>>
>> It would, of course, make Exim that much friendlier to i18n contexts to
>>
>> have this!
>>
>
> You mean this? http://exim.org/exim-html-current/doc/html/spec_html/ch-customizing_bounce_and_warning_messages.html
Not quite … that’s dealing with just customizing the messages, not
specifying what the encoding of those messages is to be.
-FG
