3 ms·
I’ve been doing the same thing for years and haven’t had any trouble except for Mailchimp. Their overly-clever validation decided mailchimp@example.com is a sha
by user3939382 5y ago
I’ve been doing the same thing for years and haven’t had any trouble except for Mailchimp. Their overly-clever validation decided mailchimp@example.com is a shared email account (it wasn’t going to be) and blocked me from using it. Their email support apologized but said they couldn’t fix the false positive, and that they hoped the email I used instead wasn’t reflective of my opinion: mailchimp-morons@example.com.
- DistressedDrone 5y agoWhy would that even be a problem?
- vxNsr 5y agoDo you have a personal set up for managing these emails and disabling the bad ones? or are you using something like 33mail? Just curious.
- xdrosenheim 5y agoI do the same thing, I catch every mail my domain receives and send it to a catch-all inbox. When ever an e-mail is "compromised" or is being abused, I can just forward <abused-mail>@<domain> to null space.