Windows mail error 0x800CCC0F

[grime]

I'm getting the following error when Windows Mail attempts to send or recieve
mail using the Windows Mail client or Windows Live Mail (it used to work just
fine).

Your server has unexpectedly terminated the connection. Possible causes for
this include server problems, network problems, or a long period of
inactivity. Account: 'XTRA', Server: 'pop3.xtra.co.nz', Protocol: POP3, Port:
995, Secure(SSL): Yes, Error Number: 0x800CCC0F

Unfortunately error 0x800CCC0F appears somewhat generic and nothing I do
gets rid of it. My initial reaction is that there is a server problem, but
this isn't the case. I've tried all the recommended client side things (check
your network config, mail settings etc). I can telnet to the pop3 and smtp
ports. I can run a smtp diagnostic utility
(http://www.whitepeaksoftware.com/) successfully with exactly the same
settings fail for Windows Mail and Live Mail. WIndows Mail/Live Mail both
still work when using non secure (SSL) mail servers. My ISP only allows pop3
and smtp over SSL, so this isn't an option.

My theory is that Windows Mail and Live Mail share some Windows SSL code
that the smtp diagnostic utility doesn't. My problem is that I have no way of
proving this, let alone fixing it. Is there anyone that can shed some light
on this? Can I "reinstall" Windows Mail? Perhaps run mail in some sort of
diagnositc mode? My next step will be to load Thunderbird and give up on
Windows Mail. 8-(

I'm running Wndows Vista Home Premium, using Windows OneCare for anti virus,
spam protection and firewall. I've tried removing OneCare and turing off
the Windows firewall. No change.

Thanks in advance.

 

[Gary VanderMolen]

Telnet was designed way before SSL became popular. Telnet has no
feasible way of simulating the SSL handshake, so you can't really
troubleshoot SSL mail servers with it.

In the Troubleshooting section at
http://xtra.co.nz/help/0,,5739-7780440,00.html
they say you can use alternate (non-SSL) settings. Why not give those
a try?

 

[wjw]

I'm getting the following error when Windows Mail attempts to send or recieve
mail using the Windows Mail client or Windows Live Mail (it used to work just
fine).

Your server has unexpectedly terminated the connection. Possible causes for
this include server problems, network problems, or a long period of
inactivity. Account: 'XTRA', Server: 'pop3.xtra.co.nz', Protocol: POP3, Port:
995, Secure(SSL): Yes, Error Number: 0x800CCC0F

Unfortunately error 0x800CCC0F appears somewhat generic and nothing I do
gets rid of it. My initial reaction is that there is a server problem, but
this isn't the case. I've tried all the recommended client side things (check
your network config, mail settings etc). I can telnet to the pop3 and smtp
ports. I can run a smtp diagnostic utility
(http://www.whitepeaksoftware.com/) successfully with exactly the same
settings fail for Windows Mail and Live Mail. WIndows Mail/Live Mail both
still work when using non secure (SSL) mail servers. My ISP only allows pop3
and smtp over SSL, so this isn't an option.

My theory is that Windows Mail and Live Mail share some Windows SSL code
that the smtp diagnostic utility doesn't. My problem is that I have no way of
proving this, let alone fixing it. Is there anyone that can shed some light
on this? Can I "reinstall" Windows Mail? Perhaps run mail in some sort of
diagnositc mode? My next step will be to load Thunderbird and give up on
Windows Mail. 8-(

I'm running Wndows Vista Home Premium, using Windows OneCare for anti virus,
spam protection and firewall. I've tried removing OneCare and turing off
the Windows firewall. No change.

Thanks in advance.

 

[grime]

Gary

I agree that telnet has no SSL capabilities, but using it helps proves that
you have no connectivity issues (eg firewall rules etc) getting a connection
between your computer and the mail server. The SMTP utility I mentioned goes
a step or two further as it does have SSL capabilities (but I only found it a
day or two ago).

I didn't realise XTRA allowed non-SSL connections - thank you for this. This
was useful as a diagnostic (and worked in this case), but I am very relucant
to to use this permenantly as that would mean I send my usercode/password and
email over the internet in the clear.

 

[andarkian zog]

I'm getting the following error when Windows Mail attempts to send or recieve
mail using the Windows Mail client or Windows Live Mail (it used to work just
fine).

Your server has unexpectedly terminated the connection. Possible causes for
this include server problems, network problems, or a long period of
inactivity. Account: 'XTRA', Server: 'pop3.xtra.co.nz', Protocol: POP3, Port:
995, Secure(SSL): Yes, Error Number: 0x800CCC0F

Unfortunately error 0x800CCC0F appears somewhat generic and nothing I do
gets rid of it. My initial reaction is that there is a server problem, but
this isn't the case. I've tried all the recommended client side things (check
your network config, mail settings etc). I can telnet to the pop3 and smtp
ports. I can run a smtp diagnostic utility
(http://www.whitepeaksoftware.com/) successfully with exactly the same
settings fail for Windows Mail and Live Mail. WIndows Mail/Live Mail both
still work when using non secure (SSL) mail servers. My ISP only allows pop3
and smtp over SSL, so this isn't an option.

My theory is that Windows Mail and Live Mail share some Windows SSL code
that the smtp diagnostic utility doesn't. My problem is that I have no way of
proving this, let alone fixing it. Is there anyone that can shed some light
on this? Can I "reinstall" Windows Mail? Perhaps run mail in some sort of
diagnositc mode? My next step will be to load Thunderbird and give up on
Windows Mail. 8-(

I'm running Wndows Vista Home Premium, using Windows OneCare for anti virus,
spam protection and firewall. I've tried removing OneCare and turing off
the Windows firewall. No change.

Thanks in advance.

 

[andarkian zog]

I'm getting the following error when Windows Mail attempts to send or recieve
mail using the Windows Mail client or Windows Live Mail (it used to work just
fine).

Your server has unexpectedly terminated the connection. Possible causes for
this include server problems, network problems, or a long period of
inactivity. Account: 'XTRA', Server: 'pop3.xtra.co.nz', Protocol: POP3, Port:
995, Secure(SSL): Yes, Error Number: 0x800CCC0F

Unfortunately error 0x800CCC0F appears somewhat generic and nothing I do
gets rid of it. My initial reaction is that there is a server problem, but
this isn't the case. I've tried all the recommended client side things (check
your network config, mail settings etc). I can telnet to the pop3 and smtp
ports. I can run a smtp diagnostic utility
(http://www.whitepeaksoftware.com/) successfully with exactly the same
settings fail for Windows Mail and Live Mail. WIndows Mail/Live Mail both
still work when using non secure (SSL) mail servers. My ISP only allows pop3
and smtp over SSL, so this isn't an option.

My theory is that Windows Mail and Live Mail share some Windows SSL code
that the smtp diagnostic utility doesn't. My problem is that I have no way of
proving this, let alone fixing it. Is there anyone that can shed some light
on this? Can I "reinstall" Windows Mail? Perhaps run mail in some sort of
diagnositc mode? My next step will be to load Thunderbird and give up on
Windows Mail. 8-(

I'm running Wndows Vista Home Premium, using Windows OneCare for anti virus,
spam protection and firewall. I've tried removing OneCare and turing off
the Windows firewall. No change.

Thanks in advance.

I am receving the same error trying to connect with my BT% mail account.
this only started happening this afternoon. Message is as follows _

Your server has unexpectedly terminated the connection. Possible causes for
this include server problems, network problems, or a long period of
inactivity. Subject 'Fw: Curry joke', Account: 'mail.btinternet.com', Server:
'mail.btinternet.com', Protocol: SMTP, Server Response: '451 See
http://pobox.com/~djb/docs/smtplf.html.', Port: 25, Secure(SSL): No, Server
Error: 451, Error Number: 0x800CCC0F

 

[andarkian zog]

It would appear that the problem was due to the following :-

Bare LFs in SMTP
Most likely you're here because your mailer displayed the pointer ``See
http://pobox.com/~djb/docs/smtplf.html.''
Where did that pointer come from?
It was generated by qmail, an Internet message transfer agent. Your mailer
tried to send an e-mail message to a server running qmail. Unfortunately,
qmail spotted a problem: your mailer sent a bare LF.
Why should I worry about bare LFs?
You can't get mail through to msn.com and thousands of other systems around
the Internet. Your mailer is violating 822bis section 2.3, which specifically
prohibits all bare LFs.

I deleted the offending email in my outbox and all appears to be well again.
Am now receibing and sending emails.

I deleted the offending email in m

 

[Gary VanderMolen]

The only other suggestion I have is that some third party security programs
don't work well with SSL email. Something to look into.

I would not be too concerned about sending one's email password in the
clear. I've been doing that for some 25 years without an incident.
Someone would have to tap into your local network with a sophisticated
packet sniffer in order to get that password. Unless you are some high
profile celebrity, why would they go to that trouble?

 

[Gary VanderMolen]

Thanks for your follow-up report.