For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

NB! DigitalOcean blocks outgoing SMTP ports (25, 465 and 587) on droplets by default, so EmailEngine on a droplet can not send email over SMTP. Reading email over IMAP, and sending through the Gmail API or Microsoft Graph, work normally.

EmailEngine provides access to email accounts through a REST API. It keeps a live connection to every account, turns API requests into IMAP, SMTP, Gmail API or Microsoft Graph calls, and watches for changes, notifying your app with webhooks when messages arrive, change or are deleted.

It is built for developers and businesses that need reliable email integration without dealing with IMAP, SMTP and OAuth2 details themselves. EmailEngine does much more than a basic email library: it handles OAuth2 token management, sending, and change notifications for every account in one place.

Software Included

Creating an App using the Control Panel

Click the Deploy to DigitalOcean button to create a Droplet based on this 1-Click App. If you aren’t logged in, this link will prompt you to log in with your DigitalOcean account.

Creating an App using the API

In addition to creating a Droplet from the EmailEngine 1-Click App using the control panel, you can also use the DigitalOcean API. As an example, to create a 4GB EmailEngine Droplet in the SFO2 region, you can use the following curl command. You need to either save your API access token to an environment variable or substitute it in the command below.

curl -X POST -H 'Content-Type: application/json' \
         -H 'Authorization: Bearer '$TOKEN'' -d \
        '{"name":"choose_a_name","region":"sfo2","size":"s-2vcpu-4gb","image":"postalsystemso-emailengine"}' \
        "https://api.digitalocean.com/v2/droplets"

Getting Started After Deploying EmailEngine

1. Optional: create a DNS A record pointing your domain to the droplet’s public IP address. If you skip this, the setup can generate a test domain for you.
2. Log in to the droplet over SSH: ssh root@your_droplet_public_ipv4. The setup starts automatically and asks for your domain name and an admin password. It then requests an HTTPS certificate for your domain.
3. Open https://your_domain/ in a browser.
4. Sign in with the username “admin” and the password from step 2.
5. Start your 14-day trial by clicking the Start a 14-day trial button.

Next Steps

1. Add an email account on the Accounts page to start monitoring it.
2. Generate an access token on the Access Tokens page.
3. Try API requests for the account on the API Reference page.
4. Keep EmailEngine up to date by running: sudo /opt/upgrade-emailengine.sh