Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

MXRecords and reverse lookup for SMTP services.

Greetings EE Gods.....

I have an exchange server that sends SMTP out one IP, however gets NAT'd to a second.  In Addition, the outbound IP address is NOT MXRecorded because that is not our Primary IP address to the ISP.  I have three, and what I need to do is fool the destination end to believe it is coming from one IP vice another.  My outbound data is *.*.*.5, however my MXRecord is on my primary line at *.*.*.3

I need the data to continue out on .5, but have the destination think its coming from .3 so I don't get caught in spam filters.  I do NOT have the ability to add a record to the MXRecord.

Thankyou.
0
mtmadhatt
Asked:
mtmadhatt
  • 3
  • 2
1 Solution
 
Chris DentPowerShell DeveloperCommented:

The MX Record effects Inbound mail only. It has no impact at all on Outbound mail.

On the other hand, you must have a PTR record and a valid name for the IP address the server does use to send out mail. Can you add those? The name will be via your DNS host (if that's not yourself), and the name must be set on the SMTP service. The PTR record is normally set by your ISP (or whoever provides the network connection the SMTP server uses).

If you can't have those then you must relay mail out through a third party if you expect mail to be delivered reliably.

Chris
0
 
mtmadhattAuthor Commented:
ok. We know that our PTR records point to *.*.*.3, but our data goes out *.*.*.5.
We are having difficulty getting our PTR, sorry for the  bad nouns, moved.

How can I virtually make the distant end think *.3 even though it is coming from *.5?

Thanks.
0
 
Chris DentPowerShell DeveloperCommented:

No, I'm afraid not.

You need to be able to establish a TCP connection, that means it needs to get the response back from the remote server. It cannot possibly get that response if you're faking the IP (bad return path).

You can't change the network address translation so it uses .5?

For the PTR records, it's basically an IP pointing to a name, so rather than it pointing to .3, it's .3 pointing to a name (if you see what I mean).

Chris
0
 
mtmadhattAuthor Commented:
I was afraid you were going to say that.  Ok, so it sounds like i"m down to two possible solutions.  I know where to go from here.
Thanks.
0
 
Chris DentPowerShell DeveloperCommented:

Good luck :)

Chris
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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