OL2003 can't sent e-mail

[Joe McGuire]

Is anybody experiencing this problem with Comcast? Starting yesterday I am
unable to send any e-mail from OL 2003, although I can receive e-mail. When
I try to send I get this error message: "Task 'JWM-Comcast - Sending'
reported error (0x800CCC78): 'Unable to send the message. Please verify the
e-mail address in your account properties. The server responded: 530
Authentication Required.'" Of course I checked all the settings and even
spent around a half houront he phone with a Comcast tech who said he had no
idea how to fix this. A recent e-mail from another tech (I presume) says it
is an Outlook problem. It seems to have started at the same time as Comcast
modified its home page. If I bypass OL and go to my web mail box i can send
and receive with no problem. Any idea what is the problem?

 

[createwindow]

Dear Joe McGuire,

Most probably Comcast changed something. Turn on Outlook logging.
Tools / Options / Other (tab) / Advanced Options Tick Enable logging
(troubleshoting).

Try your connection and send again. Look at the log file it will be in
your temp folder. Open a command prompt and type %temp% & hit enter.
Proly it wil be Documents And Settings\ <user>\Local Settings\Temp <-
need to "show hidden files to see this.

Hope that helps.

CreateWindow
http://mymessagetaker.com
The while-you-were-out message program you have been looking for!

 

[Joe McGuire]

Thanks. The command did not work but I found the temp folder easly enough
anyway. I found what seems to be the glitch. Somehow OL is using an
obsolete e-mail address, one of several I had at Comcast and which I removed
a while ago. This would explain the otherwise puzzling instruction to check
my e-mail address. I can't find that "rogue" e-mail address anywhere in my
OL settings but it must be in OL somewhere. Any idea how I can correct it?

 

[Joe McGuire]

And meanwhile OL won't give up the valiant attempt to send the e-mails, so
the error message pops up every few minutes!

 

[Joe McGuire]

Just for fun I deleted the last remaining e-mail account and then re-created
it after closing and restarting OL. I got the same error message, thus
suggesting that the "rogue" e-mail address is planted somewhere.

 

[Brian Tillman]

Just for fun I deleted the last remaining e-mail account and then
re-created it after closing and restarting OL. I got the same error
message, thus suggesting that the "rogue" e-mail address is planted
somewhere.

A new mail profile should fix that problem, unless you have an undeliverable
read receipt in the Outbox (and you can't see those, normally).

 

[Joe McGuire]

I must be missing something crucial. After setting up a new Windows user
profile it appears I need to reinstall all my Microsoft Office software,
inclulding Outlook, all of which is already installed, not to mention pretty
much reconstructing most of my software--including trying to figure out
where Outlook Express is located so I can access this forum, and having
Windows create a whole lot of unwanted folders. When I try to shut down I
am told that others are using the computer, which is absurd. Meanwhile, to
submit this I have to restart the computer to get to my old profile. There
must be something wrong with OL (including a bad setting somewhere) since my
wife uses the same version of OL and does not have this problem. Is there
any way to actually find the problem? Is there a bad registry entry? The
log shows the bad e-mail address. It must be stored somewhere.

 

[Joe McGuire]

What I had described as a "rogue" e-mail address appeared in the "MAIL
FROM:" line in the log. That e-mial address now shows up as "<*****>" (5
asterisks).

2007.10.29 23:03:46 SMTP (smtp.comcast.net): [tx] MAIL FROM: <*****>
2007.10.29 23:03:46 SMTP (smtp.comcast.net): <rx> 530 Authentication
required

I assume that something I have been doing along the way modified that
address.

 

[Joe McGuire]

Success at last! Far simpler than creating a new profile I found that
merely adding a new e-mail account (same as the old, actually) to OL and
then removing the old one solved the problem. Still no idea why the problem
occured or exactly what it was but since the problem seems to be fixed the
question seems a little metaphysical. I am deleting the new profile I
created.

JWM

 

[Brian Tillman]

Success at last! Far simpler than creating a new profile I found that
merely adding a new e-mail account (same as the old, actually) to OL
and then removing the old one solved the problem. Still no idea why
the problem occured or exactly what it was but since the problem
seems to be fixed the question seems a little metaphysical. I am
deleting the new profile I created.

I never told you to create a new WIndows user profile. I said a new _mail_
profile. The Mail applet in Control Panel does that.