7 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Connection timed out| From | Sent On | Attachments |
|---|---|---|
| Bowie Bailey | May 8, 2009 12:26 pm | |
| Brian A. Seklecki | May 8, 2009 12:41 pm | |
| Bowie Bailey | May 8, 2009 1:06 pm | |
| Sam Varshavchik | May 8, 2009 3:46 pm | |
| Bowie Bailey | May 9, 2009 6:12 am | |
| Sam Varshavchik | May 9, 2009 6:26 am | |
| Bowie Bailey | May 9, 2009 5:40 pm |
| Subject: | Re: [courier-users] Connection timed out | |
|---|---|---|
| From: | Bowie Bailey (Bowi...@BUC.com) | |
| Date: | May 9, 2009 6:12:45 am | |
| List: | net.sourceforge.lists.courier-users | |
Sam Varshavchik wrote:
Bowie Bailey writes:
I happened to be watching my server when a message came through that was being forwarded to another server. When it stayed in the queue longer than expected, I looked into it. This is what the logs show:
------------------------------------------------ May 8 07:43:31 bnofmail courierd: newmsg,id=00140010.4A041AE3.000045AD: dns; localhost (localhost [127.0.0.1]) May 8 07:43:31 bnofmail courierd: started,id=00140010.4A041AE3.000045AD,from=<bo-b...@b.email.newegg.com>,module=esmtp,host=mail.bowiebailey.com,addr=<bow...@mail.bowiebailey.com>
May 8 08:00:11 bnofmail courieresmtp: id=00140010.4A041AE3.000045AD,from=<bo-b...@b.email.newegg.com>,addr=<bow...@mail.bowiebailey.com>: 500 couriertls: connect: Connection timed out May 8 08:00:11 bnofmail courieresmtp: id=00140010.4A041AE3.000045AD,from=<bo-b...@b.email.newegg.com>,addr=<bow...@mail.bowiebailey.com>,status: failure May 8 08:00:11 bnofmail courierd: completed,id=00140010.4A041AE3.000045AD May 8 08:00:11 bnofmail courierd: started,id=00140010.4A041AE3.000045AD,from=<>,module=dsn,host=,addr=<bo-b...@b.email.newegg.com>
May 8 08:00:11 bnofmail courierd: completed,id=00140010.4A041AE3.000045AD
------------------------------------------------
One delivery attempt, a timeout, and an immediate bounce. Why wasn't this message held in the queue and retried later? A bit more digging shows a few more messages like this. One of them was retried seven times before being bounced, but it was still only in the queue for 2 1/2 hours. Do I have something misconfigured?
No -- this is not a real connection timeout. The error message is from couriertls. The connection was established, an SSL handshake was sent, but the remote server failed to respond. It's an SSL protocol-level error.
In that case, I guess I'll just set "SECURITY=NONE" for that server. Should that take care of it?
I still don't understand why this message bounced so quickly. Shouldn't the message have been held in the queue and retried for a week?
-- Bowie
------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________ courier-users mailing list cour...@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users