Mail Getting Bounced Back 1

[ts8586]

Our mail/Exchange guru is out sick today, so (hopefully) I have an easy question that one of you fine folks may be able to answer. A user is trying to send an e-mail to someone that he regularly sends to. However, today they're getting bounced back with the following message:

The following recipient(s) cannot be reached:

John Doe (JDoe@acme-anvils.com) on 12/1/2008 11:33 AM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<MAIL.XXX.local #5.7.1 smtp;554 5.7.1 123.123.123.123: on real-time blacklist dnsbl-1.uceprotect.net>

Obviously I changed the name, domain name, and IP address, so hopefully that will eliminate the sarcastic responses!

Any help would be greatly appreciated.

 

[Davetoo]

Is the recipient external to your Exchange server? If yes, then clearly the problem is on the recipients server and not yours, and they need to resolve the problem.

Looking closer, however, it appears your server is on a blacklist (real-time blacklist dnsbl-1.uceprotect.net), which is something you need to check into with that black list provider.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!

 

[ts8586]

Yes Davetoo, the recipient is on a totally different exchange server. Should I look into the blacklist issue first before I contact "Acme Anvils" to see if they're blocking us?

 

[Davetoo]

I would contact them to see if their admin will manually allow the email until you can resolve the black list issue if one exists.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!

 

[58sniper]

That RBL is going to be a problem until it's dealt with. You need to determine WHY you're on that list. Go to the page

http://www.uceprotect.net/en/rblcheck.php

on their site and plug in your IP.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Zelandakh]

It is often caused by the IP address being seen as dynamic even when it is fixed.