Fastmail Problems

[Maral Mende]

Sometimes problems connecting may be caused by a single program, like your usual browser or your email client. If you are seeing connection problems in your email client, try going to our homepage at fastmail.com with your browser.

If you still can't load our page, try going to other websites. If you can't load any pages at all, there may be a problem with your home network. If you can load other pages, but not Fastmail, your internet provider might be having trouble reaching us.

We sometimes see problems with specific internet providers' routing to Fastmail. When you try to access Fastmail, your browser sends your internet provider a request to load fastmail.com. Routing issues happen when the internet provider is sending traffic for fastmail.com to the wrong IP address, which means your request is not reaching us at all. This causes the website to appear to be offline entirely.

To test whether this is the case, try connecting to a different internet provider, e.g. mobile data or using the internet connection at a workplace. If you can load Fastmail from these networks, the problem is probably with your internet provider.

It will greatly speed up the resolution of your issue if you let our support team know what you have already tried to fix the problem. It will also speed up resolution if you include a traceroute of the connection between your computer and Fastmail.

I have recently moved my multiple email servers to FastMail and I am very happy with the result, but I am having a few problems with the integration between the two of them. I have seen in the forum that other people are using both, but I have not found the solution to my problems.

In part 1, I explained the complexity of my email setup.I used part 2 to talk about why I wanted to migrate away from the (admittedly very good) tools provided by GooglePart 3 went over the steps I took to prepare for the migrationPart 4 proceeded to talk about how you can copy email from Gmail to FastMail and also included some links to some other useful resources onlineIn part 5, I covered some of the specific issues that arose duing the migration (e.g. DNS configuration)Finally, I used part 6 to list the good and bad things that I have experienced during (and since) this migration

The list of problems that I have experienced is almost non-existent, and the few issues I have had were my own fault! At one point in my migration, I had my Apple Mail app (on OS X) set up with both my Gmail and my new FastMail account. This meant that I effectively had duplicates of everything.

But when you need them, their Advanced settings are there and they could probably keep you occupied for several days (every option in the left-sidebar opens a whole page of preferences). Click to enlarge:

