luckily I do not need to send emails very regularly, nor do I expect to need to in the near future, so the current issue where fastmail recognizes my nameservers have changed but *doesn't* recognize my SPF records have changed shouldn't impact much
but, uh, perhaps I shouldn't have done this on a whim like this
I blame caffeine
and further cementing my decision to move away from mailinabox, the very first thing it told me was
nc: getaddrinfo for host "aspmx.l.google.com" port 25: Temporary failure in name resolution and then complaining that port 25 is blocked when it's just some stupid issue with dns resolution
I've had a lot of these random intermittent issues that don't make any sense (and plus, my fastmail account is about half the cost)
This is unstable.systems, a general-purpose invite-only Mastodon instance. We'll always be pretty small, and we hope to be a comfortable instance to be on.