Outlook-You do not have permission to send to this recipient

Outlook XP and You do not have permission to send to this recipient.

Outlook XP has recently and randomly started generating the following error:

"You do not have permission to send to this recipient. For assistance, contact your system administrator. <cae02.cae-usa.com #5.7.1>"

Copying the contents of the problem message and pasting it into a new message works just fine. The only thing I could find in Microsofts Knowledgebase had to do with DNS and the inability to send any messages to certain domains. There are no events logged when these messages bounce. The messages bounce immediately after sending. So far this has only happened with forwarded messages with random senders and recipients.

I’m running Exchange 2000 SP3 on Server 2000 SP4 and Outlook XP on Windows XP SP1.

Any suggestions?

Everytime I've had this happen here the user either manually typed in the address with a typo, or they had a typo in the address stored in the address book. If you can send OK by replying, I almost garantee you have a typo. Check it closely.

If that doesn't take care of it, then your network admin may need to set up an SMTP connector to that domain via these instructions:

http://www.amset.info/exchange/smtp-connector.asp

Chances are though if it's only one user having the problem, the typo is almost the sure fire answer.

I wish it was the case of a typo. The addresses are coming out of the global address list. The affected users and recipients are random. The problem only seems to arise when a message is forwarded. So far it has been a different user and different recipient each incident. If it were the same senders and/or recipients the problem would be a whole lot easier to track down. Most of the recipients are in different domains.
Bizarre huh?

Yeah -- that does throw a bit of a kink into it.

Hmmm....I'll give it some thought.

I don't know if this will provide any ideas for troubleshooting, but it does provide a nifty little trick for testing your relays via Telnet. If nothing else the article is worth that:

http://www.winnetmag.com/MicrosoftExcha ... _7696.html

Definitely it is a problem with Exchange, check this MS page I found:

http://support.microsoft.com/default.aspx?kbid=274638&product=exch2k

Hope it helps, let us know how it goes