I can receive email but cannot send it.

J

Jeff Stephenson [MSFT]

Most of the time, this error is caused by failure to properly authenticate
to the outgoing server.

Yes, any relation with SP2 is likely just coincidence that about the time
you installed SP2 your ISP started requiring authentication...
 
G

Guest

Then why am I able to send emails when using other email programs (such as
Lydia Email Agent)? I am using the same server and the SMTP settings are
exactly the same. No authentication is required and therefore is not set up
for it. Any other suggestions?
 
J

Jeff Stephenson [MSFT]

Then why am I able to send emails when using other email programs (such as
Lydia Email Agent)? I am using the same server and the SMTP settings are
exactly the same. No authentication is required and therefore is not set up
for it. Any other suggestions?

Can you send email to the same recipient with the other programs? Usually
when authentication is required, the server will accept all mail for the
domain that it handles, but reject recipients in any other domain, so you
*will* be able to send to recipients in the domain with no authentication.

Humor us and try turning on authentication. If that doesn't work, could
you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and post
the OPMLog.log file after you get the error?
 
G

Guest

I think I may have solved it on my own. When I added Outlook and Port 25 to
the firewall settings, I restarted Outlook, but did not restart the computer
(nor was I prompted to do so). I accepted the result at face value.
Tonight, after booting up, I decided to test outlook express and it worked
fine. So I retested Outlook and now it works. So for everyone who has
performed the firewall settings and are still having a problem, try rebooting
your PC - even though Windows may NOT prompt you to do so.

While the problem is solved (for now), it seems rather frustrating to have
to go through so many steps just to send an email. You would think Microsoft
would have configured the firewall in SP2 to automatically configure itself
to permit email programs -- particularly it's own product -- to send and
receive messages without incident. They should remember that average user is
not computer savvy and is not likely to go messing around with firewall
settings.

Sorry, Jeff, I know you're just the messenger so I am not griping at you
directly! Thanks for all your help and input!

Denise
 
B

Brian Tillman

DeniseNY said:
While the problem is solved (for now), it seems rather frustrating to
have to go through so many steps just to send an email. You would
think Microsoft would have configured the firewall in SP2 to
automatically configure itself to permit email programs --
particularly it's own product -- to send and receive messages without
incident.

That, I think, is the exactly wrong thing to do. A firewall's purpose is to
block access in an out of a computer. The user of that computer is best
served by a firewall that allows nothing in or out but that can be adjusted
to suit the user's requirements under the user's strict control.
They should remember that average user is not computer
savvy and is not likely to go messing around with firewall settings.

In this modern day of computing threats, ignorance is not bliss. It
behooves each computer user to educate himself on the possibilities of
compromise. If you can't learn the basics of computer security, you
shouldn't be operating a computer any more than someone who can't learn the
basics of highway safety should ne operating an automobile.

I would agree, however, that the possibility of needing to adjust the
firewall should be more prominently displayed.
 
G

Guest

Thanks Brian. You were right.

I was able to ping the server, but unable to telnet to it. So I looked up
my ISP -- not the company that hosts my mail, but the real ISP, the folks who
let the house connect to the internet -- and found that they don't allow
third parties (e.g. my mail host) to use port 25.

Why I'd been able to use port 25 before installing Office's Service Pack 3,
but not after, is a mystery. But it's an academic one: I found the login
and password for the ISP (something I've never used, since we're broadband),
and put those in my "outgoing/SMTP authentication" fields. Now my mail sends
fine, and it still looks like it's coming from my third-party server.

Thanks again.

- Chris
 
J

Jeff Stephenson [MSFT]

You would think Microsoft would have configured the firewall in SP2 to
automatically configure itself to permit email programs -- particularly
it's own product -- to send and receive messages without incident.

While I'm not a lawyer, I believe that having the Windows firewall (part of
the operating system) know about Outlook (an application) would violate
Microsoft's consent agreement with the Department of Justice. My
understanding is that Windows is not allowed to know about anything except
the programs that ship with it (like Outlook Express) so as to provide a
level playing field for other companies that develop applications.

As to allowing just any "email" program to send, how do you tell a
legitimate email program from a virus trying to spread itself via email?
They both try to send through port 25. As Brian pointed out in another
post, the user is the only one that knows which programs are legitimate.
 
G

Guest

pegasus said:
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?
 
G

Guest

pegasus said:
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?
 
G

Guest

I am glad to know I am not alone in this but this is really starting to tick
me off. Charter (my ISP), Dell (who I purchased from) and Microsoft are all
basically telling me that it is the other's fault. I have read all 132
threads here and tried all the helpful insights and nothing corrected the
problem. I have tried emailing with the Firewall turned off and with my
AntiVirus disabled. It all started 3 weeks ago and actually sent for about
30 seconds yesterday (at another location, not connected at home-it hasn't
sent from here in about 2 weeks). Here are my particulars.

