ODK Central not Sending Emails to Users

Note that I haven’t changed any of the default settings since installing ODK Central a little over a year ago. I don’t have time to go into this right now but figured this info might be helpful to y’all as I thought I saw a note to add something about changing the default settings after doing a fresh install in the ODK Central Docs…This is what the DigitalOcean team sent me:


Thanks for reaching out about this.

We understand you have concerns regarding SMTP restrictions in place on your account. DigitalOcean is not a dedicated email host and stopping spam is a constant fight. Due to this, restrictions have been imposed on all accounts.

We would also like to provide some additional background on this issue. Since IP addresses in cloud environments get used and released back to available pools very frequently, they are considered dynamic and untrustworthy. For example, you’re currently assigned an IP address and you're a responsible mail user. You follow all best practices for mail and never send spam or unsolicited mail. Later, when you no longer need that Droplet, you destroy it and the IP address is free to be assigned to another DigitalOcean user. That user takes the opportunity to send out a large volume of spam before our Security team takes action on the offending account.

Mail providers like Gmail, Microsoft, and others cannot determine if email coming from an IP is legitimate or not until it gains a poor reputation. By that time, the damage had already been done. It's safer to just block all mail coming from platforms, like Internet Service Providers and Cloud hosting environments, where IP addresses are dynamically assigned and inherently risky.
While this does reduce avenues that spammers have available to them, it also impacts legitimate users. Our Abuse Operations team is working with SBLs to get the IPs delisted. Due to this, we are restricting SMTP traffic across the DigitalOcean platform. This means that we are unable to remove the SMTP restriction that is placed on your account.

We understand that your workflow may have email needs. As a solution to this restriction, we have partnered with SendGrid to offer all our customers a better solution where you would not need to worry about IP reputation and blacklisting. Through SendGrid, you will be able to send 100 free emails per day and if your requirement is beyond the free tier, feel free to reach out to SendGrid support to opt for a better plan to meet your requirement. Additionally, you should have access to Port 2525 on your account. You can also make use of a REST API for SMTP with SendGrid, which allows you to send emails via HTTP requests instead of the traditional SMTP protocol.

You can read more about our SMTP policy here:
Why is SMTP blocked? | DigitalOcean Documentation

Do let us know if there are any further queries.

2 Likes

Thanks for sharing this helpful context. We'll update the docs and suggest SendGrid for folks using DigitalOcean.

This means that we are unable to remove the SMTP restriction that is placed on your account.

well, they’re certainly able to, they just won’t for you :wink:

I wonder if they also have such restrictions (and if so, if they can be lifted) on their “Reserved IPs” (I’ve used those once, they’re basically NAT gateways). One of those combined with a Linux policy routing rule to route all outbound SMTP “through” that reserved IP (eg ip route add default via $DO_RESERVED_IP_GW table 9000 && ip rule add from all ipproto tcp dport 25 lookup 9000) may be an alternative to using Sendgrid.

*) one can discover the gateway IP ($DO_RESERVED_IP_GW in the example policy routing setup) from the cloudinit config saved in json somewhere on disk (/etc/cloudinit/?) IIRC.