Secondary mail delivery FQDN

Hi,

Our mails are delivered to mail.company.com (which has an MX record to our external IP Address).
It goes through our Exchange 2007 Edge Transport Server and is then delivered to the main Exchange 2008 HUB Transport server.

Recently we've registered a secondary MX address, mail2.company.com, that corresponds with our second external IP Address. We want to have this as a backup mail delivery address in case provider 1 goes down.

My question is 2-fold (first question being the main issue) :

Do I need to configure something on the Edge Transport server in order for both mail and mail2.company.com to work ? (like adding an FQDN somewhere or an extra receive connector ?)

And secondly, our provider warned for spammers who particulary aim at secondary MX records. Is this true ? Will we see more spam attempts simply because we've added a backup mail domain ?
Both internet connection go through the same forefront server with specific antispam settings, not to mention antispam settings on the Edge server, so I don't think it matters that much but still.
LVL 3
vindenAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

shauncroucherCommented:
Do I need to configure something on the Edge Transport server in order for both mail and mail2.company.com to work ? (like adding an FQDN somewhere or an extra receive connector ?)

** No, nothing needed on Exchange **

And secondly, our provider warned for spammers who particulary aim at secondary MX records. Is this true ? Will we see more spam attempts simply because we've added a backup mail domain ?

** Yes, that is true, a lot of spammers will use secondary on purpose, so you will see more attempts **

Shaun
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
shauncroucherCommented:
I'm assuming you use NAT or some other method to send SMTP traffic from the public IP's to the same local IP for Edge?

Shaun
0
vindenAuthor Commented:
There's a rule called "Allow incoming email by publishing smtp mail server" on our Forefront server (which is the security server and also the Edge transport server).
I have no idea if that is called NAT technically.

0
shauncroucherCommented:
What I mean is that if you have 2 internet services, Exchange won't care about this. Providing you send the SMTP traffic to the Exchange server listening connector, it doesn't mind what IP address it is coming from.

Shaun
0
vindenAuthor Commented:
Everything I needed to know. Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.