I can receive email but cannot send it.

[Nate]

Jeff, the actual error mssage is (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."

...K, I have talked with my server....and they say all of the default
settings that OUTLOOK uses, should connect me. I am using COX digital cable,
and am using GNX online as my server... What else could I possibly change
within outlook to make it match my server if there were somthing to change?
That is confusing. Becuase I am almost certain everything is inputed the
right way. And what could my isp have to do with this? And if I didn't have a
firewall, that shouldn't matter (I have put one up though now) So, I am stuck.
And what other questions should I be asking.

Thanks Again.
Nate

 

[Jeff Stephenson [MSFT]]

Your problem is that you're connecting to the Internet with one service
provider (COX) but trying to connect to the SMTP server of another provider
(GNX). What's happening is that COX is blocking your access to GNX's
server. This is unfortunately very common - their claim is that it reduces
spam, but I personally don't think that any reduction in spam that comes
from this is worth the impact on users. You might want to complain to COX
about this.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights

Jeff, the actual error mssage is (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."

..K, I have talked with my server....and they say all of the default
settings that OUTLOOK uses, should connect me. I am using COX digital cable,
and am using GNX online as my server... What else could I possibly change
within outlook to make it match my server if there were somthing to change?
That is confusing. Becuase I am almost certain everything is inputed the
right way. And what could my isp have to do with this? And if I didn't have a
firewall, that shouldn't matter (I have put one up though now) So, I am stuck.
And what other questions should I be asking.

Thanks Again.
Nate

 

[Ron Adams]

I have tried all of these fixes and still no email. The firewall in SP-2
will not let me add Outlook to the exeptions list. I am running Windows
Media Center with Office 2003 Pro. When I try to add Outlook to the
exceptions list it just says "Windows firewall cannot add Microsoft Office
Outlook 2003 to the list of exceptions". and that is all it says. I have 2
other computers one is XP home and the other is XP Pro both have SP-2 and I
have no trouble with those.

 

[Suzyc]

I've go the SAME problem. My error number is 554, and ISP
says it is not them. Tried the same things, and also
deleted and re-added my accounts, and added updates.
Nothing worked (yet). Any ideas?

 

[Jeff Stephenson [MSFT]]

ISPs always say it's not them...

What version of Outlook do you have? What is the complete text of the
error message you're getting? 554 is not a standard error code, so I have
no idea what your ISP is indicating...

 

[Dave Navarre]

I am also having this problem on one machine. It is running XP Pro and
Outlook 2003. I changed the firewall settings to include Outlook.exe, which
failed to change anything (I rebooted to make sure that it wouldn't be fixed
after a reboot). I uninstalled Service Pack 2, failed, rebooted, still
failed. I don't have another firewall installed. I know the problem is not
the account, because I set up a laptop right next to it and accessed the
account (XP Pro, not service pack 2, Outlook 2003).

Anything else it could be?

 

[Ernests]

I installed a Cox DSL service and a Linksys router and developed this
problem.... I looked up the smtp address for Cox in my area, updated Outlook,
an it worked... Pass is around...

Ernest M.

 

[DJaded]

This is redundant, but like apparently everybody else, I can receive mail but
not send. I am using Outlook 2003, I have not installed any service packs, I
do not have a Firewall and I am still connecting via a dail-up modem. I've
gotten to the point that the only "test" that fails is the SEND TEST MESSAGE:

UNABLE TO SEND TEST MESSAGE. PLEASE VERIFY THE E-MAIL ADDRESS FIELD

When I try to send an actual e-mail mewssage, it is returned as
UNDELIVERABLE -

Your message did not reach some or all of the intended recipients.

Subject: Setting up OUTLOOK 2003
Sent: 11/30/2004 10:05 PM

The following recipient(s) could not be reached:

'(e-mail address removed)' on 11/30/2004 10:05 PM
550 relaying to <[email protected]> prohibited by
administrator

I have sent this information to PeoplePC and their response was:

"...we would suggest you to contact support staff of Microsoft Outlook and
they can better assist you in this matter."

HELP!!!!!

 

[Brian Tillman]

This is redundant, but like apparently everybody else, I can receive
mail but not send. ....snip...
'(e-mail address removed)' on 11/30/2004 10:05 PM
550 relaying to <[email protected]> prohibited by
administrator

Usually caused by the sender (you) not properly authenticating to the
outgoing server. Fix this in the "Outgoing Server" tab of your account
properties pages.

 

[Chloe]

Yesterday I tried to send emails and I got an error message. I could receive
but not send. I tried all the usual things several times: turned off the
computer, turned off my router and cable modem, checked all my connections,
started fresh. The problem persists. Is this a problem with Outlook?

 

[Jeff Stephenson [MSFT]]

What version of Outlook do you have? What sort of mail account(s)? Do you
get an error message when you try to send? If so, what is the text?

 

[BrianJ]

I'm another victim of the "can't send" problem with Outlook 2000. Just
became a problem in the last few days. I'm on a Linksys wireless network
sharing a broadband connection over Comcast.

Read all the postings on this site and tried:
1. Turn off Norton and all other firewalls and anti-virus programs.
2. Put Outlook as an exception to Firewall
3. E-mailed Comcast support - they referred me to Microsoft.
4. E-mailed another Server account (Micorsoft's bCentral) and was referred
to Comcast.

None of the above attempts changed my situation. Still can't send e-mail
over Outlook 2000 (part of Office 200) but I can receive from Comcast and
from bCentral.

Three other people in my office using Outlook and our wireless network have
the same troubles.

Help????

 

[Jeff Stephenson [MSFT]]

I'm another victim of the "can't send" problem with Outlook 2000. Just
became a problem in the last few days. I'm on a Linksys wireless network
sharing a broadband connection over Comcast.

What happens when you try to send? Any error messages?

 

[fakeyjake]

I am having the same problem; started yesterday when messages are "sent",
they go into the outbox but never are sent. I do not get any error message,
and I have not made any changes to my outlook setup. I installed sp2 some
time ago, so this is not the problem. Help!

 

[Jeff Stephenson [MSFT]]

I am having the same problem; started yesterday when messages are "sent",
they go into the outbox but never are sent. I do not get any error message,
and I have not made any changes to my outlook setup. I installed sp2 some
time ago, so this is not the problem. Help!

Are the messages in the outbox in italics? If not, try opening them and
clicking on "Send" again. Not a long-term solution, I know, but it could
help get the mail out...

 

[Ingrid]

Please help...I also can receive e-mail, but cannot send. I have spent the
last several hours trying to figure out what is wrong. This is a home
computer so I don't have a network. I have tried Jordan's suggestion: I
fixed this problem by adding Outlook to the firewall exception list. Go toBut I cannot firnd the Firewall Tab. I have Outlook 2002 XP. Please help
if you have any suggestions.

 

[Jeff Stephenson [MSFT]]

Please help...I also can receive e-mail, but cannot send. I have spent the
last several hours trying to figure out what is wrong. This is a home
computer so I don't have a network. I have tried Jordan's suggestion: I
fixed this problem by adding Outlook to the firewall exception list. Go to
But I cannot firnd the Firewall Tab. I have Outlook 2002 XP. Please help
if you have any suggestions.

What version of Outlook do you have? Do you get an error message when you
try to send? If so, what is it?

 

[Brian Tillman]

Please help...I also can receive e-mail, but cannot send. I have
spent the last several hours trying to figure out what is wrong.

Are you properly authenticating to your outgoing server? In Outlook, click
Tools>Email Accounts>Next. Select your account. Click Change, then More
Settings, then the Outgoing Server tab. CHeck the box that says "My
outgoing server (SMTP) requires authentication"

This is a home computer so I don't have a network. I have tried
Jordan's suggestion: I fixed this problem by adding Outlook to the
firewall exception list. Go to
But I cannot firnd the Firewall Tab.

For Windows XP SP2, it's a tab on Control Panel>Security Center>Windows
Firewall

 

[Bill Bauman]

OK, I keep reading the replies from Microsoft, and I can't take it anymore.
There is clearly a problem with either Windows XP SP2, Outlook 2003 SP1, or
Exchange 2003, or some combination of the like.

I was running Exchange 2000 with Outlook 2003 and everything was sending
fine. My Exchange 2000 server was due to go end of life, so I installed a
new Exchange 2003 server, and now, SMTP is just broken. The only fix I've
derived is to disable all SMTP authentication. I've enbaled Relay for my
internal subnet and will just use VPN as my solution. But this is
ridiculous. Clearly authentication is broken in some manner.

Any ETA on a fix from Microsoft?

I'm willing to be if I go back to Outlook 2003 no SP, and Windows XP SP1 or
no SP1 or Windows 2000 Pro SP3, I won't have any problems. Anyone want to
take that bet?

-Bill Bauman

 

[Jeff Stephenson [MSFT]]

OK, I keep reading the replies from Microsoft, and I can't take it anymore.
There is clearly a problem with either Windows XP SP2, Outlook 2003 SP1, or
Exchange 2003, or some combination of the like.

No, in most cases ISPs have started requiring authentication and either
have not notified their users or the users didn't read the notification.
It has nothing to do with any of the products you mention.

I was running Exchange 2000 with Outlook 2003 and everything was sending
fine. My Exchange 2000 server was due to go end of life, so I installed a
new Exchange 2003 server, and now, SMTP is just broken.

How? What happens? Are your users connecting to Exchange via an Exchange
account or via POP3/SMTP?

The only fix I've derived is to disable all SMTP authentication. I've
enbaled Relay for my internal subnet and will just use VPN as my
solution. But this is ridiculous. Clearly authentication is broken in
some manner.

What sort of authentication are you using? Were you using that same form
when you were using Exchange 2000?