I'm having an odd problem with outgoing email in Outlook 2003.

I just got a new laptop w/XP Pro and loaded the MS Office Standard Suite w/SP1. I also downloaded and installed Office SP3.



I set up Outlook email w/all my POP3 settings and tested the settings in Outlook -- all fine.

Incoming email is no problem. However for some outgoing emails, I get an immediate (and I mean instantaneous) bounce-back message that looks like the following:

Your message did not reach some or all of the intended recipients.
Subject: Test
Sent: 2/5/2010 12:13 PM
The following recipient(s) could not be reached:
sthelsey@optonline.net on 2/5/2010 12:13 PM
None of your e-mail accounts could send to this recipient.

The problem seems to be specific to certain email addresses. Some addresses I send to are fine; others get that instant bounce back. And there seems to be no domain patterns. For example, some gmail addresses work, others don't.

To check to make sure it's not my ISP or settings, I set up Outlook Express w/the same settings and all emails went out flawlessly -- no bounce back issue.

What's curious is how quickly the emails bounce back. It's not like it's traveling to the recipient, and being processed, and then returned. It's like it's being immediately rejected.

I've uninstalled and re-installed Outlook 2003 and SP3 to no avail. I also did a system restore to an earlier point to see if some software I loaded might be causing a conflict, but the problem persists. I also disbaled my anti-virus software...problem still persists. Anyone have any idea what the problem could be?

Hi Mark,
I am having a similar problem with Outlook 2007 after changing to Win 7. This is what I wrote on another forum but no takers yet:
Outlook 2007 &Win 7.
I am having problems sending emails to some addresses and get this message from "System Administrator":
Your message did not reach some or all of the intended recipients.

Subject: FW: Election
Sent: 07/02/2010 16:54

The following recipient(s) cannot be reached:

Where does this come from?
Not Norton because it does it with NIS uninstalled.
Not ISP because it doesn't happen on my XP laptop.
It's really frustrating because my correspondence is now split between my PC and my laptop.
P.S. It tries all three of the accounts I have on Outlook and the failure message comes back to a different account to that which sent it.

Thanks for the validation -- at least I know I'm not going crazy. Wondering if it's worth the $39.99 MS charges for a support chat for Outlook 2003. Are they good at disgnosisng and fixing complex issues like this?

Have you tried to send the same email to reachable and unreachable email addresses?

Do you think which returns the error, your email server or outlook? The error message seems generated by your email server, if so, my wild guess is your email doesn't like your email, which could suggest an improper header format. I'm wondering if your outlook has actually talked to your server for these unreachable emails.

Hi Matrix,
Yes the same test message sent many, many times to "good" and "bad" addresses and there seems to be no common factor on the failed ones.
I am convinced it is not my email server or why could I get them through to same addresses from laptop running XP.
I think failure message is from operating system.
Note that it always tries all my accounts and then records failure - I have an event log if anyone can decipher it.

Please post your event log file, maybe someone can help.

Hi Mark,
It might be the only way but is there a time limit? Before ruling Norton out, I spent hours on the phone doing various test emails; uninstalling re-installing etc. so be ready for a big phone bill.
By the way, the other aspect is not being able to do a clean un-install for Office although you may be better placed to do that on XP. That is what I would try first in your position. Unfortunately the MS procedure for clean uninstall doesn't seem to work on Win 7

Hi Matrix- we can but hope, here it is:

2010.01.26 21:00:05 David's Sapo Email: Synch operation started (flags = 00000001)
2010.01.26 21:00:05 David's Sapo Email: UploadItems: 1 messages to send
2010.01.26 21:00:05 SMTP (smtp.sapo.pt): Begin execution
2010.01.26 21:00:05 SMTP (smtp.sapo.pt): End execution
2010.01.26 21:00:06 David's Sapo Email: FinishSend for AcctID 18 , now stamped it with AcctID 19 .
2010.01.26 21:00:06 David's Sapo Email: ReportStatus: RSF_COMPLETED, hr = 0x00000000
2010.01.26 21:00:06 David's Sapo Email: Synch operation completed
2010.01.26 21:00:06 Sue's Sapo Email: Synch operation started (flags = 00000001)
2010.01.26 21:00:06 Sue's Sapo Email: UploadItems: 1 messages to send
2010.01.26 21:00:06 SMTP (smtp.sapo.pt): Begin execution
2010.01.26 21:00:06 SMTP (smtp.sapo.pt): End execution
2010.01.26 21:00:06 Sue's Sapo Email: FinishSend for AcctID 19 , now stamped it with AcctID 20 .
2010.01.26 21:00:06 Sue's Sapo Email: ReportStatus: RSF_COMPLETED, hr = 0x00000000
2010.01.26 21:00:06 Sue's Sapo Email: Synch operation completed
2010.01.26 21:00:06 Bluebottle Email: Synch operation started (flags = 00000001)
2010.01.26 21:00:06 Bluebottle Email: UploadItems: 1 messages to send
2010.01.26 21:00:06 SMTP (smtp.bluebottle.com): Begin execution
2010.01.26 21:00:06 SMTP (smtp.bluebottle.com): End execution
2010.01.26 21:00:06 Bluebottle Email: ReportStatus: RSF_COMPLETED, hr = 0x00000000
2010.01.26 21:00:06 Bluebottle Email: Synch operation completed
2010.01.26 21:03:19 Resource manager terminated

