Moving MX Mail Servers from Google Apps to Fastmail

FromLine · 5 Jan 2016, 02:16 PM

Moving a domain from Google Apps (Google mail with your own domain) to Fastmail.

Changed the MX Mail servers as follows:

10 in1.smtp.messagingengine.com
20 in2.smtp.messagingengine.com

Are these MX Mail servers correct?

I added the domain to the Virtual Domain list at Fastmail

I added the appropriate aliases.

It seems like the MX Mail Servers are connected to Fastmail, since it states "Us"

It's been a couple of hours or so, but email sent to the domain is still going to the Google Mail account.

Does it take a full 24 hours to propagate?

Here's a screenshot of the Fastmail Virtual domain setup.

http://i.imgur.com/EX7xzH2.png

Since is says "Us", am I all connected at Fastmail?

FredOnline · 5 Jan 2016, 02:49 PM

Are you using the Fastmail DNS and are your DNS records correct at your registrar?

See Section 2:

https://www.fastmail.com/help/receiv...ins-setup.html

FromLine · 5 Jan 2016, 02:51 PM

Fastmail is not hosting my nameserver.

FredOnline · 5 Jan 2016, 02:55 PM

Looking at the MX records you've quoted, I think they should be:

in1-smtp, etc.

With a dash and not a dot between "in1 or in2" and "smtp" etc.

FromLine · 5 Jan 2016, 02:58 PM

I copied the same MX Mail Servers that were at my webhost, as I have two active Virtual domains with FM already.

If those were working, these should be okay as well.

FredOnline · 5 Jan 2016, 02:59 PM

What TTL did you use?

FromLine · 5 Jan 2016, 03:01 PM

Doesn't matter.

Since I started this thread, I'm receiving emails now at FM with the new domain, so everything seems to be setup properly.

petergh · 5 Jan 2016, 03:11 PM

MX records may take up to 24 hours to propagate to ALL MX servers, but some may update faster than that. That's why you'll see some mail going to your old mail server, and some to your new mail server until all records have propagated fully.

The host names in{1,2}.smtp.messagingengine.com are still valid, but deprecated. The recommended values are in1-smtp.messagingengine.com and in2-smtp.messagingengine.com. See this blog post from 2012: https://blog.fastmail.com/2012/01/06...s-for-domains/.

To see what MX records are reported for your domain by a handful of MX servers globally, try http://mob.net/~ted/tools/mx.php3.

FromLine · 5 Jan 2016, 03:13 PM

Thanks.

Should I change my MX Mail records on all my virtual domains to:

in1-smtp.messagingengine.com

in2-smtp.messagingengine.com

petergh · 5 Jan 2016, 03:20 PM

[double post - ignore]

petergh · 5 Jan 2016, 03:22 PM

Quote:

Originally Posted by FromLine

Thanks.

Should I change my MX Mail records on all my virtual domains to:

in1-smtp.messagingengine.com

in2-smtp.messagingengine.com

It wouldn't hurt, and sooner or later Fastmail is probably going to ask you to do it anyway.

FredOnline · 5 Jan 2016, 04:15 PM

Quote:

Originally Posted by FromLine

Doesn't matter.

Since I started this thread, I'm receiving emails now at FM with the new domain, so everything seems to be setup properly.

You're welcome.

As a matter of interest, what TTL did you set?

FromLine · 5 Jan 2016, 04:26 PM

Quote:

Originally Posted by FredOnline

What TTL did you use?

Just had to look up TTL:

"TTL: "Time to Live." How long it will take to update the record. This is measured in seconds. A TTL of 3600 seconds means records will take an hour to update. A TTL of 86400 means records will take a day to update. A higher TTL value means less traffic load for the DNS server, but it also means that changing the MX records will take longer"

https://www.google.com/support/enter...te/mx_faq.html

I didn't set a TTL, so I suppose whatever the default is.

I didn't see an option to enter a TTL.

FromLine · 5 Jan 2016, 04:48 PM

Fastmail caught my paste error:

Unfortunately the domain you've setup is not currently delivering email to our servers because the MX records for the domain do not point to our servers.

Current mail exchanges pointed to by this domain:
n2-smtp.messagingengine.com, priority=20
n1-smtp.messagingengine.com, priority=10

Required MX records for delivery directly to FastMail:
10 in1-smtp.messagingengine.com
20 in2-smtp.messagingengine.com

(This is the raw content of the DNS MX records. Depending on your name server configuration, you may be required to enter the numbers 10 and 20 into a field called "priority" or "preference" instead of including them at the start of the record.)

I didn't past the "i" properly.

FromLine · 5 Jan 2016, 04:59 PM

