Rackspace Cloud Office suffers security breach
doublepulsar.com
doublepulsar.com
0. Set your MX record TTLs as low as possible. Even if you aren't ready to change over yet, it will lower propagation delay when you are ready to cut over.
1. Lower your DMARC record TTL, and consider changing it to report only (p=none). If you keep it strict (P=reject), be sure to check your reports for rejections after any changes.
2. Aliases in rackspace aren't in the mailbox list export. This isn't just Bill instead of William, but also info@domain.com or helpdesk@domain.com etc...
3. Allow lists/block lists can be exported from rackspace, and imported in Microsoft but consider starting over from zero if you can. Allow lists are risky.
4. If you are using any advanced email threat protection tools such as Barracuda or Mimecast, they can queue email for re-delivery once the new MX is up.
My email is in my profile if anyone has specific questions.
At least then when it shits the bed everyone else will be smothered, also.
[0] https://techcrunch.com/2016/08/26/rackspace-to-go-private-af...
[1] https://www.rackspace.com/newsroom/rackspace-technology-anno...
The support was top-notch. I could call a phone number and within minutes be on with the engineer who could actually fix an issue.
That changed around 2016 and support went downhill. Then the cloud product started to fall. When we engaged Rackspace, they suggested we migrate to AWS. So, we did.
Haven’t looked back.
Now using AWS WAF which admittedly costs more but not in wall clock time!