dplaw
asked on
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:
user@domain.com on 10/29/2008 7:39 AM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<myserver.mydomain.com #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
From: postmaster@mydomain.com
To: user@mydomainm.om
Date: Wed, 29 Oct 2008 08:39:03 -0400
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-statu s;
boundary="9B095B5ADSN=_01C 92941B7E41 B040001F76 5myserver@ mydomain.c om"
X-DSNContext: 7ce717b1 - 1391 - 00000002 - C00402D1
Message-ID: <pm0RnzXot0000038f@myserve r@mydomain .com>
Subject: Delivery Status Notification (Failure)
--9B095B5ADSN=_01C92941B7E 41B040001F 765myserve r@mydomain
Content-Type: text/plain; charset=unicode-1-1-utf-7
--9B095B5ADSN=_01C92941B7E 41B040001F 765 myserver@mydomain
Content-Type: message/delivery-status
--9B095B5ADSN=_01C92941B7E 41B040001F 765 myserver@mydomain
Content-Type: message/rfc822
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:messag e
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----_=_NextPart_ 001_01C92F A2.94518E3 0"
Subject: Aspen Shares
Date: Thu, 16 Oct 2008 11:19:27 -0400
Message-ID: <FDC6907B94EEC34A8A43562DB 12A981F03B B38BC@myse rver@mydom ain.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: Aspen Shares
Thread-Index: AckvopQu39s+zJiTT7u3NYgI8X WV8Q==
From: "Laub, Graham R. \(PHL\)" <user@mydomain.com>
To: <user@domain.com>
Cc: <user2@domain.com>
------_=_NextPart_001_01C9 2FA2.94518 E30
Content-Type: multipart/alternative;
boundary="----_=_NextPart_ 002_01C92F A2.94518E3 0"
------_=_NextPart_002_01C9 2FA2.94518 E30
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
------_=_NextPart_002_01C9 2FA2.94518 E30
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
------_=_NextPart_002_01C9 2FA2.94518 E30--
------_=_NextPart_001_01C9 2FA2.94518 E30
Content-Type: application/vnd.ms-excel;
name="771949_1.XLS"
Content-Transfer-Encoding: base64
Content-Description: 771949_1.XLS
Content-Disposition: attachment;
filename="771949_1.XLS"
------_=_NextPart_001_01C9 2FA2.94518 E30--
--9B095B5ADSN=_01C92941B7E 41B040001F 765 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.
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:
user@domain.com on 10/29/2008 7:39 AM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<myserver.mydomain.com #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
From: postmaster@mydomain.com
To: user@mydomainm.om
Date: Wed, 29 Oct 2008 08:39:03 -0400
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-statu
boundary="9B095B5ADSN=_01C
X-DSNContext: 7ce717b1 - 1391 - 00000002 - C00402D1
Message-ID: <pm0RnzXot0000038f@myserve
Subject: Delivery Status Notification (Failure)
--9B095B5ADSN=_01C92941B7E
Content-Type: text/plain; charset=unicode-1-1-utf-7
--9B095B5ADSN=_01C92941B7E
Content-Type: message/delivery-status
--9B095B5ADSN=_01C92941B7E
Content-Type: message/rfc822
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:messag
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----_=_NextPart_
Subject: Aspen Shares
Date: Thu, 16 Oct 2008 11:19:27 -0400
Message-ID: <FDC6907B94EEC34A8A43562DB
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: Aspen Shares
Thread-Index: AckvopQu39s+zJiTT7u3NYgI8X
From: "Laub, Graham R. \(PHL\)" <user@mydomain.com>
To: <user@domain.com>
Cc: <user2@domain.com>
------_=_NextPart_001_01C9
Content-Type: multipart/alternative;
boundary="----_=_NextPart_
------_=_NextPart_002_01C9
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding:
------_=_NextPart_002_01C9
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding:
------_=_NextPart_002_01C9
------_=_NextPart_001_01C9
Content-Type: application/vnd.ms-excel;
name="771949_1.XLS"
Content-Transfer-Encoding:
Content-Description: 771949_1.XLS
Content-Disposition: attachment;
filename="771949_1.XLS"
------_=_NextPart_001_01C9
--9B095B5ADSN=_01C92941B7E
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.
ASKER
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?
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.
https://www.experts-exchange.com/questions/22890476/Exchange-2003-NDR-held-until-server-restart-most-related-to-451-4-7-1-Greylisting.html?sfQueryTermInfo=1+4.7.1
Also this site is full of these errors and other people offering solutions.
Please see the following link for more info on this problem.
https://www.experts-exchange.com/questions/22890476/Exchange-2003-NDR-held-until-server-restart-most-related-to-451-4-7-1-Greylisting.html?sfQueryTermInfo=1+4.7.1
ASKER
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.
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.
ASKER
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?
And thank you about the registry key info. What exactly does that alter?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
florin,
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?
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?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The recipient's server is using greylisting (see here for explanation http://dempa.init5.net/2005/03/13/spam-greylisting/). 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.
regards