Email & Delivery Channels
Delivery channels power OTP, password reset, verification email, ticket activity messages, scheduled reports, and operational alerts. Configure them before requiring email-based security flows.
Mailers
- SMTP: recommended for production.
- Sendmail: useful on servers with local mail transport.
- Log: useful locally because messages are written to logs instead of being sent.
SMTP Fields
SMTP setup includes host, port, username, password, encryption, timeout, reply-to, from address, and from name. Encryption can be TLS, SSL, or none depending on provider requirements.
Twilio SMS and WhatsApp
SMS and WhatsApp delivery require Twilio SID, Twilio token, country code, SMS from number, WhatsApp from number, and enabled channel toggles. WhatsApp sender values usually include the whatsapp: prefix.
OTP Safety
If OTP is required but all delivery channels are disabled or broken, users can be locked out. Confirm email delivery works before enforcing OTP for admins. Keep TOTP recovery codes available for admin accounts.
Testing
- Save channel settings.
- Send a test email to an address you can access.
- If SMS or WhatsApp are enabled, send a test message to a known number.
- Check delivery logs and application logs if the test does not arrive.
Common Fixes
- Use the exact SMTP encryption and port from the provider.
- Use app passwords when the provider requires them.
- Set
APP_URLcorrectly so email links point to the right domain. - Run a queue worker if mail is queued.