Email delivery, attachments and read receipts

Understand supported enclosure file types

Use only extensions accepted by the upload helper.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Enclosed File / Additional Email Attachment

Before you begin

Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.

What this guide covers

Use only extensions accepted by the upload helper. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Choose PDF, PNG, JPG, JPEG, DOC or DOCX.
Avoid renamed executable or unsupported archive files.
Send a controlled test and verify the stored MIME/type.

Fields, choices and supported possibilities

Action scopeUse only extensions accepted by the upload helper.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Enclosed File / Additional Email Attachment

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Code-backed validations and workflow rules

The server checks the lowercase filename extension against pdf, png, jpg, jpeg, doc and docx.
The HTML accept attribute mirrors those formats but server extension checking remains authoritative.

Expected result and verification

The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
Any warning, missing file or failed send is investigated rather than bypassed.

Security, privacy and operational checks

Apply least privilege and verify recipient identity before sending or exposing public links.
Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
Test configuration and deployment changes with controlled records before production-wide use.
Interpret email opens and e-signatures according to their documented technical limitations.