Outlook 2003 - Word 2003 as e-mail editor problem

  • Thread starter Thread starter Very Frustated
  • Start date Start date
V

Very Frustated

I am using Outlook 2003 as my e-mail client. Since about 2 months ago I am
not able to SEND my e-mails using POP3 account if "Use Microsoft Office Word
2003 to edit e-mail messages" option is checked or if I use mail-merge
feature in Word.

I have reinstalled my system and all the applications but the problem still
persists.

Both Windows XP Pro and Office 2003 Pro are fully updated.

Please HELP.
 
Very Frustated said:
I am using Outlook 2003 as my e-mail client. Since about 2 months ago
I am not able to SEND my e-mails using POP3 account if "Use Microsoft
Office Word 2003 to edit e-mail messages" option is checked or if I
use mail-merge feature in Word.

What happens when you try?
 
Thanks for taking interest in this problem, I am sorry for not supplying the
full information earlier.

Anyway, "Outlook Send and Receive Progress" idles, it reports that it is
processing but the progress bar is not moving, until it times out and
reports an error 0x8004210B it also reports 0x800CCC67 afterwards.

If I do not use Word as an e-mail editor everything works fine!
 
Very Frustated said:
Thanks for taking interest in this problem, I am sorry for not
supplying the full information earlier.

Anyway, "Outlook Send and Receive Progress" idles, it reports that it
is processing but the progress bar is not moving, until it times out
and reports an error 0x8004210B it also reports 0x800CCC67 afterwards.

If I do not use Word as an e-mail editor everything works fine!

The first message indicated that something is interfering with the
communications between the mail client (Outlook) and the mail server. The
second seems to indicate unexpected commands passing between the two. The
most likely cause is that there is an add-in, like and antivirus or -spam
scanner sitting between Outlook and the server scanning messages passing
between the two. If you have one, disable the message scanning feature and
try again. In addition, you should try lengthening the server timeout value
found on the Advanced tab of your account properties pages. Some mail
scanners need to be uninstalled and reinstalled without the mail integration
features in order to truly get them to stop interfering. Symantec's
products are examples.
 
That is what exactly what I thought initially. I had Symantec Internet
Security and since after uninstalling and reinstalling it along with MS
Office the problem didn't go away, I wiped and reinstalled my C partition to
make sure it is gone from my computer.

Currently I have no anti-virus of anti-spam software installed - only
Windows XP Pro and Office 2003 Pro (yes I know it is dangerous but I have no
choice since I have been trying to figure this problem for 5 days now).

As I mentioned before, if I turn off MS Word as an e-mail aditor feature
everything works fine, my hunch is that some update or feature in Win
Firewall or Outlook Anti-Spam is causing this. I have already tried
lengthening the timeout but with no success.

Any other ideas? I am ready to try anything since I can not figure why is
this happening even on a clean install.

Very thankful, VEEERY Frustated
 
Very Frustated said:
Currently I have no anti-virus of anti-spam software installed - only
Windows XP Pro and Office 2003 Pro (yes I know it is dangerous but I
have no choice since I have been trying to figure this problem for 5
days now).

You should certainly have an antivirus program installed, just without any
mail integration.
As I mentioned before, if I turn off MS Word as an e-mail aditor
feature everything works fine, my hunch is that some update or
feature in Win Firewall or Outlook Anti-Spam is causing this. I have
already tried lengthening the timeout but with no success.

If it happens with Word but not without, then check for any Word add-ins.
Create a new Normal.dot to see if that helps.
 
How do I create a new Normal.dot?

BTW I noticed that even without Word the messages won't go through if I add
an attachment.

Also, outlook reports error 0x800CCC0F much before the timeout setting (3
minutes). As mentioned before it also reports 0x800CCC67 afterwards.
 
Very Frustated said:
How do I create a new Normal.dot?

Enable searching hidden files and folders, search for the file and delete
it. Word will recreate it when next it runs.
Also, outlook reports error 0x800CCC0F much before the timeout setting (3
minutes). As mentioned before it also reports 0x800CCC67 afterwards.

Normally I'd say try creating a new mail profile, but since you wiped your
hard drive and reinstalled everything, obviously you did that. I'm afraid
I'm at a loss at this point.
 
Brian, thank you for all your help. Even though we didn't solve the problem
I appreciate your effort. I will keep trying and if there is new information
or if I somehow figure out the solution I will let you know. I was 100% sure
it was Word but now that I can't send attachments it is a whole other story.
Since I am convinced that MS update brought this about (I believe I
eliminated most of the other possible causes by reinstalling the system, and
also creating a new profile for Outlook)do you know how I can turn off spam
filters in Outlook to test this theory?
 
Very Frustated said:
Since I am convinced that MS
update brought this about (I believe I eliminated most of the other
possible causes by reinstalling the system, and also creating a new
profile for Outlook)do you know how I can turn off spam filters in
Outlook to test this theory?

The only way I know is with Actions>Junk E-mail>Junk E-mail Options.
 
Hey Brian,

well I figured out the problem and it wasn't Outlook related. As ashamed as
I am to admit, it was a "user-error". My router settings were not in sync
with updated ISP server information. What really threw me off was the fact
that certain e-mails went through regardless, and others didn't. Go figure :)


Again thank you for all your help.
 
I'm having problems similar to yours. Cna you tell me what router settings
were causing you grief?

Thanks!
 
My problem turned out not to ahve anything to do with router settings - it
was a set of bad Tcpip settings in the registry. Problem solved.
 
Back
Top