On 2015-08-20 5:42 AM, Heiko Schlittermann wrote:
Daryl Richards <[email protected]> (Mi 19 Aug 2015 20:02:45 CEST):
I am having this problem as well, on one server, and I am not using
split_spool_directory..
And the other conditions to trigger that bug are the same?
exim_dumpdb <spool-dir> wait-<transport>
shows message ids, waiting for the remote host. The host is reachable
already and after sending the first message down to that host, Exim
crashes?
Correct. This is happening when a system sends many messages to an
email-to-SMS gateway, so many destination addresses at the same host.
They all go through, but some crash after delivery and end up frozen on
the queue. If I thaw them and run the queue, it cleans up without
attempting another delivery..
From mailq:
41m 878 1ZSOSe-0002UV-U7 <[email protected]> *** frozen ***
D [email protected]
From exim_dumpdb:
mail.txt.bell.ca 1ZSOSe-0002Ul-VJ 1ZSOSe-0002UU-VP 1ZSOSe-0002Um-Ud
1ZSOZc-0002m2-U8 1ZSOZd-0002mG-02 1ZSOZd-0002lz-0d 1ZSOZl-0002oF-IJ
1ZSOZl-0002oI-FN 1ZSOZl-0002oX-Hw 1ZSOaY-0002rn-Dz 1ZSOaY-0002rq-DP
1ZSOaY-0002rz-D3
The dumpdb line shows the destination host, and various message ids, but
not the one that is frozen.. ??
--
Daryl Richards
Isle Technical Services Inc.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
details at http://www.exim.org/ ##
