asked on

Exchange 2010 - Unable to Relay

A system we have sends routine emails out to the company that makes it with support information. That email is sent via our Exchange 2010 server. When I generate this email and send it to my local email account it works fine. When I do the same and send it to any external account it fails with 550 errors related to relaying.
Also, when I try to send an email to any outside address via telnet i get the same thing...See below. Any idea what changes I need to make?

220 cas1.domain.local Microsoft ESMTP MAIL Service ready at Wed, 28 Mar 2012 08:05:28 -0400
helo cas1.domain.local
250 cas1.domain.local Hello [10.170.1.183]
mail from:localaccount@domain.com
250 2.1.0 Sender OK
rcpt to:xxxxxxxx@gmail.com
550 5.7.1 Unable to relay

I should note, other than this we are having NO issues in Exchange at all.

ASKER CERTIFIED SOLUTION

FostWare

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

akalbfell

ASKER

This is our current connector settings. If I understand correctly, we are currently allowing all IP's to send from, but there is a seperate setting to relay to outside which we dont have enabled?

Oriba

Hi

Please see attached screen shot

Under "Organization Configuration" --> "Hub Transport"

Open the send connector and verify that you have "*" for address

This setting tels the send connector wich network to serv...

Let me know (More ideas in the pocket)
ScreenHunter-06-Mar.-28-15.15.jpg

akalbfell

ASKER

I do.

akalbfell

ASKER

I figured it out. See here for what I followed.

http://www.marcvalk.net/2009/12/exchange-2010-relaying-to-external-email-addresses/

akalbfell

ASKER

I've requested that this question be closed as follows:

Accepted answer: 0 points for akalbfell's comment #37776697

for the following reason:

Figured out on own

FostWare

The link the Author provided, contains information from the official documentation as I've linked.

If the problem had a different underlying issue or the fix was not contained in the first link provided, then the Author comment should state what was different - even if it is just to help the next person searching for a solution.

akalbfell

ASKER

Sorry didn't notice the article you provided mentioned the same solution all the way at the bottom.