Running Windows XP (with SP2-currently completely updated))
Inspiron 600M
Office Basic Outlook 2003 (currently completely updated)
Vexira Anti-virus (currently completely updated)
Windows Firewall

Error messages when sending:

Task 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).’

Task Sending' reported error (0x800CCC60) : ‘Your outgoing (SMTP) e-mail
server has reported an internal error. If you continue to receive this
message, contact your server administrator or Internet service provider
(ISP). The server responded: +OK InterMail POP3 server ready.’

Task 'Sending' reported error (0x8004210B) : 'The operation timed out
waiting for a response from the sending (SMTP) server. If you continue to
receive this message, contact your server administrator or Internet service
provider (ISP).'

I get the same error messages with Outlook Express but an IT friend of mine
told me that would be expected since they are both MS products. I haven't
been able to down load any other software to test it (Eudora, etc.).

In SAFE MODE, Outlook will not even open (something about an error in
installation).

I have reinstalled Office at least 6 times.

I have reformatted my computer completely, twice.

Charter says they do not offer secured authentification and haven't changed
to it. They couldn't even offer it to me to try.

I tried Port 25, everything timed out. I switched to Port 110 and now it
quickly gives me the error messages and somtimes times out.

All my email settings are correct and Charter did not have an IP address for
me to try (smtp.charter.net is all they offer to customers). The tech
support said they do own their server and weren't getting from anyone else.
They also said that if I can connect through the Internet (using Internet
Explorer) but can't through Outlook it was an Outlook problem. They said the
connection works the same it just uses Explorer for it or Outlook (the
protocol and server connection is the same).

I think that is everything. If you can get me to send email then you are
the greatest.
 
K

Ken Slovak - [MVP - Outlook]

It doesn't sound like you need secure password authentication, it sounds
like you need to log into your server before you try to send. You might also
have to log on to receive before you send.

Your incoming server should be set to 110 unless told otherwise by the ISP.
Outgoing is 25, again unless the ISP tells you otherwise.

In your Outgoing Server tab check "My outgoing server (SMTP) requires
authentication". Leave "Use same settings as my incoming mail server"
selected.

If that doesn't work select the "Log on to incoming mail server before
sending mail".

See if that helps.
 
G

Guest

I have this exact same problem. One day it was working fine, the next,
without my changing the settings, it would no longer send. I have installed
other mail clients and determined that they work just fine. I've tried the
reinstall process as well, nothing seems to work.
 
G

Guest

This it the error message I got with your suggestions with Use same settings
as my incoming mail server" and "Log on to incoming mail server before
sending mail".

Send test e-mail message: The specified server was found, but there was no
response from the server. Please verify that the port and SSL information is
correct. To access these settings close this dialog, then click More
Settings and click on the Advanced tab.

On the test settings everything worked but the sending test message, which
has been the problem.



John
 
K

Ken Slovak - [MVP - Outlook]

Based on that error message you do need SSL, so you need to clear things up
with your ISP.

Unfortunately the code used in sending a message and the test send are
different, so it's not a very accurate diagnostic tool.
 
G

Guest

I am using Office Professional 2003 & Windows XP. For many days now I have
not been able to send e-mails via Outlook. Albeit that Outlook Express did
allow me to send and a new profile on the same computer also allowed me to
send via Outlook at least one from each. I like others who have reported
this problem deleted and re-established my Email Account detail, turned off
my router, computer etc but to no avail. My ISP provider denies
responsibility and advises that it is a Microsoft Problem. The main error
messages are as follows:

Your server has unexpectedly terminated the connection. Possible caues for
this include server problems, network problems or a long periof of
inactivity. or
Mail.bigpond.com sending reported error Ox800421OB. The oeration timed out
waiting for a response from the sending (SMTP) server. If you contiune to
receive this message, contact your server administrator or Internet Service
Provider. or
Task Mail bigpond.com. Sending reported error 0X800CCCOB. Unknown error.

Help please
 
B

Brian Tillman

Rowie said:
Your server has unexpectedly terminated the connection. Possible
caues for this include server problems, network problems or a long
periof of inactivity. or
Mail.bigpond.com sending reported error Ox800421OB. The oeration
timed out waiting for a response from the sending (SMTP) server. If
you contiune to receive this message, contact your server
administrator or Internet Service Provider.
http://www.google.com/search?q=0x8004210B

Task Mail bigpond.com. Sending reported error 0X800CCCOB. Unknown
error.

http://www.google.com/search?q=0X800CCC0B
 
B

Brian Tillman

pisces_312 said:
i have the same problem when it comes to sending out messages. i can
only receive them.

Chances are you're not properly authenticating to your outgoing server.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top