Outlook 2003 cannot send email

[F. Edwin Felty]

This problem started yesterday morning about 1000. Previously, Outlook has
worked without fail for about 6 months, when I had to replace a failing
harddrive with a clean install. If I try to send an email, the send fails
with the error 0x80042109. If I send a 'test your settings' email, I get a
more verbose message that says the server was found, but did not respond.
Now, the details:

I found 2 articles about the error 0x80042109 that talked about 'being on
the MSN network and trying to send through another system', but I have no
connection to MSN.

I have my own domain name and email address package through 'Godaddy'.

There are two other email addresses in this domain/email package that are
unaffected.

Yesterday I spent about 2 hours on the phone with 'Godaddy' tech support,
examined all settings, tried alternate port of 587 and 3535 for SMTP and
finally, the tech said I should call my ISP. The theory being that, since
everything was in order, Comcast must be blocking my access. Since I'm not
using Comcast's email system, I found this puzzling, but called them anyway.

Comcast checked the line and pinged my modem and pronounced it 'not their
problem'.

I have run a 'detect and repair' that 'Completed Successfully' and a
'scanpst.exe' that found 6 errors that it repaired, with no change in the
problem.

I disables the windows firewall and the Avast antivirus v. 4.8 and still
doesn't work.
I waited overnight to see if the problem disappeared as glitches sometime
do, but no joy.

Interestingly enough, Outlook automatically does a 'Send/Receive' at 5
minute intervals, and the email I had been trying to send for 24 hours, went
out at 0959. I tried to send another test email, and clunk, broke again.

Doing an 'Outlook /safe' does not solve the problem and I finally
uninstalled Office 2003, I thought completely. I then turned off the
computer and disconnected the power for 5 minutes.

I then turned the computer back on and reinstalled Office 2003, and much to
my surprise, all my settings were still there, so I really didn't get a
complete uninstall.

At this point I am completely out of ideas. If anyone has seen anything like
this (and knows the solution), any suggestions would be greatly appreciated.

Thanks again for listening,

Eddie in Loveland

"A television can insult your intelligence, but nothing rubs it in like a
computer."

PS. Sorry about the crosspost...I'm desperate!

 

[VanguardLH]

This problem started yesterday morning about 1000. Previously, Outlook has
worked without fail for about 6 months, when I had to replace a failing
harddrive with a clean install. If I try to send an email, the send fails
with the error 0x80042109. If I send a 'test your settings' email, I get a
more verbose message that says the server was found, but did not respond.
Now, the details:

I found 2 articles about the error 0x80042109 that talked about 'being on
the MSN network and trying to send through another system', but I have no
connection to MSN.

I have my own domain name and email address package through 'Godaddy'.

There are two other email addresses in this domain/email package that are
unaffected.

Yesterday I spent about 2 hours on the phone with 'Godaddy' tech support,
examined all settings, tried alternate port of 587 and 3535 for SMTP and
finally, the tech said I should call my ISP. The theory being that, since
everything was in order, Comcast must be blocking my access. Since I'm not
using Comcast's email system, I found this puzzling, but called them anyway.

Comcast checked the line and pinged my modem and pronounced it 'not their
problem'.

I have run a 'detect and repair' that 'Completed Successfully' and a
'scanpst.exe' that found 6 errors that it repaired, with no change in the
problem.

I disables the windows firewall and the Avast antivirus v. 4.8 and still
doesn't work.
I waited overnight to see if the problem disappeared as glitches sometime
do, but no joy.

Interestingly enough, Outlook automatically does a 'Send/Receive' at 5
minute intervals, and the email I had been trying to send for 24 hours, went
out at 0959. I tried to send another test email, and clunk, broke again.

Doing an 'Outlook /safe' does not solve the problem and I finally
uninstalled Office 2003, I thought completely. I then turned off the
computer and disconnected the power for 5 minutes.

I then turned the computer back on and reinstalled Office 2003, and much to
my surprise, all my settings were still there, so I really didn't get a
complete uninstall.

At this point I am completely out of ideas. If anyone has seen anything like
this (and knows the solution), any suggestions would be greatly appreciated.

Thanks again for listening,

Eddie in Loveland

"A television can insult your intelligence, but nothing rubs it in like a
computer."

PS. Sorry about the crosspost...I'm desperate!

