https://bugs.exim.org/show_bug.cgi?id=3085
--- Comment #2 from Forza <[email protected]> --- The issue seems to be that Exim didn't escape characters that are outside of the us-ascii/7-bit. As far as I know, Exim mostly does that in the logs (I see plenty of lines with escaped characters like \360\237\216\211). Here we see malformed double quotes: 2024-03-17T19:23:33.698+00:00 notice exim[5673]: [12\21] F From: "̼" <[email protected]> 2024-03-17T19:23:33.698+00:00 notice exim[5673]: [13\21] R Reply-To: "̼" <[email protected]> The subject line has strange characters: 2024-03-17T19:23:33.698+00:00 notice exim[5673]: [15\21] Subject: 2030 ı Ҿ ̷ ̰ŷ ϼ! Having json output would be OK, but overkill. In the fail2ban case I need to have either plain text or UTF-8/Unicode, and not mixed mode. The same applies to syslog. -- You are receiving this mail because: You are on the CC list for the bug. -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/ ## unsubscribe (doesn't require an account): ## [email protected] ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
