preping

SMTP relay

SMTP that just works.

Already have an app, a CMS or a plugin that sends email over SMTP? Point it at Preping and every message gets proper authentication, delivery tracking and a readable log. No code changes.

Start free See pricing

9,000 emails free every month · No card needed

Four settings, done

Host, port 587 (STARTTLS) or 465 (TLS), username "preping" and any API key as the password.

Works with everything

WordPress, WooCommerce, Laravel, Django, Rails, Node, PHP mailers, printers and scanners. If it speaks SMTP, it works.

Same logs as the API

Every SMTP message shows up in your email list with its full timeline: sent, delivered, opened, bounced.

Sending-only keys

Create a key that can only send. If it leaks from a config file, it can't read your contacts or change settings.

Bounces handled for you

Hard bounces and spam complaints are suppressed automatically, which protects your sender reputation.

Test before you go live

Use a test key and messages land in your Sandbox inbox instead of real inboxes.

Three steps. That's it.

  1. 1Create an API keyIn Developers, create a sending-only key.
  2. 2Fill in four fieldsHost, port 587, username preping, and the key as the password.
  3. 3Send a testUse your app's "send test email" button and watch it arrive in the Sandbox inbox.

Questions

Which port should I use?+

Port 587 with STARTTLS works almost everywhere. Use 465 if your app only supports implicit TLS.

Can I use SMTP and the API together?+

Yes. Both share the same domains, limits, suppression list and logs.

Does SMTP work for newsletters?+

It works, but campaigns in the dashboard give you segments, A/B tests and unsubscribe handling built in.

Email API

The email API you can learn in one minute.

Transactional email

Receipts, OTPs and resets that arrive. Every time.

Bulk email

Send to thousands. Land in the inbox.

Your first email is a minute away.

Start free