My god! I was like 24 hours trying to install a e-mail server. Tried iredmail not worked at all, tried many other stuff, ended up with citadel (not working too).

Now i see the problem! Wow, its kinda a relief anyway... I'm going to open a ticket.

Same:

DigitalOcean, why don't have transparency about server and network limitations?
why don't put a disclaimer in your tutorials about MAIL SERVERS?

This is outrageous. I have spent the past days trying to figure out what the problem was.

I have been also an AWS/EC2 user and they have always been very transparent as to when restrictions to my account were in place. Being left in the dark while paying for full server service was extremely disrespectful.

To me it only shows Digital Ocean should be used with caution for production.

+2 Same:

DigitalOcean, why don't have transparency about server and network limitations?
why don't put a disclaimer in your tutorials about MAIL SERVERS?

--

I`m having the same problem right now. I have a client who is concerned because cannot send e-mails after I migrated his site to DigitalOcean. I spent days looking for the trouble and just now I discovered this block. I always recommend DigitalOcean for new customers, but I am rethinking this approach. Better go to Linode and have no nasty surprises like this. This is disrespectful attitude with developers.

+3!

DigitalOcean, why don't have transparency about server and network limitations?
why don't put a disclaimer in your tutorials about MAIL SERVERS?

--

+1

One day wasted on this issue too. Thanks, Digital Ocean.

My nodejs app magically stopped working when running on my droplet.. After a considerable amount of time looking for the problem, changing code, checkin versions, going back and forth from dev server and the production (Digital Ocean) I found this.

Thankfully I found this..

I never had a bad experience with Digital Ocean, until now...

Got my ticket, now lets wait and see...

+6!

DigitalOcean, why don't have transparency about server and network limitations?
why don't put a disclaimer in your tutorials about MAIL SERVERS?

Three days wasted on this issue too. Thanks, Digital Ocean.

There's definitely a lack of transparency here, so, add me to that list.

I had this working for years on a server and all of a sudden without any announcement it was blocked/failed.

It's also non-obvious and under-documented that it's possible for IPv6 mail to be completely blocked even if IPv4 isn't (so, even if you think you're in the clear because things work where you tested, you can end up with periodic failures if you're dealing with somewhere that has IPv6 mail servers in their DNS rotation like say Office365 or Gmail).

Digital ocean should clarify and add a reminder when you have to deal with SMTP.

I just contacted the support to know why my smtp.office365.com was always timed out.

They asked me the following informations :

1. Your name.
2. What business or individual you are going to send mail on behalf of as well as their website (if one exists).
3. What kind of mail you're going to be sending (password resets, newsletters, marketing mail, transactional mail such as order confirmations).
4. If you're sending on behalf of a business or an individual that is not yourself, what is your relationship to that business or individual.

And then :
"After giving some informations about the purpose "Thank you for reaching out to us. I am passing this ticket over to our Trust and Safety team for further review.""