https://bugs.exim.org/show_bug.cgi?id=1810
--- Comment #5 from Matt Rubright <matt.rubright@???> ---
In my case 'unseen' was not involved. If you're referring to routing
configuration, it's pretty simple - all messages are routed to an external
relay service. The logging indicated that messages were not being delivered,
though they actually were. Typical messages were like this:
2016-04-06 08:12:44 1anmKC-0006el-Ko <= sender@??? H=(C-UNCCharlotte)
[xx.xx.xx.xx] P=esmtps X=TLSv1:AES256-SHA:256 CV=no S=5823
id=F6F68A2AD7301FBDD5AD535E07015B60F5D6EE60@C-UNCCHARLOTTE
2016-04-06 08:12:45 1anmKC-0006el-Ko Spool file 1anZWh-0000Sr-3Q-D not found
2016-04-06 08:12:45 1anmKC-0006el-Ko == recipient@??? R=noauthsmarthost
T=remote_smtp defer (-1): smtp transport process returned non-zero status
0x000b: terminated by signal 11
2016-04-06 08:12:45 1anmKC-0006el-Ko Frozen
I do have 'split_spool_directory = true'. I'm afraid I don't know for certain
if the -H file was missing. What I can say is that after falling back to 4.85,
I was able to use the 'exim -M <messageID>' command to unfreeze messages and
they were cleared off the queue logging this:
2016-04-06 09:28:49 1anmKC-0006el-Ko Unfrozen by forced delivery
2016-04-06 09:28:49 1anmKC-0006el-Ko Completed
I've since discovered in my system logs a ton of these messages:
Apr 6 06:06:06 myhostname01 kernel: exim[1494]: segfault at 0 ip
0000000000467943 sp 00007ffc8fbc1ed0 error 4 in exim-4.86_2-2[400000+d0000]
--
You are receiving this mail because:
You are on the CC list for the bug.
