Exchange Server Forums

#5.7.1. Unable to relay for ...

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Message Routing >> #5.7.1. Unable to relay for ...

Page: [1]

Message

<< Older Topic Newer Topic >>

#5.7.1. Unable to relay for ... - 21.Jan.2005 4:43:00 AM

belinda

Posts: 30
Joined: 16.Jan.2004
From: Sydney, Australia
Status: offline

I am getting the following error when i attempt to send an email to an external domain which has no affiliation or association with our own domain.

You do not have permission to send to this recipient. For assistance, contact your system administrator.
<ourdomain.com.au #5.7.1 smtp;550 5.7.1 Unable to relay for user@anotherdomain.com.au>

I am also unable to browse to their website URL. I do not get this error for any other email recipients that i send to however this one is a problem. I have checked with the recipient and they have been receiving emamil from other clients without a problem.

Any ideas?

Post #: 1

Featured Links*

RE: #5.7.1. Unable to relay for ... - 23.Jan.2005 11:04:00 PM

silence

Posts: 4
Joined: 21.Jan.2005
From: Zagreb, Croatia
Status: offline

Yo!

Looks like you cannot reach that IP address range anyhow - using SMTP or HTTP protocol. Have you tried tracing a route to the IP address of the Website or SMTP server? Maybe your ISP has a problem with routing to that specific IP range, you should check it out. Or somebody else along the route path has that problem - tracert wil show you... of course only if the ICMP is allowed along the route.

You should also try to telnet both their HTTP server on tcp port 80 and SMTP server on TCP port 25, to check connectivity.

Post a reply when you check this stuff out...

Cheers!

(in reply to belinda)

Post #: 2

RE: #5.7.1. Unable to relay for ... - 23.Jan.2005 11:40:00 PM

belinda

Posts: 30
Joined: 16.Jan.2004
From: Sydney, Australia
Status: offline

The tracert completes successfully for both the IP address and FQDN. I can still not send email to their domain. I can telnet to their mail server on port 25 but cannot telnet to their web server on same IP for port 80.

I can browse their WWW via a web browser now however still get same unable to relay message when i try to email the domain.

Would it be something on their end?

(in reply to belinda)

Post #: 3

RE: #5.7.1. Unable to relay for ... - 25.Jan.2005 10:08:00 AM

silence

Posts: 4
Joined: 21.Jan.2005
From: Zagreb, Croatia
Status: offline

Microsoft wrote:

Numerical Code: 5.7.1
Possible Cause:
General access denied, sender access denied - the sender of the message does not have the privileges necessary
complete delivery.
You are trying to relay your mail via another SMTP server and it does not permit you to relay.
The recipient might have mailbox delivery restrictions enabled. For example, a recipient's mailbox delivery restrict
was sent to receive from a Distribution List only and non-member's email will be rejected with this error.
Troubleshooting: Check system privileges and attributes for the contact and retry the message. Also make sure you ar
running Exchange 2000 Service Pack 1 or later for other potential known issues.

I wrote: [Smile]

Also, maybe you should somehow contact postmaster@unaccessibledomain and ask him to give you the URL of their DNSbl provider (if any), so you can check status of your public IP with them - if they consider your IP as an open relay SMTP server, you will be blocked for e-mail delivery to that domain (users mostly get NDR with code 5.7.1).

Hope this helps.

Cheers!

(in reply to belinda)

Post #: 4

RE: #5.7.1. Unable to relay for ... - 25.Jan.2005 6:17:00 PM

Richard Fleming

Posts: 85
Joined: 24.Oct.2002
From: Toronto, ONT [Canada]
Status: offline

Simplest thing I can suggest to you is this. When you prevent relaying except for those who are authenticated... which is the default config on Exchange 2003... you have to do this...

In your Outlook client, you have to specify that the outgoing server requires authentication. This means that when you log in to send mail, it'll send your user credentials to the SMTP server and everything should work with no problem after that.

Rich

(in reply to belinda)

Post #: 5

RE: #5.7.1. Unable to relay for ... - 25.Jan.2005 6:31:00 PM

silence

Posts: 4
Joined: 21.Jan.2005
From: Zagreb, Croatia
Status: offline

I understand now... when you send e-mail to ANY domain, you get that NDR.

You should check what Rich said... and maybe you could allow all your LAN subnets to relay through your Virtual SMTP server.

silence

(in reply to belinda)

Post #: 6

RE: #5.7.1. Unable to relay for ... - 3.Feb.2005 7:08:00 PM

Guest

One of my users got the error:
"You do not have permission to send to this recipient. For assistance,contact your sytem administrator. <mailsrvr #5.7.1 smtp;550 5.7.1 <myusersemail@mydomain.com>...Access denied>"

On Exchange 2000.
My solution? I made the user check the email address and turns out he was attempting to email a .com when it should have been .net.

(in reply to belinda)

Post #: 7

RE: #5.7.1. Unable to relay for ... - 28.Feb.2005 4:44:00 PM

skipg@lordandbenoit.com

Posts: 1
Joined: 28.Feb.2005
From: Worcester, MA USA
Status: offline

I recently experienced a similar problem trying to send email to <recipient>@juno.com. I solved the problem by setting up a second "smart host" SMTP connector for the domains juno.com and netzero.com. I simply forwarded the email to my ISP's SMTP server. There is an explanation of how routing works in

Microsoft explanation of Routing

Hope this helps,
Skip

(in reply to belinda)

Post #: 8