Your application or website rely on your database to deliver information about products and services to your customers. You can’t afford to have your database lose performance, lose availability or become unresponsive – even for just a few minutes.
Solved
Is there a way to have "split" email on a domain? Some accounts to office 365 and some to a pop server?
Posted on 2016-08-22
Right now I have a bunch of mail accounts on my domain and the MX record points to a POP mail server. I pay a flat rate per month for the email / web hosting.
Each computer I manage has a unique email address to send out reports, pass, fail results from the backup program. That way if any machine gets compromised, that email account can be shut down and not affect the other computers ability to email reports.
But I'd like to move to office 365 for myself for the exchange mail hosting of my account.
Is there a way to set things up so I can keep having an unlimited number of accounts for the computers I manage and my account be on o365?
Or is the answer to change ALL?? :( the computers to a different domain that's on the pop server and my domain is on 0365?
thanks!
Each computer I manage has a unique email address to send out reports, pass, fail results from the backup program. That way if any machine gets compromised, that email account can be shut down and not affect the other computers ability to email reports.
But I'd like to move to office 365 for myself for the exchange mail hosting of my account.
Is there a way to set things up so I can keep having an unlimited number of accounts for the computers I manage and my account be on o365?
Or is the answer to change ALL?? :( the computers to a different domain that's on the pop server and my domain is on 0365?
thanks!
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
5
3
2
12 Comments
Active 1 day ago
It really depends on the small details. But in general you can do the so-called simple domain sharing as detailed here: http://web.archive.org/web/20150429002219/http://community.office365.com/en-us/w/exchange/786.simple-domain-sharing-for-smtp-email-addresses.aspx
Or a newer version of the article available here: https://support.office.com/en-us/article/Pilot-Office-365-with-a-few-email-addresses-on-your-custom-domain-39cee536-6a03-40cf-b9c1-f301bb6001d7
Or a newer version of the article available here: https://support.office.com/en-us/article/Pilot-Office-365-with-a-few-email-addresses-on-your-custom-domain-39cee536-6a03-40cf-b9c1-f301bb6001d7
Active today
Hi,
you can have that mix. After you register your domain to office 365, there are 2 options:
1. Create mailbox for your account on Office 365, change MX to point to Office 365. Then configure Exchange on o365, to be non-authority for your domain, so that it will automatically forward email for all other accounts not on o365 to your mail server. That way your users are going to receive email as before.
OR
2. Create mailbox for your account on Office 365. Then configure your mail server to forward email to you account on o365. Forward can be done via default office 365 address, such as username@company.onmicroso
Regards,
Ivan.
you can have that mix. After you register your domain to office 365, there are 2 options:
1. Create mailbox for your account on Office 365, change MX to point to Office 365. Then configure Exchange on o365, to be non-authority for your domain, so that it will automatically forward email for all other accounts not on o365 to your mail server. That way your users are going to receive email as before.
OR
2. Create mailbox for your account on Office 365. Then configure your mail server to forward email to you account on o365. Forward can be done via default office 365 address, such as username@company.onmicroso
Regards,
Ivan.
Active today
THANKS GUYS!!!
so now I need to ask - does this approach make more sense / just as stable an arrangement as putting the machines on a different domain?
And when the machines are sending email to me on the same domain, will that cause problems? The pop server will get the mail, it'll be for the same domain. If it doesn't look at public MX record, it'll see that it's the mail server for the domain and it never gets to me?
so now I need to ask - does this approach make more sense / just as stable an arrangement as putting the machines on a different domain?
And when the machines are sending email to me on the same domain, will that cause problems? The pop server will get the mail, it'll be for the same domain. If it doesn't look at public MX record, it'll see that it's the mail server for the domain and it never gets to me?
Active today
And Ivan - which of your 2 ways is 'better'?
vasil and your 2nd way have the mail going through the current mail server. I kinda like mail getting to o365 first - microsoft's servers are liekly more stable than hostgators.
Is there a doc for your method 1? I don't know how to do:
Then configure Exchange on o365, to be non-authority for your domain,
vasil and your 2nd way have the mail going through the current mail server. I kinda like mail getting to o365 first - microsoft's servers are liekly more stable than hostgators.
Is there a doc for your method 1? I don't know how to do:
Then configure Exchange on o365, to be non-authority for your domain,
Active 1 day ago
It's the "internal relay" setting - it will "instruct" Exchange to check for the recipients and if such are not found, it will route the message to where your MX points at. If your MX points at the same system (O365), this will simply create a mail loop/NDRs, so it should stay pointed at your current hoster.
Internal delivery is always "direct", it will not look at the MX no matter what the domain is set for.
Whichever way you choose, you obviously cannot have the MX record pointing at both systems, so you need to "compensate" for it. One method is using the Internal relay configuration, another method is simply using forwarding. You can achieve the same with Connectors as well, but generally speaking those are more complicated.
Internal delivery is always "direct", it will not look at the MX no matter what the domain is set for.
Whichever way you choose, you obviously cannot have the MX record pointing at both systems, so you need to "compensate" for it. One method is using the Internal relay configuration, another method is simply using forwarding. You can achieve the same with Connectors as well, but generally speaking those are more complicated.
Active today
Hi,
for me first choice is better, since all email will go via Office 365, and that way you will have good antispam protection.
Your clients, that are left on old mail server, will have to either change the way they are sending email to you, by sending you email to username@company.onmicroso
The way you do it, is configure forward for all email from your mailbox to your new mailbox on office 365, via default email address that you will receive when creating mailbox there. That mail address is something like username@company.onmicroso
Your user don't need to know anything, and you will receive all email. When you reply to them they will think it came from you normal mailbox.
PS: You should configure send connector (on office 365 exchange) between your office 365 and old mail server, since MX is going to point to Office 365. if you don't have send connector, email sent from you will go into loop.
Regards,
Ivan.
for me first choice is better, since all email will go via Office 365, and that way you will have good antispam protection.
Your clients, that are left on old mail server, will have to either change the way they are sending email to you, by sending you email to username@company.onmicroso
The way you do it, is configure forward for all email from your mailbox to your new mailbox on office 365, via default email address that you will receive when creating mailbox there. That mail address is something like username@company.onmicroso
Your user don't need to know anything, and you will receive all email. When you reply to them they will think it came from you normal mailbox.
PS: You should configure send connector (on office 365 exchange) between your office 365 and old mail server, since MX is going to point to Office 365. if you don't have send connector, email sent from you will go into loop.
Regards,
Ivan.
Active today
So, in short, for first solution..
1. Register your domain to office 365.
When logged to o365 --> Settings --> Domains --> Add Domain
2. Verify your domain and after that do not choose to automatically set up DNS records and so on, since you want to configure everything, and then take care of DNS records.
3. Create mailbox for your self, and change primary SMTP from username@company.onmicroso
This is done in Exchange --> Recipients --> edit your mailbox --> email address --> add new address.
4. Configure new domain as internal relay
This is done in Exchange --> mail flow --> accepted domain
5. Configure connectors from office 365 to you old mail server.
Link: https://technet.microsoft.com/en-US/library/ms.exch.eac.ConnectorIsConnectorNeeded(EXCHG.150).aspx?v=15.1.549.29&l=1&s=BPOS_S_E15_0
6. Configure forward for your old mailbox, to forward all email to your office 365 default address, such as username@company.onmicroso
7. Test to see if your users can send email to that address.
8. If it is ok, then reconfigure MX to point to office 365. Take care of TTL, and possible lower it before doing this. I would do it during then night and on Saturday or so, when email flow is low. You should test everything to see if it is working ok after this.
Maybe I have missed something, since this is a "fast publish", before lunch :)
Regards,
Ivan.
1. Register your domain to office 365.
When logged to o365 --> Settings --> Domains --> Add Domain
2. Verify your domain and after that do not choose to automatically set up DNS records and so on, since you want to configure everything, and then take care of DNS records.
3. Create mailbox for your self, and change primary SMTP from username@company.onmicroso
This is done in Exchange --> Recipients --> edit your mailbox --> email address --> add new address.
4. Configure new domain as internal relay
This is done in Exchange --> mail flow --> accepted domain
5. Configure connectors from office 365 to you old mail server.
Link: https://technet.microsoft.com/en-US/library/ms.exch.eac.ConnectorIsConnectorNeeded(EXCHG.150).aspx?v=15.1.549.29&l=1&s=BPOS_S_E15_0
6. Configure forward for your old mailbox, to forward all email to your office 365 default address, such as username@company.onmicroso
7. Test to see if your users can send email to that address.
8. If it is ok, then reconfigure MX to point to office 365. Take care of TTL, and possible lower it before doing this. I would do it during then night and on Saturday or so, when email flow is low. You should test everything to see if it is working ok after this.
Maybe I have missed something, since this is a "fast publish", before lunch :)
Regards,
Ivan.
Active today
Thanks!!!
But all that said, would you do that vs. just have a different domain for the client email (this is NOT something a client user actually uses... this is just an email address that is stored in their PCs for shadowprotect to send reports. they don't use them. it's only for the machine to automatically be able to send emails to me.
touching each machine to change the email address stored on it seems like a pain, but I really don't like jury rigged / kluged things. they inevitablly break.
thoughts?
But all that said, would you do that vs. just have a different domain for the client email (this is NOT something a client user actually uses... this is just an email address that is stored in their PCs for shadowprotect to send reports. they don't use them. it's only for the machine to automatically be able to send emails to me.
touching each machine to change the email address stored on it seems like a pain, but I really don't like jury rigged / kluged things. they inevitablly break.
thoughts?
Featured Post
Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
It’s the first day of March, the weather is starting to warm up and the excitement of the upcoming St. Patrick’s Day holiday can be felt throughout the world.
This article describes how to import an Outlook PST file to Office 365 using a third party product to avoid Microsoft's Azure command line tool, saving you time.
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …
The Email Laundry PDF encryption service allows companies to send confidential encrypted emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…
Suggested Courses
Course of the Month11 days, 7 hours left to enroll
719 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.