Skip to main content

header image

MailFlow Relay

Welcome to the Documentation for MailFlow Relay, the sane email forwarding engine for those that just want to send some emails in peace.

Why MailFlow Relay?​

This project was born out of necessity, the inability to find a provider willing to take our money and the sheer spite of "it can't be that hard now can it?".

Not-Usescases​

We are not:

  • An email server
  • A mailbox provider
  • A marketing campaign system
  • A spam generator

If you need traditional mailboxes or advanced analytics features look elsewhere.

Usecases​

This solution is for you if your targets meet these requirements:

  • Exclusively external targets (like private email addresses at the usual providers)
  • Large amounts of forwarding lists of nontrivial (>10) size
  • Non-realtime sending1

This system was build for clubs and associations that do not run their own dedicated mailserver. Our core target audience is that of non-technical groups without extreme edgecase requirements.

note

We aim to be as invisible as possible while enhancing some everyday usecases on an as-needed basis. Ideally no one except maybe the postmaster ever needs to think about forwards again.

Features​

All bases covered​

We support all basic features you would expect a modern email management system to have. COre fratures include but are by far not limited to:

  • Bounce handling
  • Unlimited amounts of lists2
  • Unlimited list sizes2
  • Safeguards against obvious misconfigurations
  • Certificate validation on all inbound paths
  • Event-logs

Additional features​

Mailflow Relay additionally supports a few optional features not found on traditional simple forwarding systems:

  • Infinitely recursive forwarding lists (will not unroll self-refferencial lists, includes deduplication)
  • Zero-config3 Templating support4
  • Basic list security filters4
  • Self-service signup/unsubscribe for lists4

Getting started​

These docs are splt by interest group to enable everyone to find what they need as fast as possible.

For Users​

Your organization uses our software? You want to know what you can do with this? have a look here for quickstarts and other guides!

For Administrators​

You are running an instance or consider to? Then check out the admin docs!

Footnotes​

  1. Average pipeline-processing times for lists up to 300 targets are below 200ms but outbound delivery depends on your providers ratelimiting ↩

  2. Limited only by what your server can handle ↩ ↩2

  3. By default only very basic info is provided but more context can be made available ↩

  4. This is an optional per-list feature. ↩ ↩2 ↩3