Email redirection

abc.com  MX perference = 10, mail exchanger = MAIL1.abc.com
abc.com  MX perference = 20, mail exchanger = MAIL2.abc.com

Independent Mail server
MAIL1.abc.com (Exchange 2007)
MAIL2.abc.com (Linux postfix server)

Supposed some unknown email or MAIL1 email service down. Based on MX record, those email will be auto tried to send to MAIL2 server.  The both server have their own user accounts, so those email are also rejected by MAIL2 server.
 
As I know, some ISP will have some services to hold those unreceived email, and then send back to clients when MAIL1 service is normally restarted


Question:
1. Can I set MAIL2 for temporary pick up all MAIL1 incoming email when MAIL1 is down, same as ISP service? Is it possible (MAIL1 = Exchange / MAIL2 = Linux)  or (MAIL1 &  MAIL2 are both running Exchange) ? If worked, what I need to prepare?

2. If not, how can I prevent all MAIL1 unacceptable email redirect to MAIL2?


Thanks !
LVL 13
rhinocerosAsked:
Who is Participating?
 
ChrisCommented:
i don't think that will work if you have to different mail server apps and OS's. If you have two Hub Transport Servers for Exchange then you could set up an NLB that would provide redunancy.

if you want mail2 to take over you chould change the NAT'ing on your firewallso that mail1 record points to mail2, but obviously this is a manual step.

You could potentially use a DNS round robin to point at the two server but that might interfere with normal mail flow when both are available. You would need to separate those from client access dns records i.e. OWA.

To do this you would need to set up the shared namespace (i.e. non authoritative for the domain name)  on exchange 2007 so the two servers bounce the mail between them.
0
 
setasoujiroCommented:
you can do this by setting up a catchall for that domain or server 2.
then distribute the mails using pop or whatever to server1

to prevent the mail being rerouted, just remove the mx
0
 
ghodderCommented:
On my network, we have our primary Exchange 2010 server which handles all user mailboxes. We also have a Linux VPS which hosts all our websites and is configured to be the backup MX.

For each Internet domain we have public DNS records something like "contoso.com. IN MX 10 exchange.contoso.com." and "contoso.com. IN MX 20 backupmx.contoso.com.". That means any time someone wants to send us email, they will try the lowest valued MX first (i.e. exchange.contoso.com), and if that can't be contacted, they'll try the VPS.

The VPS is then configured as a "remote" mail exchanger (terminology depends which Linux mail daemon you plan to use) but basically it's configured so that it will accept mail for the particular domain, but it also knows the domain is not hosted locally. If it receives an email for that domain it will continually try to deliver it to the lowest DNS record being our Exchange server.

Any mail server software should be capable of this setup (especially where Exchange or Linux is envolved), it's just a case of setting it up.
0
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

 
einaraCommented:
In our network, we have 3 Linux Postfix servers that has the MX role. Our Exchangeservers are not in the MX records.

The transportrules on the Postfixservers are set to route mail to the accepted domains on the different Exchange servers.

If one of the Exchangeservers is down, the Linuxservers cache the mail until the Exchange is up again. Then the cached mail will be delivered to the Exchange.

We want to separate the MX from the Exchange, and our solution works great for us.
0
 
rhinocerosAuthor Commented:
Thanks everyone !

setasoujiro:
>>to prevent the mail being rerouted, just remove the mx

MAIL1.abc.com (Exchange 2007)
MAIL2.abc.com (Linux postfix server)
Independent Mail server, they have their jobs and different accunts....
e.g john@MAIL1.abc.com
e.g mary@MAIL2.abc.com

abc.com  MX perference = 10, mail exchanger = MAIL1.abc.com
abc.com  MX perference = 20, mail exchanger = MAIL2.abc.com
In my opinion, mx record is to redirect email to a mail host. Except reroute problem, so the above mx reocrd setting is wrong? If true, what I need to change ?

ghodder:
I will get more info about VPS.

einara:
>>Our Exchangeservers are not in the MX records.
Mx record is to redirect email to a mail host. No MX is also worked?
0
 
einaraCommented:
That's correct. MX points only to the Linux servers. Postfix sends the mail to the Exchangeservers (after SPAM checks etc) via the transport config in Postfix.

For example if we had a domain called abc.com. The MX for that domain points to one of our Linux Postfix servers. In the transport config on the Postfix server, it says that domain abc.com is going to be sent to Exchangeserver1.com. That Exchangeserver has domain abc.com in its accepted domain list. This config lessens the burden on the Exchangeservers, since all SPAM/viruschecks happens on the Linuxservers.

No need for the MX to point directly to an Exchange.
0
 
rhinocerosAuthor Commented:
Any further idea please? Thanks !
0
 
ChrisCommented:
i can suggest an external spam provider that does proper caching of the mail so that it will hold it all for you
0
 
ghodderCommented:
As @irweazelwallis suggested, you could use an external spam filtering provider. That way the public Internet never knows the public IP of your Exchange server (you could configure port 25 to only accept email from your spam provider) and it would avoid the necessity of managing your own backup MX with the added benefit of spam filtering. They would filter any spam/viruses etc, then forward the mail to your Exchange server. In the event the Exchange server is not available (e.g. network outage or hardware failure), they will cache all your email for a period of time until the server is back up and running.

I've been using a Barracuda Spam Firewall appliance on my network for the past 3yrs and it's been excellent. Barracuda also have a cloud filtering product which might be suitable in your case. They will cache your email for up to 96 hours if your local server is unavailable.

McAfee have a SaaS inbound filtering product with various subscription options. The SaaS Inbound Filtering product would be suitable for you.

Webroot gave us a demo of their SaaS filtering service and it also looked quite capable of doing the job.

There are plenty of other providers around. Those are just the few that I've had direct dealings with and would recommend off the top of my head.
0
 
ChrisCommented:
Webroot is one i have used. they will be able to cache I think up to 7 days of emails
That would be the easiest method of trying to cache you emails if one server is offline
0
 
rhinocerosAuthor Commented:
Although I did not get the finally answer, thanks everyone!
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.

All Courses

From novice to tech pro — start learning today.