Our email send/receive has worked fairly consistently for over two years.
'Send 'suddenly disabled itself about two weeks ago. We have made no changes
and comcast says it isn't their problem. We have read all of the postings
and are unable to find a solution that applies specifically to our problem -
the magical 587 also causes an error. thanks



The connection to the server has failed. Subject 'test', Account: 'mail',
Server: 'smtp.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket
Error: 10060, Error Number: 0x800CCC0E

I've had the identical problem for the same time period. Have you found a
solution?

"Glenn" wrote:

> Our email send/receive has worked fairly consistently for over two years.
> 'Send 'suddenly disabled itself about two weeks ago. We have made no changes
> and comcast says it isn't their problem. We have read all of the postings
> and are unable to find a solution that applies specifically to our problem -
> the magical 587 also causes an error. thanks
>
> The connection to the server has failed. Subject 'test', Account: 'mail',
> Server: 'smtp.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket
> Error: 10060, Error Number: 0x800CCC0E

"Eric" <Eric@xxxxxx> wrote in message
news:F1B13A47-D7AF-4E3D-898F-82A436B9BF4F@xxxxxx

> I've had the identical problem for the same time period. Have you found a
> solution?
>
> "Glenn" wrote:
>

>> Our email send/receive has worked fairly consistently for over two years.
>> 'Send 'suddenly disabled itself about two weeks ago. We have made no
>> changes
>> and comcast says it isn't their problem. We have read all of the
>> postings
>> and are unable to find a solution that applies specifically to our
>> problem -
>> the magical 587 also causes an error. thanks
>>
>> The connection to the server has failed. Subject 'test', Account: 'mail',
>> Server: 'smtp.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No,
>> Socket
>> Error: 10060, Error Number: 0x800CCC0E

Comcast no longer uses port 25, they now use port 587.
Tools>accounts>your account>properties>advanced tab.

See the link for all the account settings:
http://www.comcast.com/Customers/FAQ...s.ashx?Id=2288

--
Regards Steve.
MS-MVP. MAIL. [DTS] UK.
http://www.getsafeonline.org/

Your error message reflects use of port 25 rather than port 587.
Please post the exact error message obtained when using port 587.

--
Gary VanderMolen, MS-MVP (Mail)


"Glenn" <Glenn@xxxxxx> wrote in message news9F8D4E9-94EE-44B5-BF9A-50E1C451EC2D@xxxxxx

> Our email send/receive has worked fairly consistently for over two years.
> 'Send 'suddenly disabled itself about two weeks ago. We have made no changes
> and comcast says it isn't their problem. We have read all of the postings
> and are unable to find a solution that applies specifically to our problem -
> the magical 587 also causes an error. thanks
>
> The connection to the server has failed. Subject 'test', Account: 'mail',
> Server: 'smtp.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket
> Error: 10060, Error Number: 0x800CCC0E

The last poster, Gary, was exactly correct. I had the same problem and
switched the send email settings to port 587 and everything is fine. Mine
was also somehow switched to port 25. Not sure how that could happen.

Go to "tools", "accounts", POP3, "properties", "advanced" when on the
windows mail page in your account while logged in.

Change the setting from 25 to 587.

Should be good to go.

Brad



"Glenn" wrote:

> Our email send/receive has worked fairly consistently for over two years.
> 'Send 'suddenly disabled itself about two weeks ago. We have made no changes
> and comcast says it isn't their problem. We have read all of the postings
> and are unable to find a solution that applies specifically to our problem -
> the magical 587 also causes an error. thanks
>
> The connection to the server has failed. Subject 'test', Account: 'mail',
> Server: 'smtp.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket
> Error: 10060, Error Number: 0x800CCC0E

After weeks of frustation, I tried Brad's suggestion to switch port 25 to
587 and the e-mails are now being sent. Thanks

"Brad Sparks" wrote:

> The last poster, Gary, was exactly correct. I had the same problem and
> switched the send email settings to port 587 and everything is fine. Mine
> was also somehow switched to port 25. Not sure how that could happen.
>
> Go to "tools", "accounts", POP3, "properties", "advanced" when on the
> windows mail page in your account while logged in.
>
> Change the setting from 25 to 587.
>
> Should be good to go.
>
> Brad
>
>
>
> "Glenn" wrote:
>

