Skip to content

Email transport

FedMS uses Symfony Mailer Lite as the outbound mail framework. The transport is configured at:

1
/admin/config/system/mailer-transport

Transports

You can configure multiple transports and pick one as the default. Common choices:

Transport When to use
SMTP Default — connect to your organization's SMTP server or a provider like SendGrid, Mailgun, Postmark, SES.
Sendmail The local sendmail binary (rarely used in containerized deployments).
PHP mail The PHP mail() function (don't use in production).
null Discards mail. Useful in CI / dev environments.

For most managed-SaaS instances, LakeDrops pre-configures the SMTP transport to a reliable provider. You typically don't need to change this.

Per-environment overrides

If you need different transports in different environments (e.g. null in dev, SMTP in production), use a config-split:

  • develop split → transport set to null.
  • live split → transport set to the production SMTP.

The four splits shipped with FedMS (develop, live, test, this_site) make this idiomatic.

Testing mail

The mailpit service in the Docker development stack catches all mail in dev. Open https://mailpit-<your-instance> to inspect every message the application sends.

In production, send a test message via:

1
/admin/config/system/mailer-transport/test

From / Reply-To addresses

The default From address is the Site mail address:

1
/admin/config/system/site-information

For per-template overrides (e.g. an event's notifications coming from a per-org From address), use the Email templates page after installing the Send Email recipe.

Common problems

Symptom Likely cause
No mail being sent Transport is null or php_mail without DNS.
Mail landing in spam Missing SPF/DKIM/DMARC for the From domain.
"Connection refused" in logs Firewall blocking SMTP egress.
Inconsistent From between events Per-template From override not configured.

Next steps