Files
lasuite-messages/deploy/env/mta-in-py.defaults
T

47 lines
1.7 KiB
Plaintext

# Defaults for the pure-Python (aiosmtpd) inbound MTA. The Postfix-based
# `mta-in` service does not consume these.
# PYMTA_HOSTNAME is intentionally left unset so the shared MYHOSTNAME env
# wins (matching the Postfix variant). Set explicitly to override.
PYMTA_SMTP_HOST=0.0.0.0
PYMTA_SMTP_PORT=25
PYMTA_METRICS_HOST=0.0.0.0
PYMTA_METRICS_PORT=9100
PYMTA_LOG_LEVEL=INFO
# Match the existing Postfix dev config: per-IP cap off (the dev/test load
# all comes from loopback), large global cap for `test_connection_limits`.
PYMTA_MAX_SESSIONS_PER_IP=0
PYMTA_MAX_SESSIONS_TOTAL=2000
# Inbound limits.
PYMTA_MAX_RECIPIENTS=100
PYMTA_MAX_ENVELOPES_PER_CONNECTION=20
# Timeouts (seconds). PYMTA_COMMAND_TIMEOUT is the idle gap allowed between
# complete commands; PYMTA_DATA_TIMEOUT is a separate total budget for the
# whole DATA phase (354 -> last body byte -> MDA deliver -> reply).
PYMTA_COMMAND_TIMEOUT=120
PYMTA_DATA_TIMEOUT=300
# STARTTLS off by default in dev (no cert wired).
PYMTA_TLS_CERT_FILE=
PYMTA_TLS_KEY_FILE=
# SMTPUTF8 advertised: the MDA accepts UTF-8 envelope addresses.
PYMTA_ENABLE_SMTPUTF8=true
# PROXY protocol off in dev: the test suite connects to pymta directly, so the
# TCP peer IS the client.
#
# Behind a load balancer, set PYMTA_ENABLE_PROXY_PROTOCOL=true AND
# PYMTA_TRUSTED_PROXIES to the balancer's IPs/CIDRs. pymta refuses to start
# with PROXY protocol on and no allowlist. (The Postfix image drives the same
# feature from its own ENABLE_PROXY_PROTOCOL=haproxy; pymta ignores that name.)
#
# A balancer WITHOUT PROXY protocol is not a supported configuration: every
# session would bucket under the balancer's IP and every message would be
# stamped with it as the sender's address.
PYMTA_ENABLE_PROXY_PROTOCOL=false
PYMTA_TRUSTED_PROXIES=