Understand newsletter send success and failure
Follow this guide to review how each SMTP attempt changes recipient and campaign evidence. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Letter Manager → Email Marketing / Newsletter → History → Details
Before you start
- Use an authorised account and confirm the source CRM record or setting is correct.
- Follow the exact route shown above; do not force database values to imitate a completed action.
What you’ll accomplish
Review how each SMTP attempt changes recipient and campaign evidence. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Go to campaign Details.
- Verify successful rows show sent and sent_at.
- Check failed rows and their stored email-debug or exception message.
- Correct SMTP or recipient data before a future campaign.
Fields and options to review
Action scopeCheck how each SMTP attempt changes recipient and campaign evidence.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → History → Details
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- Every attempted row is marked sent or failed; failures count against the rolling attempt limit.
- The module does not automatically requeue failed recipients in the supplied release.
How to confirm it worked
- The requested record, output or setting is created or updated through the supported module flow.
- Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
- An error message is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
- Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
- Test configuration changes with controlled records before production-wide use.
- Retain or delete evidence only under an authorised retention process.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.