2022-11-20 13:15:45 -05:00
# shellcheck disable=SC2034,SC2148
2021-04-27 17:18:32 -04:00
## Vaultwarden Configuration File
2018-06-12 15:09:42 -04:00
## Uncomment any of the following lines to change the defaults
2020-09-12 15:47:24 -04:00
##
## Be aware that most of these settings will be overridden if they were changed
2020-08-13 11:49:25 -04:00
## in the admin interface. Those overrides are stored within DATA_FOLDER/config.json .
2022-02-16 14:42:12 -05:00
##
2022-11-20 13:15:45 -05:00
## By default, Vaultwarden expects for this file to be named ".env" and located
2022-02-16 14:42:12 -05:00
## in the current working directory. If this is not the case, the environment
## variable ENV_FILE can be set to the location of this file prior to starting
2022-11-20 13:15:45 -05:00
## Vaultwarden.
2018-06-12 15:09:42 -04:00
## Main data folder
# DATA_FOLDER=data
2019-06-02 07:44:59 -04:00
## Database URL
## When using SQLite, this is the path to the DB file, default to %DATA_FOLDER%/db.sqlite3
2018-02-09 19:00:55 -05:00
# DATABASE_URL=data/db.sqlite3
2020-08-13 05:33:22 -04:00
## When using MySQL, specify an appropriate connection URI.
## Details: https://docs.diesel.rs/diesel/mysql/struct.MysqlConnection.html
# DATABASE_URL=mysql://user:password@host[:port]/database_name
## When using PostgreSQL, specify an appropriate connection URI (recommended)
## or keyword/value connection string.
## Details:
## - https://docs.diesel.rs/diesel/pg/struct.PgConnection.html
## - https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING
# DATABASE_URL=postgresql://user:password@host[:port]/database_name
2019-06-02 07:44:59 -04:00
2020-10-06 09:23:55 -04:00
## Database max connections
## Define the size of the connection pool used for connecting to the database.
# DATABASE_MAX_CONNS=10
2022-04-26 20:50:20 -04:00
## Database connection initialization
## Allows SQL statements to be run whenever a new database connection is created.
2022-04-29 03:26:49 -04:00
## This is mainly useful for connection-scoped pragmas.
## If empty, a database-specific default is used:
## - SQLite: "PRAGMA busy_timeout = 5000; PRAGMA synchronous = NORMAL;"
## - MySQL: ""
## - PostgreSQL: ""
# DATABASE_CONN_INIT=""
2022-04-26 20:50:20 -04:00
2019-06-02 07:44:59 -04:00
## Individual folders, these override %DATA_FOLDER%
2018-06-12 15:09:42 -04:00
# RSA_KEY_FILENAME=data/rsa_key
2018-02-09 19:00:55 -05:00
# ICON_CACHE_FOLDER=data/icon_cache
# ATTACHMENTS_FOLDER=data/attachments
2021-03-14 18:35:55 -04:00
# SENDS_FOLDER=data/sends
2022-05-24 03:38:16 -04:00
# TMP_FOLDER=data/tmp
2018-02-09 19:00:55 -05:00
2019-01-12 19:39:29 -05:00
## Templates data folder, by default uses embedded templates
## Check source code to see the format
# TEMPLATES_FOLDER=/path/to/templates
2019-01-20 11:43:56 -05:00
## Automatically reload the templates for every request, slow, use only for development
# RELOAD_TEMPLATES=false
2019-01-12 19:39:29 -05:00
2021-03-29 05:16:20 -04:00
## Client IP Header, used to identify the IP of the client, defaults to "X-Real-IP"
2019-12-27 12:42:39 -05:00
## Set to the string "none" (without quotes), to disable any headers and just use the remote IP
2021-03-29 05:16:20 -04:00
# IP_HEADER=X-Real-IP
2019-12-27 12:42:39 -05:00
2018-12-18 16:33:31 -05:00
## Cache time-to-live for successfully obtained icons, in seconds (0 is "forever")
# ICON_CACHE_TTL=2592000
## Cache time-to-live for icons which weren't available, in seconds (0 is "forever")
# ICON_CACHE_NEGTTL=259200
2018-06-12 15:09:42 -04:00
## Web vault settings
# WEB_VAULT_FOLDER=web-vault/
# WEB_VAULT_ENABLED=true
2019-01-15 09:28:25 -05:00
## Enables websocket notifications
# WEBSOCKET_ENABLED=false
2018-09-28 07:46:13 -04:00
## Controls the WebSocket server address and port
# WEBSOCKET_ADDRESS=0.0.0.0
2018-09-13 14:59:51 -04:00
# WEBSOCKET_PORT=3012
2021-05-11 23:07:32 -04:00
## Controls whether users are allowed to create Bitwarden Sends.
## This setting applies globally to all users.
## To control this on a per-org basis instead, use the "Disable Send" org policy.
# SENDS_ALLOWED=true
2021-10-19 04:27:50 -04:00
## Controls whether users can enable emergency access to their accounts.
## This setting applies globally to all users.
# EMERGENCY_ACCESS_ALLOWED=true
2022-11-20 13:15:45 -05:00
## Controls whether event logging is enabled for organizations
## This setting applies to organizations.
## Default this is disabled. Also check the EVENT_CLEANUP_SCHEDULE and EVENTS_DAYS_RETAIN settings.
# ORG_EVENTS_ENABLED=false
## Number of days to retain events stored in the database.
## If unset (the default), events are kept indefently and also disables the scheduled job!
# EVENTS_DAYS_RETAIN=
2021-04-02 23:16:49 -04:00
## Job scheduler settings
##
## Job schedules use a cron-like syntax (as parsed by https://crates.io/crates/cron),
## and are always in terms of UTC time (regardless of your local time zone settings).
##
2022-11-20 13:15:45 -05:00
## The schedule format is a bit different from crontab as crontab does not contains seconds.
## You can test the the format here: https://crontab.guru, but remove the first digit!
## SEC MIN HOUR DAY OF MONTH MONTH DAY OF WEEK
## "0 30 9,12,15 1,15 May-Aug Mon,Wed,Fri"
## "0 30 * * * * "
## "0 30 1 * * * "
##
2021-04-02 23:16:49 -04:00
## How often (in ms) the job scheduler thread checks for jobs that need running.
## Set to 0 to globally disable scheduled jobs.
# JOB_POLL_INTERVAL_MS=30000
##
## Cron schedule of the job that checks for Sends past their deletion date.
2021-04-06 02:12:36 -04:00
## Defaults to hourly (5 minutes after the hour). Set blank to disable this job.
# SEND_PURGE_SCHEDULE="0 5 * * * *"
2021-04-02 23:52:15 -04:00
##
## Cron schedule of the job that checks for trashed items to delete permanently.
2021-04-06 02:12:36 -04:00
## Defaults to daily (5 minutes after midnight). Set blank to disable this job.
# TRASH_PURGE_SCHEDULE="0 5 0 * * *"
2021-03-24 15:15:55 -04:00
##
2021-10-25 04:36:05 -04:00
## Cron schedule of the job that checks for incomplete 2FA logins.
## Defaults to once every minute. Set blank to disable this job.
# INCOMPLETE_2FA_SCHEDULE="30 * * * * *"
##
2021-10-19 04:27:50 -04:00
## Cron schedule of the job that sends expiration reminders to emergency access grantors.
2022-11-26 13:07:28 -05:00
## Defaults to hourly (3 minutes after the hour). Set blank to disable this job.
# EMERGENCY_NOTIFICATION_REMINDER_SCHEDULE="0 3 * * * *"
2021-03-24 15:15:55 -04:00
##
2021-10-19 04:27:50 -04:00
## Cron schedule of the job that grants emergency access requests that have met the required wait time.
2022-11-26 13:07:28 -05:00
## Defaults to hourly (7 minutes after the hour). Set blank to disable this job.
# EMERGENCY_REQUEST_TIMEOUT_SCHEDULE="0 7 * * * *"
2022-11-20 13:15:45 -05:00
##
## Cron schedule of the job that cleans old events from the event table.
## Defaults to daily. Set blank to disable this job. Also without EVENTS_DAYS_RETAIN set, this job will not start.
# EVENT_CLEANUP_SCHEDULE="0 10 0 * * *"
2021-04-02 23:16:49 -04:00
2019-12-06 16:19:07 -05:00
## Enable extended logging, which shows timestamps and targets in the logs
2018-12-06 14:35:25 -05:00
# EXTENDED_LOGGING=true
2020-07-23 00:50:49 -04:00
## Timestamp format used in extended logging.
## Format specifiers: https://docs.rs/chrono/latest/chrono/format/strftime
2020-07-23 17:19:51 -04:00
# LOG_TIMESTAMP_FORMAT="%Y-%m-%d %H:%M:%S.%3f"
2020-07-23 00:50:49 -04:00
2018-12-06 14:35:25 -05:00
## Logging to file
# LOG_FILE=/path/to/log
2019-04-27 14:14:37 -04:00
## Logging to Syslog
## This requires extended logging
# USE_SYSLOG=false
2019-03-25 09:12:41 -04:00
## Log level
## Change the verbosity of the log output
## Valid values are "trace", "debug", "info", "warn", "error" and "off"
2020-09-12 15:47:24 -04:00
## Setting it to "trace" or "debug" would also show logs for mounted
2019-12-06 16:19:07 -05:00
## routes and static file, websocket and alive requests
2019-03-25 09:12:41 -04:00
# LOG_LEVEL=Info
2019-02-18 09:57:21 -05:00
## Enable WAL for the DB
## Set to false to avoid enabling WAL during startup.
## Note that if the DB already has WAL enabled, you will also need to disable WAL in the DB,
2022-11-20 13:15:45 -05:00
## this setting only prevents Vaultwarden from automatically enabling it on start.
2019-02-18 09:57:21 -05:00
## Please read project wiki page about this setting first before changing the value as it can
2021-05-14 09:36:42 -04:00
## cause performance degradation or might render the service unable to start.
2019-02-18 09:57:21 -05:00
# ENABLE_DB_WAL=true
2020-10-04 08:13:31 -04:00
## Database connection retries
## Number of times to retry the database connection during startup, with 1 second delay between each retry, set to 0 to retry indefinitely
# DB_CONNECTION_RETRIES=15
2021-12-20 04:34:31 -05:00
## Icon service
## The predefined icon services are: internal, bitwarden, duckduckgo, google.
## To specify a custom icon service, set a URL template with exactly one instance of `{}`,
## which is replaced with the domain. For example: `https://icon.example.com/domain/{}`.
##
## `internal` refers to Vaultwarden's built-in icon fetching implementation.
2021-12-29 21:01:32 -05:00
## If an external service is set, an icon request to Vaultwarden will return an HTTP
2021-12-20 04:34:31 -05:00
## redirect to the corresponding icon at the external service. An external service may
## be useful if your Vaultwarden instance has no external network connectivity, or if
## you are concerned that someone may probe your instance to try to detect whether icons
## for certain sites have been cached.
# ICON_SERVICE=internal
2021-12-29 21:01:32 -05:00
## Icon redirect code
## The HTTP status code to use for redirects to an external icon service.
2022-01-09 02:40:35 -05:00
## The supported codes are 301 (legacy permanent), 302 (legacy temporary), 307 (temporary), and 308 (permanent).
2021-12-29 21:01:32 -05:00
## Temporary redirects are useful while testing different icon services, but once a service
2022-01-09 02:40:35 -05:00
## has been decided on, consider using permanent redirects for cacheability. The legacy codes
## are currently better supported by the Bitwarden clients.
# ICON_REDIRECT_CODE=302
2021-12-29 21:01:32 -05:00
2019-01-28 17:58:32 -05:00
## Disable icon downloading
2021-12-20 04:34:31 -05:00
## Set to true to disable icon downloading in the internal icon service.
## This still serves existing icons from $ICON_CACHE_FOLDER, without generating any external
## network requests. $ICON_CACHE_TTL must also be set to 0; otherwise, the existing icons
## will be deleted eventually, but won't be downloaded again.
2019-01-28 17:58:32 -05:00
# DISABLE_ICON_DOWNLOAD=false
2019-02-12 15:56:28 -05:00
## Icon download timeout
## Configure the timeout value when downloading the favicons.
## The default is 10 seconds, but this could be to low on slower network connections
# ICON_DOWNLOAD_TIMEOUT=10
2019-03-18 17:12:39 -04:00
## Icon blacklist Regex
## Any domains or IPs that match this regex won't be fetched by the icon service.
## Useful to hide other servers in the local network. Check the WIKI for more details
2020-12-08 11:33:15 -05:00
## NOTE: Always enclose this regex withing single quotes!
# ICON_BLACKLIST_REGEX='^(192\.168\.0\.[0-9]+|192\.168\.1\.[0-9]+)$'
2019-03-18 17:12:39 -04:00
2019-10-08 07:30:17 -04:00
## Any IP which is not defined as a global IP will be blacklisted.
2020-10-06 12:54:21 -04:00
## Useful to secure your internal environment: See https://en.wikipedia.org/wiki/Reserved_IP_addresses for a list of IPs which it will block
2019-10-08 07:30:17 -04:00
# ICON_BLACKLIST_NON_GLOBAL_IPS=true
2019-03-18 17:12:39 -04:00
## Disable 2FA remember
## Enabling this would force the users to use a second factor to login every time.
## Note that the checkbox would still be present, but ignored.
# DISABLE_2FA_REMEMBER=false
2020-10-06 12:54:21 -04:00
## Maximum attempts before an email token is reset and a new email will need to be sent.
# EMAIL_ATTEMPTS_LIMIT=3
## Token expiration time
## Maximum time in seconds a token is valid. The time the user has to open email client and copy token.
# EMAIL_EXPIRATION_TIME=600
## Email token size
2022-01-24 04:17:00 -05:00
## Number of digits in an email 2FA token (min: 6, max: 255).
2020-10-06 12:54:21 -04:00
## Note that the Bitwarden clients are hardcoded to mention 6 digit codes regardless of this setting!
# EMAIL_TOKEN_SIZE=6
2018-12-18 12:52:58 -05:00
## Controls if new users can register
# SIGNUPS_ALLOWED=true
2019-11-25 00:28:49 -05:00
## Controls if new users need to verify their email address upon registration
## Note that setting this option to true prevents logins until the email address has been verified!
## The welcome email will include a verification link, and login attempts will periodically
## trigger another verification email to be sent.
# SIGNUPS_VERIFY=false
## If SIGNUPS_VERIFY is set to true, this limits how many seconds after the last time
## an email verification link has been sent another verification email will be sent
# SIGNUPS_VERIFY_RESEND_TIME=3600
## If SIGNUPS_VERIFY is set to true, this limits how many times an email verification
## email will be re-sent upon an attempted login.
# SIGNUPS_VERIFY_RESEND_LIMIT=6
2019-11-16 17:01:45 -05:00
## Controls if new users from a list of comma-separated domains can register
## even if SIGNUPS_ALLOWED is set to false
# SIGNUPS_DOMAINS_WHITELIST=example.com,example.net,example.org
2020-08-06 01:35:29 -04:00
## Controls which users can create new orgs.
## Blank or 'all' means all users can create orgs (this is the default):
# ORG_CREATION_USERS=
## 'none' means no users can create orgs:
# ORG_CREATION_USERS=none
## A comma-separated list means only those users can create orgs:
# ORG_CREATION_USERS=admin1@example.com,admin2@example.com
2018-12-18 12:52:58 -05:00
## Token for the admin interface, preferably use a long random string
## One option is to use 'openssl rand -base64 48'
## If not set, the admin panel is disabled
# ADMIN_TOKEN=Vy2VyYTTsKPv8W5aEOWUbB/Bt3DEKePbHmI4m9VcemUMS2rEviDowNAFqYi1xjmp
2019-10-08 13:33:27 -04:00
## Enable this to bypass the admin panel security. This option is only
## meant to be used with the use of a separate auth layer in front
2019-02-20 15:44:35 -05:00
# DISABLE_ADMIN_TOKEN=false
2018-12-18 12:52:58 -05:00
## Invitations org admins to invite users, even when signups are disabled
# INVITATIONS_ALLOWED=true
2020-10-06 12:54:21 -04:00
## Name shown in the invitation emails that don't come from a specific organization
2021-04-27 17:18:32 -04:00
# INVITATION_ORG_NAME=Vaultwarden
2020-10-06 12:54:21 -04:00
2022-10-08 12:31:34 -04:00
## The number of hours after which an organization invite token, emergency access invite token,
## email verification token and deletion request token will expire (must be at least 1)
# INVITATION_EXPIRATION_HOURS=120
2021-07-13 09:17:03 -04:00
## Per-organization attachment storage limit (KB)
## Max kilobytes of attachment storage allowed per organization.
## When this limit is reached, organization members will not be allowed to upload further attachments for ciphers owned by that organization.
2020-10-06 12:54:21 -04:00
# ORG_ATTACHMENT_LIMIT=
2021-07-13 09:17:03 -04:00
## Per-user attachment storage limit (KB)
## Max kilobytes of attachment storage allowed per user.
## When this limit is reached, the user will not be allowed to upload further attachments.
2020-10-06 12:54:21 -04:00
# USER_ATTACHMENT_LIMIT=
2021-05-16 20:51:54 -04:00
## Number of days to wait before auto-deleting a trashed item.
## If unset (the default), trashed items are not auto-deleted.
## This setting applies globally, so make sure to inform all users of any changes to this setting.
# TRASH_AUTO_DELETE_DAYS=
2018-12-18 12:52:58 -05:00
2021-10-25 04:36:05 -04:00
## Number of minutes to wait before a 2FA-enabled login is considered incomplete,
## resulting in an email notification. An incomplete 2FA login is one where the correct
## master password was provided but the required 2FA step was not completed, which
## potentially indicates a master password compromise. Set to 0 to disable this check.
## This setting applies globally to all users.
# INCOMPLETE_2FA_TIME_LIMIT=3
2018-06-12 15:09:42 -04:00
## Controls the PBBKDF password iterations to apply on the server
## The change only applies when the password is changed
# PASSWORD_ITERATIONS=100000
2018-02-09 19:00:55 -05:00
2022-06-30 23:46:17 -04:00
## Controls whether users can set password hints. This setting applies globally to all users.
# PASSWORD_HINTS_ALLOWED=true
2021-07-10 04:20:37 -04:00
## Controls whether a password hint should be shown directly in the web page if
## SMTP service is not configured. Not recommended for publicly-accessible instances
## as this provides unauthenticated access to potentially sensitive data.
# SHOW_PASSWORD_HINT=false
2018-08-10 09:21:42 -04:00
2018-07-12 17:28:01 -04:00
## Domain settings
## The domain must match the address from where you access the server
2019-02-08 13:21:48 -05:00
## It's recommended to configure this value, otherwise certain functionality might not work,
## like attachment downloads, email links and U2F.
2018-07-12 17:28:01 -04:00
## For U2F to work, the server must use HTTPS, you can use Let's Encrypt for free certs
2022-06-13 06:56:41 -04:00
# DOMAIN=https://vw.domain.tld:8443
2018-07-12 17:28:01 -04:00
2020-10-06 12:54:21 -04:00
## Allowed iframe ancestors (Know the risks!)
## https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors
## Allows other domains to embed the web vault into an iframe, useful for embedding into secure intranets
## This adds the configured value to the 'Content-Security-Policy' headers 'frame-ancestors' value.
## Multiple values must be separated with a whitespace.
# ALLOWED_IFRAME_ANCESTORS=
2021-12-24 19:10:21 -05:00
## Number of seconds, on average, between login requests from the same IP address before rate limiting kicks in.
# LOGIN_RATELIMIT_SECONDS=60
## Allow a burst of requests of up to this size, while maintaining the average indicated by `LOGIN_RATELIMIT_SECONDS`.
## Note that this applies to both the login and the 2FA, so it's recommended to allow a burst size of at least 2.
# LOGIN_RATELIMIT_MAX_BURST=10
2022-11-22 09:12:06 -05:00
## Number of seconds, on average, between admin login requests from the same IP address before rate limiting kicks in.
2021-12-24 19:10:21 -05:00
# ADMIN_RATELIMIT_SECONDS=300
## Allow a burst of requests of up to this size, while maintaining the average indicated by `ADMIN_RATELIMIT_SECONDS`.
# ADMIN_RATELIMIT_MAX_BURST=3
2018-11-15 20:40:27 -05:00
## Yubico (Yubikey) Settings
## Set your Client ID and Secret Key for Yubikey OTP
## You can generate it here: https://upgrade.yubico.com/getapikey/
2018-11-15 20:54:53 -05:00
## You can optionally specify a custom OTP server
2018-11-15 20:40:27 -05:00
# YUBICO_CLIENT_ID=11111
# YUBICO_SECRET_KEY=AAAAAAAAAAAAAAAAAAAAAAAA
2018-11-15 20:54:53 -05:00
# YUBICO_SERVER=http://yourdomain.com/wsapi/2.0/verify
2018-11-15 20:40:27 -05:00
2019-04-07 12:58:15 -04:00
## Duo Settings
2019-04-27 14:14:37 -04:00
## You need to configure all options to enable global Duo support, otherwise users would need to configure it themselves
2019-04-07 12:58:15 -04:00
## Create an account and protect an application as mentioned in this link (only the first step, not the rest):
## https://help.bitwarden.com/article/setup-two-step-login-duo/#create-a-duo-security-account
## Then set the following options, based on the values obtained from the last step:
# DUO_IKEY=<Integration Key>
# DUO_SKEY=<Secret Key>
# DUO_HOST=<API Hostname>
## After that, you should be able to follow the rest of the guide linked above,
## ignoring the fields that ask for the values that you already configured beforehand.
2019-11-07 11:11:29 -05:00
## Authenticator Settings
## Disable authenticator time drifted codes to be valid.
## TOTP codes of the previous and next 30 seconds will be invalid
2020-09-12 15:47:24 -04:00
##
2019-11-07 11:11:29 -05:00
## According to the RFC6238 (https://tools.ietf.org/html/rfc6238),
## we allow by default the TOTP code which was valid one step back and one in the future.
## This can however allow attackers to be a bit more lucky with there attempts because there are 3 valid codes.
## You can disable this, so that only the current TOTP Code is allowed.
## Keep in mind that when a sever drifts out of time, valid codes could be marked as invalid.
## In any case, if a code has been used it can not be used again, also codes which predates it will be invalid.
2021-05-14 09:36:42 -04:00
# AUTHENTICATOR_DISABLE_TIME_DRIFT=false
2019-11-07 11:11:29 -05:00
2021-05-31 16:13:02 -04:00
## Rocket specific settings
## See https://rocket.rs/v0.4/guide/configuration/ for more details.
# ROCKET_ADDRESS=0.0.0.0
# ROCKET_PORT=80 # Defaults to 80 in the Docker images, or 8000 otherwise.
# ROCKET_WORKERS=10
2018-02-09 19:00:55 -05:00
# ROCKET_TLS={certs="/path/to/certs.pem",key="/path/to/key.pem"}
2018-08-15 02:32:19 -04:00
2018-09-13 14:59:51 -04:00
## Mail specific settings, set SMTP_HOST and SMTP_FROM to enable the mail service.
2019-02-08 13:21:48 -05:00
## To make sure the email links are pointing to the correct host, set the DOMAIN variable.
2018-09-13 14:59:51 -04:00
## Note: if SMTP_USERNAME is specified, SMTP_PASSWORD is mandatory
2018-08-15 02:32:19 -04:00
# SMTP_HOST=smtp.domain.tld
2021-04-27 17:18:32 -04:00
# SMTP_FROM=vaultwarden@domain.tld
# SMTP_FROM_NAME=Vaultwarden
2022-02-22 14:48:00 -05:00
# SMTP_SECURITY=starttls # ("starttls", "force_tls", "off") Enable a secure connection. Default is "starttls" (Explicit - ports 587 or 25), "force_tls" (Implicit - port 465) or "off", no encryption (port 25)
2022-11-12 16:39:41 -05:00
# SMTP_PORT=587 # Ports 587 (submission) and 25 (smtp) are standard without encryption and with encryption via STARTTLS (Explicit TLS). Port 465 (submissions) is used for encrypted submission (Implicit TLS).
2018-08-15 02:32:19 -04:00
# SMTP_USERNAME=username
2019-02-20 15:44:35 -05:00
# SMTP_PASSWORD=password
2020-10-06 12:54:21 -04:00
# SMTP_TIMEOUT=15
2020-09-12 15:47:24 -04:00
## Defaults for SSL is "Plain" and "Login" and nothing for Non-SSL connections.
## Possible values: ["Plain", "Login", "Xoauth2"].
## Multiple options need to be separated by a comma ','.
2019-08-23 19:22:14 -04:00
# SMTP_AUTH_MECHANISM="Plain"
2020-10-06 12:54:21 -04:00
## Server name sent during the SMTP HELO
## By default this value should be is on the machine's hostname,
## but might need to be changed in case it trips some anti-spam filters
# HELO_NAME=
2022-09-30 13:14:26 -04:00
## Embed images as email attachments
# SMTP_EMBED_IMAGES=false
2020-11-18 06:07:08 -05:00
## SMTP debugging
## When set to true this will output very detailed SMTP messages.
## WARNING: This could contain sensitive information like passwords and usernames! Only enable this during troubleshooting!
# SMTP_DEBUG=false
## Accept Invalid Hostnames
## DANGEROUS: This option introduces significant vulnerabilities to man-in-the-middle attacks!
## Only use this as a last resort if you are not able to use a valid certificate.
# SMTP_ACCEPT_INVALID_HOSTNAMES=false
## Accept Invalid Certificates
## DANGEROUS: This option introduces significant vulnerabilities to man-in-the-middle attacks!
## Only use this as a last resort if you are not able to use a valid certificate.
## If the Certificate is valid but the hostname doesn't match, please use SMTP_ACCEPT_INVALID_HOSTNAMES instead.
# SMTP_ACCEPT_INVALID_CERTS=false
2020-10-06 12:54:21 -04:00
## Require new device emails. When a user logs in an email is required to be sent.
## If sending the email fails the login attempt will fail!!
# REQUIRE_DEVICE_EMAIL=false
## HIBP Api Key
## HaveIBeenPwned API Key, request it here: https://haveibeenpwned.com/API/Key
# HIBP_API_KEY=
2019-11-11 05:19:58 -05:00
# vim: syntax=ini