Exchange Online Migration From POP3
-
@JaredBusch said:
But it does not hurt to set it all up now, because the SRV record is an inclusive one, not a restrictive one. Or am I forgetting what the -all does.
The SRV record is for lync, not for SPF.
The TXT record is for old school SPF. As I learned here (or that other forum) there is now an official SPF record type, it's best to have both if you want to cover all bases, as older DNS servers won't recognize the newer SPF record type.
And you're right, if he's adding them to Cloudflare now, he might as well put them all in.
-
@Dashrender said:
The SRV record is for lync, not for SPF.
Yes, I was thinking TXT record. Sorry to confuse.
-
@Dashrender said:
@JaredBusch said:
But it does not hurt to set it all up now, because the SRV record is an inclusive one, not a restrictive one. Or am I forgetting what the -all does.
The SRV record is for lync, not for SPF.
The TXT record is for old school SPF. As I learned here (or that other forum) there is now an official SPF record type, it's best to have both if you want to cover all bases, as older DNS servers won't recognize the newer SPF record type.
And you're right, if he's adding them to Cloudflare now, he might as well put them all in.
And it is OK to proceed with CloudFlare now or better to wait until this evening?
-
@garak0410 said:
And it is OK to proceed with CloudFlare now or better to wait until this evening?
If everything is imported matching the POP3 provider, I would just do it now. because it will be transparent.
-
On that note, AFK for lunch.
-
@JaredBusch said:
@garak0410 said:
And it is OK to proceed with CloudFlare now or better to wait until this evening?
If everything is imported matching the POP3 provider, I would just do it now. because it will be transparent.
Great...going to proceed...
-
@JaredBusch said:
@garak0410 said:
And it is OK to proceed with CloudFlare now or better to wait until this evening?
If everything is imported matching the POP3 provider, I would just do it now. because it will be transparent.
Agreed, as long as the settings are all the same, computers on the internet won't really see a difference.
-
Here's a question that will help determine if you need to do more for autodiscover to work.
Let's assume your domain is acme.com for email
What is your domain name inside your network?
If your domain name is acme.com, then you will need to add a DNS entry internally to your DNS server for autodiscover just like you did at cloudflare.
If your domain name is something like acme.local, then you need to do nothing.
-
@Dashrender said:
@JaredBusch said:
@garak0410 said:
And it is OK to proceed with CloudFlare now or better to wait until this evening?
If everything is imported matching the POP3 provider, I would just do it now. because it will be transparent.
Agreed, as long as the settings are all the same, computers on the internet won't really see a difference.
I noticed CloudFlare did not bring over autoconfig and autodiscover of the POP3 provider DNS settings...will add those with my autodiscover for O365.
-
@garak0410 said:
@Dashrender said:
@JaredBusch said:
@garak0410 said:
And it is OK to proceed with CloudFlare now or better to wait until this evening?
If everything is imported matching the POP3 provider, I would just do it now. because it will be transparent.
Agreed, as long as the settings are all the same, computers on the internet won't really see a difference.
I noticed CloudFlare did not bring over autoconfig and autodiscover of the POP3 provider DNS settings...will add those with my autodiscover for O365.
Hit a snag...when adding the O365 autodiscover, it gave me this message:
You cannot add a CNAME record when there is already an A, AAAA, or CNAME record with the same 'name' value
The original autodiscover is an "A"...
-
@garak0410 said:
I noticed CloudFlare did not bring over autoconfig and autodiscover of the POP3 provider DNS settings...will add those with my autodiscover for O365.
How long ago did you add them? Assuming there is a poll feature in cloudflare so you can repoll the old DNS hosts, that should pull them, but personally, I'd simply open two windows side by side and compare, any that are missing, just add to cloudflare manually.
-
@garak0410 said:
Hit a snag...when adding the O365 autodiscover, it gave me this message:
You cannot add a CNAME record when there is already an A, AAAA, or CNAME record with the same 'name' value
The original autodiscover is an "A"...
So it is there. perhaps on a different page.
-
@Dashrender said:
@garak0410 said:
Hit a snag...when adding the O365 autodiscover, it gave me this message:
You cannot add a CNAME record when there is already an A, AAAA, or CNAME record with the same 'name' value
The original autodiscover is an "A"...
So it is there. perhaps on a different page.
I had to manually enter the autodiscover info from the existing POP3 provider into CloudFlare because it didn't carry over...did that...went to add the O365 AutoDiscover info and that's when I got the error...
And both were entered autodiscover.domainname.com
-
Wondering if I should make the name autodiscover.outlook.com as well as the value, since I already have that autodiscover....or will that not work?
-
I've made the move to CloudFlare...just going to have to fix this autodiscover problem with O365
-
@garak0410 said:
Wondering if I should make the name autodiscover.outlook.com as well as the value, since I already have that autodiscover....or will that not work?
This won't work.
When you configure Outlook it takes your domain name for example [email protected] and looks for a DNS entry at autodiscover.acme.com -
@garak0410 said:
I had to manually enter the autodiscover info from the existing POP3 provider into CloudFlare because it didn't carry over...did that...went to add the O365 AutoDiscover info and that's when I got the error...
And both were entered autodiscover.domainname.com
OK hold on a second.. was there an autodiscover record in your old POP3 CP? was it something like A record Autodiscover xxx.xxx.xxx.xxx?
If so, you can't have two records with the same name. That old autodiscover record points to your old POP3 setup... You'll need to delete that record and create a new CNAME pointing to the one provided by O365.
This shouldn't affect anything because the clients that need to talk to the old POP3 are already configured to connect to it (though I suppose that for some craziness, they could be trying to pickup mail from autodiscover.acme.com, and if that's the case, you will break receipt of new mail from the POP3 provider).
Please confirm this by looking at the settings in one of your preconfigured Outlook clients.. what is the server name for POP3 and SMTP, make sure it's not autodiscover.somethingorother.com
-
@Dashrender said:
@garak0410 said:
I had to manually enter the autodiscover info from the existing POP3 provider into CloudFlare because it didn't carry over...did that...went to add the O365 AutoDiscover info and that's when I got the error...
And both were entered autodiscover.domainname.com
OK hold on a second.. was there an autodiscover record in your old POP3 CP? was it something like A record Autodiscover xxx.xxx.xxx.xxx?
If so, you can't have two records with the same name. That old autodiscover record points to your old POP3 setup... You'll need to delete that record and create a new CNAME pointing to the one provided by O365.
Correct...I brought over the old Autodiscover pointing to POP3...so it is safe to delete, add O365 and we can still receive POP3? And thanks for the patience...would rather be safe....
-
@Dashrender said:
@garak0410 said:
I had to manually enter the autodiscover info from the existing POP3 provider into CloudFlare because it didn't carry over...did that...went to add the O365 AutoDiscover info and that's when I got the error...
And both were entered autodiscover.domainname.com
OK hold on a second.. was there an autodiscover record in your old POP3 CP? was it something like A record Autodiscover xxx.xxx.xxx.xxx?
If so, you can't have two records with the same name. That old autodiscover record points to your old POP3 setup... You'll need to delete that record and create a new CNAME pointing to the one provided by O365.
This shouldn't affect anything because the clients that need to talk to the old POP3 are already configured to connect to it (though I suppose that for some craziness, they could be trying to pickup mail from autodiscover.acme.com, and if that's the case, you will break receipt of new mail from the POP3 provider).
Please confirm this by looking at the settings in one of your preconfigured Outlook clients.. what is the server name for POP3 and SMTP, make sure it's not autodiscover.somethingorother.com
They are all pointing to mail.domainname.com...so should be safe to delete and add the O365 autodiscover...
-
What is interesting now, is after I moved to CloudFlare and added all but the MX from O365, waited 15 minutes and clicked next in O365, it said it found the info except for MX records and autodiscover. However, a check of all my O365 records now show X's, even 30 minutes later...wonder why I found it at first (after 15 mins) but not now...
