[exim] Re: tainted uux transport

2023-07-31 Thread Randy Bush via Exim-users
> https://jimbobmcgee.wordpress.com/2020/07/29/de-tainting-exim-configuration-variables/ that bogus lookup("*") is definitely not for post prandial use. randy -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ##

[exim] ARC / remove own Authentication-Results: header

2023-07-31 Thread Robert Lister via Exim-users
Hello, According to this spec for ARC: https://github.com/Exim/exim/blob/master/doc/doc-txt/experimental-spec.txt#L472 It is recommended to remove any Authentication-Results: header claiming to be from my own identifier: " Note that it would be wise to strip incoming messages of A-R headers

[exim] Re: Starting Swift_SmtpTransport

2023-07-31 Thread Ltc Hotspot via Exim-users
Jeremy, cPanel recommends an upgrade from TLS 1.1 connections to TLS 1.2 connections. See, " [23:12:57 35-236-118-198 root@95097357 ~]cPs# grep -i openssl_options /etc/exim.conf* /etc/exim.conf:openssl_options = +no_sslv2 +no_sslv3 +no_tlsv1 +no_tlsv1_1 /etc/exim.conf.localopts:openssl_options=+

[exim] Re: Starting Swift_SmtpTransport

2023-07-31 Thread Jeremy Harris via Exim-users
On 31/07/2023 23:12, Ltc Hotspot via Exim-users wrote: What is the cause of the following error message: STARTTLS << 220 TLS go ahead !! Unable to connect with TLS encryption (code: 0)" Apart from pointing out that it fails at the stage of making a TLS session... What do you recommend a

[exim] Starting Swift_SmtpTransport

2023-07-31 Thread Ltc Hotspot via Exim-users
Hi everyone, What is the cause of the following error message: "Unable to connect with TLS encryption Log data: ++ Starting Swift_SmtpTransport << 220-35-236-118-198.cprapid.com ESMTP Exim 4.96 #2 Mon, 31 Jul 2023 14:55:26 -0700 220-We do not authorize the use of this system to transport unsolic

[exim] Re: tainted uux transport

2023-07-31 Thread Markus Reschke via Exim-users
Hi Randy! On Mon, 31 Jul 2023, Randy Bush via Exim-users wrote: force_uucp: driver = manualroute domains = ! +local_domains route_data = ${lookup{$domain}partial-lsearch{/usr/local/etc/exim/ro.uucp}} In case you can't create a list of known domains, e.g. when routing to a UUCP smarthost,

[exim] Re: tainted uux transport

2023-07-31 Thread Jeremy Harris via Exim-users
On 31/07/2023 17:55, Randy Bush via Exim-users wrote: force_uucp: driver = manualroute domains = ! +local_domains Would it be feasible for you to have a definitive, limited, list of acceptable domains to check against here - rather than "anything but the local list"? Basically, it is tha

[exim] Re: tainted uux transport

2023-07-31 Thread Andreas Barth via Exim-users
Hi, had been some time since I tried that last, so if my remarks are not useful I'm sorry. * Randy Bush via Exim-users (exim-users@lists.exim.org) [230731 18:57]: > >> 2023-07-30 14:23:11 1qQ7KA-000BIX-27 ** f...@foo.com R=force_uucp T=uux: > >> Tainted > >> arg 4 for uux transport command: '

[exim] Re: tainted uux transport

2023-07-31 Thread Randy Bush via Exim-users
>> 2023-07-30 14:23:11 1qQ7KA-000BIX-27 ** f...@foo.com R=force_uucp T=uux: >> Tainted >> arg 4 for uux transport command: '(@foo.com)' >> >> uux: >>driver = pipe >>command = "/usr/local/bin/uux - -r $host!rmail >> ($local_part_suffix@$domain)" >>path = "/usr/local/bin:/usr/bin:/bin"

[exim] Re: is UTF spamsenders now a thing?

2023-07-31 Thread Jasen Betts via Exim-users
On 2023-07-28, Cyborg via Exim-users wrote: > > ## No help required , this is just an info for you guys ## > > Hi, > > we have a new kind of spammer at our mailborder: > > 1qOF7T-002mUk-2Y H=(timesquareas.yachts) [216.9.227.107] Warning: > processing file "" for "To: X -> From: >