On 19/06/2019 00:40, Randy Bush via Exim-users wrote: > did the fix for the recent vuln possibly cause this? > > this is exim forwarding to exim > Exim version 4.92 #4 (FreeBSD 11.2) built 25-May-2019 01:19:44 > to > Exim version 4.90_1 #4 built 04-Jun-2019 18:44:51 > > any thing i can do to ameliorate? > > randy > > 2019-06-18 22:54:35 1hdMzr-000ESq-8e <= > [email protected] > H=(mail-182-80.mailgun.info) [23.253.182.80] P=utf8esmtps > X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no S=4623 DKIM=notify.docker.com > id=20190618225434.73328.89257@7bfeb10228df > 2019-06-18 23:02:58 1hdMzr-000ESq-8e H=test.psg.com [2001:418:8006::18]: utf8 > support required but not offered for forwarding
Possibly indirectly, if the newer build included utf8 support and the older did not. You could: - ask the sender if they really needed to use SMTPUTF8, and persuade them not it if/when it is not needed by the message (actually, looking at the env-from there, it probably was) - ask the system you're forwarding to to update to add international character support - discover that you shouldn't really have been forwarding that message, and close an open relay - investigate the message and discover it was spam anyway - configure to disable support for international characters on reception -- Cheers, Jeremy -- ## 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/
