Cannot Send Outgoing Mail in Vista Windows Mail Personal Edition

When I go to send an outgoing mail message, it gets to the Outbox and Windows
Mail blows up there. I get the following error message: "Your server has
unexpectedly terminated the connection. Possible causes for this include
server problems, network problems, or a long period of inactivity. Subject
'Testing', Account: 'mail.comcast.net', Server: 'SMTP.comcast.net', Protocol:
SMTP, Port: 25, Secure(SSL): No, Socket Error: 10053, Error Number:
0x800CCC0F". I noticed there are several other people within this community
having the same problem.

Note I have deleted all mesaages from the my inbox, outbox sent items, draft
and delete items boxes. The problem still persists. Is this a bug? If so,
when will it be fixed?

"Jciplev" <Jciplev@discussions.microsoft.com> wrote in message
news:ADD442E1-CA97-4781-AE9C-7BA97A8785DC@microsoft.com...
> When I go to send an outgoing mail message, it gets to the Outbox and
> Windows
> Mail blows up there. I get the following error message: "Your server has
> unexpectedly terminated the connection. Possible causes for this include
> server problems, network problems, or a long period of inactivity. Subject
> 'Testing', Account: 'mail.comcast.net', Server: 'SMTP.comcast.net',
> Protocol:
> SMTP, Port: 25, Secure(SSL): No, Socket Error: 10053, Error Number:
> 0x800CCC0F". I noticed there are several other people within this
> community
> having the same problem.
>

change the SMTP.comcast.net to smtp.comcast.net

Se if that has any bearing on the UNIX server which is expecting lowercase.



> Note I have deleted all mesaages from the my inbox, outbox sent items,
> draft
> and delete items boxes. The problem still persists. Is this a bug? If
> so,
> when will it be fixed?
>

Why delete all the messages? Doesn't do a thing except lose you mail..


>

You are not the only one with this dilemma. I got a new laptop with Vista
home premium on it and have the same result as you . I have not found any
solutuion yet except to rely on my yahoo and aim mailboxes for e-mail.
If anyone knows the solution to this situation. please inform me at
Sairung99@yahoo.com. Thank you.

"Jciplev" wrote:

> When I go to send an outgoing mail message, it gets to the Outbox and Windows
> Mail blows up there. I get the following error message: "Your server has
> unexpectedly terminated the connection. Possible causes for this include
> server problems, network problems, or a long period of inactivity. Subject
> 'Testing', Account: 'mail.comcast.net', Server: 'SMTP.comcast.net', Protocol:
> SMTP, Port: 25, Secure(SSL): No, Socket Error: 10053, Error Number:
> 0x800CCC0F". I noticed there are several other people within this community
> having the same problem.
>
> Note I have deleted all mesaages from the my inbox, outbox sent items, draft
> and delete items boxes. The problem still persists. Is this a bug? If so,
> when will it be fixed?
>
>

I am having the same issues, no revolve yet.

"Sairung" wrote:

> You are not the only one with this dilemma. I got a new laptop with Vista
> home premium on it and have the same result as you . I have not found any
> solutuion yet except to rely on my yahoo and aim mailboxes for e-mail.
> If anyone knows the solution to this situation. please inform me at
> Sairung99@yahoo.com. Thank you.
>
> "Jciplev" wrote:
>
> > When I go to send an outgoing mail message, it gets to the Outbox and Windows
> > Mail blows up there. I get the following error message: "Your server has
> > unexpectedly terminated the connection. Possible causes for this include
> > server problems, network problems, or a long period of inactivity. Subject
> > 'Testing', Account: 'mail.comcast.net', Server: 'SMTP.comcast.net', Protocol:
> > SMTP, Port: 25, Secure(SSL): No, Socket Error: 10053, Error Number:
> > 0x800CCC0F". I noticed there are several other people within this community
> > having the same problem.
> >
> > Note I have deleted all mesaages from the my inbox, outbox sent items, draft
> > and delete items boxes. The problem still persists. Is this a bug? If so,
> > when will it be fixed?
> >
> >

"DGuess" <majik@mindspring.oops> wrote in message news:eGV1eC%23cHHA.1508@TK2MSFTNGP06.phx.gbl...
>
> change the SMTP.comcast.net to smtp.comcast.net
>
> Se if that has any bearing on the UNIX server which is expecting lowercase.

That should not make any difference, since by Internet convention,
server names are case-insensitive. It is true that for a Unix server,
www.comcast.net/INFO.html can go to a different place than
www.comcast.net/info.html.
--
Gary VanderMolen

According to your ISP:
http://www.comcast.net/help/faq/inde...=Emailtop17686
the outgoing mail server should be on port 587, not on port 25
as you have it.

Gary VanderMolen

"Jciplev" <Jciplev@discussions.microsoft.com> wrote in message news:ADD442E1-CA97-4781-AE9C-7BA97A8785DC@microsoft.com...
> When I go to send an outgoing mail message, it gets to the Outbox and Windows
> Mail blows up there. I get the following error message: "Your server has
> unexpectedly terminated the connection. Possible causes for this include
> server problems, network problems, or a long period of inactivity. Subject
> 'Testing', Account: 'mail.comcast.net', Server: 'SMTP.comcast.net', Protocol:
> SMTP, Port: 25, Secure(SSL): No, Socket Error: 10053, Error Number:
> 0x800CCC0F". I noticed there are several other people within this community
> having the same problem.
>
> Note I have deleted all mesaages from the my inbox, outbox sent items, draft
> and delete items boxes. The problem still persists. Is this a bug? If so,
> when will it be fixed?

