Transactional email services

✉️ ✉️ ✉️ ✉️ ✉️

Send many automated emails reliably.

fortrabbit has no sendmail, so PHP's mail() function does not send. Apps send e-mail such as password resets and invoices through a transactional mail provider, by SMTP or by its API.

This page covers e-mail sent by the app. For mailboxes on an own domain, see e-mail hosting.

No sendmail

PHP's mail function hands the mail to a local sendmail, which fortrabbit does not have, see limits. This does not send:

$to      = 'firstname.lastname@gmail.com';
$subject = 'Welcome to our service';
$message = 'hello, nice to have you here …';
$headers = 'From: webmaster@mycoolapp.com'

mail($to, $subject, $message, $headers);
php

Mail sent straight from a web server, without the SPF and DKIM records of a real mail server, ends up in spam or is rejected by the large mail providers anyway.

About transactional emails

Transactional e-mail is sent by the app to one person, triggered by an action: a sign-up confirmation, a password reset, an invoice. Transactional mail providers deliver it by SMTP or API, help with the SPF and DKIM records of the domain, and log every message with bounces and opens. The SMTP ports are open in the outgoing firewall. See providers.

Written by a human. Review, grammar checks and typo fixes by AI.

AI use & editorial processEdit on GitHub ↗