|
Answer/Solution: A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a reboot. Right, its being dropped because it times out. The server in question can initiate an SMTP connection, but if there's no route back to the sever that initiated a connection to mine, it will time out. If the packets can't find their way back, it breaks the connection. The problem is routing - packets get routed to my server because my net block (destination address) is routable, but the return traffic back to a "null routed" net block (destination address) will time out. However you slice it, SMTP wont respond when the server is attempting to communicate. I cant believe that I'm the only one having this problem. Is there anyone else seeing multiple 10054's with SMTP not timing out? Is anyone else using Sprint that has a mail server receiving lots of SPAM that doesn't have a 10054 problem? This forum is cool!! -----Original Message-----
| |||||||||
Title: Message
- [IMail Forum] SMTP Timeouts and send error 10054 Mike VandeBerg
- RE: [IMail Forum] SMTP Timeouts and send error 10054 Jamie Orth
- RE: [IMail Forum] SMTP Timeouts and send error 1... Mike VandeBerg
- RE: [IMail Forum] SMTP Timeouts and send err... Patrick Childers
- RE: [IMail Forum] SMTP Timeouts and send... Mike VandeBerg
- RE: [IMail Forum] SMTP Timeouts and... Mike VandeBerg
- RE: [IMail Forum] SMTP Timeouts... Len Conrad
- RE: [IMail Forum] SMTP Time... Mike VandeBerg
- Re: [IMail Forum] SMTP Timeouts and... Eric Shanbrom
- Mike VandeBerg
