The recipient has been deleted or has no e-mail address.

I have a user that receives the following Undeliverable message when using Company Exchange and his Personal POP e-mail account in the same Outlook.

Tried many things, but I can't get it to stop happening.

Here's the rejection e-mail (edited for privacy):

Your message did not reach some or all of the intended recipients.

      Subject:      (subject here)
      Sent:      (date here)

The following recipient(s) cannot be reached:

      =SMTP:(email address here) on
            The recipient has been deleted or has no e-mail address.

The e-mails are all valid.  I have verified all the MX records... Am at my rope's end.  Can anyone please help?
Who is Participating?
Question PAQ'd, 500 points refunded, and stored in the solution database.
delptAuthor Commented:
The KB article has to do with Microsoft Mail Remote 3.2  (which is old and unsupported, btw).

This is Microsoft Outlook 2007.

What do they have to do with each other?
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Where is your MX Pointing? any kind of spam box like barracuda or something??
let me conform the issue

when an external user sends mail to this internal user .. the external user gets this NDR right...?
delptAuthor Commented:
No... Let me attempt to clarify:

External user is on VPN to corporate network and using Outlook 2007.
Outlook 2007 sends and receives mail for both the company (exchange) e-mail and the user's personal (POP3/SMTP) e-mail.
Both Exchange e-mail and POP3/SMTP e-mail appear to be configured correctly in Outlook.

The user gets this message sporadically when sending mail to non-corporate users using either e-mail account.
Happens on both accounts but I think it's more frequent with their personal account.

The error goes away if one of the accounts is removed from Outlook.
The goal is to have both e-mail accounts on that user's Outlook without this issue presenting itself.

Hope this helps!
delptAuthor Commented:
Also, Company MX is pointing to Postini Spam Filter, but the user never gets the error when sending to internal company users.
you have 2 SMTP address on your server.
you have configured both on one outlook 2007 for a user
when you send a mail to any external domain .. you get the error ??
when you remove one of the account.. you no more get the error... is that the issue..??

What happens when you log in to OWA and send / receive email?? do u still get the NDR??
delptAuthor Commented:
The problem is at the client level, I think.
When outlook is connecting to ONLY exchange, it works fine.
When you add a second account to outlook (POP/SMTP) is when the errors happen.
Unfortunately for me, the user cannot reliably re-create the error, but it does happen on a daily basis.

The error happens most often when the user is sending e-mail from their personal account to another non-company account, but it is not isolated to this.

It does, however, always happen while sending to external, non-company accounts.

If you use OWA, there is no NDR.
If you remove one account from Outlook, there is no NDR.

Only when using both accounts on the same Outlook are there sporadic NDRs.
Since owa works fine.. its sure that there is no issue with the server,.
You are correct. its somethign with the client itself.
try to create a new profile on a different client machine and try the same...
let me know the results..

delptAuthor Commented:
Unfortunately, creating a new profile on the workstation is not an option.
This was happening with Outlook 2003, and it was completely uninstalled  and Outlook 2007 was installed and the problem still happens...

Any idea what could be the issue?
delptAuthor Commented:
delptAuthor Commented:
create a new profile on a different compter and see if its working.... atleast for testing !
we need to narrow down the issue...
delptAuthor Commented:
So, I got the problem to stop. Not sure why this worked but it did...

Instead of both e-mail addresses delivering to the same inbox (which MS said should work; emphasis on the *should*), I have it sending one mailbox to one inbox and another mailbox to an inbox in a PST file.

As soon as this was set up, the problem ceased.

I'll chalk it up to another Microsoft bug.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.