On Mon, Aug 19, 2024 at 03:13:40PM +0100, Stuart Henderson wrote: > On 2024/08/19 15:26, Theo Buehler wrote: > > On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote: > > > > > > > > > On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote: > > > > > > > > So quite odd, the whole thing. > > > > > > > > > > That's indeed quite odd if connecting with openssl s_client works. > > > I really think you should try out asking exim devs. > > > > It would be helpful to have a reproducer or a backtrace. It is > > impossible to gather much info from this discussion. > > Install the debug-exim package to match the exim package that you've > installed (whether that's self built or from the snapshot - reinstall > the main package if unsure whether they match). Then > > # mkdir /var/crash/exim (i assume that is the process name; adjust if not) > # sysctl kern.nosuidcoredump=3 > > Trigger a crash, see if you get a /var/crash/exim/$PID.core and if so, > point egdb at it.
I did a bit of that and it looks if I read this correctly that the pain point is in the DKIM handling, collection of bts at https://nxdomain.no/~peter/exim-gdb-traces.txt 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.