Quote:

Originally Posted by petergh

The recommended values are in1-smtp.messagingengine.com and in2-smtp.messagingengine.com

In the future, please list them like this:

in1-smtp.messagingengine.com

in2-smtp.messagingengine.com

I copied from the middle of the sentence,and didn't get the "i" copied.

5 Jan 2016, 02:16 PM	#1
FromLine The "e" in e-mail Join Date: Jan 2002 Posts: 2,619	Moving MX Mail Servers from Google Apps to Fastmail Moving a domain from Google Apps (Google mail with your own domain) to Fastmail. Changed the MX Mail servers as follows: 10 in1.smtp.messagingengine.com 20 in2.smtp.messagingengine.com Are these MX Mail servers correct? I added the domain to the Virtual Domain list at Fastmail I added the appropriate aliases. It seems like the MX Mail Servers are connected to Fastmail, since it states "Us" It's been a couple of hours or so, but email sent to the domain is still going to the Google Mail account. Does it take a full 24 hours to propagate? Here's a screenshot of the Fastmail Virtual domain setup. http://i.imgur.com/EX7xzH2.png Since is says "Us", am I all connected at Fastmail?

5 Jan 2016, 03:11 PM	#8
petergh Master of the @ Join Date: Jan 2002 Location: Denmark Posts: 1,302	MX records may take up to 24 hours to propagate to ALL MX servers, but some may update faster than that. That's why you'll see some mail going to your old mail server, and some to your new mail server until all records have propagated fully. The host names in{1,2}.smtp.messagingengine.com are still valid, but deprecated. The recommended values are in1-smtp.messagingengine.com and in2-smtp.messagingengine.com. See this blog post from 2012: https://blog.fastmail.com/2012/01/06...s-for-domains/. To see what MX records are reported for your domain by a handful of MX servers globally, try http://mob.net/~ted/tools/mx.php3. Last edited by petergh : 5 Jan 2016 at 03:20 PM.

5 Jan 2016, 02:49 PM	#2
FredOnline The "e" in e-mail Join Date: Apr 2011 Location: Manchester UK Posts: 2,616	Are you using the Fastmail DNS and are your DNS records correct at your registrar? See Section 2: https://www.fastmail.com/help/receiv...ins-setup.html

5 Jan 2016, 02:51 PM	#3
FromLine The "e" in e-mail Join Date: Jan 2002 Posts: 2,619	Fastmail is not hosting my nameserver.

5 Jan 2016, 02:55 PM	#4
FredOnline The "e" in e-mail Join Date: Apr 2011 Location: Manchester UK Posts: 2,616	Looking at the MX records you've quoted, I think they should be: in1-smtp, etc. With a dash and not a dot between "in1 or in2" and "smtp" etc.

5 Jan 2016, 02:58 PM	#5
FromLine The "e" in e-mail Join Date: Jan 2002 Posts: 2,619	I copied the same MX Mail Servers that were at my webhost, as I have two active Virtual domains with FM already. If those were working, these should be okay as well.

5 Jan 2016, 02:59 PM	#6
FredOnline The "e" in e-mail Join Date: Apr 2011 Location: Manchester UK Posts: 2,616	What TTL did you use?

5 Jan 2016, 03:01 PM	#7
FromLine The "e" in e-mail Join Date: Jan 2002 Posts: 2,619	Doesn't matter. Since I started this thread, I'm receiving emails now at FM with the new domain, so everything seems to be setup properly.

5 Jan 2016, 03:13 PM	#9
FromLine The "e" in e-mail Join Date: Jan 2002 Posts: 2,619	Thanks. Should I change my MX Mail records on all my virtual domains to: in1-smtp.messagingengine.com in2-smtp.messagingengine.com

5 Jan 2016, 03:20 PM	#10
petergh Master of the @ Join Date: Jan 2002 Location: Denmark Posts: 1,302	[double post - ignore]

5 Jan 2016, 04:48 PM	#14
FromLine The "e" in e-mail Join Date: Jan 2002 Posts: 2,619	Fastmail caught my paste error: Unfortunately the domain you've setup is not currently delivering email to our servers because the MX records for the domain do not point to our servers. Current mail exchanges pointed to by this domain: n2-smtp.messagingengine.com, priority=20 n1-smtp.messagingengine.com, priority=10 Required MX records for delivery directly to FastMail: 10 in1-smtp.messagingengine.com 20 in2-smtp.messagingengine.com (This is the raw content of the DNS MX records. Depending on your name server configuration, you may be required to enter the numbers 10 and 20 into a field called "priority" or "preference" instead of including them at the start of the record.) I didn't past the "i" properly.