Posts: 403
Joined: 23.Nov.2004
From: UK
Status: offline
We have one user who has occasional problems sending Internet email. They get bounced back with the following error:
The following recipient(s) could not be reached:
username@domain.com on 11/08/2005 13:11 You do not have permission to send to this recipient. For assistance, contact your system administrator. MSEXCH:MSExchangeIS:/DC=com/DC=domain:servername
There is nothing in Event Viewer to suggest why this might be happening and it only happens to this one person.
Is there any solutions to the first post as I am facing the same problem? It does not happen to all users but to one or two users only.
They cannot send the email to the particular domain name user but able to send to other domain name user. I had searched through the postings but still face the same problem. This is the NDR sent back to the user
From: System Administrator Sent: Friday, December 16, 2005 10:14 AM To: user1@contoso.com Cc: user2@contoso.com Subject: Undeliverable: Subject to user Your message did not reach some or all of the intended recipients. Subject: Subject to user Sent: 12/16/2005 10:14 AM The following recipient(s) could not be reached: user1@contoso.com on 12/16/2005 10:14 AM You do not have permission to send to this recipient. For assistance, contact your system administrator. MSEXCH:MSExchangeIS:/DC=local/DC=exchserver:EXCHSERVER
Posts: 8196
Joined: 7.Jan.2004
From: California, USA
Status: offline
I've seen this happen in instances where you (as the sender) do not have reverse-DNS set up. Some receiving mail systems will not accept mail without being able to perform a reverse-DNS lookup to confirm the mail is coming from a legitimate source.
_____________________________
Regards,
Dean T. Uemura Microsoft MVP - Exchange exchangeguy.blogspot.com uemurad@yahoo.com
How do you ensure that the email source ip address is from my exchange server? Below are some of my server settings
DNS record hosted by external ISP DNS server Domain: nwtraders.com MX : mail.nwtraders.com 201.212.145.21(Public IP)
Internal DNS hosted by exchange server SP1 192.168.1.10(Private IP) Domain: nwtraders.local Setup a forward zone nwtraders.com. Add MX and A record for mail 192.168.1.10
I read in one of the previous post that I need to add the public MX ip into the internal DNS. Will that help?
All my users had their delivery restriction set as from Everyone.
Please advise.
< Message edited by yaphui_gts -- 16.Dec.2005 6:18:43 PM >
Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
Check your smtpsvc logs. Also have the remote domain look into the issue as well and have them check their smtp logs. It's possible that your specific user is being blocked on their end.
Posts: 926
Joined: 11.Mar.2005
From: Virginia, USA
Status: offline
I would check the user PC to make sure, there is no virus worm and Etc.
If this user had sent virus or spam to this recipient, in the past his or her SMTP address might have Recorded as a bad address on the receiving exchange organization, just like adding someone into Block senders Within outlook, so you need to make sure you user has no bad history on the recipient side.
That explains why you can send e-mail without having any problem but this specific user.
I suggest getting touch with other side organization Exc administrator, and asking him to take a look at the spam rules Or sender block list to see your user SMTP is exist or listed anywhere.
We had just migrated the mail hosting from a ISP to hosting the exchange server on our own. Previously before we changed to exchange, the user do not face this problem and they are using POP to download and send email. After we had switch to using exchange, one to three of my users are facing the permission rights.
Posts: 926
Joined: 11.Mar.2005
From: Virginia, USA
Status: offline
I am not sure about your environment, but couple other thing you can try
Here one of them I can think of right of the bat. It is a good idea to backup this user e-mail first
Go to ADUC Right down all the settings member ship and so fort for this user (Hopefully his account SID id is not associated with Any of the apps or existing settings)
Now I will ask you to delete this user, Go back and create a new user with same name and so forth, Take care all previous setting and make sure it is the same as before
Don’t create a mailbox. Without the mail box===================> this is sort of important since we will re connect the previous mail box
Now we have your previous user with new name and all the membership setting, of course with a new SID ID. And you have no mail box associating with this user yet
Now go to ESM Drill down to your mail store Mailboxes Run cleanup agent You will see red X associating with the deleted mail box That is the original mail box Now make a right click and Reconnect Type the name of the user (which will be the same name, we have just created)
Test to see if this person can send e-mail to same recipient
Hopefully this will take care of the problem, again if I were you I would make sure On the recipient side your user SMTP address is not listed as a spam source, You know any spam filter can record and smtp address as a spam source and will refuse to accept e-mails
Even in the ESM Message delivery Sender filtering
Block messages that claim to be from the following senders
How do you know your user is not listed there on the recipient Exchange server
Better of to getting touch with them and ask them if their end is okay accepting a Message from your user
We used to have this problem. The problem occurred only when people used the outlook's "resend this message"-feature on messages which had been originally sent on our old qmail linux mail server.
I am running into this same issue, the only catch is that it only happens when the user tries forward a contact with a vcard. The user can send e-mail to the recipient who is also on the same server, however when they try to forward a contact as a vcard through outlook they get the message: You do not have permission to send to this recipient. For assistance, contact your system administrator. MSEXCH:MSExchangeIS:/DC=com/DC=XXX:XXX
They can forward contacts as vcards to other people, it seems random when exchange decides to deny delivery.
I had the same problem, but the solution was really simple (for my case):
I had Exchange 2003 and Outlook 2003 in cached mode. The user used the "From" field instead the "To" field and as Outlook is in cached mode the message seems to be send but then we get back an error message.
Generally, this error can be found everytime you try to send a message on Behalf of but you do not have the correct rights.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> Message Routing >> You do not have permission to send to this recipient 
You do not have permission to send to this recipient - 
RE: You do not have permission to send to this recipient - ![[Razz]](/image/smiles/tongue.gif)
RE: You do not have permission to send to this recipient - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
