| |||||||||||||||||||||||||||||||
|
I am looking to understand/learn what is going wrong and see how on the postfix side I can figure out whats going on. This is happening from 3 postfix servers, and happening to several clients, me being the common factor. These two links will show you the connections on the exchange side: http://www.web56.net/ebay/retries1.jpg http://www.web56.net/ebay/retries2.jpg My question is 1st: Why does the postfix timeout not drop the connection on the postfix side ( which may or may not drop the exchange side it of course has no control of that ) This shows me the connection is active, and it's longer then the timeouts in postfix. 3F18D2A08A6* 6389 Sat May 3 09:20:37 hocxpx sixo 2nd: with the settings I have is there something additional I should be setting to insure I drop my connection if their connection takes too long? I think these are logical questions to ask and please understand I am not fully versed in all of the high level things that happen during normal and abnormal email communications. Hence why I am here asking.... I will place all the info I can here so you don't have to revert back to the original post. I am trying to provide as much as I can dig up in order to help see my problem clearer... Thanks everyone! Joey --- When the connection from postfix eventually times out I see : (conversation with client's server here timed out while sending end of data -- message may be sent more than once) --- When the connection from postfix is stuck on the clients server I see: 3F18D2A08A6* 6389 Sat May 3 09:20:37 hocxpx sixo --- The log files show me this: May 5 10:44:48 houston postfix/smtp[5448]: 3F18D2A08A6: to=<sixo>, relay=none, delay=177852, delays=177852/0.03/0.09/0, dsn=4.4.1, status=deferred (connect to myserver.server.net[28.144.16.5]:25: Connection refused) May 5 10:44:48 houston postfix/smtp[5449]: 518A52A080A: to=<sixo>, relay=none, delay=82012, delays=82012/0.03/0.08/0, dsn=4.4.1, status=deferred (connect to myserver.server.net[28.144.165.5]:25: Connection refused) --- Default Timeouts are in effect and show this: connection_cache_protocol_timeout = 5s daemon_timeout = 18000s ipc_timeout = 3600s lmtp_connect_timeout = 0s lmtp_data_done_timeout = 600s lmtp_data_init_timeout = 120s lmtp_data_xfer_timeout = 180s lmtp_lhlo_timeout = 300s lmtp_mail_timeout = 300s lmtp_quit_timeout = 300s lmtp_rcpt_timeout = 300s lmtp_rset_timeout = 20s lmtp_starttls_timeout = 300s lmtp_tls_session_cache_timeout = 3600s lmtp_xforward_timeout = 300s milter_command_timeout = 30s milter_connect_timeout = 30s milter_content_timeout = 300s qmqpd_timeout = 300s smtp_connect_timeout = 30s smtp_data_done_timeout = 600s smtp_data_init_timeout = 120s smtp_data_xfer_timeout = 180s smtp_helo_timeout = 300s smtp_mail_timeout = 300s smtp_quit_timeout = 300s smtp_rcpt_timeout = 300s smtp_rset_timeout = 20s smtp_starttls_timeout = 300s smtp_tls_session_cache_timeout = 3600s smtp_xforward_timeout = 300s smtpd_policy_service_timeout = 100s smtpd_proxy_timeout = 100s smtpd_starttls_timeout = 300s smtpd_timeout = 300s smtpd_tls_session_cache_timeout = 3600s trigger_timeout = 10s
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com