Operations Playbook
Operational guides for email hosting administrators — server monitoring, deliverability tuning, incident response, and scaling your email infrastructure.
for ""
No articles match your search.
Try different keywords or .
All
Email Forwarding
Business Email
Operations Playbook
Email Migration
Deliverability & DNS
Providers Compared
Webmail & Productivity
Drive & Storage
Affiliates
Who keeps email working when the only administrator is away?
Keep email manageable when the only administrator is away. Assign backup contacts and compare hosting, recovery and sending responsibilities.
·
Alexey Bulygin
Let a client add their next employee without your login
Let a client manage their own domain without your agency login. Check roles, add an employee and agree who handles limits, support and departures.
·
Alexey Bulygin
White label email: what to check before your first client
Prepare email for your first White Label customer with checks for branding, login, recovery and domain access. Agree support, billing and service boundaries.
·
Alexey Bulygin
Three brands in one email account: who should see what?
Manage three brands in one email account with clear mailbox owners and domain access. Check sending routes, responsibilities and shared storage.
·
Alexey Bulygin
A Mailbox Per Device: Email as a Machine Interface
Backup appliances, monitors and controllers all emit alerts by SMTP because that was the integration available when they were designed. This covers why one shared address degrades, what per-device addressing fixes, and when an alias does the job instead.
·
Alexey Bulygin
Forty Domains, One Account, and No Spreadsheet
Nothing breaks at forty domains — per-domain work simply becomes the job, so DNS checking gets skipped and a broken record sits unnoticed for months. This covers what turns collective, the plan limits, and the two cases against consolidating.
·
Alexey Bulygin
Email Ingest Over IMAP: A Mailbox as an Application Input
Suppliers send invoices, machines emit alerts, forms deliver submissions — all to an address nobody reads programmatically. This covers the five decisions that make an ingest script durable, and when a webhook is plainly the better answer.
·
Alexey Bulygin
Mailbox Storage Quotas: Stopping One Archive Starving the Rest
Agency permits a million mailboxes and provides 200 GB, so storage is the real constraint rather than the count. This covers sizing quotas in tiers, what happens at the limit, and the three fixes when the pool is genuinely full.
·
Alexey Bulygin
What to Do With a Mailbox When Someone Leaves
The decision usually gets made in a hurry on somebody last afternoon, which is how history gets lost. This covers the four dispositions, the credential inventory nobody does, and the sequence that avoids both losing mail and leaving access open.
·
Alexey Bulygin
Giving an AI Email Assistant Real Access to Your Mail Estate
Drafting replies is the narrow version. An assistant that speaks MCP reads your actual estate and changes it, which is where the tedious work lives — this covers what it is good at, what it should never be trusted with, and how to scope it.
·
Alexey Bulygin
Running Hundreds of Mailboxes Without a Per-Seat Bill
Hundreds of mailboxes usually means a letting agency, a manufacturer or a membership body, not a large employer. This covers the arithmetic, the storage constraint that replaces the bill, and the three cases where the model does not fit.
·
Alexey Bulygin
A Mailbox Per Project, Not Per Person
Per-seat pricing forces you to organise email by headcount, so history vanishes when staff leave. A mailbox per job, property or client inverts that — this covers the cost arithmetic, why folders don't substitute, and where the pattern fails.
·
Alexey Bulygin