Users claim personal family domains are being falsely flagged for commercial use, leaving long-time G Suite Legacy customers facing a pay-up-or-lose-access ultimatum
It IS a big hassle. I use Amazon SES for outbound which mostly solves the spam rejection problem based on IP, but the system still has to protect its domain reputation by being setup well. Inbound is an issue because downtime can mean lost email, so I have two other systems acting as MX relays. I also have to deal with spam, monitor disk space and a bunch of other things that for most would not be worth the hassle.
Ohhh, great points. I considered most of those things, but somehow didn’t even consider the potential consequences of downtime. Maybe I’ll only self-host an email service for throwaway email addresses then, and not for important things.
It IS a big hassle. I use Amazon SES for outbound which mostly solves the spam rejection problem based on IP, but the system still has to protect its domain reputation by being setup well. Inbound is an issue because downtime can mean lost email, so I have two other systems acting as MX relays. I also have to deal with spam, monitor disk space and a bunch of other things that for most would not be worth the hassle.
Ohhh, great points. I considered most of those things, but somehow didn’t even consider the potential consequences of downtime. Maybe I’ll only self-host an email service for throwaway email addresses then, and not for important things.
Thanks for the insight.