| |||||||||||||||||||||||||||||||
|
> That makes perfect sense when we have the connection refused, however the mail queue shows the below before we get the refused message: > 3F18D2A08A6* 6389 Sat May 3 09:20:37 hocxpx > sixo This means the message is in the active queue, it says nothing about connections. Messages in the active queue destined to a congested destination wait their turn to be given to a delivery agent for processing. Your logs show only rapid "Connection refused" errors, show logging of deliveries that are *not* deferred due to "Connection refused". > And on the client server side ( exchange ) I see connections up to 10 > days... and the connections are still open on our side. You present no evidence of this. If you have stuck deliveries to exchange, debug (and post details of) the stuck connections, not the ones that fail as a result of Exchange running out of connection slots. > This is where my question about timeouts etc stems from. ( original post ). The timeouts are irrelevant. Look for broken firewalls, broken path MTU, ... report detailed facts to support *all* your anecdotal claims. -- Viktor. Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header. To unsubscribe from the postfix-users list, visit http://www.postfix.org/lists.html or click the link below: <mailto:majordomo?body=unsubscribe%20postfix-users> If my response solves your problem, the best way to thank me is to not send an "it worked, thanks" follow-up. If you must respond, please put "It worked, thanks" in the "Subject" so I can delete these quickly.
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com