• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 535
  • Last Modified:

Email Outbound IP

If outbound email is going out on a different ip address than the mx records, is there a way to fix this with dns or similar?
0
Jack_son_
Asked:
Jack_son_
  • 4
  • 3
  • 2
  • +2
2 Solutions
 
n2fcCommented:
MX records control INCOMING email for your domain...

Your OUTBOUND email can either be sent to the RECIPIENT's server (by way of THEIR MX records) or relayed on your behalf via a valid SMTP connection.
0
 
icfireCommented:
You can use a smarthost, or add the ip to an alternative MX record.  
0
 
Jack_son_Author Commented:
So this shouldnt matter?  So just add a second MX?  This ip wouldnt be usable for email delivery.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
icfireCommented:
technically no it shouldn't matter.  You can add a second MX record with a high priority and as long as the first SMTP server is there it will not make it to the second one.  I assumed that you were having issues sending mail because someone was doing a MX lookup and complaining that the IP doesn't match the MX record.  
0
 
bfelskeCommented:
I'm wondering if you're asking this due to a rdns issue...in any case on your fiirewall you could create a policy to NAT the outbound traffic from your mailserver to the public address you have setup for your mx record.
0
 
Jack_son_Author Commented:
So use the same address public ip address for outbound mail as inbound?  
0
 
bfelskeCommented:
Yes, you can NAT the outbound to be the same as the mx inbound, all the rdns and mx lookups that recipient mail systems do would then recieve the expected results.
0
 
Jack_son_Author Commented:
Ok, the difficulty is the configuration in the firewall.    Since multiple inside devices share the same public ip as they all work towards email, it seems it has to exit on a separate ip.  I will try to work around this though.
0
 
bfelskeCommented:
Depending on your firewall you'll likely need to setup a dynamic ip pool that would be used for outbound traffic...in this case you would create a pool of one address...then use that pool for your outbound NAT on a new outbound policy that specifies your internal mail server to all outbound hosts.   the policy should be placed just above your outbound policy for all to all.
0
 
Alan HardistyCo-OwnerCommented:
The important part of MX records is that your Sending FQDN e.g., mail.yourdomain.com resolves correctly to the IP Address that you are sending from and that Reverse DNS is setup on that IP Address, and that Reverse DNS correctly resolves to the same IP.
If you have an MX record that points to one IP address, it is not important.  Just make sure that the IP you send from e.g. 123.123.123.123 has Reverse DNS configured for example, mail.yourdomain.com and that mail.yourdomain.com resolves to IP address 123.123.123.123 in DNS using mail.yourdomain.com.
0
 
Jack_son_Author Commented:
Thanks, this answered my qustion
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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