Files
authentik/docs/topics/troubleshooting/emails.md
Teffen Ellis 582812b3ec website: Flesh out docs split.
website: Copy files during build.

website: Allow for mixed env builds.

website: Reduce build size.

website: Expose build.

website: Add build memory debugging.

WIP: Disable broken links check to compare memory usage.

website: Update deps.

website: Clean up API paths.

website: Flesh out 3.8 fixes.

Format.

website: Update ignore paths.

Website: Clean up integrations build.

website: Fix paths.

website: Optimize remark.

website: Update deps.

website: Format.

website: Remove linking.

website: Fix paths.

wip: Attempt API only build.

Prep.

Migrate render to runtime. Tidy sidebar.

Clean up templates.

docs: Move directory. WIP

docs: Flesh out split.

website: Fix issue where routes have collisions.
2025-07-01 21:53:19 +02:00

765 B

title
title
Troubleshooting Email sending

:::info Some hosting providers block outgoing SMTP ports, in which case you'll have to host an SMTP relay on a different port with a different provider. :::

To test if an email stage, or the global email settings are configured correctly, you can run the following command:

ak test_email <to address> [-S <stage name>]

If you omit the -S parameter, the email will be sent using the global settings. Otherwise, the settings of the specified stage will be used.

To run this command with docker-compose, use

docker compose exec worker ak test_email [...]

To run this command with Kubernetes, use

kubectl exec -it deployment/authentik-worker -c worker -- ak test_email [...]