Re: [exim] Subject / Topic (T=) encoding in exim mainlog

Top Page
Delete this message
Reply to this message
Author: Jeremy Harris
Date:  
To: exim-users
Subject: Re: [exim] Subject / Topic (T=) encoding in exim mainlog
On 15/11/17 14:51, Gryzli Bugbear via Exim-users wrote:
> Hello group !
>
> I'm trying to find what is the encoding that exim uses, when logging 
> Topic(T=)/Subject to exim mainlog.
>
> Currently cyrillic subjects are logged to something like this :
>
> \321\201\321\200\320\276\320\272\320\276\320\262\320\265


The usual low-numbered control characters are replaced with
"\n" escapes ( n, r, b, v, f ).

Anything outside the range 32 to 126 inclusive is replaced with
"\ddd" octal escapes _unless_ the char is > 127 and the
"print_topbitchars" option is set.


Logging is not intended as input for automated parsing, but for
humans... and has a western bias. In particular it knows
nothing about UTF-8. There's an open bug in the area, 282, which
wonders what ought to be done.
--
Cheers,
Jeremy