Send mail from your app on blitz.cloud
How an app on blitz.cloud sends password resets, invitations and notifications. On Pro and Business through your own mailbox on port 587, on the free plan through a mail service on port 2525 or over HTTPS.
Most apps send mail now and then: a password reset, an invitation, a notification. Spam goes out the same way, so blitz.cloud closes the mail ports to the outside and opens only the one that needs a login.
| Port | Free | Pro and Business |
|---|---|---|
| 587, with STARTTLS | Closed | Open |
| 2525 and HTTPS | Open | Open |
| 25 and 465 | Closed | Closed |
On Pro and Business: through your own mailbox
Port 587 always asks for a login, so whatever your app sends goes out from your own mailbox, with your provider's name and reputation behind it. That's the mailbox you already have at IONOS, Gmail, Microsoft 365 or Strato.
Put the settings under Environment in the app. The names depend on the app; look for host, port, user and password. These are the usual ones:
SMTP_HOST=smtp.ionos.de
SMTP_PORT=587
SMTP_USER=info@your-domain.de
SMTP_PASSWORD=your mailbox password
| Provider | Server | Port |
|---|---|---|
| IONOS | smtp.ionos.de | 587 |
| Gmail and Google Workspace | smtp.gmail.com | 587 |
| Microsoft 365 and Outlook | smtp.office365.com | 587 |
| Strato | smtp.strato.de | 587 |
Three things go wrong often:
- Port 465. Many help pages give 465 first. That port is closed here, so the app waits until it gives up. Take 587.
- SSL instead of STARTTLS. Port 587 starts unencrypted and then switches to encryption. If the app asks, choose STARTTLS (sometimes just called "TLS"), not "SSL/TLS". In apps built on Node.js with nodemailer that's
SMTP_SECURE=false, which still encrypts on 587. - Gmail with your normal password. Gmail wants an app password for this, which you create in your Google account under Security.
Restart the app after changing its settings. Mail works within a minute of taking Pro. When Pro ends, port 587 closes again, at the latest after the 14 days of grace.
On the free plan: a mail service
Use a service that sends mail for apps. Mailgun, SendGrid and Postmark take mail on port 2525, which is open on every plan, or over their HTTPS API. You verify your domain with them once, and they give you the server, user and password to put under Environment:
SMTP_HOST=smtp.mailgun.org
SMTP_PORT=2525
When the app can't reach its mail server
If an app stops because its mail server didn't answer on 25, 465 or 587, its page in the dashboard says so and names the port. An app that keeps running only writes the error to its log, usually with "ETIMEDOUT" or "Connection timed out" and the port. You can find that under Status and logs.
What blitz.cloud doesn't do
blitz.cloud doesn't host mailboxes, and apps can't receive mail on port 25. Keep your mailbox, your info@ address and your MX records with your mail provider. Your app sends through it, and replies land there as usual.
Read next
Environment variables and persistent files on blitz.cloud
Set encrypted environment variables for your apps on blitz.cloud and keep files across restarts with persistent storage. Limits and what isn't backed up.
blitz.cloud plan limits - apps, memory, storage and databases
Exact limits of the blitz.cloud free plan: apps, memory, storage and databases. How memory is reserved per app, CPU, and what is not limited.
App status, logs and troubleshooting on blitz.cloud
What an app's status means on blitz.cloud, what the five tabs show, how to restore an earlier version, and how to fix why an app won't start.
Put your first app online today.
Start on the free plan, no credit card. Move to Pro when an app has to stay online.
Put your app online