December 29, 2004
None of your e-mail accounts could send to this recipient.
Joy. I'm blogging this just in case anyone else runs into this.
When you send an e-mail message in Microsoft Office Outlook 2003, the From field in the e-mail message that is in your Sent Items folder may not contain any e-mail addresses. Also, you may receive a non-delivery report (NDR) message in your Inbox folder that is similar to the following:
Your message did not reach some or all of the intended recipients.
This issue occurs if all the following are true:
* You are using Microsoft Office Outlook 2003 Service Pack 1 (SP1).
* You are using either a Post Office Protocol version 3 (POP3) account or an Internet Message Access Protocol (IMAP) account.
* The e-mail message was sent to one or more people who are not in your domain.
* Outlook 2003 is configured to receive an NDR message for all recipients.
This is documented in Microsoft KB 872896, which states "Currently, there is no resolution for this issue." I was actually so desperate that I called PSS. They said it's slated to be fixed in Service Pack 2. There's no date yet for SP2. Joy.
UPDATE: I was able to get it working again by uninstalling office, reinstalling office, and not installing any office updates (there doesn't appear to be a way to just uninstall Office SP1).
Posted on December 29, 2004 at 10:08 AM | Permalink
I'm glad you go it to work... But what about those, like me, that pirated O2K3 with SP1 slipstreamed?
Posted by: Ghar Bellows | Jan 4, 2005 5:47:12 AM
I ran into the same behavior. In my case, it turned out that the problem was I had manually configured (sans wizard) the POP3 account and missed setting that outbound mail was to be authenticated. (Missed it because of the form layout change). Turned on outbound authentication and it was solved.
Posted by: Brian Cooksey | Jan 31, 2005 9:29:33 AM
I fixed mine by making sure that the account "logged on to the incoming mail server before sending mail". Everything is fine now, but it was very frustrating for a number of months. Sometimes resending fixed it and sometimes it didn't. Now it seems to be fixed.
Posted by: Jim Stilwell | Feb 6, 2005 6:01:50 PM
Thank you Brian Jan 31 your response I think has worked for me.
Posted by: Philadelphia | Feb 11, 2005 4:04:35 PM
I had the same problem and none of your suggestions worked for me. I resolved the issue by deleting my email account in Outlook 2003, then recreating it. Now all works fine once again. Glad I tried this before I uninstalled/reinstalled Office.
Posted by: Ron Fleischer | Feb 18, 2005 10:15:34 PM
My case is even worse... I tried all of the solutions each of you has tried, still does not work! As an MSDN Universal customer, I tried talking to MS, they basically told me to wait until the new release. I guess I'll try to go back version 2002...
Posted by: Dave Abraham | Feb 20, 2005 7:34:54 AM
I just wanted to throw another piece of advice into the mix.
I ran into the same problem but I was able to fix it with my firewall settings. I'm using a Cisco Pix 506e with Pix IOS 6.3(4). It was an upgrade from 6.2(2). I'm forwarding ports to an Exchange server on an internal IP and when trying to telnet to port 25 on the public, I was getting a scrambled SMTP banner. There's a line in the running config for an smtp fixup protocol:
fixup protocol smtp 25
I think that that was there and functional before the update, so I'm not sure if new devices with 6.3(4) have that enable by default or not. At any rate, I had to remove it with:
no fixup protocol smtp 25
After making the firewall change, the smtp port (when telnetted to from the public IP) was displaying the correct banner and I stopped getting errors about my account not having permission to send.
Hope this helps somebody,
Posted by: 7antrum | Feb 25, 2005 9:40:01 AM
I was playing around with my Bluetooth and Infrared connections when it all went awry for me. What I feel is happening is that because I have multiple connections enabled (LAN, bluetooth, infrared), Outlook doesn't know what to choose so it "guesses" which connection to go for. That explains why I was getting the problem intermittently. By disabling Bluetooth and Infrared and leaving the LAN on, everything worked fine.
It isn't perfect, but I hope it helps someone.
Posted by: Rob Farnell | Mar 2, 2005 2:58:56 AM
The fix by Posted by: Ghar Bellows | January 4, 2005 05:47 AM Worked for me
I ran into the same behavior. In my case, it turned out that the problem was I had manually configured (sans wizard) the POP3 account and missed setting that outbound mail was to be authenticated. (Missed it because of the form layout change). Turned on outbound authentication and it was solved
I, this post, was tearing my hair out trying to fix this. I uninstalled Outlook 2003 several times, cleaned registry, etc. I have entered my email address several times on several computers, I never had to authenticate before, but what ever works!!!! I will take it.
Also, it worked on an non SP1 and with SP1. So much for technicians on line. Thnk you Ghar very much!!!!
Posted by: Mike | Mar 8, 2005 5:46:45 PM
What worked for me was checking the authentication for outgoing server!
On your account setting in M Office 2003 go to more settings / outgoing server/ and check the button for outgoing server needs authentication.
So no format, no uninstalling and no deleting mails!
Hopes this helps……
Posted by: ddtt07 | Mar 24, 2005 11:37:30 AM
I corrected the situation by going to e-mail accounts, More Settings, Outgoing Server tab, check my outgoing server (SMTP) requires athentication. then I checked the Logon Using button then entered my user name and password and check the Remember password box.
Posted by: Phil Stone | Mar 27, 2005 4:57:17 AM
I had the same problem, but I found a different way to resolve it. I have multiple POP3 accounts set up. I tried the outgoing authentication but that did not work. Finally, I went to Tools, Send/Receive, and then you can choose to only Send/Receive for one account. I did a new Send/Receive for that account only and it worked! There is a chance that if you have multiple POP3 accounts this could work for you as well.
Posted by: Mike | Mar 28, 2005 3:50:26 AM
Yet another cause for this problem. I had the same problem sending mails to one particular contact after setting-up my new pc with office 2003. I had added this contact to my address-book by right-clicking on the address in a mail I received and selecting "Add to contacts". This person had his address formatted this way: Tatata [mailto:firstname.lastname@example.org] It tuned out that outlook had added the contact with "MAILTO" as message type and generated this error because no outgoing server supported the MAILTO protocol. I changed the message type to SMTP for this contact and the problem was gone.
Posted by: Steven Segers | Apr 3, 2005 9:14:31 AM
Hi, I seem to have a situation that I haven't read in any of these posts. I have my business email with bellsouth on my laptop, and my home email is on charter. When I bring my laptop home and use it wirelessly, I cannot send from Outlook 2k3. I can receive, but when I send emails I get the system admin message that "None of your e-mail accounts could send to this recipient."
Anyone had this happen? It also happens when I go to coffee shops with non-bellsouth portals.
Posted by: Mark | Apr 26, 2005 2:06:40 PM
Well i tried all of these "fixes" and i get the same error... so i guess i'm waiting for sp2 for office or i might just jump the IE boat and take a ride on the Firefox and Thunderbird jounery.
Posted by: G | May 1, 2005 7:45:12 PM
I tried all of the settings as well, with no luck.
Still gives the same cannot sent to this recipient.
I am typing the actual address in(Making sure address/contact email addresses are being used correctly)
Posted by: Shawn | May 6, 2005 3:40:45 PM
I had this issue and it was as authentication issue with the Exchange server. The computer is a shared machine between three people, so the windows logon name was location name of the site, we'll say "location". The excjange account was set up with the username of the Mgr. of the location, lets say jsmith. The exchange account will try to authenticate with the logon credentials of the user account that is currently signed on, but that is not the same credentials of the exchange account. So under the exchange properties select More settings>Advanced>Logon network security>select none. Now it will ask for the logon password and domian of the proper user.
Posted by: Eric D | May 12, 2005 8:58:53 AM
I had this same issue. I got the usual 'None of your e-mail accounts could send to this recipient.' message and the 'From' field in the Sent Items folder was empty.
To fix it I very simply went to Tools > E-mail Accounts > View or Change Exisiting Email Account, selected the email account that was having issues and deleted the saved password. I then used the 'Test Account Settings' button, was prompted for the password, checked to save the password and then exitied the View or Change Exisiting Email Account dialog boxes.
I then sent a message normally and the 'From' field once again had all the information to be able to send messages successfully. For some reason it seems that Outlook 'loses' its account setting and then throws the 'None of your e-mail accounts could send to this recipient' as a result.
Hope this Helps!
Posted by: diegoo | May 31, 2005 6:21:53 AM
I am using ol2k3 and Exchange server. The user is logged in to the same user/password as his exchange mailbox. He just sent a message to 4 recipients, got the error.
I really do not want to remove office or ol2k3 from the ceo's computer to fix this error!
Most of the fixes will not work, since I am using exchange server.
Anyone else come up with a 'fix' for exchange server users?
Posted by: Phil Hunt | Jun 7, 2005 9:09:56 AM
I am having the exact same issue, none of the suggestions above worked. Here are the symptoms: I am on Bellsouth for e-mail using a POP3. I have Outlook 2003 SP1. I can receive e-mail with no issue, but when I try to send e-mail to any other account other than Bellsouth the error "None of your e-mail accounts could send to this recipient" is returned with an undeliverable in the subject line. The odd part to me is I can send any e-mails I want to bellsouth.net users, but an e-mail to an aol.com or yahoo.com or earthlink user and it will not send. I contacted Bellsouth, they said to reboot my PC. Of course that has not changed the situation! ANY HELP is GREATLY appreciated!!! Thanks, Kayla Griffin
Posted by: Kayla Griffin | Jun 21, 2005 6:48:16 AM
WRT the Bell South problem, often you will have SMTP outbound servers that require authentication (or not) but that cannot be accessed if you are not physically connected to the vendors' network - we have that with Telus here in BC Canada. When you are not on the Bell South network you'll need to set a different server for the SMTP outbound setting in Outlook - one specific to (or accessable from) the network you are currently on.
Posted by: Jason Kennedy | Jun 27, 2005 6:40:35 AM
I had the same problem with Outlook 2003 SP! on XP Home SP2 while working on a clients computer. I could receive email but got the "None of your e-mail accounts could send to this recipient.
" message when trying to send.
I could successfully use Outlook test to send and receive a message but I could not send to another domain. I could receive all email. Turns out the ISP my client was using would not let a DSL account send via them based on what their tech rep said. When I hooked the computer to a dialup modem, I could send and receive just fine.
Posted by: Old_Software | Jun 27, 2005 2:13:12 PM
Not sure if this is relevant for any of you, but here's how we resolved this recently. We had a team member in Rome, Italy, who was accessing the Internet through Dialer.net. In order for him to be able to send and receive emails, he had to create a "dummy" dialer.net POP account, in addition to his normal POP account. As I understand it, the dummy POP account was used to "open-up the channel", so that the other POP account could use that channel to do what it needed to do (send/receive email). So the setup looked like this:
Dialer.net Account (aka dummy to open-up communication channel)
Incoming (POP3): mail.dialer.net (logon info is same as for dialer.net account)
Outgoing (SMTP): smtp.dialer.net (outgoing server requires authentication using same account info as for logon above)
Primary POP Account (aka real account of interest)
Incoming (POP3): mail.whatever.com (logon info as per normal)
Outgoing (SMTP): smtp.dialer.net (outgoing server requires authentication using same account info as for dialer.net logon info above)
Perhaps if some of you are using an ISP other than your regular one, looking into the possibility to create a dummy POP account with them might solve the issue the way it worked for us?
Posted by: Dax Harvey | Jun 29, 2005 11:32:33 AM
hi guys, I have the same problem and I FIX IT!!! changing the following setting in: Tools, e-mail accounts, more settings, outgoing server and ther yo shoul setup My outgoing server (smtp) requires authentication and log on using yo shoul write your username and password and check also remember my password.
Posted by: Shompalue | Jul 21, 2005 11:21:30 AM
I have got the same problem but totally different reason and solution.
I copied an e-mail address from other person e-mail who also use Outlook 2k3 to my new message's TO field.
When I sent this e-mail. I have got the same error message.
Reason: the copied e-mail address contained the e-mail type as "MAIL TO" rather than empty or "smtp". (even saved in the contacts)
Solution: Change the e-mail type to SMTP and the problem solved.
Hope this help.
Posted by: Joshua | Aug 4, 2005 7:44:37 PM
The comments to this entry are closed.