You do not have permission to send to this recipient

I am completely stumped on this one.   A user got back a NDR this morning stating the followings.

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

      Subject:      Aspen Shares
      Sent:      10/16/2008 11:19 AM

The following recipient(s) cannot be reached: on 10/29/2008 7:39 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            < #4.7.1 smtp;451 4.7.1 Please try again later>

The heading attached to that same e-mail are

Microsoft Mail Internet Headers Version 2.0
Date: Wed, 29 Oct 2008 08:39:03 -0400
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
X-DSNContext: 7ce717b1 - 1391 - 00000002 - C00402D1
Message-ID: <>
Subject: Delivery Status Notification (Failure)
Content-Type: text/plain; charset=unicode-1-1-utf-7
--9B095B5ADSN=_01C92941B7E41B040001F765 myserver@mydomain

Content-Type: message/delivery-status
--9B095B5ADSN=_01C92941B7E41B040001F765 myserver@mydomain

Content-Type: message/rfc822
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
Subject: Aspen Shares
Date: Thu, 16 Oct 2008 11:19:27 -0400
Message-ID: <>
X-MS-Has-Attach: yes
Thread-Topic: Aspen Shares
Thread-Index: AckvopQu39s+zJiTT7u3NYgI8XWV8Q==
From: "Laub, Graham R. \(PHL\)" <>
To: <>
Cc: <>
Content-Type: multipart/alternative;
Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

Content-Type: application/;
Content-Transfer-Encoding: base64
Content-Description: 771949_1.XLS
Content-Disposition: attachment;

--9B095B5ADSN=_01C92941B7E41B040001F765 myserver@mydomain

Now it did make it to the CCd user and both the undeliverable are from the same person.

This is strange because I have my NDRs set up for 12 hours.  I looked at some of the others and that he had in the past and they are all 12 hours.  I was able to telnet in to the recipients server.

Also,  I keep an eye on my queses everyday and did not notice this one at all.

I read something on greylisting but when I did that was mentioned in the undeliverable message.

Thanks for any and all help.
Who is Participating?
florin_sConnect With a Mentor Commented:
The key is for the messages not showing up in the queue,remember after you configure the key you must restart the SMTP service, or if you do not wish to configure the key apply the hotfix from microsoft:   -  this supposedly solves the greylist bug problem

For configuring the retry follow the" Configure Retry Tries and Intervals" from microsoft:


The recipient's server is using greylisting (see here for explanation Your smarthost is probably setup with a retry interval that is shorter than the recipient's greylisting interval. Have the rety interval increased on the smarthost.

dplawAuthor Commented:
I did look into that.  Is there anyway to tell if there are?  You mention that they are, if you don't mind me asking how do you know that?  If I provided that mail server name and internet address does this help?
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

This is a typical error, I have encountered also with my company.
Also this site is full of these errors and other people offering solutions.
Please see the following link for more info on this problem.
dplawAuthor Commented:
Thank you for that link.  But I run Windows 2000 and not 2003 per the link above.  Also, can you help me define bug?  I just got another one of these that says Greylisted for 5 minutes.  Is that on the receives end that does that or mine?  If it is greylisted for 5 minutes and gets sent back what does that mean?
The registry fix applies to 2000 and 2003.
The error that you received is an attempt of your exchange server to send mail to the other organisation that has the graylist implemented, as I said before try to increase the retry interval on your smart host.
Apply the registry fix, If you are worried about this you can make a backup of the registry first.
dplawAuthor Commented:
ok.  My retry interval is set for 10 minutes for the first 3 times.  What do you suggest I set it to?

And thank you about the registry key info.  What exactly does that alter?
dplawAuthor Commented:

The first link strictly talks about Windows 2003 which I do not run, so I am a little hesitent on applly that hotfix.  

You mentioned above that I should increase my interval retry's I posted above my current times, you do not think that is fast enough?
florin_sConnect With a Mentor Commented:

I have seen your retry interval that you posted and as you said it was ok,until now.
This is from the article that I have send you:

Configure Retry Tries and Intervals
If a message cannot be delivered on the first try, the Microsoft Simple Mail Transport Protocol (SMTP) Service sends it again from the Queue directory after a specified time. You can set the interval between delivery tries and also designate the number of times to try to deliver a message. After the limit is reached, the non-delivery report (NDR) and messages are sent to the Badmail directory.

You can use these settings to increase your server output speed, but these settings affect outgoing messages only and have no effect on the rate at which other servers process incoming messages. To configure these settings, follow these steps:
1.      In the Microsoft Management Console (MMC), click to select the SMTP virtual server, and then click Properties on the Action menu.
2.      Click the Delivery tab.
3.      For First retry interval (minutes), type a value for the time to try delivery before posting the first notification. The default is 15 minutes.
4.      For Second retry interval (minutes), type a value for the time to try delivery before posting the second notification. The default is 30 minutes, which is 30 minutes after the first retry interval.
5.      For Third retry interval (minutes), type a value for the time to try delivery before posting the third notification. The default is 60 minutes, which is 60 minutes after the second retry interval.
6.      For Subsequent retry interval (minutes), type a value for the time to try delivery before posting a notification. The default is 240 minutes.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.