Hi Mark and anyone else who may get this problem.
I am cautiously optimistic that I have possibly found a remedy.
I made a list of addresses that I knew failed every time and then, one by one, deleted them from Contacts and retyped the data into a new entry (not accepting any drop down suggestions) and saved them.
So far I have been able to send to four of the addresses that previously gave a failure notification. Fingers crossed!

Wow. I tried this on a couple of emails and indeed they went through fine. Thank you!!!

Good news Mark.
I am hopeful we have found a cure (possibly!!!) but a little annoyed that I don't know what was corrupted. I went through the "faulty" email contact data with the proverbial fine tooth comb and there was nothing wrong that I could see. So what little error was introduced? In my case I am pretty certain that it was done with "Easy Transfer" when moving from XP to Win 7 but in your case?
Oh well, I am sure there will be another little Microsoft problem to prioritise on and at least I don't have to go back and un-install Win 7 and start all over again.
Nice speaking to you and good luck.

I have found a workaround for this, but not a solution
On my computer it is when the email address, mine or the person I am sending to is in quotes.
If I right click on the contact and copy the pure address rather than the one in quotes it works fine. so Jack@aol.com works but "jack@aol.com" bounces.

But this is really annoying; I'm not techie enough to understand how to fix it.

Just some feedback to benefit others with this very vexing problem.

The solution I found by trial and error after weeks of thrashing around more less matches the others here.

I moved from Windows XP to Windows 7 64-bit using PCMover and, because my trusty Outlook 2003 would no longer work with 64-bit I installed Outlook 2007. I started getting the problems mentioned here (Your message did not reach some or all of the intended recipients....etc. etc.). To compound my puzzlement, each time the error arose I discovered that Outlook had changed the account from which the message was sent.

I tried reinstalling Outlook 2007, deleting and reinstalling accounts, etc. etc. etc. and nothing worked. Then, each time the error came up I opened the adressee's file in Contacts and retyped the email address. This was a bit of a slog, of course, because if the message had been sent to 8 people, for example, I didn't know which address to change so I had to go through and change them all.

Anyway, the problem seems to have stopped but, as someone else said here, it is annoying that one doesn't know how it arose. It seems that when the Outlook addresses are transferred to the new installation in Windows 7 some of them become corrupted in a way that makes Outlook (a) change the Sender account and (b) throw up this error message.

Paddy

Just some feedback to benefit others with this very vexing problem.

The solution I found by trial and error after weeks of thrashing around more less matches the others here.

I moved from Windows XP to Windows 7 64-bit using PCMover and, because my trusty Outlook 2003 would no longer work with 64-bit I installed Outlook 2007. I started getting the problems mentioned here (Your message did not reach some or all of the intended recipients....etc. etc.). To compound my puzzlement, each time the error arose I discovered that Outlook had changed the account from which the message was sent.

I tried reinstalling Outlook 2007, deleting and reinstalling accounts, etc. etc. etc. and nothing worked. Then, each time the error came up I opened the adressee's file in Contacts and retyped the email address. This was a bit of a slog, of course, because if the message had been sent to 8 people, for example, I didn't know which address to change so I had to go through and change them all.

Anyway, the problem seems to have stopped but, as someone else said here, it is annoying that one doesn't know how it arose. It seems that when the Outlook addresses are transferred to the new installation in Windows 7 some of them become corrupted in a way that makes Outlook (a) change the Sender account and (b) throw up this error message.

I'm also very disappointed with Microsoft for not having a paper on this problem which, it seems, has been known - together with its solution - for quite some while.

Paddy

I am still having the odd lesser used email addresses rejected 4 months on, for the same reason and in my case, take a note of all the address data, delete the contact, and then enter it all afresh.
I love Win 7 (it is what it should have been after XP) but am totally exasperated that Microsoft can't sort this out and at least acknowledge that there is a problem. I wonder if it will still be there with Outlook 2010?
One more reason to go Apple next time.