Virtual server host with reasonable mail policies?

[Ken D'Ambrosio]

On 2022-12-30 16:37, Benjamin Scott wrote:

> FWIW, my DO VM can initiate TCP to 25 outbound on both IPv4 and IPv6.
> It is likely grandfathered, however.  They have a somewhat
> vaguely-defined blocking policy:
> 
> https://docs.digitalocean.com/support/why-is-smtp-blocked/

Ohhhh... nice to know.  Last time I'd checked -- when IPv6 suddenly was 
blocking my outbound -- it was an intentional block, with no intention 
to remove it.  I guess times have changed.  (The rationale was that, 
apparently, RBLs were blocking entire v6 subnets, so rather than maybe 
not be able to send email, they'd save everyone the unpleasantness of 
uncertainty, and simply block it entirely.)

> FYI, this was fixed in Postfix at some point.  I don't recall when.

Good deal.

> There seems to be an increasing trend of DO having their
> ASNs/netblocks ending up on blacklists.  Allegedly (according to the
> blacklists) this is because DO doesn't police their customers closely
> enough and/or respond to abuse reports in a good fashion.

Huh.  I did have to bounce the first IP I got some six(?) years ago, but 
been smooth sailing since.  However, it's good to know it's not a DO 
priority.  I'll keep my eyes open for bounced/bitbucketed e-mails.  
Indeed, right now, I'm waiting on a reply to an e-mail I sent to a guy 
who's usually really quick with replies.  But it's also a holiday, 
basically, so I'm not getting exercise jumping to conclusions.

> They also have an official position of very strongly discouraging
> running email within their systems:

Boo!  Hiss!

-Ken