Understand valid-email filtering
This guide explains that why a contact or lead with a missing or malformed address is not offered as a recipient. 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 → Recipient selector
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
Know why a contact or lead with a missing or malformed address is not offered as a recipient. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Go to the source CRM contact or lead record.
- Correct the email address using the normal CRM form.
- Return to Letter Manager and reload the newsletter directory.
- Search for the corrected record.
Fields and options to review
Action scopeKnow why a contact or lead with a missing or malformed address is not offered as a recipient.
Module version1.0.0
NavigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Recipient selector
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- Both directory loading and campaign creation validate email addresses.
- A selected key that no longer resolves to a valid directory entry is rejected at campaign creation.
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.