Re: [exim] message has lines too long for transport

On 31.05.2022 13:40, Heiko Schlichting via Exim-users wrote: > Jarland Donnell wrote: >> A new variable was added in 4.95: message_linelength_limit >> >> This defaults to RFC spec which is 998 characters, but that's not where the >> conversation should end. Absolutely no one out there is creating

Re: [exim] message has lines too long for transport

On 1.06.2022 10:39, Arkadiusz Miśkiewicz wrote: > On 31.05.2022 13:40, Heiko Schlichting via Exim-users wrote: >> Jarland Donnell wrote: >>> A new variable was added in 4.95: message_linelength_limit >>> >>> This defaults to RFC spec which is 998 characters, but that's not where the >>>

[exim] catching brute foce smtp auth - what condition?

Hello. How to catch brute foce smtp auth attempts only? (== bad login or password provided) Condition like: ${if eq{$authentication_failed}{1}} doesn't work because it also catches cases where client cancelled smtp auth attempt (rfc2554 and "*"). Exim internally sees difference: 535

Re: [exim] exim maildirsize quota calculation in the face of symlinks

On 10.02.2022 13:06, Jasen Betts via Exim-users wrote: > On 2022-02-10, Maarten van Baarsel via Exim-users wrote: >> Currently, I'm also using a plugin in dovecot: >> >> https://wiki.dovecot.org/Plugins/MailboxAlias >> >> However, this plugin solves the alias problem with a symlink in the >>

[exim] too long line but which one?

Hi, how to log that too long line(s), so it will be easy to point where the problem is in case of mail incoming via smtp ? deny message = maximum allowed line length is 998 octets, \ got $max_received_linelength condition = ${if >

Re: [exim] selecting random ip from file

W dniu 12.05.2021 o 11:42, Jeremy Harris via Exim-users pisze: > On 12/05/2021 10:11, Arkadiusz Miśkiewicz via Exim-users wrote: >> example.com: 1.1.1.1, 2.2.2.2, 3.3.3.3 >> >> The number of ip addresses can be different for each domain listed there. >> >>

[exim] selecting random ip from file

Hello. in smtp transport I'm doing something like: interface = <; ${lookup{$sender_address_domain} nwildlsearch{/etc/mail/custom_ip} } which contains: example.com: 1.1.1.1 That works fine but I would like to have few IPs assigned to a domain and let exim choose these randomly like

Re: [exim] Problem with tls_certificate and multiple domains

On 16/10/2019 07:58, Heiko Schlittermann via Exim-users wrote: > Heiko Schlittermann via Exim-users (Mi 16 Okt 2019 > 06:48:25 CEST): >> TLS_DOMAIN = ${if def:tls_in_sni {${lc:tls_in_sni}}{example.com}} >> >> tls_certificate = /etc/exim/private/certs/TLS_DOMAIN/cert.pem >>

Re: [exim] MySQL Connection errors – SSL?

On Monday 14 of May 2018, Kai Bojens via Exim-users wrote: > Hello everybody. > I'am using MySQL for several lookups and everything worked fine for many > years with a „5.0.32-Debian_7etch12” MySQL Server. Today I switched the > backend to „10.2.14-MariaDB-10.2.14+maria~xenial” and everything

Re: [exim] Exim 4.91: option "hosts_try_dane" unknown

On Monday 16 of April 2018, Max Kostikov via Exim-users wrote: > Is this option deprecated now? > Found nothing about this in ChangeLog and NewStuff. > (system is FreeBSD 11.1-RELEASE-p9) config variable name has changed to SUPPORT_DANE -- Arkadiusz Miśkiewicz, arekm / ( maven.pl |

Re: [exim] Exim 4.91 released

On Monday 16 of April 2018, Heiko Schlittermann via Exim-users wrote: > Odhiambo Washington via Exim-users (Mo 16 Apr 2018 > 11:27:06 CEST): … > > > gcc -o exim > > > > drtables.o(.text+0xea): In function `init_lookup_list': > > : undefined reference to