Email
Email in SuiteCRM 8: UI, scheduler and workflows
In short
- Admin test mail does not prove the job path.
- After upgrades, queues and stored SMTP data can diverge.
- Stable email is CRM config + OS cron + provider limits + flow design.
Treat email as three systems under one label: UI, scheduler and workflow.
Path A
Low visibility
CRM action→Legacy mailer→Provider→Recipient?
UI test OK says little about queues and background errors.
Path B
Controlled sending
CRM action→Queue / control→Provider→Traceable status
Make failures visible — not only “re-save SMTP”.
Ops trap
Provider limits
Many SMTP providers throttle. Without queueing and error handling, the remainder of a run fails in ways that are hard to reconstruct. Limits are provider-specific.
SuiteSMTP aims at clearer delivery visibility in the CRM context. It does not replace OS cron or sound flow design.
SuiteSMTP ↗