error - can't send out BUT can receive mail

  • Thread starter Thread starter Penny
  • Start date Start date
P

Penny

Receiving this error:
The connection to the server has failed. Subject 'Fw: Medical Update
09*09*09' Account: 'mail.eskimo.com', Server: 'mail.eskimo.com',
Protocol:SMTP, Port:25, Secure(SSL): No, Socket Error: 10060, Error
Number:0x800CCC0E

Scenario: Tried to forward a digest version of medical alert from county
website. It errored out and sat in the outbox. I decided to just talk to the
person so I deleted it from outbox. Since then NOTHING will pass the outbox
and it is hung up on the medical update failing THE ONE I DELETED! How do I
clear this from the system and get the others to pass and WHY did this happen
so I don't do it again? Thanks for any help.
 
I don't know if I can help but getting help might depend on knowing what
antivirus software you are using. This is the type of thing that AV software
sometimes messes up. So what AV software are you using?
 
Looks like you are running into a port 25 block. When you got that error,
who was providing your Internet connection?
If other than Eskimo.com, what you experienced is normal. As a general
rule, the owner of the SMTP server you are using must be the same as the
entity providing your Internet connection at that moment. For more on this
see http://www.postcastserver.com/help/Port_25_Blocking.aspx

The available workarounds when sending away from home are as follows:

1. Use webmail for sending (via your browser).
2. Ask your home ISP if they have a port other than '25' for SMTP.
3. If you use the same away-from-home connection frequently,
substitute the SMTP server belonging to that connection. This is a bit
tricky, but if you want to go that route, I can provide more details.
4. If you frequently send from multiple locations, get a free Gmail account,
configure it for POP access, set it up in Windows Mail, and use that for
your sending chores. Gmail uses port 465 for SMTP, which is not blocked
like port 25 is.
 
Penny said:
Receiving this error:
The connection to the server has failed. Subject 'Fw: Medical Update
09*09*09' Account: 'mail.eskimo.com', Server: 'mail.eskimo.com',
Protocol:SMTP, Port:25, Secure(SSL): No, Socket Error: 10060, Error
Number:0x800CCC0E

Scenario: Tried to forward a digest version of medical alert from county
website. It errored out and sat in the outbox. I decided to just talk to
the
person so I deleted it from outbox. Since then NOTHING will pass the
outbox
and it is hung up on the medical update failing THE ONE I DELETED! How do
I
clear this from the system and get the others to pass and WHY did this
happen
so I don't do it again? Thanks for any help.
Click to expand...
 
Penny said:
Receiving this error:
The connection to the server has failed. Subject 'Fw: Medical Update
09*09*09' Account: 'mail.eskimo.com', Server: 'mail.eskimo.com',
Protocol:SMTP, Port:25, Secure(SSL): No, Socket Error: 10060, Error
Number:0x800CCC0E

Scenario: Tried to forward a digest version of medical alert from county
website. It errored out and sat in the outbox. I decided to just talk to the
person so I deleted it from outbox. Since then NOTHING will pass the outbox
and it is hung up on the medical update failing THE ONE I DELETED! How do I
clear this from the system and get the others to pass and WHY did this happen
so I don't do it again? Thanks for any help.
Click to expand...


Thank you all for suggestions. Turns out Verizon is blocking port 25 so they
gave me their work around port #. Gary was right. I appreciate the responses
as I was at a loss. - Penny
 
Gary VanderMolen said:
Looks like you are running into a port 25 block. When you got that error,
who was providing your Internet connection?
If other than Eskimo.com, what you experienced is normal. As a general
rule, the owner of the SMTP server you are using must be the same as the
entity providing your Internet connection at that moment. For more on this
see http://www.postcastserver.com/help/Port_25_Blocking.aspx

The available workarounds when sending away from home are as follows:

1. Use webmail for sending (via your browser).
2. Ask your home ISP if they have a port other than '25' for SMTP.
3. If you use the same away-from-home connection frequently,
substitute the SMTP server belonging to that connection. This is a bit
tricky, but if you want to go that route, I can provide more details.
4. If you frequently send from multiple locations, get a free Gmail account,
configure it for POP access, set it up in Windows Mail, and use that for
your sending chores. Gmail uses port 465 for SMTP, which is not blocked
like port 25 is.


--
Gary VanderMolen, MS-MVP (Mail)
http://mvp.support.microsoft.com/profile/VanderMolen





You were right on the money! Thanks!
Click to expand...
 
Back
Top