I changed this and got another error message

"Gary VanderMolen" wrote:

> According to your ISP:
> http://www.comcast.net/help/faq/inde...=Emailtop17686
> the outgoing mail server should be on port 587, not on port 25
> as you have it.
>
> Gary VanderMolen
>
> "Jciplev" <Jciplev@discussions.microsoft.com> wrote in message news:ADD442E1-CA97-4781-AE9C-7BA97A8785DC@microsoft.com...
> > When I go to send an outgoing mail message, it gets to the Outbox and Windows
> > Mail blows up there. I get the following error message: "Your server has
> > unexpectedly terminated the connection. Possible causes for this include
> > server problems, network problems, or a long period of inactivity. Subject
> > 'Testing', Account: 'mail.comcast.net', Server: 'SMTP.comcast.net', Protocol:
> > SMTP, Port: 25, Secure(SSL): No, Socket Error: 10053, Error Number:
> > 0x800CCC0F". I noticed there are several other people within this community
> > having the same problem.
> >
> > Note I have deleted all mesaages from the my inbox, outbox sent items, draft
> > and delete items boxes. The problem still persists. Is this a bug? If so,
> > when will it be fixed?
>

Well, if I hadn't seen it happen before I wouldn't have believed it myself.

So, you can take for whatever it's worth but I've seen it happen and that
was "all" that was changed on the computer in Nashville that was using
Comcast cable.


"Gary VanderMolen" <gary@NoMail.invalid> wrote in message
news:OvyfBX$cHHA.4916@TK2MSFTNGP06.phx.gbl...
> "DGuess" <majik@mindspring.oops> wrote in message
> news:eGV1eC%23cHHA.1508@TK2MSFTNGP06.phx.gbl...
>>
>> change the SMTP.comcast.net to smtp.comcast.net
>>
>> Se if that has any bearing on the UNIX server which is expecting
>> lowercase.
>
> That should not make any difference, since by Internet convention,
> server names are case-insensitive. It is true that for a Unix server,
> www.comcast.net/INFO.html can go to a different place than
> www.comcast.net/info.html.
> --
> Gary VanderMolen

http://online.comcast.net/faqs/faq-d...sp?intFaqID=47
Don't see it tell it on this site.


"Gary VanderMolen" <gary@NoMail.invalid> wrote in message
news:epR36e$cHHA.284@TK2MSFTNGP05.phx.gbl...
> According to your ISP:
> http://www.comcast.net/help/faq/inde...=Emailtop17686
> the outgoing mail server should be on port 587, not on port 25
> as you have it.
>
> Gary VanderMolen
>
> "Jciplev" <Jciplev@discussions.microsoft.com> wrote in message
> news:ADD442E1-CA97-4781-AE9C-7BA97A8785DC@microsoft.com...
>> When I go to send an outgoing mail message, it gets to the Outbox and
>> Windows Mail blows up there. I get the following error message: "Your
>> server has unexpectedly terminated the connection. Possible causes for
>> this include server problems, network problems, or a long period of
>> inactivity. Subject 'Testing', Account: 'mail.comcast.net', Server:
>> 'SMTP.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket
>> Error: 10053, Error Number: 0x800CCC0F". I noticed there are several
>> other people within this community having the same problem. Note I have
>> deleted all mesaages from the my inbox, outbox sent items, draft and
>> delete items boxes. The problem still persists. Is this a bug? If so,
>> when will it be fixed?

Was the new error message different?
Please post it here verbatim.

Gary VanderMolen

"twizzlerlady" <twizzlerlady@discussions.microsoft.com> wrote in message
news:FE54FC6E-B733-4B9A-812D-747E98FED7B3@microsoft.com...
>I changed this and got another error message
>
> "Gary VanderMolen" wrote:
>
>> According to your ISP:
>> http://www.comcast.net/help/faq/inde...=Emailtop17686
>> the outgoing mail server should be on port 587, not on port 25
>> as you have it.
>>
>> Gary VanderMolen
>>
>> "Jciplev" <Jciplev@discussions.microsoft.com> wrote in message news:ADD442E1-CA97-4781-AE9C-7BA97A8785DC@microsoft.com...
>> > When I go to send an outgoing mail message, it gets to the Outbox and Windows
>> > Mail blows up there. I get the following error message: "Your server has
>> > unexpectedly terminated the connection. Possible causes for this include
>> > server problems, network problems, or a long period of inactivity. Subject
>> > 'Testing', Account: 'mail.comcast.net', Server: 'SMTP.comcast.net', Protocol:
>> > SMTP, Port: 25, Secure(SSL): No, Socket Error: 10053, Error Number:
>> > 0x800CCC0F". I noticed there are several other people within this community
>> > having the same problem.
>> >
>> > Note I have deleted all mesaages from the my inbox, outbox sent items, draft
>> > and delete items boxes. The problem still persists. Is this a bug? If so,
>> > when will it be fixed?
>>