On 15/11/17 14:51, Gryzli Bugbear via Exim-users wrote: > > 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
Doesn't a message with such subject violate the spec? It ought to be rfc-2047-encoded, right? Or does exim decode it and then log the decoded version? That would be a mistake, IMHO; it should just log the rfc-2047 form. On 2017-11-17 16:14, Jeremy Harris wrote: > 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. And what happens when print_topbitchars _is_ set? I have read that part of the exim spec, but it doesn't quite answer this. Does it just copy out the raw bits without any encoding? -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet, fetch the TXT record for the domain. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