The web app has four main components: Mail, Address Book (I easily imported my addresses from OS X Contacts app), Notes (a simple way of collecting some thoughts in the style of Simplenote [2], and Files.

So on the one hand, the former news might encourage more people to move away from Gmail but the latter news item means that Apple's Mail app needs some fixes before being ready to work with FastMail under 10.9 (of course, web access to FastMail is unaffected). This is making me consider waiting a little while before upgrading to 10.9.

One of the reasons I chose FastMail was that I knew that they supported personal domains[2]. You still get your own FastMail email address as well (and this becomes your account name) but I don't intend to ever use this as an email address.

The only hitch in this process was due to my own stupidity. I use SaneBox to pre-filter my Gmail and I needed to tell SaneBox to work with FastMail instead. Foolishly, I did this while my mail was still being imported in the background. This may or may not have been the reason why I ended up with two sets of my SaneBox folders under FastMail. This was easy to resolve though [2].

Michael Crusoe gave me a useful tip on twitter about this. Simply make a filtering rule in Gmail to forward all spam email. I did something slightly different and made a rule to not move any email to the Spam folder[3].

In my last blog post, I explained the complexity of my email setup before I began the migration from Gmail to FastMail. Although I will move on to explaining how I did the migration, I thought I should briefly touch on why I did it.

Google experiments with lots of different products and increasingly they are honing down their portfolio to a smaller number of (revenue-generating) services. They have discontinued more services than most companies will ever launch. Many of these are products that you will have never heard of, but closure of services like the popular Google Reader sparked outrage across the web[2].

You can even do this for email aliases. My Apple email account lets me set up a few free aliases. This allows me to have one email address that I can use for me and my wife (emails to this account go to me, but get autoforwarded to her[3]). So my Gmail account contained four accounts at this point.

For a year or so, I was happy with my email setup. Everything was routed to one place (Gmail) but on my Mac or iPhone I only needed to have one account set up and yet I could still send email from my Work or Apple email accounts (including aliases).

At some point though I realized that I might not be with Gmail forever. So I decided to invest in a domain name which, in theory, would stay with me forever and would give me the opportunity to have a stable email address for the rest of my life. This email address could be moved between providers as and when I needed to move.

So I bought a domain name with the awesome Hover registrar (please click here to use my referral link if you consider using them). For $5 a month, Hover will forward email from your chosen email address (e.g. gre...@mos-eisley-cantina.com) to another address. So while I could have used Hover as the email host, I decided to stick with Gmail and just forward email to it as before.

Over the last few days I have finally decided to leave all of the above setup behind and move to FastMail. Why and how I did this, will be the subject of future blog posts in the coming days. However, my early experience is that FastMail is excellent and I have no regrets about making this move.

I use a third party email called fastmail for my office email and personale email. On the whole its work out cheaper than google an godaddy. When I was with wix i had no problem with this issue. I would add my SPF records, MX and DKIM record without any problem but with squarespace it seems like there is issues with SPF records. See attachment. it seems pretty straight forward but fastmail does not seem to see this entry from squarespace. I bought my domain through squarespace. I need some help on this matter.

Added my spf records to wix and it worked fine. The only reason I added for Zoho Books is that I send my invoice directly out of zoho books to my clients and soem clients say they never received those emails. I remove teh zoho spf record and see if it works and give you feedback.

If Fastmail is having system outages or experiencing othercritical issues, red down notifications appear on the status page. Inmost cases, it means that core functions are not working properly, orthere is some other serious customer-impacting event underway.

Warn notifications are used when Fastmail is undergoing anon-critical issue like minor service issues, performance degradation,non-core bugs, capacity issues, or problems affecting a small number ofusers.

Fastmail does not publish a feed of proactive maintenance events on theirstatus page at this time. If they do, be sure to let us knowand we'll aggregate Fastmail maintenance events into your unified calendar.

Because Fastmail has several components, each with theirindividual statuses, StatusGator can differentiate the status of eachcomponent in our notifications to you. This means, you canfilter your status page notificationsbased on the services, regions, or components you utilize.This is an essential feature for complex services with many componentsor services spread out across many regions.

All showing as fine in Fastmail. The issue seems specific to fastmail rather than the TLD as other online on forums have commented that moving their email to their own hosted platform resolves the issue. How strange, will keep playing about this it

I can't get any mail account to work, every single time I start mail and have to enter a password for the email accounts (all 12 of them) I get this error when I click save, therefore No Email Works ?:

I had the same problem (fastmail), but now it has gone away. What I mean by that is that I fiddled around with it for a while, shutdown Mail.app, and an hour later, after reading your message, fired it up again to see if our messages matched and boom. It works.

Open Keychain Access and remove any stored passwords for those accounts. Or just delete the keychain and reboot, letting it create a new one. I've seen a few other threads where Microsoft applications kept giving credential errors and required the deletion of the matching entries in the keychain.

I also ran into this error; I managed to get this to work by opening Keychain Access, selecting one of my mail accounts' password entry, revealing the password (requiring entering my login credentials), and then restarting Mail.app.

I upgraded a working system to Sierra, and immediately after the upgrade my existing email accounts were broken. I shut down, rebooted, and everything was OK. (Well, at least the accounts worked - there were numerous other bugs.)

Did you sign into your icloud account and sync the keychain? That is causing the problem for me and the mail program would open but only for a few minutes and it would shut down. Just deleting the Keychain entries was not enough, iCloud would just add them back. I had to uncheck the Keychain in the iCloud prefs and added the mail account manually and everything is now working great!! I must have some corrupted entries in the keychain or the settings have changed from El Capitan and Mail doesn't like them.

3a8082e126