Your app speaks SMTP. Fine, keep it. Change three settings and your trusty old stack inherits the deliverability, telemetry and bounce handling of a modern platform — zero rewrites.
If your app can send SMTP, it's already integrated. Swap the host, paste your server token as both username and password, and mail starts flowing through our infrastructure before your coffee cools.
These are the only settings your app needs. Everything else — authentication, queueing, retries — is our problem now.
| Setting | Value |
|---|---|
| Host | smtp.postedapi.org |
| Ports | 587 or 2525 (STARTTLS), 465 (SSL) |
| Username | Your server token |
| Password | Your server token |
| Auth | LOGIN |
Port 2525 is there for hosts that block 587. It happens more often than you'd think.
SMTP traffic rides the exact same rails as our API. Same carefully vetted IPs, same sending speeds, same automatic bounce suppression — nothing about your mail gets second-class treatment just because it arrived over port 587.
WordPress, Laravel, Rails Action Mailer, that cron job from 2014, any SMTP client at all. If it can open a socket, it can send through PostedApi.
Issue one SMTP credential per environment — staging, production, the throwaway test box — and revoke any of them in a single click.
Every message lands in the dashboard: delivery time, provider response, opens and bounces — searchable for 45 days, included in every plan.
Create your account, copy five settings into your app, and watch your delivery rates climb. Your code never has to know.
PostedApi