On 2015-11-27, Felipe Gasper <felipe@???> wrote:
> On 27 Nov 2015 6:05 AM, Jasen Betts wrote:
>> On 2015-11-26, Felipe Gasper <felipe@???> wrote:
>>> Hi all,
>>>
>>> When I do:
>>>
>>> fail text "$home:/Nööö!!!"
>>>
>>> … I get a fail message with:
>>>
>>> /home/mortal:/N\303\266\303\266\303\266!!!
>>>
>>> This (with US-ASCII encoding) appears to be hard-coded into
>>> src/deliver.c … is there any motion in the direction of being able to
>>> specify an encoding for fail messages?
>>
>> As far as I understandthe rules of SMTP:
>>
>> The only other charset allowed is UTF8 and that only if the HOST
>> advertises "SMTPUTF8" in in response to "EHLO" _and_ the client says
>> "SMTPUTF8" after the <address> part of the SMTP "MAIL FROM" command.
>>
>> SMTPUTF8 support in exim is still considered experimental, but if building
>> with EXPERIMENTAL_INTERNATIONAL enabled does not allow UTF8 in
>> responses I would consider that a bug. (not that I have any authority)
>>
>
> But why is this relevant for the message body?
>
> The argument to “fail text” is put into the message body, not the
> headers … ?
Oops! nothing whatoever.
I had the mistaken idea that system filters ran before exim accepts
the message, but they don't.
--
\_(ツ)_
