Recipient directory and selection

Understand valid-email filtering

Know why a contact or lead with a missing or malformed address is not offered as a recipient.

Audience: CRM staffPermission: Staff loginModule v1.0.0
Exact navigationAdmin Area → Letter Manager → Email Marketing / Newsletter → Recipient selector
Before you begin
  • 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 this guide covers

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.

Exact step-by-step process

  1. Open the source CRM contact or lead record.
  2. Correct the email address using the normal CRM form.
  3. Return to Letter Manager and reload the newsletter directory.
  4. Search for the corrected record.

Fields, choices and supported possibilities

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
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • 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.

Expected result and verification

  • 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.