Solved

exch 2003 internal email: The following recipient(s) cannot be reached:  You do not have permission to send to this recipient

Posted on 2013-01-24
5
588 Views
Last Modified: 2013-02-22
The following recipient(s) cannot be reached:

      xxxx xxxx on 1/24/2013 11:58 AM

            You do not have permission to send to this recipient.  For assistance, contact your system administrator.

This started out with the user being unable to send to one user, and now gets this error back from almost every user.
0
Comment
Question by:SonicVoom
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 5

Expert Comment

by:Harsem
ID: 38816573
Hello,

I think in Active Directory you may have a non-default setting for your users:
Restriction defaultsIn AD under a user or group config you have got the "Exchange general" Tab and a "Delivery Restrictions" button. The attached is the default.

I think you may have non-default values in there for your users.

Jens
0
 
LVL 2

Accepted Solution

by:
SonicVoom earned 0 total points
ID: 38817398
Thanks; I checked that out and all appear to be default.

I saw a number of posts involving reverse DNS issues that are linked to this symptom. I purged some bad records, and the user was able to send emails... for about 20 minutes. Then started having the same problem!
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38818930
Unusual to get this on internal email.
Just to verify - one user cannot email anyone else, or everyone cannot email the one user?

In the properties of the user in ADUC, verify that permission inheritance is enabled.
Anything odd about the user? Special characters in the email address, anything like that?

Simon.
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38823727
If its one user lets try to take a User dump and ensure its normal if still things look unusual we can verify Permissions and then if still not then last option and least time consuming for this issue would be to re-created AD and Mailbox for the user after taking PST and user dump details.

Please ensure its working using OWA\Webmail

- Rancy
0
 
LVL 2

Author Closing Comment

by:SonicVoom
ID: 38917263
Since I cleaned up some DNS records, the problem stopped.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Mailbox Delegation List 45 121
exchange , email 8 42
Office 365 Spam 3 32
have server generate smtp request for testing 2 20
This article explains how to install and use the NTBackup utility that comes with Windows Server.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question