Transactional email

Transactional emails that always arrive on time.

Transactional emails are the messages your system sends automatically after a single user's action: an order confirmation, a password reset, an invoice, a notification. Not marketing, then, but promises your system makes to your customer — and they have to land in the inbox within seconds. 2mail builds the infrastructure for that: a separate sending channel with authentication, retry logic and full logging.

Within seconds Processed with priority, separate from bulk traffic.
Its own reputation A separate channel, protected from campaigns.
Automatic retry 2mail retries temporary errors by itself.
Full logging Every send and delivery remains traceable.
Definition

What are transactional emails?

Transactional emails are messages your system sends automatically as the direct result of a single user's action: an order, a password reset, an invoice, a payment confirmation. The recipient triggered it themselves, expects the message — and expects it immediately.

That is what sets them apart from a newsletter or campaign, which you schedule yourself and send to an entire list in one go. Transactional emails — also called system emails — go out one at a time, the moment something happens, and their content differs per recipient. Nobody subscribes to them and nobody unsubscribes: they are part of the service itself.

That is why transactional mail is business-critical in a way marketing mail is not. A campaign that leaves an hour later is annoying; a password reset that keeps someone waiting for an hour is a support ticket — or a customer who gives up. If these emails are slow, land in spam or simply disappear, that directly undermines trust in your service.

Use cases

Four places where system mail is business-critical

From the first order to an alert at 3 a.m. — these are the emails your customers and colleagues genuinely expect.

E-commerce

Order confirmation

Right after the purchase, your customer wants it in black and white that the order went through. If that confirmation fails to arrive, doubt follows, along with a support email or a duplicate order. 2mail delivers the confirmation — and the shipping notification after it — within seconds.

Order #10482 confirmed
SaaS & webapps

Password reset

A reset link that arrives too late is the most frustrating experience a user can have with your app — and an immediate reason to drop out. Account verifications and magic links require the same immediate, reliable delivery.

Your reset link is valid for 30 minutes
Invoicing

Invoice & payment confirmation

Invoices and payment confirmations come straight out of your accounting or invoicing software and by definition contain customer data. They have to arrive, and you have to be able to demonstrate afterwards that they did — 2mail takes care of both with logging per send.

Payment received · invoice 2026-0417
System administration

Alerts & notifications

A failed backup, a disk filling up, a monitoring alert: these are emails that have to reach the right person immediately, including outside office hours. A delay or a spam folder makes such an alert worthless.

Alert · backup failed on node-03
Under the hood

The journey of a system email

From an event in your application to a traceable delivery confirmation — in four steps.

Step 01

Event in your app

A customer places an order or requests a reset. Your application composes the email and hands it over to 2mail via SMTP.

Step 02

2mail relay & authentication

The mail arrives on the transactional channel, is signed with SPF, DKIM and DMARC and queued for immediate sending.

Step 03

Delivery with retry

The receiving server accepts the mail. If that temporarily fails — greylisting, throttling — 2mail retries automatically.

Step 04

Logging & follow-up

The send, the delivery and any bounce are recorded. When a support question comes in, you find the answer straight away.

Why separate them

Transactional is not marketing

Mailbox providers assign reputation per IP and per domain, not per email. If you run both streams through the same infrastructure, your password reset shares the reputation of your latest newsletter.

Transactional

Via 2mail — the critical channel

  • Triggered by a single user — the direct result of one concrete action.
  • Sent individually & immediately to one existing, active address.
  • Expected by the recipient, so a very low chance of spam complaints.
  • Zero tolerance for delay — too late is as good as not arrived.

Marketing

Campaigns — the promotional channel

  • Triggered by you — you decide when a campaign goes out.
  • Sent in bulk to large lists in a single sending moment.
  • More prone to complaints & bounces, which weighs on reputation.
  • Tolerates postponement — leaving an hour later is not a problem.

If a newsletter attracts spam complaints or high bounce rates, that can drag down the delivery of your invoices and resets — exactly the emails that cannot take any delay. At 2mail, transactional and marketing mail therefore run over separate sending streams, each with its own reputation build-up. Your transactional channel is authenticated with SPF, DKIM and DMARC per domain and runs on Belgian servers that meet the GDPR requirements for processing personal data.

Want to know how to connect an application technically? Read how the 2mail SMTP relay works, or dive into deliverability to understand why authentication and reputation determine whether your mail reaches the inbox.

And the other stream? That is described under email marketing and campaigns, with the practical side — list, authentication, spreading and measurement — under sending a mailing.

Frequently asked questions about transactional email

Any email your system sends automatically as a result of a user action: order confirmations, password resets, invoices, payment confirmations and system notifications. The recipient expects this message, and expects it fast.
Marketing campaigns are more prone to spam complaints and bounces. By routing transactional traffic through a separate, warmed-up channel, the reputation of your critical email stays protected against a disappointing campaign.
Transactional email is processed with priority and typically delivered within seconds. In the event of a temporary issue at the recipient, 2mail automatically retries until the email is delivered.
You connect your webshop, CRM, ERP or server through SMTP over TLS on port 587 using your own login. No changes to your software are needed, you simply enter the SMTP details.
Yes. Every send, delivery and bounce is logged, so when a support question comes in ("did the customer receive their invoice?") you find the answer right away.
Yes, they are two words for the same kind of message. "System email" emphasises where the message comes from (your application sends it itself), "transactional email" emphasises why it goes out (as a result of one action by one user). You will come across both terms; they mean the same thing.
A newsletter is something you schedule yourself and it goes out in one movement to an entire list; a transactional email leaves automatically, one at a time, the moment something happens, and its content differs per recipient. Nobody subscribes to order confirmations: they are part of the service itself.
No. An order confirmation, invoice or password reset follows from a contract or from an action the recipient took themselves, so it does not require the opt-in that commercial email does. That changes the moment you add promotional content: the marketing rules then apply to that part after all.

Need reliable system mail?

Connect your application to the 2mail SMTP relay and let your order confirmations, password resets and invoices arrive exactly when they should. JAAN bv has provided email infrastructure for Belgian companies from Zelzate since 2000, with personal support at every step.

Call us
Send an email