1316 Views 4 Replies Latest reply: Nov 3, 2009 6:53 AM by Screaming.Pict
Thanks for the response. I have previously seen Mail.app fail to send and bring the message back up telling me this- but that usually happens quite some time after trying to send, if at all, and I don't recall ever having this error happen in the office (where they are blocking these ports).
I have had similar issues when travelling and trying to send through hotel networks that typically block port 25- even then I rarely get a failure message (note that this has been happening both on 10.5.x and my clean install of 10.6.x)
I did check to see if the network here was doing some spoofing on SMTP ports but it isn't;
#####:~ #####$ time telnet smtp.me.com 25
telnet: connect to address 126.96.36.199: Operation timed out
telnet: Unable to connect to remote host
I get the same 1m15s timeout on port 465 & 587, yet Mail.app never seems to give up trying.
I tried sending to an external SMTP server without SSL to see if the behaviour was any different- but after 15 mins it's still trying so I guess not.
You should keep your smtp.me.com set to be presented on Port 587 for best result when traveling. Most every venue blocks using it and similar SMTP on Port 25. Of course your work venue may block every other SMTP.
Did you get a chance to test whether Activity will let you quickly cancel a Send on the blocked SMTP?