Self-hosted applications and the Basic auth shutdown
The applications on this page have something in common that decides whether a free relay is the right answer for them: they mail people who already know who you are.
An invitation to your own photo library, a password reset for your own Git server, a second-factor enrolment on your own login portal. Nobody is deciding whether to trust the sender, so a generated @msgwing.com address costs nothing. A shop receipt from an unfamiliar domain costs the sale — which is why WooCommerce is handled differently.
| Application | What its mail is for |
|---|---|
| Immich | a notification when a new user is created |
| Vaultwarden | invitations to new users, valid for five days |
| Gitea | registration and account-activation mail |
| Authelia | identity-verification mail when a user registers a second factor |
| Paperless-ngx | password resets and account mail for the people who use it |
| changedetection.io | a notification when a watched page changes, to whoever set up the watch |
| n8n | whatever a workflow is built to send - failure alerts, status digests, form-submission notices - through its Send Email node, to whoever the workflow author configured |
| Netdata | health alerts when a monitored metric crosses a threshold - disk full, CPU pinned, a service down |
Each page names the exact settings, quotes where they came from, and states the one limit most likely to catch you out on that particular application.
What is not here
Jellyfin, Portainer and Wiki.js are all in the same position and are not covered yet. They are missing because nobody has read their documentation carefully enough to name the settings without guessing, not because they do not fit.
Tell us which one you run and it moves up the list.
Related
- Connection values and every other application
- WordPress and WooCommerce
- What breaks at the end of December 2026
- Tools that are a better fit than this one
Last reviewed 2026-08-29.
Updated 29 Aug 2026