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?

------------------------------------------------------------------------------ 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