Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 506
  • Last Modified:

How to set up the MX record and SMTP Configuration

I have two questions regarding my Exchnage 2010 configuration
Brief description
I have one Mail Server (that house my mail store)
I have one Client Access Server that is also my Hub Transport Server
I use Barracuda 400 application as my Edge Transport Server

1st question:  Do I set my MX record for DNS to point to my Barracuda System or should it point to the Mail serve or Hub Tranport Server.

2nd question:   I have applications running on now Exchange Severs that need to send email out external.  I tried configuring a send connector for those network ip but it does not seem to work.   Should I have them configure to send out email via BarracudaSystem?
0
mobot
Asked:
mobot
  • 4
  • 2
3 Solutions
 
Peter HutchisonSenior Network Systems SpecialistCommented:
Your MX record should point to your Edge Transport server. This will look after incoming and outgoing mail to a from your main Exchange systems.

I would set up a new 'Receive Connector' on Hub transport server with a list of IPs of the application servers that need to send to it. The existing send connectors will look after sending out email to external users.
0
 
R--RCommented:
Normally the MX is pointed to the companys firewall. Which was then natted to the Exchange server.
Point MX record to Barracuda 400 & then configure Barracuda 400 to relay mails to Hub transport server.

Check this from http://exchangeserverpro.com to create connector for application to send emails via exchange server.

http://exchangeserverpro.com/how-to-configure-a-relay-connector-for-exchange-server-2010/
0
 
mobotAuthor Commented:
This is the weirdest thing I have tried what you but have suggested and the applications still cannot relay through my sever.   My configuration

Hub Tranport
  Receive Connectors - Custom
      Allow2Relay
           General - FQDN is correct
            Network - Receive mail from remote sever - 172.16.0.0/24 and 172.16.19.191
            Authentication - Transport Layer Security (check); I had even check Basis Authentication
              Permission Groups - none check and had tried it with Anonymous users checked

They still cannot send email, what am I missing
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Peter HutchisonSenior Network Systems SpecialistCommented:
How does the application connect? Does it use a username and password to connect to Exchange, to enable relay the user should have a mailbox (even if its empty), you cannot use a plain Ad a/c. Then you need at least Basic Authentication.

If no username and password, then you need to use Anonymous connection, if sending external mail, then you need to apply more permissions to your Connector to allow it:

# set-relay-access.ps1
Param($name)
Get-ReceiveConnector $name | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"
0
 
mobotAuthor Commented:
It is connecting without an user account and password.   I will try to the set relay setting to see if that fixes the problem.   Thank you.
0
 
mobotAuthor Commented:
Also, I can get it to relay if explictly add an i.p. address but it does not work if try to use the network with CIDR mask.  For example 172.16.0.0/22
0
 
mobotAuthor Commented:
It solved all but one problem where I still have to put in individual ip address of devices needing to relay an email message.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now