News for hackers. Stuff that matters.
Re:Fastmail – 20 Years Old by ocdtrekkie on Thursday November 21, 2019 @04:03PM (#21599591)
So, I knew I wanted to use my own email domain going forwards to prevent this problem in the future. I got [email protected] set up, and forwarded it to Gmail. Then for about a year and a half, anytime I looked at account settings anywhere I'd change it from my Gmail address to my own address. (But it all still ended up in the same inbox.)

When I decided to switch to FastMail in 2016, I repointed that address at FastMail and the vast majority of stuff moved with me... instantly. FastMail also has tools to import your mail archive using IMAP for what's already in your Gmail account.

Now that all of my mail uses my own domain name, if I ever needed to leave FastMail, it'd be painless... none of my mail is going to a FastMail address to begin with.

My strong recommendation is that people do this even if they intend to stick with Gmail for the time being, just to give themselves the future option.

Re:Fastmail – 20 Years Old by xwowsersx on Thursday November 21, 2019 @04:19PM (#21599740)
Good idea, thanks for sharing. So I set up an MX record (on Route 53) to point to Fastmail and also set up DKIM by adding several CNAME records for fm1._domainkey.mydomain.com. FM confirmed pretty quick that those changes were made. The last bit is SPF config. I added a TXT record as per the instructions, but I keep rechecking with FM and it's not verified. Emails from FM currently show up as being sent "via messagingengine.com". Any ideas - do I just need to wait?
Re:Fastmail – 20 Years Old by xwowsersx on Thursday November 21, 2019 @04:24PM (#21599806)
Scratch that, seems to be working now. Not showing up as "via messagingengine.com" anymore in spite of the fact that it still hasn't verified SPF. Looking forward to cleaning up my email by switching to FM!