Hi there,
I already posted about this problem some months ago. Upon re-visiting it I
found out that the listening Exim process (version 4.10) hangs during batched
SMTP input.
After a message in this session has been successfully received it just sits
there doing nothing. Sometimes this last for some hours!!
Without having had a look at Exim's source code from my observations it seems
that there aren't any provisions in the source for a timeout between messages
in BSMTP. Shouldn't there be a (configurable) timeout that forces closure of
the session after a certain time has run out without a further message having
been received? Can you (Phil?) confirm this?
Here's a small debugging log snippet:
SMTP>> 250 OK id=18fHY6-0008Qg-00
[...]
forked delivery process 32446
Process 32406 is ready for new message
smtp_setup_msg entered
[...]
SMTP>> 250 OK id=18fHaN-0008Qg-00
[...]
forked delivery process 32453
Process 32406 is ready for new message
smtp_setup_msg entered
At this point the Exim process seems to stall.
It's not very easy to debug this kind of problems since you can easily become
confused with debugging output from the different Exim processes.
Thanks for any insights,
Ralf
--
L I N U X .~.
The Choice /V\
of a GNU /( )\
Generation ^^-^^
