4 ms·

IIRC though DO tries to make sure a released IP is returned back to you if you re-provision quickly, you run the risk of losing your well groomed IP for outboun

IIRC though DO tries to make sure a released IP is returned back to you if you re-provision quickly, you run the risk of losing your well groomed IP for outbound mail if there is an issue with your droplet. Additionally, IIRC they forbid outbound SMTP on their Floating IP system. (I can't find an official doc on this matter). Either way, you can't get a PTR for your floating IP, which can harm deliverability[1] For that reason, you may want to consider AWS & an Elastic IP that you can own, groom, and move around [2] [1] https://ideas.digitalocean.com/ideas/DO-I-1023 https://ideas.digitalocean.com/ideas/DO-I-1023 [2] https://aws.amazon.com/premiumsupport/knowledge-center/ec2-port-25-throttle/ https://aws.amazon.com/premiumsupport/knowledge-center/ec2-p...

StudentStuff 7y ago
Don't destroy your droplet then? Digital Ocean supports reinstalling VMs in place without destroying the VM. Floating IPs for a mailserver (esp. outbound) sounds a bit silly, mail infrastructure is more fault tolerant than other systems, to the point that a minute or two of downtime is far from the end of the world.
tambre 7y ago
Furthermore, DigitalOcean silently drops all SMTP traffic on IPv6, which can be really confusing since you'll simply timeout and it isn't mentioned in the documentation. They do that because they implemented IPv6 against all standard industry practices (which were helpfully gathered in a RFC) and within hours of launching IPv6 the few /64s from which they were allocating customers /124s to landed on blacklists. It's been 5 years since and they still have no plans to do IPv6 properly and allocate /64s [0]. This is the main reason I switched to Linode, who will happily allocate you a IPv6 range (/116, /64, /56) that can be rerouted between VPSes with a simple ticket (takes <1 hour). [0]: https://ideas.digitalocean.com/ideas/DO-I-1366 https://ideas.digitalocean.com/ideas/DO-I-1366
- richjdsmith 7y ago
  Damn.... I wish I'd seen this literally yesterday.

StudentStuff 7y ago

Don't destroy your droplet then? Digital Ocean supports reinstalling VMs in place without destroying the VM. Floating IPs for a mailserver (esp. outbound) sounds a bit silly, mail infrastructure is more fault tolerant than other systems, to the point that a minute or two of downtime is far from the end of the world.

tambre 7y ago

Furthermore, DigitalOcean silently drops all SMTP traffic on IPv6, which can be really confusing since you'll simply timeout and it isn't mentioned in the documentation. They do that because they implemented IPv6 against all standard industry practices (which were helpfully gathered in a RFC) and within hours of launching IPv6 the few /64s from which they were allocating customers /124s to landed on blacklists. It's been 5 years since and they still have no plans to do IPv6 properly and allocate /64s [0]. This is the main reason I switched to Linode, who will happily allocate you a IPv6 range (/116, /64, /56) that can be rerouted between VPSes with a simple ticket (takes <1 hour). [0]: https://ideas.digitalocean.com/ideas/DO-I-1366 https://ideas.digitalocean.com/ideas/DO-I-1366

richjdsmith 7y ago
Damn.... I wish I'd seen this literally yesterday.