Probably could've been a much shorter post if you just had showed the
complete error message. No, not a description, summary, paraphrase, or
diagnosis of the error message but just the error message itself in
full. Copy the error message or copy it verbatim (although you might
want to munge your username, if shown).

 

[F. Edwin Felty]

Probably could've been a much shorter post if you just had showed the
complete error message. No, not a description, summary, paraphrase,
or diagnosis of the error message but just the error message itself in
full. Copy the error message or copy it verbatim (although you might
want to munge your username, if shown).

OK:

When sending an email;


Task 'Ed's Mail - Sending' reported error (0x80042109) : 'Outlook is unable
to connect to your outgoing (SMTP) e-mail server. If you continue to receive
this message, contact your server administrator or Internet service provider
(ISP).'

When sending a 'Test your Email settings:

Send test email: The specified server was found, but there was no responce
from the server. Please verify that the port and SSL information is correct.
To access these settings close this dialogue, click on More Settings, and
click on the Advanced tab. ...and further

Find outgoing mailserver (SMTP): Outlook could not connect to the outgoing
mailserver (SMTP). The problem could be the server name or port, or your
server may not support SSL. Verify your port and SSL settings in More
Settings under the Advanced tab.

There ya' go. It would be easier to include the exact messages, if it were
possible to copy and paste them, but Microsoft has rendered this impossible.
For those of use that type with two fingers, that makes it difficult.

Eddie in Loveland

"Money can't buy happiness, but it sure makes misery easier to live with."

 

[J R Smith]

I just went through this same problem. After much investigation, it seems that Comcast cut off my outgoing emails because one of them had supposedly sent a virus.

I have several email addresses which had used different SMTP's. Some were from a local ISP that hosts some websites, and some used Comcast. When it was all said and done, I had to use use the Comcast SMTP on everything.

They have instructions on the Comcast website about changing the SMTP port to 587, but it is not quite that simple. Under Tools, Email Accounts, Change, More Settings, Outgoing Server, check "My Server (SMTP) requires Authecantition", Check "Log On Using" and add your "Comcast User Name and Password". Go to Advanced and change the outgoing SMTP to 587. Click OK and do a "Test Account Setting"

Hopefully this will solve your problem.


fef wrote on Sun, 29 June 2008 08:2

 

[F. Edwin Felty]

I just went through this same problem. After much investigation, it
seems that Comcast cut off my outgoing emails because one of them had
supposedly sent a virus.

I have several email addresses which had used different SMTP's. Some
were from a local ISP that hosts some websites, and some used
Comcast. When it was all said and done, I had to use use the Comcast
SMTP on everything.

They have instructions on the Comcast website about changing the SMTP
port to 587, but it is not quite that simple. Under Tools, Email
Accounts, Change, More Settings, Outgoing Server, check "My Server
(SMTP) requires Authecantition", Check "Log On Using" and add your
"Comcast User Name and Password". Go to Advanced and change the
outgoing SMTP to 587. Click OK and do a "Test Account Setting"

Hopefully this will solve your problem.

OK...thanks for the reply. I have found that email accounts set up on other
systems (my sister has a HughesNet satellite west of town) using HughesNet's
SMTP and POP server's everything works fine...at least so far.

Thanks Again,

Eddie in Loveland

"I'm old enough to know that I don't know a thing ...." - Anon.

 

[N. Miller]

J R Smith wrote:

OK...thanks for the reply. I have found that email accounts set up on other
systems (my sister has a HughesNet satellite west of town) using HughesNet's
SMTP and POP server's everything works fine...at least so far.

If Comcast has cut off your access to port 25, you need to revisit your
Godaddy account, and figure out how to configure it for use with an
alternate port. Godaddy has a way to set that up just for ISPs which block
outbound port 25. Most third party E-mail Service Providers have ways to
access their message submission servers on some port other than port 25. I
have not used outbound port 25, except for certain tests, in a long time.
All of the message submission servers I use on a regular, or even irregular,
basis allow access on either port 465 w/SSL, or port 587 w/ or w/o STARTTLS
(aka, "TLS").

 

[F. Edwin Felty]

