Solved

Office 365 Migration and MX entry

Posted on 2016-10-12
7
51 Views
Last Modified: 2016-10-12
Hi, we are planning following scenario:

What we have now:

Domain test.de associated to a Webserver product at our hosting provider.
The MX entry for test.de goes to the mail cluster of the hosting provider.
We have mailboxes user@test.de online hosted form the hosting provider.
We have an internal exchange server that fetches e-mail from online malboxes via POP3.
Outgoing mail from exchange to the internet is sent by using the smarthost (SMTP) from out hosting provider.
Newsletter-tools are also using the provider`s smarthost for sending e-mails withe the sender adresse e.g. newsletter@test.de.


What we are planning:

Migrate our  internal mailboxes over to Office 365.
Change the MX record for test.de to Office 365.
We will have a spf entry entry that includes as well the Office365 server and the mailcluster servers from the hosting provider.
The domain managemet for test.de stays at the hosting provider.

Is it possible and save that we will still use the mailboxe newsletter@test.de that is located at the hosting provider for outgoing smtp mail (as smarthost) with newsletter tools?

The background is that Office 365 limits outgoing mail per minute and day and that ist notacceptable for newsletters.

I`m afraid that there could be problems with spam-handling if we send as sender newsletter@test.de and the MX record shows to another server (Office 365) than the sending server (hosting provider). Would there be a problem with "Smtp Reverse Dns Mismatch"?

How do you handle that?

Many thanks in advance!
0
Comment
Question by:Systemadministration
  • 2
  • 2
  • 2
  • +1
7 Comments
 
LVL 24

Assisted Solution

by:-MAS
-MAS earned 250 total points
Comment Utility
You dont need to worry about this.
You can keep one mailbox in the current server and move the rest to the O365.
Keep both the MX entries till you successfully configure hybrid configuration.
Once you are done with it you can delete the old MX entry.

FYI your onprem mailboxes are sending emails through the on-prem exchange server as if you are sending before doing a hybrid.

Reverse DNS is not a requirement of O365. It will still remain the same.
1
 

Author Comment

by:Systemadministration
Comment Utility
We are not planning to do a real exchange hybrid configuration.
What I just want is to have mailboxes for the newsletters on the "old" provider side and send valid e-mails to the internet alltough the MX record is not there anymore.
Would that be a problem?
0
 
LVL 49

Accepted Solution

by:
Akhater earned 250 total points
Comment Utility
You should NOT send newsletters thru office 365, if you are happy with your current provider to send newsletters and you keep that IP in the SPF there is no reason why you will not be able to send newsletter from your hostprovider no matter if your MX is on office 365 or not.

You will just not be able to receive emails sent to newsletter@test.de on your old provider

for the reverse DNs you can just have any record pointing to your other host IP address something like SMTP-News.test.de or anything
0
IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 

Author Comment

by:Systemadministration
Comment Utility

for the reverse DNs you can just have any record pointing to your other host IP address something like SMTP-News.test.de or anything

OK, if I understand it right I won`t have to change anythin regarding Reverse Lookup, because the outgoing mail on my provider side is already running over the mailcluster and it is working fine now.
0
 
LVL 49

Expert Comment

by:Akhater
Comment Utility
you don't manage the reverse lookup zone of your provider anyway, you couldn't change it even if you want/had to
0
 
LVL 38

Expert Comment

by:Adam Brown
Comment Utility
You'll be able to do this without any changes to your MX records. You just need to make sure that your SPF records include the IP address your mail server is sending from.
0
 
LVL 24

Expert Comment

by:-MAS
Comment Utility
Agree with Adam. Just required to add IP in the SPF record.
I missed out in my post.
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…

772 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

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now