Package: nullmailer
Version: 1.00RC7-22

Log details:
Mar 30 06:27:35 mace nullmailer[18037]: Trigger pulled.
Mar 30 06:27:35 mace nullmailer[18037]: Rescanning queue.
Mar 30 06:27:35 mace nullmailer[18037]: Starting delivery, 1 message(s) in 
queue.
Mar 30 06:27:35 mace nullmailer[18037]: Starting delivery: protocol: smtp host: 
hammer.websitemanagers.com.au file: 1143664053.14512
Mar 30 08:19:37 mace nullmailer[18037]: Sending process crashed or was killed.
Mar 30 08:19:37 mace nullmailer[18037]: Delivery complete, 1 message(s) remain.
Mar 30 08:19:37 mace nullmailer[18037]: Trigger pulled.
Mar 30 08:19:37 mace nullmailer[18037]: Rescanning queue.
Mar 30 08:19:37 mace nullmailer[18037]: Starting delivery, 20 message(s) in 
queue.
Mar 30 08:19:37 mace nullmailer[18037]: Starting delivery: protocol: smtp host: 
hammer.websitemanagers.com.au file: 1143668136.21115
Mar 30 08:19:37 mace nullmailer[26800]: smtp: Succeeded: 250 ok 1143670777 qp 
19823
Mar 30 08:19:37 mace nullmailer[18037]: Sent file.
Mar 30 08:19:37 mace nullmailer[18037]: Starting delivery: protocol: smtp host: 
hammer.websitemanagers.com.au file: 1143665122.16300
Mar 30 08:19:38 mace nullmailer[26802]: smtp: Succeeded: 250 ok 1143670778 qp 
19837


Basically, our SMTP server frequantly becomes really slow to respond, and 
sometimes times
out etc. It seems that nullmailer will never recover from this error, and it 
just hangs.
Eventually I'll notice and kill the child null-mailer process, which then 
allows the
trigger to be pulled, and all pending emails are sent with no problem.

I'm not sure exactly what the server is doing to cause the problem, but I do 
know that
nullmailer should handle it better, and eventually deliver the messages. 
Perhaps nullmailer
doesn't timeout the connection and retry, perhaps it doesn't recognise when the 
connection
has died, and retry, etc... This happens consistently at least twice per week 
in our
environment for quite some time. 

If you need more information, let me know and I'll try to dig it up. I kind of 
assumed this
was a known bug, but couldn't find any open bugs refering to this.

Running Debian stable

Regards,
Adam

-- 
Adam Goryachev
Website Managers
Ph:  +61 2 8304 0000                      [EMAIL PROTECTED]
Fax: +61 2 8304 0001                       www.websitemanagers.com.au



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to