Hello again,
>
> That's ... rather worrying to see in a backtrace; smtp_read_response()
> is very well-used code and we shouldn't be seeing surprises there.
>
> Any chance that you could compile Exim with debug information (-ggdb)
> and _not_ strip it, so we can see more information in the backtrace?
>
Yes, now more information:
(gdb) bt
#0 0x000000000046b660 in smtp_read_response
(inblock=0x7ffff18bad50,buffer=0x7ffff18b9d10 "220 proksima.home.pl ESMTP
IdeaSmtpServer v0.70 ready.\r", size=4041, okdigit=50, timeout=300) at
smtp_out.c:512
#1 0x0000000000491950 in smtp_deliver (addrlist=0x16f07820,
host=0x16f07a60, host_af=2, port=25, interface=0x16f07ba0 "193.99.999.99",
tblock=0x16efcea0, copy_host=0, message_defer=0x7ffff18bae74,
suppress_tls=0) at smtp.c:945
#2 0x000000000049451e in smtp_transport_entry (tblock=0x16efcea0,
addrlist=0x16f07820) at smtp.c:2735
#3 0x00000000004232c1 in do_remote_deliveries (fallback=0) at
deliver.c:3878
#4 0x00000000004265ea in deliver_message (id=0x7ffff18fbf3a
"1R2n60-00060M-EI", forced=0, give_up=0) at deliver.c:6007
#5 0x000000000042f884 in main (argc=3, cargv=<value optimized out>) at
exim.c:4212
