Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

MS Exchange 2007 - 3rd party application

Posted on 2013-12-11
2
Medium Priority
?
161 Views
Last Modified: 2013-12-29
Hello everyone,

We have a third party application that runs on a server external to our organization. This application needs to send emails from a mailbox on our Exchange 2007 server, so that the emails going out appear to be coming from this email address and any bounce backs are routed back to the third party application on the external server so that they can deal with it.
 
Is there a way that we can accomplish this? If so, how? I presume it has something to do with creating a new receive connector and specifying the external server’s IP address as the only server allowed to do this. I’m just uncertain about all of the steps involved that will make this happen.

Thank you all in advance for reading/answering my questions

Cheers
0
Comment
Question by:Bibecu
2 Comments
 
LVL 9

Accepted Solution

by:
guswebb earned 2000 total points
ID: 39712460
The 3rd party application can send emails from whatever address you like e.g. mail@mydomain.com. You will need to make sure that it's IP address is authoritative for sending mail from your chosen domain name. You do this via setting an SPF record in DNS (see https://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/) and also by applying reverse DNS to your IP to match the FQDN of your 3rd party's externally facing IP address e.g. mail.mydomain.com. Your ISP can set that for you. Adopting these steps will *help* deliverability of those emails but does not guarantee it. There are other ways in which you can increase the chances of your mail landing in the correct places and not being filtered on the recipient's end.

The problem you face now is that your Exchange server will be currently set to receive all inbound traffic for your domain. So, any bounce backs will be delivered to your Exchange server and not the 3rd-party application. You could change this by altering the MX records for your domain to include the IP address of the 3rd party application and giving it a higher priority than your current MX record that points to your Exchange server, however when you do that, *all* mail for your domain will then route to the 3rd party application's IP address and not to your Exchange server.

I would suggest you don't follow this last step but instead allow the bounce backs to be delivered to your Exchange server. You can forward them on from there using a mailbox rule to the other server for processing, if that's what you need to do.

What processing are you wanting to do on the bounce backs exactly?
0
 

Author Closing Comment

by:Bibecu
ID: 39744556
Sorry for the delay, I was away on vacation .   Thanks for your answer, very good
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
Today as you open your Outlook, you witness an error message: “Outlook is using an old copy of your Outlook Data File…”. Probably, Outlook is accessing an old OST file.
Viewers will learn the different options available in the Backstage view in Excel 2013.
The viewer will learn how to use a discrete random variable to simulate the return on an investment over a period of years, create a Monte Carlo simulation using the discrete random variable, and create a graph to represent the possible returns over…

876 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question