SMTP 10053 Software Caused Connection Abort - ultra important please help.
Posted on 2004-09-09
SBS 2000 Server
Reinstalled veritas BE due to logs being corrupt then reboot.
Exchange runs a pop3 connector to a single catch all mailbox which is delievred to 5 or so users locally
Local Email send receive works fine.
Local email sent to extranal domain name works fine
All send mail works fine
All mails downloaded by the pop3 connector disappear into the ether.
The connector connects fine and with advanced logging on all seems well - no errors at all -
this information message
Event Type: Information
Event Source: POP3 Connector
Event Category: Delivery
Event ID: 4032
A recipient has been processed. Recipient information:
NDR Status Code: 600
Error Code: 00002745
SMTP Name: email@example.com
SMTP Host: mini-1.mini.local
among the normal ones - looks like an error but comes up in blue as information.
No errors at all elsewhere
Balls to this i think the pop3 connector in sbs is rubbish anyway so i instal EFS which is much better now i get some more info from the EFS logs
09/09/2004 13:26 --> connecting to SMTP server
09/09/2004 13:26 --> Unknown: The current connection has been aborted by the network or intermediate services. (10053)
telnet localhost 25 results in -
C:\Documents and Settings\Administrator>telnet localhost 25
Connecting To localhost...Could not open a connection to host on port 25 : Conne
so basically pop3 connectors (ms or efs ones) use smtp for local delivery but fail with little or no errors and emails disappear. the local smtp services is not responding.
nothing else has changed on the server which has been running for 3 years no problems except an uninstall of backup exec.
have done numerous reboots, restarts of the smtp, have checked all the securioty settings and anyway SMTP works fine for sneding mail just not local delievry. local delivery works fine if a client sends a mail to firstname.lastname@example.org or email@example.com it just seems like the pop3 clients cant use smtp like its blocking everything except itself from using the service.
seeing as everything was working ok until i recommended an install of BE my head is really on the block.
urgent help required been working on it for last 8 hours straight my mind s fried.
btw i think 10053 is some kind of winsock error.
all dns, pings, mx lookups all seem fine.