# E09. Deployment and mail-guide analysis

## Source and acquisition

The 23 July record describes an HTML guide retrieved through the unauthenticated route loaded by the administration frontend. The guide covers server setup, business email configuration, GitHub-user collection and spam-filter troubleshooting. No authenticated mailbox or administration API was queried in that acquisition record. This report relies on the saved analysis. [S1]

## Mail-provider evidence

Example DNS configuration refers to Namecheap Private Email. The associated sender tooling uses `mail.privateemail.com`, although some variable names contain ZOHO. A variable label is therefore insufficient to identify the actual provider. The case record links a discussed outbound relay to shared Private Email infrastructure. Other tenants on that relay cannot be attributed to the campaign merely through co-residence. [S1]

Later received-message records contain Mailgun-related evidence. That is compatible with different providers across messages or periods. The guide's deliverability discussion is not proof of why a provider changed, nor of which provider handled every campaign message.

## Workflow evidence

The guide describes GitHub API and web-based user collection and includes generic domain, server and email setup instructions. This is consistent with reusable recruitment operations. Sender configuration and the harvester provide more direct evidence of the collection-to-messaging relationship than the guide alone; E08 covers those artifacts.

The record identifies text resembling copied assistant output in the troubleshooting section. Such text supports a limited observation about the document's composition. It does not identify its author, quantify reliance on AI, measure technical skill or establish the number of operators. Second-person instructions can be written for oneself as well as a team.

## Assessment

Provider attribution should follow configured endpoints and received headers. Shared relay addresses are contextual infrastructure observations, not campaign-exclusive indicators. The guide describes intended procedures, not verified execution of them. Recovered account values and operational credentials are omitted, and no provider status or network observation was refreshed for this report.