If Comcast has cut off your access to port 25, you need to revisit
your Godaddy account, and figure out how to configure it for use with
an alternate port. Godaddy has a way to set that up just for ISPs
which block outbound port 25. Most third party E-mail Service
Providers have ways to access their message submission servers on
some port other than port 25. I have not used outbound port 25,
except for certain tests, in a long time. All of the message
submission servers I use on a regular, or even irregular, basis allow
access on either port 465 w/SSL, or port 587 w/ or w/o STARTTLS (aka,
"TLS").

Thanks for the Reply...I worked on this very problem yersteday wirh Godaddy
and tried alternate ports 80, and 3535 for SMTP, but it still doesn't work.
I haggled some more with Comcast yesterday afternoon about the question of
port 25 being blocked and they said it was not being blocked, so as a test I
set up an SMTP account on their servers and it works fine. Now I'm left with
a reasonable certainty that something has happened to this install of this
OS and/or Outlook 2003. I'm building a new box as I have the money to buy
the parts and should be up and running by the end of August, so I think I
will let things ride as they are. I can send on Comcast and receive through
my Godaddy account for now.

BTW, I've read your posts often over at GRC and have learned a lot. Thanks
again for that.

Eddie in Loveland

"You know what I did before I got married? Anything I wanted to. - Henny
Youngman

 

[James Truelove]

This problem started yesterday morning about 1000. Previously, Outlook has
worked without fail for about 6 months, when I had to replace a failing
harddrive with a clean install. If I try to send an email, the send fails
with the error 0x80042109. If I send a 'test your settings' email, I get a
more verbose message that says the server was found, but did not respond.
Now, the details:

I found 2 articles about the error 0x80042109 that talked about 'being on
the MSN network and trying to send through another system', but I have no
connection to MSN.

I have my own domain name and email address package through 'Godaddy'.

There are two other email addresses in this domain/email package that are
unaffected.

Yesterday I spent about 2 hours on the phone with 'Godaddy' tech support,
examined all settings, tried alternate port of 587 and 3535 for SMTP and
finally, the tech said I should call my ISP. The theory being that, since
everything was in order, Comcast must be blocking my access. Since I'm not
using Comcast's email system, I found this puzzling, but called them
anyway.

Comcast checked the line and pinged my modem and pronounced it 'not their
problem'.

I have run a 'detect and repair' that 'Completed Successfully' and a
'scanpst.exe' that found 6 errors that it repaired, with no change in the
problem.

I disables the windows firewall and the Avast antivirus v. 4.8 and still
doesn't work.
I waited overnight to see if the problem disappeared as glitches sometime
do, but no joy.

Interestingly enough, Outlook automatically does a 'Send/Receive' at 5
minute intervals, and the email I had been trying to send for 24 hours,
went out at 0959. I tried to send another test email, and clunk, broke
again.

Doing an 'Outlook /safe' does not solve the problem and I finally
uninstalled Office 2003, I thought completely. I then turned off the
computer and disconnected the power for 5 minutes.

I then turned the computer back on and reinstalled Office 2003, and much
to my surprise, all my settings were still there, so I really didn't get a
complete uninstall.

At this point I am completely out of ideas. If anyone has seen anything
like this (and knows the solution), any suggestions would be greatly
appreciated.

Thanks again for listening,

Eddie in Loveland

"A television can insult your intelligence, but nothing rubs it in like a
computer."

PS. Sorry about the crosspost...I'm desperate!

Daft question maybe but presume you have ticked the box "My server requires
authentication" in outgoing server settings?

 

[F. Edwin Felty]

Daft question maybe but presume you have ticked the box "My server
requires authentication" in outgoing server settings?

Yep...been there, done that.

Eddie in Loveland

"You know what I did before I got married? Anything I wanted to. - Henny
Youngman

 

[N. Miller]

Thanks for the Reply...I worked on this very problem yersteday wirh Godaddy
and tried alternate ports 80, and 3535 for SMTP, but it still doesn't work.
I haggled some more with Comcast yesterday afternoon about the question of
port 25 being blocked and they said it was not being blocked, so as a test I
set up an SMTP account on their servers and it works fine. Now I'm left with
a reasonable certainty that something has happened to this install of this
OS and/or Outlook 2003.

I am not at my sister's, now, so no way to test 'smtp.comcast.net' for
methods of access. I know of three.

OTOH, if you can't get Outlook to work with GoDaddy, I am not so sure it
would be an Outlook problem; especially if the same installation works with
the Comcast servers.

