[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 369
  • Last Modified:

Undeliverabl Email" You do not have permission to send to this recipient"

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

      Subject:      RE: this is the right address
I am OK if I use internet mail but the corporate email is giving me this problem.

The following recipient(s) could not be reached:

      savannah.r.flores@moody.edu on 10/17/2007 2:00 PM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            <romailfe2.vta.org #4.7.1 smtp;450 4.7.1 <savannah.r.flores@moody.edu>... try again later>
0
Akbarzadeh_s
Asked:
Akbarzadeh_s
  • 9
  • 5
  • 4
  • +1
1 Solution
 
Ahmed Abdel SalamCommented:
to solve this,
in AD
right click the recipient, properties, exchange general. be sure this user is allowed to recieve mails from the sender.
0
 
Akbarzadeh_sAuthor Commented:
My users all they are allowed to  receive from everyone.  Thanks and lets try some thing else.
0
 
SembeeCommented:
You shouldn't see those errors. That is a 4.x.x code which is temporary and shouldn't generate an error back to the user. The messages should stay in the queues until the server tries again.

It looks like greylisting, so there is a chance it is the greylisting bug.
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_22904992.html

If it isn't that, then something else is interfering with the SMTP traffic and causing temporary failures to be treated as fatal.

Simon.

--
If your question has been answered, please remember to accept the answer and close the question.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
Akbarzadeh_sAuthor Commented:
I tracked the message and an NDR gets generated which it was attached to my original email. The last location moody even say that "The tracking database on moody is not available or the message has left the Exchange organizatiion.  Faclity:Microsft Exchange Management ID no:c1032751
0
 
SembeeCommented:
Doesn't mean it is YOUR server that is generating the error. It could be another server up the chain.

Simon.

--
If your question has been answered, please remember to accept the answer and close the question.

0
 
Akbarzadeh_sAuthor Commented:
I understand.  But I could use my web mail and send to the user without any problem.  Some thing stoping this email from being send out from the server?
0
 
Ahmed Abdel SalamCommented:
this problem happened for this user only or some other users ??
0
 
Akbarzadeh_sAuthor Commented:
This email address is the only one reported to generate NDR.
savannah.r.flores@moody.edu
0
 
Ahmed Abdel SalamCommented:
I have a suggestion which not looks good but I think it can solve the problem, backup this mailbox, delete it and recreate it again. I had some strengh problems like this before and solve it by doing that  so just try it.
0
 
Akbarzadeh_sAuthor Commented:
But who ever in our organization send to this email address get the NDR and not only me.
0
 
Ahmed Abdel SalamCommented:
it's fine, I am not telling that delete ur mailbox and re-create it. I am suggesting that you can delete savannah.r.flores@moody.edu mailbox then recreate it.
0
 
SembeeCommented:
The server responsible for that domain is using greylisting.
You should not be seeing the NDR when greylisting is involved. If you send the email again immediately, it should be delivered correctly.

However what you need to find out is why you are seeing the greylisting NDR. As I wrote above, the error is temporary and temporary error NDRs should not be delivered to the sender. Therefore something is not working correctly. Something is either interfering with the traffic or not processing the NDR correctly. Have you made the change I outlined in the Q I linked to above?

Does your email go straight to the internet, or does it go through anther product or appliance? What else is on the Exchange server?

Deleting accounts is not going to fix this problem, I don't see why that has been suggested.

Simon.

--
If your question has been answered, please remember to accept the answer and close the question.
0
 
Akbarzadeh_sAuthor Commented:
I agree that deleting account is not the solution and since the the questioned email address is not even in our company.  
I have not applied any reg changes because this is the only email account I can not send to.
The SMTP out going mail gets routed from the back end server to front end server goes through the ISA servers and then to the appliances and out to the INTERNET.
0
 
SembeeCommented:
Is the server that is mentioned in the NDR your Exchange server or another server in the stream?

The fact that this is the only domain you are seeing the error with is not a good reason why you should not apply the registry change.
The usual signs of this problem is that messages are only NDR back to the user when the server is rebooted. The fact that you are seeing the message at all is unusual. I make the change as standard on all Exchange 2003 servers I maintain.

Simon.

--
Once your question has been answered, please remember to accept an answer and close the question.
0
 
Akbarzadeh_sAuthor Commented:
The server is one of my Exchange front end server that all outgoing SMTP goes from back end server to front end servers.
I can send to the recipient using my comcast account but using our corporate exchange system gives us the NDR?  Usually the NDR gets created after trying for couples of day but this one comes back very quick saying:
The following recipient(s) could not be reached:

      savannah.r.flores@moody.edu on 10/17/2007 2:00 PM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            <romailfe2.vta.org #4.7.1 SMTP;450 4.7.1 <savannah.r.flores@moody.edu>... try again later>
0
 
SembeeCommented:
The reason the NDR comes back immediately is because the remote server is rejecting it. As I wrote above, the NDR should not be seen by the user - it is a temporary error - therefore as it is one of your servers then the problem is with that machine - AV, Antispam software are the usual culprits.

Simon.

--
Once your question has been answered, please remember to accept an answer and close the question.
0
 
Akbarzadeh_sAuthor Commented:
The problem is resloved now.  Thanks
This question can be close.
0
 
fraserorgCommented:
How did you resolve the problem Akbarzadeh?
0
 
Akbarzadeh_sAuthor Commented:
Our Macfee appliences were blocking it.
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 9
  • 5
  • 4
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now