iemails
Pricing
Log inGet started
Get started
SMTP relayTLS on every connection

SMTP that just
plugs in and sends

Point any app, framework or tool at smtp.iemails.co and get iemails deliverability without writing a line of new code. Four settings, one API key, and your email is in better hands.

Start sending free Read the SMTP guide
3,000 free emails a monthNo credit cardWorks with any SMTP client
SMTPsmtp.iemails.co:465Live session
Connection detailsConnecting…
Hostsmtp.iemails.co
Port465 (SSL/TLS)
Usernameiemails
Passwordem_live_••••••••4b2c
Delivery timeline
  1. Connected and encryptedSSL/TLS · TLS 1.3—
  2. AuthenticatedAPI key · sending access—
  3. Message accepted250 Queued as em_9Tq4Xc2Lp—
  4. Delivered to inboxgmail-smtp-in.l.google.com · 250 OK—
No new libraryKeep the mailer you already have. Change four settings and you are done.
Encrypted, alwaysImplicit TLS on port 465, from the first byte. Plain-text connections are never accepted.
API key as passwordScope it to sending or one domain, rotate it any time.
Same logs and webhooksEvery relayed email gets the events the REST API gets.
Quick integration

Works with the tools
you already run

WordPress, Supabase Auth, Laravel, GitLab, Grafana — if it has an SMTP settings screen, it can send through iemails. Pick yours and copy the settings.

Pick your tool23 guides
mailer.tsNode.js · Nodemailer
1import nodemailer from 'nodemailer';
2
3const transport = nodemailer.createTransport({
4 host: 'smtp.iemails.co',
5 port: 465,
6 secure: true,
7 auth: { user: 'iemails', pass: process.env.IEMAILS_KEY },
8});
9
10await transport.sendMail({
11 from: 'iemails <[email protected]>',
12 to: '[email protected]',
13 subject: 'Confirm your account',
14 html: '<p>One click and you are in.</p>',
15});
Use an API key as the passwordSend from a verified domain
Secure

Encrypted from
the first hello

Every connection is protected between your app and our servers. Port 465 is TLS from the first byte, so nothing, not even the greeting, crosses the wire in the clear.

smtp.iemails.co:465SMTPS
Handshake
  1. 1Open a connection to port 465TCP · smtp.iemails.co
  2. 2TLS handshake, before anything elseTLS 1.2 or 1.3 · certificate checked
  3. 3Authenticate with your API keyAUTH PLAIN, inside the encrypted channel
  4. 4Send the messageMAIL FROM · RCPT TO · DATA
1port: 465
2secure: true // TLS from the first byte
In most clients this is the “SSL/TLS” or “secure” option. STARTTLS is not offered.
Brightloom
“We changed four settings in Supabase and our login emails stopped landing in spam the same day. No code, no deploy — and every message now shows up in the logs.”
PN
Priya Nair
CTO, Brightloom
One platform

Two ways in.
One set of logs.

SMTP is not a second-class citizen. Relayed mail runs through the same pipeline as the REST API, so your team sees every email in one place, whichever door it came through.

  • Relayed mail is signed with DKIM for your domain, just like API sends.
  • Delivered, bounced, opened and clicked events fire your webhooks.
  • Bounces and complaints add to the same suppression list.
Get startedCompare with the API
app.iemails.co/emailsAll sources
SMTPYour invoice for October[email protected]Delivered12:04:32
APIConfirm your account[email protected]Delivered12:04:18
SMTPReset your password[email protected]Opened12:03:51
SMTPNew comment on “Q4 plan”[email protected]Clicked12:03:07
APIYour trial ends tomorrow[email protected]Delivered12:02:44
Dependable

An SMTP service
you can count on

Sign-ups, password resets and alerts often depend on SMTP. The relay behind them is built to stay up, stay secure and stay out of your way.

99.99%uptime SLA

Always on

Relay servers in multiple regions with automatic failover. If one goes quiet, your client never notices.

View live status
SOC 2Type II · GDPR

Secure and compliant

TLS on every connection, scoped API keys, audit logs and a signed DPA — ready for your security review.

Visit the security center
< 1 hrtypical first reply

Support from engineers

Stuck on a client setting? Talk to the people who run the relay. Scale and Enterprise teams get a shared Slack channel.

See Enterprise
FAQ

Questions
about SMTP

Can’t find your client’s settings? Send us a message and an engineer will walk you through it.

Talk to an engineer

It is a mail server that accepts email from your application and delivers it for you. Instead of running your own mail server, you point your app or tool at smtp.iemails.co and we handle signing, sending, retries and deliverability.

Host smtp.iemails.co, username iemails, and an API key as the password. Use port 465 with SSL/TLS (implicit TLS). You will find the same values under Settings → SMTP in your dashboard.

Use SMTP when a tool or framework only speaks SMTP, or when you want to switch providers without touching code. Use the REST API for new code: it adds scheduling, batch sends, tags and idempotency keys. Both share the same deliverability, logs and webhooks.

Always. The relay listens only on port 465, which is encrypted from the first byte. There is no unencrypted or STARTTLS port.

Yes. Each relayed message gets an email id, a full event timeline in the dashboard, and the same webhook events as an API send: delivered, bounced, complained, opened and clicked.

Any address on a domain you have verified in iemails. Messages from unverified domains are rejected during the SMTP conversation, so nothing goes out by mistake.

Yes. Anything your client puts in the MIME message is relayed as is, including attachments up to 40 MB in total and your own headers.

SMTP shares your account’s plan limits with the API. The free plan includes 3,000 emails a month and up to 100 a day, and paid plans raise both. Talk to us if you need more.

Start relaying
in minutes

Create a free account, verify your domain, paste four settings. Your app sends through iemails before your coffee cools.

Sign up for free See pricing
iemails

Email infrastructure for teams who would rather read a trace than a support ticket.

Keizersgracht 241
1016 EA Amsterdam, NL

All systems operational·Status
Features
Email APISMTP relayAutomationsAudiencesBroadcastsInboundTemplatesWebhooksDedicated IPs
Resources
ChangelogPricingEnterpriseSecuritySOC 2GDPRBrand
Company
AboutBlogCareersCustomersPhilosophy
Help
SupportStatusMigrateKnowledge baseLegal
Community
EventsOpen sourceInsidersWallpapers
SOC 2 Type IIGDPR readyISO 2700199.99% uptime SLA
© 2026 iemails, Inc. Built in Amsterdam and Bengaluru.
PrivacyTermsDPASecurityCookies