What happens when you open a command prompt and try to access the GoDaddy
server using a Telnet command? Since access to Comcast works, you can see
what a proper response should look like by typing, 'telnet smtp.comcast.net
25' at the prompt.

 

[F. Edwin Felty]

I am not at my sister's, now, so no way to test 'smtp.comcast.net' for
methods of access. I know of three.

OTOH, if you can't get Outlook to work with GoDaddy, I am not so sure
it would be an Outlook problem; especially if the same installation
works with the Comcast servers.

What happens when you open a command prompt and try to access the
GoDaddy server using a Telnet command? Since access to Comcast works,
you can see what a proper response should look like by typing,
'telnet smtp.comcast.net 25' at the prompt.

Ok...I did that and took note of the response. When I trid the same with the
Godaddy SMTP server, I got:

Connecting to smtpout.secureserver.net...Could not open the connection to
the host on port 25: Connect failed

I confess that I don't know anything about telnet, but it seems to
demonstrate that the problem is with the Godaddy servers...yes??

 

[F. Edwin Felty]

I am not at my sister's, now, so no way to test 'smtp.comcast.net' for
methods of access. I know of three.

OTOH, if you can't get Outlook to work with GoDaddy, I am not so sure
it would be an Outlook problem; especially if the same installation
works with the Comcast servers.

What happens when you open a command prompt and try to access the
GoDaddy server using a Telnet command? Since access to Comcast works,
you can see what a proper response should look like by typing,
'telnet smtp.comcast.net 25' at the prompt.

I called Godaddy and they want a similar test from another location. Also, I
just discovered that I cannot get to www.godaddy.com , I get an IE7 cannot
display the page error. This justs get weirder the longer it goes on!!

 

[Brian Tillman]

Ok...I did that and took note of the response. When I trid the same
with the Godaddy SMTP server, I got:

Connecting to smtpout.secureserver.net...Could not open the
connection to the host on port 25: Connect failed

I confess that I don't know anything about telnet, but it seems to
demonstrate that the problem is with the Godaddy servers...yes??

It is unlikely that Comcast and GoDaddy allow connections to port 25.

 

[F. Edwin Felty]

It is unlikely that Comcast and GoDaddy allow connections to port 25.

Actually, they do, but after reading Mr. Smith's last recommendation and
thinking for a while, I did a quick and dirty install of XP Pro SP3 on
another logical drive. As soo as it was finished I retried the telnet
excercise and , lo and behold, I can telnet both Comcast AND Godaddy. I can
now get to their website too. It seems that there is a problem of some kind
on my system that only affects Godaddy's SMTP server and website so that I
can't get there from here. Worse, today this box is hard freezing about
every 10 minutes and requires a power off reboot to get going again. Looks
like I'm doing a wipe and reinstall today. Gotta go, time running out!!

 

[N. Miller]

It is unlikely that Comcast and GoDaddy allow connections to port 25.

Eh? Surely not Comcast!

| C:\Documents and Settings\User>telnet smtp.comcast.net 25
| Connecting To smtp.comcast.net...
| 220 OMTA09.emeryville.ca.mail.comcast.net comcast ESMTP server ready
| quit
| 221 2.0.0 OMTA09.emeryville.ca.mail.comcast.net comcast closing connection
|
|
| Connection to host lost.

Sure looks like a successful connection to Comcast from where I sit. The
only problem is that Comcast requires SMTP AUTH to actually use the
connection, and I don't have a Comcast account.

| C:\Documents and Settings\User>telnet smtpout.secureserver.net 25
| Connecting To smtpout.secureserver.net...
| 220 smtpauth16.prod.mesa1.secureserver.net ESMTP
| quit
| 221 Good bye.
|
|
| Connection to host lost.

Oops. Looks like GoDaddy is allowing port 25 access as well. I have a domain
registered with them, but never took the time to set up email, so once
again, I can't use that connection.

 

[N. Miller]

N. Miller wrote:

I called Godaddy and they want a similar test from another location. Also, I
just discovered that I cannot get to www.godaddy.com , I get an IE7 cannot
display the page error. This justs get weirder the longer it goes on!!

