Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60

Deprecated: YoastSEO_Vendor\League\OAuth2\Client\Provider\AbstractProvider::authorize(): Implicitly marking parameter $redirectHandler as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/league/oauth2-client/src/Provider/AbstractProvider.php on line 416

Deprecated: YoastSEO_Vendor\GuzzleHttp\Client::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/Client.php on line 181

Deprecated: YoastSEO_Vendor\GuzzleHttp\ClientInterface::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/ClientInterface.php on line 77
{"id":1208,"date":"2012-08-21T00:01:14","date_gmt":"2012-08-20T22:01:14","guid":{"rendered":"https:\/\/blog.sharedove.com\/adisjugo\/?p=1208"},"modified":"2012-08-21T00:01:14","modified_gmt":"2012-08-20T22:01:14","slug":"how-did-i-move-my-mothers-email-and-my-wifes-web-site-to-office365-and-didnt-get-killed-in-the-process-part-3-my-mothers-mail","status":"publish","type":"post","link":"https:\/\/blog.sharedove.com\/adisjugo\/index.php\/2012\/08\/21\/how-did-i-move-my-mothers-email-and-my-wifes-web-site-to-office365-and-didnt-get-killed-in-the-process-part-3-my-mothers-mail\/","title":{"rendered":"How did I move my mother\u2019s email and my wife\u2019s web site to Office365, and didn\u2019t get killed in the process \/\/ Part 3: My mother’s mail"},"content":{"rendered":"

In the first post of this mini series on migrating my private Linux\/cPanel\/IMAP based stack to Office 365, I was writing about my motivation for making this move<\/a>. The second post was on planning the migration process and verifying my domain(s) with Office 365<\/a>, This post will be about actual migration of IMAP e-mail accounts from my Linux server to Office 365.<\/p>\n

First thing first \u2013 let\u2019s create required user accounts. Even if that email addresses will be inactive upon creation (DNS records are still pointing to the Linux server), we need to create them first, so that mails would have a place to arrive, when DNS records are changed.<\/p>\n

Go to the users, and create your user, on wished domain (the domain must be registered with Office 365 and verified<\/a>, if it is not, please read my previous post<\/a>)<\/p>\n

$\"024$ <\/a><\/p>\n

If you need to, you can click on \u201cMore\u201d tab, and then on \u201cExchange \/ Change mailbox settings\u201d to add some aliases for this account:<\/p>\n

$\"020$ <\/a><\/p>\n

$\"021-_user_alias_03\"$ <\/a><\/p>\n

Now, when all of the required user accounts have been created, let\u2019s change the DNS.<\/p>\n

In your Office 365 admin panel, click on the \u201cDomains\u201d link. Your domain should already have status \u201cverified\u201d. If this is not the case, please read my previous post on domain verification with Office 365.<\/a><\/p>\n

$\"008-05\"$ <\/a><\/p>\n

Click on the domain name (in my case, my test domain \u201cprogressive.ba\u201d, and then click on the DNS settings link:<\/p>\n

$\"008-05a\"$ <\/a><\/p>\n

On the following screen, you\u2019ll see all the required DNS settings, which are necessary to undertake in order that Exchange Online and Lync Online can work with this domain:<\/p>\n

$\"008$ <\/a><\/p>\n

As you see, there are quite few required DNS records: an MX record and an TXT record for the \u201croot\u201d domain (progressive.ba), CNAME records for autodiscover.progressive.ba, sip.progressive.ba and lyncdiscover.progressive.ba, and Lync-specific SRV records for _sip._tls.progressive.ba and _sipfederationtls._tcp.progressive.ba<\/p>\n

Let\u2019s first add the MX record. Login into your cPanel on your Linux server, and click on the \u201cMX Entry\u201d icon:<\/p>\n

$\"008-07\"$ <\/a><\/p>\n

Choose your domain, and then select \u201cRemote Mail Exchange\u201d and click on the \u201cChange\u201d button. After that, click on \u201cAdd New Record\u201d, and enter required MX record (progressive-ba.mail.eo.outlook.com in my case), with priority 0, and click on \u201cAdd New Record\u201d button.<\/p>\n

$\"009$ <\/a><\/p>\n

Now you should see both local, and remote (Office 365) MX records, please delete the local one \u2013 only Office 365 specific record should remain.<\/p>\n

$\"010$ <\/a><\/p>\n

Now, go back to the cPanel home, and click on the \u201cAdvanced DNS Zone Editor\u201d icon, it\u2019s time to add all the other DNS records (except SRV):<\/p>\n

$\"010a-__delete_old_,x\"$ <\/a><\/p>\n

On the next screen, please add all requested TXT and CNAME records. The result should look like on the screen below \u2013 the yellow underlined record has been added during the domain verification (previous post<\/a>), and red underlined records have been added just now (1 TXT record, and 3 CNAME records from above).<\/p>\n

$\"011\"$ <\/a><\/p>\n

The next step is to add SRV records. It is not possible to add them through the cPanel interface, but if you have access to your WHM panel, that is an easy thing to do:<\/p>\n

Go to ‘DNS Functions >> Edit DNS Zone’<\/li>\n

Select the domain for which you need to add the SRV record (\u201cprogressive.ba” in my case)<\/li>\n

Select ‘SRV’ from the drop down.<\/li>\n<\/ol>\n
Now, enter the first column with the ‘_sip._tls.YOURDOMAIN.COM’ and fill up the required fields, as requested by Office 365 above:<\/p>\n
\n
Priority: 100<\/li>\n
Weight: 1<\/li>\n
Port: 443<\/li>\n
Hostname: sipdir.online.lync.com<\/li>\n
TTL: 3600<\/li>\n<\/ul>\n
Do the same with the _sipfederationtls._tcp.YOURDOMAIN.COM\u00a0 – as requested from Office 365:<\/p>\n
\n
Priority: 100<\/li>\n
Weight: 1<\/li>\n
Port: 5061<\/li>\n
Hostname: sipfed.online.lync.com<\/li>\n
TTL: 3600<\/li>\n<\/ul>\n
If you don\u2019t have access to the WHM panel, then please ask your administrator (usually your hosting provider), to manually enter the following DNS records for you:<\/p>\n
\n_sip._tls.YOURDOMAIN.COM. 3600 IN SRV 100 1 443 sipdir.online.lync.com.\n\n_sipfederationtls._tcp.YOURDOMAIN.COM. 3600 IN SRV 100 1 5061 sipfed.online.lync.com.\n<\/pre>\n
Please change the \u201cYOURDOMAIN.COM\u201d with your real domain name.<\/p>\n
Now, when you are finished with that, take a coffee break until new records are propagated (it could be a longer coffee break if you depend on the administrator for the SRV records), and then go to the centralops.net<\/a> to check if the DNS records that you entered are successfully applied and propagated.<\/p>\n
First look up the \u201croot\u201d domain (progressive.ba in my case). One MX record, and one TXT record, entered in the previous step, should be found there:<\/p>\n
$\"dns01\"$ <\/a><\/p>\n
Now, look up the \u201cautodiscover.YOURDOMAIN.COM\u201d, \u201csip.YOURDOMAIN.COM\u201d and \u201clyncdiscover.YOURDOMAIN.COM\u201d. Each of them should have a CNAME record entered above. Please replace \u201cYOURDOMAIN.COM\u201d with your real domain name.<\/p>\n
$\"dns02a\"$ <\/a><\/p>\n
$\"dns02\"$ <\/a><\/p>\n
$\"dns03\"$ <\/a><\/p>\n
The last verification step is to look up SRV records in the _sip._tls.YOURNAME.COM and _sipfederationtls._tcp.YOURNAME.COM domains. You should get the following results:<\/p>\n
$\"dns04\"$ <\/a><\/p>\n
$\"dns05\"$ <\/a><\/p>\n
Now, when you have confirmed that all of the DNS changes are propagated, it is time to do the final test \u2013 to check if the emails are being delivered to Office 365.<\/p>\n
Go write a test mail to your account created above, or to one of the aliases. The mail should already arrive where it is intended to $\"Smile\"$ <\/p>\n
SEND:<\/p>\n
$\"022$ <\/a><\/p>\n
Receive:<\/p>\n
$\"023$ <\/a><\/p>\n
That\u2019s all for today, folks. The next episode will see us talking about mail forwarders, and moving my wife\u2019s web site to SharePoint Online.<\/p>\n
\n\t\t\t
\n\t\t\t <\/div><\/div>\n\t\t