windows mail outgoing help

HI I have been having problems on and off for 8 days and am finally fed up.
At times my outgoing works but for the majority I get this message


Your server has unexpectedly terminated the connection. Possible causes for
this include server problems, network problems, or a long period of
inactivity. Subject 'Luv My Pet 525 North Main St Providence RI', Account:
'pop.east.cox.net', Server: 'smtp.east.cox.net', Protocol: SMTP, Port: 25,
Secure(SSL): No, Socket Error: 10053, Error Number: 0x800CCC0F

I have called my server and redone everything they have asked countless
times. They are now telling me it is a vista problem. Any help is
appreciated I am tired of having to switch through windows to get important
information out.
Please help
Dawn

Disable email scanning(inbound and outbound) in your AV program and any
other resident program(malware scanners, firewall etc)
Additionally check your settings...if I recall, cox.net does not use SSL
encryption.

--
...winston
ms-mvp windows live mail


"Dawn" <skyedolphan1@xxxxxx> wrote in message
news:eOdbRDEXIHA.5984@xxxxxx
HI I have been having problems on and off for 8 days and am finally fed up.
At times my outgoing works but for the majority I get this message


Your server has unexpectedly terminated the connection. Possible causes for
this include server problems, network problems, or a long period of
inactivity. Subject 'Luv My Pet 525 North Main St Providence RI', Account:
'pop.east.cox.net', Server: 'smtp.east.cox.net', Protocol: SMTP, Port: 25,
Secure(SSL): No, Socket Error: 10053, Error Number: 0x800CCC0F

I have called my server and redone everything they have asked countless
times. They are now telling me it is a vista problem. Any help is
appreciated I am tired of having to switch through windows to get important
information out.
Please help
Dawn

On Mon, 21 Jan 2008 12:52:13 -0500, ...winston wrote:
And his error message does not indicate otherwise: "Secure (SSL): No".

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

Error codes and messages provided by WLM can be misleading or appear to be a
swag.
All settings should be checked, including SSL toggled off.

e.g. It is unlikely the the connection was dropped(the earlier posted error
code).

--
...winston
ms-mvp windows live mail


"N. Miller" <anonymous@xxxxxx> wrote in message
news:wsf1gaesaxo5.dlg@xxxxxx
On Mon, 21 Jan 2008 12:52:13 -0500, ...winston wrote:
And his error message does not indicate otherwise: "Secure (SSL): No".

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

On Mon, 21 Jan 2008 18:15:00 -0500, ...winston wrote:
I will have to defer to your knowledge (I know noting about the inner
workings of the client); but my experience is that the error message reports
the state of the settings accurately, if it is somewhat mushy about the
causes of the problems.

"Your server has unexpectedly terminated the connection." This part is,
usually, accurate. I interpret this as an established connection has been
dropped.

"ossible causes for this include server problems, network problems, or a
long period of inactivity." This is the SWAG. It is hardly an exhaustive
list of causes for a dropped connection.

The parts about the "Subject:" line, the account name, the server name, the
port, and the security protocol have all, in my experience, been dead on.

Internet searches (Google, Yahoo!, MSN, etc.) often show a multitude of
possible causes, especially when plugging in the "Socket Error:" number, or
the "Error Number:" hex code as search key words.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

"Dawn" <skyedolphan1@xxxxxx> wrote in message
news:eOdbRDEXIHA.5984@xxxxxx
You need to get more detail about your symptom.
E.g. think about previous use of the same connection:
always on the same boot? how recent was it? etc.

Also I'm not clear on the consequence of this symptom for you?
E.g. what exactly do you mean by "having to switch through windows"?
Is that anything more than just retrying a send? E.g. via Alt-T,S,S


To be very clear about your symptom you would also have to capture
a packet trace, e.g. on XP I would use netcap and format the .cap
file with Ethereal. I don't use your OS and don't know what tools
are available on it for similar diagnostics.


FYI this symptom could be caused by variable timeout settings
on the client and server and with the client therefore appearing
to the server to be not respecting the SMTP protocol.
E.g. the client might be expected to send a QUIT command
in order to close a connection instead of just assuming that
it goes away when it thinks it times out on its side. Etc.


HTH

Robert Aldwinckle
---

Agreed....the error message does contain valid information.
Though every time I see Error Number: 0x800CCC0F, it's rarely enough
indicate the real problem.

--
...winston
ms-mvp windows live mail


"N. Miller" <anonymous@xxxxxx> wrote in message
news:1l83wsjs4frtz$.dlg@xxxxxx
On Mon, 21 Jan 2008 18:15:00 -0500, ...winston wrote:
I will have to defer to your knowledge (I know noting about the inner
workings of the client); but my experience is that the error message reports
the state of the settings accurately, if it is somewhat mushy about the
causes of the problems.

"Your server has unexpectedly terminated the connection." This part is,
usually, accurate. I interpret this as an established connection has been
dropped.

"Possible causes for this include server problems, network problems, or a
long period of inactivity." This is the SWAG. It is hardly an exhaustive
list of causes for a dropped connection.

The parts about the "Subject:" line, the account name, the server name, the
port, and the security protocol have all, in my experience, been dead on.

Internet searches (Google, Yahoo!, MSN, etc.) often show a multitude of
possible causes, especially when plugging in the "Socket Error:" number, or
the "Error Number:" hex code as search key words.