On 2022-02-01 Vincent Lefevre <vinc...@vinc17.net> wrote: > On 2022-02-01 14:44:21 +0100, Vincent Lefevre wrote: > > 2022-02-01 14:23:23 1nEt2b-0008jG-97 SIGSEGV (maybe attempt to write to > > immutable memory) > > 2022-02-01 14:23:23 1nEt2b-0008jG-97 Delivery status for xxx@yyy: got 0 of > > 7 bytes (pipeheader) from transport process 35015 for transport smtp > > > > 2022-02-01 14:23:23 1nEt2b-0008jG-97 == xxx@yyy R=dnslookup T=remote_smtp > > defer (-1): smtp transport process returned non-zero status 0x000b: > > terminated by signal 11 > > 2022-02-01 14:23:23 1nEt7z-00096o-IX <= <> R=1nEt2b-0008jG-97 U=Debian-exim > > P=local S=783 > > 2022-02-01 14:23:23 1nEt2b-0008jG-97 Frozen > > 2022-02-01 14:23:23 1nEt7z-00096o-IX => vlefevre > > <postmas...@cventin.lip.ens-lyon.fr> R=local_user T=maildir_home > > 2022-02-01 14:23:23 1nEt7z-00096o-IX Completed > > 2022-02-01 14:23:23 End queue run: pid=35012 > > 2022-02-01 14:28:19 Start queue run: pid=35460 > > 2022-02-01 14:28:19 1nEt2b-0008jG-97 Message is frozen > > 2022-02-01 14:28:19 End queue run: pid=35460 > > [...] > > > > The consequence is that the mail is not sent, there are no retries, > > and the end user is not warned. So, from the end user point of view, > > the message is *silently lost*.
> Some clarification: by "end user", I mean the author of the message. > There is an error message sent to postmaster, but not to the address > of the author of the message. Yeah from exim's POV this workes out as designed. Something very much unexpected happened, let's freeze the message and tell the admin. The message is not lost. It is still in queue. Is this reproducible, happening with a specific host? Any chance of getting a coredump? cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