> > Our email send/receive has worked fairly consistently for over two years.
> > 'Send 'suddenly disabled itself about two weeks ago. We have made no changes
> > and comcast says it isn't their problem. We have read all of the postings
> > and are unable to find a solution that applies specifically to our problem -
> > the magical 587 also causes an error. thanks
> >
> > The connection to the server has failed. Subject 'test', Account: 'mail',
> > Server: 'smtp.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket
> > Error: 10060, Error Number: 0x800CCC0E

I changed the outgoing smtp to 587 and the error I received informed me that
the server required authentication. Comcast had previously told us to make
sure that was not checked. However, once I changed the outgoing server to
'requires authentication' and left the setting to match the incoming server,
everything worked fine. Thanks everyone.

"Glenn" wrote:

> Our email send/receive has worked fairly consistently for over two years.
> 'Send 'suddenly disabled itself about two weeks ago. We have made no changes
> and comcast says it isn't their problem. We have read all of the postings
> and are unable to find a solution that applies specifically to our problem -
> the magical 587 also causes an error. thanks
>
> The connection to the server has failed. Subject 'test', Account: 'mail',
> Server: 'smtp.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket
> Error: 10060, Error Number: 0x800CCC0E

Good to hear. Thanks for that report.

--
Gary VanderMolen, MS-MVP (Mail)


"dannyb" <dannyb@xxxxxx> wrote in message news:1F492464-DA34-4D3D-952D-2F3CA3832504@xxxxxx

> After weeks of frustation, I tried Brad's suggestion to switch port 25 to
> 587 and the e-mails are now being sent. Thanks
>
> "Brad Sparks" wrote:
>

>> The last poster, Gary, was exactly correct. I had the same problem and
>> switched the send email settings to port 587 and everything is fine. Mine
>> was also somehow switched to port 25. Not sure how that could happen.
>>
>> Go to "tools", "accounts", POP3, "properties", "advanced" when on the
>> windows mail page in your account while logged in.
>>
>> Change the setting from 25 to 587.
>>
>> Should be good to go.
>>
>> Brad
>>
>>
>>
>> "Glenn" wrote:
>>

>> > Our email send/receive has worked fairly consistently for over two years.
>> > 'Send 'suddenly disabled itself about two weeks ago. We have made no changes
>> > and comcast says it isn't their problem. We have read all of the postings
>> > and are unable to find a solution that applies specifically to our problem -
>> > the magical 587 also causes an error. thanks
>> >
>> > The connection to the server has failed. Subject 'test', Account: 'mail',
>> > Server: 'smtp.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket
>> > Error: 10060, Error Number: 0x800CCC0E

Yes, port 587 always requires SMTP authentication.

--
Gary VanderMolen, MS-MVP (Mail)


"Glenn" <Glenn@xxxxxx> wrote in message news:900519F3-B9E6-4BC2-9EE5-02A08579485B@xxxxxx

>I changed the outgoing smtp to 587 and the error I received informed me that
> the server required authentication. Comcast had previously told us to make
> sure that was not checked. However, once I changed the outgoing server to
> 'requires authentication' and left the setting to match the incoming server,
> everything worked fine. Thanks everyone.
>
> "Glenn" wrote:
>

>> Our email send/receive has worked fairly consistently for over two years.
>> 'Send 'suddenly disabled itself about two weeks ago. We have made no changes
>> and comcast says it isn't their problem. We have read all of the postings
>> and are unable to find a solution that applies specifically to our problem -
>> the magical 587 also causes an error. thanks
>>
>> The connection to the server has failed. Subject 'test', Account: 'mail',
>> Server: 'smtp.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket
>> Error: 10060, Error Number: 0x800CCC0E

"Glenn" <Glenn@xxxxxx> schrieb im Newsbeitrag
news9F8D4E9-94EE-44B5-BF9A-50E1C451EC2D@xxxxxx

> Our email send/receive has worked fairly consistently for over two years.
> 'Send 'suddenly disabled itself about two weeks ago. We have made no
> changes
> and comcast says it isn't their problem. We have read all of the postings
> and are unable to find a solution that applies specifically to our
> problem -
> the magical 587 also causes an error. thanks
>
> The connection to the server has failed. Subject 'test', Account: 'mail',
> Server: 'smtp.comcast.net', Protocol: SMTP, Port: 25, Secure(SSL): No,
> Socket
> Error: 10060, Error Number: 0x800CCC0E
>