You do not have permission to send to this recipient.

I have had multiple employees receive this type of message over the past several weeks.  Can you help me determine why this is occurring and how to resolve this?  


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

      Subject:      Washington Insurance Network (WIN)
      Sent:      4/23/2010 9:10 AM

The following recipient(s) cannot be reached:

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER

      Employee Name on 4/23/2010 9:10 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            MSEXCH:MSExchangeIS:/DC=local/DC=SEC:SERVER
ITPro44Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dexITCommented:
Who is sending these e-mails individuals or individuals on behalf of an individual? If so, you need to provide your users with "Receive As" rights to the person sending on behalf of.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Shreedhar EtteCommented:
Hi,

Do you have PIX? If yes then refer http://support.microsoft.com/kb/320027/

Else

# Launch Exchange System Manager (ESM) and navigate to the SMTP virtual server you are using to send messages to the Internet. View Properties -> Access -> Relay and ensure that the "Allow computers which successfully authenticate to relay" checkbox is not checked.

# Troll through the application event log on your Exchange server for errors from source MSExchangeTransport around the time of the non-delivery report (specifically look for Event ID 1709 or 1710 or any errors/warnings from MSExchangeTransport).

# Temporarily enable maximum diagnostics logging on MSExchangTransport, the Queuing Engine, and the Connection Manager for the server hosting a problematic user. Then have this user send a message to an address that typically sends non-delivery reports (NDRs) with a 5.7.1 error. Turn diagnostics logging back off, and troll the application event log on the Exchange server in question for errors or warnings specific to the message in question. (Tip: search the description field of the events for the Message-ID of the particular message). If you find specific errors or warnings, look those up on TechNet or write back if you need help resolving things further.

# Check whether 5.7.1 NDRs are happening for all messages sent from any user within your organization to a specific internet SMTP domain, or whether these errors seem specific to a given sender. If the former is the case, then you may want to contact the email administrator for the target SMTP domain (i.e., send an email to postmaster@<company.com>) asking them to confirm that their MX records are pointing to the appropriate SMTP gateway .(You can actually test this by looking up the target domain's public DNS record and attempting to telnet to port 25 of any MX records listed in the DNS record. I described how to send test messages via telnet in "How to troubleshoot problems receiving external email." The receiving server may actually send you a more specific error message through SMTP commands in response to telnet than you're getting in the NDR.

Extracted from: http://searchexchange.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid43_gci1109106_mem1,00.html
0
ComputerBeastCommented:
The recipient might have blocked the email addresses or the domain. Ask the recipient if s/he has done this.
0
The Five Tenets of the Most Secure Backup

Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.

ITPro44Author Commented:
I've had an emergency come up at work.  I won't be able to troubleshoot this for a while.  Thanks for the responses so far.
0
ITPro44Author Commented:
I'm going to close this questions as it has not been critical and I haven't had the time necessary to troubleshoot.  Thanks for your responses.
0
ITPro44Author Commented:
Ok I mistaking hit the close button... oops.  Don't know how to reverse.
0
ITPro44Author Commented:
I'm going to accept your solutions that I can review this in the future if it becomes a larger issue.

Thanks,
0
jennixchangeCommented:
also a useless NON_answer
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.