Can't send email

[brad]

Just started not being able to receive emails, sending is fine. Receiving
gets this message:



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

I cleared out my outbox, restarted windows mail, no luck. Turned Mcafee off
for emails,restarted windows mail no luck.

Thanks in advance,

Brad

 

[Gary VanderMolen]

You've got me thoroughly confused.
The subject title of this thread refers to not being able to send.
You say you can't receive, but sending is fine.
The error message you included was for a sending failure.
So which is it?

 

[brad]

My bad, it was late and I was brain dead after messing with that problem
forever.

I can not SEND. But I can RECEIVE.

Thannks if you can help.

Brad

 

[Guest]

Does your connection to that server cross over from one internet provider's
equipment to another's before it reaches the server? If so, such
connections
to port 25 are often blocked to cause problems for spammers.

You might check your setting for reaching Comcast:

<http://www.comcast.net/help/faq/index.jsp?faq=Emailtop17686&cookieattempt=1>

These instructions were written for Outlook Express, but should also work
under Windows Mail is you avoid the One Click Fix and the instructions
don't call for the HTTP protocol.

Also, to get rid of problems caused by a McAfee antivirus program, you
often have to uninstall it, not just disable part of it, and then run this
cleanup program:

<http://service.mcafee.com/FAQDocument.aspx?id=107083&lc=4105&partner=McAfee&type=TS&ia=1>

You may even have to remove your email account under Windows
Mail, then restart Windows Mail and create the account again.

You may need this fix to handle problems with mail in the Outbox
that won't go out or delete or move to the Drafts folder:

http://support.microsoft.com/default.aspx/kb/941090

If you don't know whether to use the 32-bit version or the 64-bit
version, try the 32-bit version first.

If this fixes your problem, you may want a replacement antivirus
program that doesn't cause such problems. I recommend either
avast! or AVG, either one with a custom install that tells it to
leave out the part that scans email.

http://www.avast.com/eng/avast_4_home.html

http://free.grisoft.com/doc/5390/us/frt/0?prd=aff

 

[Gary VanderMolen]

Were you at home, using your Comcast connection, when that
send error occurred?

Try changing the SMTP server port from 25 to 587.

 

[brad]

No, I am out of town for the week. I am using my mom's bellsouth.net
connection over a secure wireless router.

Thanks again,
Brad

 

[Guest]

Then connections using port 25 aren't likely to work.

 

[brad]

Does that mean I can not ever send emails when I am not at home. There must
be a way to fix this. I need to send emaiils on the road.

Please give me any suggestions.

Thanks,

Brad

 

[Bob F.]

Does that mean I can not ever send emails when I am not at home. There
must
be a way to fix this. I need to send emaiils on the road.

Please give me any suggestions.

Thanks,

Brad

No, It just means you need to get the right port number from your e-mail
provider. It will then work at home and on the road. There might even be a
different server name. The new port number will be in the hundreds.

--
BobF.
Lincoln actually got it right but was way ahead of his time when he said,
"You can have some of you computer working all of the time and all of your
computer working some of the time but..." It was he that said that, wasn't
it?

 

[Guest]

Then use a connection that uses a port other than port 25. Just trying
all the ports is a very slow way to find out which ports work, though;
there are about 65,000 ports available.

See here:

<http://www.comcast.net/help/faq/index.jsp?faq=Emailtop17686&cookieattempt=1>

These instructions were written for Outlook Express, but should also
work under Windows Mail as long as you avoid the One Click Fix
and the instructions don't call for the HTTP protocol.

 

[Gary VanderMolen]

Well, that explains it. For the reason why this situation exists, see
http://www.postcastserver.com/help/Port_25_Blocking.aspx

There are 4 possible workarounds for sending while away from home:

1. Use webmail for sending: http://www.comcast.net/webmail

2. Use a port other than '25' for SMTP, if your mail provider
has a provision for that. Unfortunately, Comcast is a dinosaur when
it comes to making provisions for traveling customers, unlike the
more enlightened connectivity providers like AT&T/SBC.

3. Use the SMTP server belonging to your current connection (Bellsouth).

4. Get a free Gmail account, configure it for POP access, and
use it for your sending chores. Gmail uses port 465 for SMTP,
which is not blocked.