This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Relay email for clients

Operations over 6 years ago

I have my Sophos UTM running at my home office. It is handeling my email at the moment, this is working fine.

No i would also like to handeling the emails from my clients before the emails reach their Exchange servers.

So i changed their MX records to my IP address.

I have created SMTP Profiles per client.

Under "Routing" i chose "DNS hostname" under Route by. I entered remote.CLIENTNAME.nl here.

I have checked the email with the Exchange Connectivity site, but i am getting error:

The server returned status code 550 - Mailbox unavailable. The server response was: Relay not permitted
Exception details:
Message: Mailbox unavailable. The server response was: Relay not permitted
Type: System.Net.Mail.SmtpFailedRecipientException

So i assume i have to enter the clients IP under "Relaying". i am right?

But which one? Upstream/Authenticated or Host-Based Relay?

This thread was automatically locked due to age.

0 Ol Deda over 6 years ago

If I understood, you want to put UTM like a bridge for the external Exchange

Normaly you have to put the exchange ip, in relay hosts

But you have to configure the exchange send/receive connectors.
Cancel
Vote Up 0 Vote Down

Cancel
0 Operations over 6 years ago in reply to Ol Deda

I am sorry if i didn't explain it correctly.

ATM i am using MCAfee SaaS as a SPAM/VIRUS filter for all my clients. So MX records towards Mcafee and in the control panel i tell mcafee which IP goes with which domain.

MCafee pulled the plug out of this product, so i have to use something new.

So i want to use my Sophos UTM as a SPAM/VIRUS filter for a couple domains, which are being hosted at different locations.

For the moment let's focus on receiving the mail through Sophos. Sending is being done by the on premise exchange servers.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ol Deda over 6 years ago in reply to Operations

The last thing will be the problem. The servers IP wil be blacklisten in minutes if they send emails from different IP not in MX Records
Cancel
Vote Up 0 Vote Down

Cancel
0 Ol Deda over 6 years ago in reply to Operations

Now, who is giving error Relay Not Permited, Sophos or Exchange client?

Under Profile name is Domain, have you put there the full MX Record for the specific exchange server?
Cancel
Vote Up 0 Vote Down

Cancel
0 Operations over 6 years ago in reply to Ol Deda

Well since i cannot find the email from Exchange Connectivity in the SMTP log from the Mail Manager, it looks like the email is being blocked before it reaches my Sophos.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ol Deda over 6 years ago in reply to Operations

A bit confused. Who generates the error Sophos while trying to send the email to exchange or what.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ol Deda over 6 years ago in reply to Ol Deda

Can you post a photo of the sophos profile (hide the names)

EDITED

under profile name is "Domain" that sophos will accept. Put there the domain name for the specific exchange. Example: domain.com
Cancel
Vote Up 0 Vote Down

Cancel
0 Operations over 6 years ago in reply to Ol Deda

I am really sorry....

I had a big OEPS moment....

In front of the SMTP profiles i just saw an ON/OFF button. With a default setting OFF.

I didn't see this switch before. Again i am really sorry to have wasted everyones time.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ol Deda over 6 years ago in reply to Operations

No Prob ☺
Cancel
Vote Up 0 Vote Down

Cancel
0 Operations over 6 years ago in reply to Operations

O no the Exchange Connectivity website is working, by normal emails are not accepted:

EMAILADRES
Remote Server returned '554 5.4.108 SMTPSEND.DNS.MxLoopback; DNS records for the next hop domain are configured in a loop -> DnsDomainIsInvalid: InfoMxLoopback'
Cancel
Vote Up 0 Vote Down

Cancel