Email delivery, attachments and read receipts

Interpret detected IP source and proxy notes

Use the recorded IP source and warning note without overstating recipient identity.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Customers → Open customer → Letter History; or Internal Full View

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 the recorded IP source and warning note without overstating recipient identity. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Review Last Open IP.
Review Last Open IP Source, such as CF-Connecting-IP, X-Forwarded-For or REMOTE_ADDR.
Read Last Open IP Note.
Treat proxy/scanner notes as material caveats in any audit conclusion.

Fields, choices and supported possibilities

Action scopeUse the recorded IP source and warning note without overstating recipient identity.

Module version1.0.0

Exact routeAdmin Area → Customers → Open customer → Letter History; or Internal Full View

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 endpoint checks several headers and takes the first syntactically valid IP.
It records the source label used.
User-agent patterns add notes for Google, Apple, Microsoft/Outlook and security scanners.

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.