Re: [exim] Taint mismatch, Ustrncpy: retry_update 826 ?

2021-01-25 Thread Andreas Metzler via Exim-users
On 2021-01-25 Mike Tubby via Exim-users wrote: > On closer inspection, I think I am generating one per message stuck on the > queue - each time Exim runs the queue - hence this may relate to > 'retry_update'? > Exim 4.93 built from source, 64-bit Devuan 3.0 Beowulf (similar to Debian 10 > but

Re: [exim] Virtual mailboxes not working on new install.

2021-01-25 Thread Adrian via Exim-users
Thanks Jeremy The current situation is that I'm in the middle of a server migration from a quirky fifteen-year-old one to a hopefully much cleaner one. Lots to migrate and troubleshoot. The situation with exim4 is that it still works, albeit still using my homebrew pipe transport script. Using

[exim] detect messages which have a from which don't match RCVD from

2021-01-25 Thread Jonathan Gilpin via Exim-users
Hi, I would like to Add a custom header to messages which have a From: which includes a specific domain name, lets say domain.com But have a RCVD From which does not contain that same domain name. This is basically to detect spoofing, How can I do this in the exim config file? Kind Regards,

Re: [exim] Taint mismatch, Ustrncpy: retry_update 826 ?

2021-01-25 Thread Jeremy Harris via Exim-users
On 25/01/2021 13:48, Mike Tubby via Exim-users wrote: retry_update 826 You didn't say what version Exim you have, but that looks possibly like Bug 2492, fixed in 4.94 -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at

Re: [exim] Taint mismatch, Ustrncpy: retry_update 826 ?

2021-01-25 Thread Mike Tubby via Exim-users
On closer inspection, I think I am generating one per message stuck on the queue - each time Exim runs the queue - hence this may relate to 'retry_update'? Exim 4.93 built from source, 64-bit Devuan 3.0 Beowulf (similar to Debian 10 but without systemd). On 25/01/2021 13:48, Mike Tubby via

[exim] Taint mismatch, Ustrncpy: retry_update 826 ?

2021-01-25 Thread Mike Tubby via Exim-users
All, I thought that I had fixed my system's issues with tainted data some months ago but I appear to be logging one of these in paniclog for each message processed: 2021-01-25 10:48:56 1l2yKc-0003H9-4x Taint mismatch, Ustrncpy: retry_update 826 2021-01-25 10:58:56 1l2yKc-0003H9-4x Taint

Re: [exim] auth disclosure on auth rejects in logfiles

2021-01-25 Thread Jeremy Harris via Exim-users
On 25/01/2021 10:36, Cyborg via Exim-users wrote: 2021-01-25 10:15:47 H= (EHLO STRING) [IP ADDRESS] X=TLS1.3:TLS_AES_128_GCM_SHA256:128 CV=no rejected AUTH PLAIN BASE64STRING : authentication is allowed only once per message in order to slow down bruteforce cracking This config part:

Re: [exim] auth disclosure on auth rejects in logfiles

2021-01-25 Thread Andrew C Aitchison via Exim-users
On Mon, 25 Jan 2021, Cyborg via Exim-users wrote: Exim: 4.94-1  Fedora 32 Build I just found out that exim logs the authcredentials in case they get rejected due to bruteforce rules: 2021-01-25 10:15:47 H= (EHLO STRING) [IP ADDRESS] X=TLS1.3:TLS_AES_128_GCM_SHA256:128 CV=no rejected AUTH

[exim] auth disclosure on auth rejects in logfiles

2021-01-25 Thread Cyborg via Exim-users
Exim: 4.94-1  Fedora 32 Build Hi, I just found out that exim logs the authcredentials in case they get rejected due to bruteforce rules: 2021-01-25 10:15:47 H= (EHLO STRING) [IP ADDRESS] X=TLS1.3:TLS_AES_128_GCM_SHA256:128 CV=no rejected AUTH PLAIN BASE64STRING : authentication is allowed