Gary VanderMolen said:Can you post the exact error message?
--
Gary VanderMolen [MS-MVP WLM]
Boomer said:I just tried it & it doesn't make any difference. It still won't send. At
this point I'm not in a real hurry to get it working but I would like it
someday when I take my next vacation. I can only imagine how some people
who rely on email for their businesses must feel.
Gary VanderMolen said:Comcast is the only ISP I know who offers port 587 for SMTP
yet does not permit it to be used outside of its network.
Try changing the SMTP port to 465, and on that same screen also
select the SSL option for the outgoing mail server.
--
Gary VanderMolen [MS MVP-WLM]
I did not have a detailed problem statement or copy of an error
message from you, but now that you mention "traveling",
this brings up an entirely different issue. Was that your problem
all along, you could not send while away from home?
That issue has very little to do with your email program.
Nearly all Internet connection providers will block attempts to
access port 25 SMTP if that server belongs to a different network.
It is an anti-spamming measure. There are four workarounds:
1. Use webmail for sending when away from home.
I first use the Windows mail when away from my homw server thinking
that it was sending because I got a copy in my sent folder.
2. Use a port other than '25' for SMTP, if your mail provider has a
provision for that. Typical alternate ports are 587 and 465.
I used 25 as instructed by the Comcast tech which didn't work & have
since tried 587 (but not 465) with the same results.
3. Get a free Gmail account, configure it for POP access, and
use it for your sending chores.
I guess it a posibitliy if all else fails.
4. Use the SMTP server belonging to your temporary connection.
Boomer said:"The connecton to the server had failed. Account 'mail.comcast.net',
server:'smtp.comcast.net',Protocol:SMTP,Secure (SSL),Yes, Socet Error:10060,
Error Number:0x800CCC0E"
Gary VanderMolen said:Can you post the exact error message?
--
Gary VanderMolen [MS-MVP WLM]
Boomer said:I just tried it & it doesn't make any difference. It still won't send. At
this point I'm not in a real hurry to get it working but I would like it
someday when I take my next vacation. I can only imagine how some people
who rely on email for their businesses must feel.
Comcast is the only ISP I know who offers port 587 for SMTP
yet does not permit it to be used outside of its network.
Try changing the SMTP port to 465, and on that same screen also
select the SSL option for the outgoing mail server.
--
Gary VanderMolen [MS MVP-WLM]
I did not have a detailed problem statement or copy of an error
message from you, but now that you mention "traveling",
this brings up an entirely different issue. Was that your problem
all along, you could not send while away from home?
That issue has very little to do with your email program.
Nearly all Internet connection providers will block attempts to
access port 25 SMTP if that server belongs to a different network.
It is an anti-spamming measure. There are four workarounds:
1. Use webmail for sending when away from home.
I first use the Windows mail when away from my homw server thinking
that it was sending because I got a copy in my sent folder.
2. Use a port other than '25' for SMTP, if your mail provider has a
provision for that. Typical alternate ports are 587 and 465.
I used 25 as instructed by the Comcast tech which didn't work & have
since tried 587 (but not 465) with the same results.
3. Get a free Gmail account, configure it for POP access, and
use it for your sending chores.
I guess it a posibitliy if all else fails.
4. Use the SMTP server belonging to your temporary connection.