SMTP Setup
Use Mailpit for local testing and a reputable transactional-mail provider for production. Never copy local blank credentials into a public deployment.
Configuration fields
| Field | Production guidance |
|---|---|
| Mailer | Usually smtp unless the provider states otherwise. |
| Host | The provider’s exact SMTP hostname. |
| Port/encryption | Use the matched secure combination supplied by the provider. |
| Username/password | Dedicated SMTP credentials stored in environment configuration. |
| From address/name | A verified domain identity guests recognize. |
Production verification
- Verify the sending domain and configure SPF, DKIM, and DMARC according to the provider.
- Enter SMTP values without exposing them in screenshots or support tickets.
- Clear configuration cache and restart queue workers after environment changes.
- Send a template test to at least two external mailbox providers.
- Verify password reset, booking confirmation, receipt, and guest-signature-link delivery.
- Review message logs and provider delivery events.
Common failures
- Connection refused: confirm host, port, firewall, and encryption pairing.
- Authentication failed: rotate the SMTP credential and confirm sending access.
- Queued but not sent: restart the queue worker and inspect failed jobs.
- Delivered to spam: verify domain authentication, content, from identity, and reputation.
- Wrong links: correct the production HTTPS application URL and clear cached configuration.
Do not send real guest mail from local development. Use Mailpit or a provider sandbox until every template and link is verified.