[bluegate010]

I just recently had weeks of headaches over getting my server's email sent to spam. After setting up a brand new domain, with SPF, DKIM, etc., I woke up one morning to find my domain wasn't resolving.

Eventually I learned it was because Radix, my TLD registry, had noticed my domain on the Spamhaus Domain Blocklist. Who knows why it was added; I definitely hadn't been sending spam. Radix, being proactive, placed a 'serverHold' DNS status on my domain name, preventing it from resolving.

Luckily Spamhaus has an automated form for dealing with false positives. Eventually Radix removed the status. (Though, a week later it was back up, for no reason. Had to badger them for over a week to get the status removed again. Would not recommend them.) It's very lucky I wasn't trying to do anything with that domain like run a business, or rely on @<domainname> addresses to work.

TL;DR the problem is definitely not overstated.

[xorcist]

I think that's a good example of overstating the problem right there. Who knows why it was added? Well, it certainly wasn't because you hadn't outsourced your email.

Your registry could (and probably would) have put your domain on hold independently of where your MX points. Nothing short of choosing another TLD will protect you from your registry playing games with you.