>Ioannis Tsouvalas: >> > >> >Ioannis Tsouvalas: >> >> 451 Requested action aborted: local error in processing >> >> 451 Temporary local problem - please try later > >These you can do nothing about, except perhaps retry when the remote >system is under less stress. > >> >> 421 4.4.1 Connection timed out (in reply to end of DATA command) >> >> 421 4.4.2 mxfront39.mail.yandex.net Error: timeout exceeded (in >> >> reply to end of DATA command) > >These could be a network-level problem such as broken IP path MTU >discovery, or TCP options that are mis-implemented by an and system >or by an intermediate system (such as a cheap firewall). > >There is some 12 years of discussion archived on-line that covers >IP path MTU problems, and some 5 years for mis-implemented TCP >options (Sack, Wscale, ...). I see that you have already turned >off some of those. > >This can be debugged by capturing network packets and making sense >of the flags, windows, ACK offsets, and retransmissions. I have >done that in earlier years but can no longer afford the time. > > Wietse
Dear Wietse thank you for your reply, it's definitely eye opening as well as frightening to say the least. I took things a step further, with setting things up the way I described on my first post, and it seems to me that I got myself into a situation I shouldn't have. I will keep looking on different ways to go around those issues, forward is the only option. Still if someone is willing to go down that debugging path with me, or has any other suggestions, I'm all ears, now more than ever. With respect, Ioannis - __________ Information from ESET Smart Security, version of virus signature database 5153 (20100528) __________ The message was checked by ESET Smart Security. http://www.eset.com