I am connecting to the Internet through an ATTIS ('at&t Yahoo! HSI)
connection. I get the following:

For Comcast:

| C:\Documents and Settings\User>telnet smtp.comcast.net 25
| Connecting To smtp.comcast.net...
| 220 OMTA09.emeryville.ca.mail.comcast.net comcast ESMTP server ready
| quit
| 221 2.0.0 OMTA09.emeryville.ca.mail.comcast.net comcast closing connection
|
|
| Connection to host lost.

For GoDaddy:

| C:\Documents and Settings\User>telnet smtpout.secureserver.net 25
| Connecting To smtpout.secureserver.net...
| 220 smtpauth16.prod.mesa1.secureserver.net ESMTP
| quit
| 221 Good bye.
|
|
| Connection to host lost.

It sounds like something may be FUBAR on your end. If Comcast were imposing
an outbound port 25 block, you'd fail to connect to 'smtp.comcast.net' using
port 25; only port 465, or port 587 would work.

Rules based personal firewalls can cause strange problems. I used to use
Kerio PFW 2.1.5. It had a bug which caused problems when the ruleset
exceeded 150 lines, or so; the rules would become scrambled causing
connectivity problems.

 

[F. Edwin Felty]

I am connecting to the Internet through an ATTIS ('at&t Yahoo! HSI)
connection. I get the following:

For Comcast:


For GoDaddy:


It sounds like something may be FUBAR on your end. If Comcast were
imposing an outbound port 25 block, you'd fail to connect to
'smtp.comcast.net' using port 25; only port 465, or port 587 would
work.

Rules based personal firewalls can cause strange problems. I used to
use Kerio PFW 2.1.5. It had a bug which caused problems when the
ruleset exceeded 150 lines, or so; the rules would become scrambled
causing connectivity problems.

Yep...as I posted earlier, a clean install of XP Pro SP3 and I can telnet to
both on port 25. The only firewall I'm using is the built in and Avast v.
4.8. The only thing I've installed lately, was Spywareblaster to see how it
works, and that was about a week ago. Unfortunately, something is definitly
FUBAR here. Well, since I'm just holding on till I can get the new box
running, I think i'll just use Comcast for SMTP for the duration (about two
months). If something happens and I can't Recieve, then I will have to do
something about it. Thanks for your help, I really appreciate your time and
trouble.

Thanks again,

Eddie in Loveland

Happiness: A good cigar, a good meal, a good cigar and a good woman -- or a
bad woman; it depends on how much happiness you can handle. -- George Burns

 

[Dave R]

OK to make it a little weirder, I have been searching this topic too. I have
'all of a sudden' started to experience outgoing email problems. I am
receiving a different error - task my.email - sending' reported error
(0x800CCC13) : unable to connect to the network. Check your network
connection or modem. OK - I tried uninstalling Norton Internet (which didn't
help) I tried uninstalling Outlook 2003 and re-installing (which didn't
help). I have several accounts in Outlook which will receive email but will
not let me send out. I tried sending from three different accounts in
Outlook 2003 and I get the same message. OK it gets weirder - I downloaded
Microsoft Live Mail and installed my accounts and all accounts are
functional. This isn't a Go-Daddy issue, nor is it an Norton issue. I left
an email in the outbox and it was sent to an AOL address. It sends me an
email that either reads 'RSET' or 'QUIT' in it. I tried the Outlook repair
tool which also didn't fix it. Ideas?

 

[Brian Tillman]

OK to make it a little weirder, I have been searching this topic too.
I have 'all of a sudden' started to experience outgoing email
problems. I am receiving a different error - task my.email -
sending' reported error (0x800CCC13) : unable to connect to the
network. Check your network connection or modem. OK - I tried
uninstalling Norton Internet (which didn't help) I tried uninstalling
Outlook 2003 and re-installing (which didn't help). I have several
accounts in Outlook which will receive email but will not let me send
out. I tried sending from three different accounts in Outlook 2003
and I get the same message. OK it gets weirder - I downloaded
Microsoft Live Mail and installed my accounts and all accounts are
functional. This isn't a Go-Daddy issue, nor is it an Norton issue.
I left an email in the outbox and it was sent to an AOL address. It
sends me an email that either reads 'RSET' or 'QUIT' in it. I tried
the Outlook repair tool which also didn't fix it. Ideas?

Did you apply last Tuesday's updates? At least one of them seems to cause
problems like this.

 

[Dave R]

Yes I have been faithful on doing all the updates. I believe the problem
started about June 21st.