SMTP relay for everything else
Not every sender speaks REST. Point any SMTP client at smtp.euromail.dev (WordPress, PHP mail(), cron jobs, hardware) and it rides the same delivery pipeline as the API.
Four lines of configuration
Port 587 with STARTTLS or 465 with implicit TLS. TLS is required either way, and AUTH is only offered after the connection is encrypted. The username is always the literal string apikey; the password is your API key. Because the convention mirrors Postmark, SendGrid, and SES, most “SMTP provider” presets work unchanged.
Host smtp.euromail.dev
Port 587 STARTTLS · 465 TLS
Username apikey
Password em_live_...Same engine, different door
Mail submitted over SMTP runs the exact pipeline as POST /v1/emails: DKIM signing, SPF and DMARC alignment, suppression checks, open and click tracking, and direct delivery to recipient mail servers from dedicated IPs. The From domain must be verified. That requirement is what keeps the relay closed.
- DKIM signing
- Automatic, per-domain keys
- Suppression checks
- Applied before delivery
- Delivery
- Direct to recipient MX
- Sender requirement
- Verified From domain