On Mon, Aug 19, 2024 at 11:11:40AM +0200, Peter N. M. Hansteen wrote: > On Mon, Aug 19, 2024 at 10:54:00AM +0200, Renaud Allard wrote: > > Your configuration looks indeed very simple without anything unusual. > > I added your tls_require_ciphers as this is the only thing that is really > > different from my test server at connection time, but I still couldn't > > reproduce the issue. > > Your certificate contains multiple wildcard SAN names, that might be part of > > the issues, although I don't see why it would be that. > > > > As a suggestion, you should consider disabling rfc1413 requests unless you > > know you need them (it's disabled by default in 4.86+). > > Yes, I can comment out that section. I was never entirely sure it adds any > actual value.
Unfortunately commenting out that section, running a new pkg_add -vurm to get a new exim produced identical results 2024-08-19 11:12:47 1sec8H-00000000P17-2SB8 == dh_iws...@vps59238.dreamhostps.com R=dnslookup T=remote_smtp defer (-54): retry time not reached for any host for 'vps59238.dreamhostps.com' 2024-08-19 11:12:47 End queue run: pid=33271 2024-08-19 11:13:00 1sfyRg-00000000IJK-0m6Q SIGSEGV (fault address: 0xffffffffe3aa2caf) 2024-08-19 11:13:00 1sfyRg-00000000IJK-0m6Q SIGSEGV (maybe attempt to write to immutable memory) 2024-08-19 11:13:00 1sfyRg-00000000IJK-0m6Q SIGSEGV (70390 handling TLS incoming connection from mail.openbsd.org [199.185.178.25] ) 2024-08-19 11:13:00 1sfyRg-00000000IJK-0m6Q backtrace 2024-08-19 11:13:00 1sfyRg-00000000IJK-0m6Q --- 2024-08-19 11:13:00 1sfyRg-00000000IJK-0m6Q 0xbe2ced3bc98 <stackdump+0x38> at /usr/local/bin/exim 2024-08-19 11:13:00 1sfyRg-00000000IJK-0m6Q --- so I reinstalled the locally built older one for now All the best, Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
