← MailLogicCONTENT HISTORY
WHAT CHANGED
Update to MailLogic
Snapshot Nov 17, 2026 · 06:14 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save MailLogic and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Set up or resume initial custom-domain email with MailLogic: connect a domain, configure receiving/email forwarding, and optionally enable explicitly requested sending. Use for requests such as \"set up my custom domain email\", \"connect example.com to MailLogic\", \"set up MailLogic for my domain\", or \"set up email forwarding for my domain\". Excludes general troubleshooting, delivery-log analysis, ongoing address or catch-all administration, replies, arbitrary email sending, and billing management.",
"included_files": [],
"name": "setup-custom-domain-email",
"skill_md_contents": "---\nname: setup-custom-domain-email\ndescription: >-\n Set up or resume initial custom-domain email with MailLogic: connect a domain,\n configure receiving/email forwarding, and optionally enable explicitly requested\n sending. Use for requests such as \"set up my custom domain email\", \"connect\n example.com to MailLogic\", \"set up MailLogic for my domain\", or \"set up email\n forwarding for my domain\". Excludes general troubleshooting, delivery-log analysis,\n ongoing address or catch-all administration, replies, arbitrary email sending,\n and billing management.\n---\n\n# Set up custom-domain email\n\nUse existing MailLogic MCP tools to complete only missing setup work. This is a resumable workflow, not a fixed sequence. Preserve tool confirmation requirements, host approvals, backend authorization, and applicable email-testing restrictions. Existing authorization need not be requested again; permission to configure email does not imply permission to send a diagnostic.\n\n## Establish intent and inspect\n\n- Start/resume with `inspect_mail_setup` for the domain established in the conversation. For a fresh request without a domain, ask for the intended domain first: do not silently select the sole visible domain. Reuse an established domain on continuation.\n- Determine the intended address, forwarding destination, and receiving/sending goal from the request and reliable context. Ask only for missing choices, when needed. Do not infer a new destination from another address, catch-all mapping, logs, or account identity. Display name is optional; omit it unless requested.\n- Generic email setup means receiving/forwarding. Paid entitlement alone never implies sending intent. Enter the sending branch only for an explicit or clear sending request; ask once if genuine ambiguity affects the next mutation.\n- Inspection is cached. `complete` describes the inspection, not completed setup. Visible selection confirms existence; `not_visible` does not prove absence. Unknown/null DNS observations are not false, and denied/unavailable sections are not empty. Follow address pagination only as needed; an incomplete page cannot establish that an address is absent.\n- Use returned readiness, account capacity, SMTP entitlement/availability, address state, and DNS requirements. Preserve catch-all state without modifying it. Reinspect only for changed state, uncertainty, or resumption—not after every action.\n\n## Choose the next unmet step\n\n| State | Action |\n|---|---|\n| Domain already visible, including pending/revoked ownership | Reuse; do not recreate. |\n| Requested domain not visible | Explain the visibility limit; use `create_domain` within the authorized setup. Backend restrictions/conflicts remain authoritative; new creation requires unrestricted credentials. |\n| DNS already ready for the requested capability | Skip that DNS work. |\n| DNS unchecked or changed externally | Deliberately use `check_domain_dns` when needed before prescribing redundant changes. It persists observations and can change ownership/routing; it is not read-only. |\n| DNS incomplete | Configure unmet requirements using the automatic or manual route below. |\n| Intended active address already has the intended destination | Reuse it. Preserve existing SMTP state even for a receiving-only request. |\n| No intended address exists and ownership is verified | Use `create_email_account` with the exact address and forwarding destination. New receiving-only addresses use `smtp_enabled=false`. MX propagation need not finish before creation. |\n| Existing destination conflicts, address is inactive, or state cannot be reconciled safely | Report the blocker; do not overwrite, delete/recreate, or change unrelated configuration. |\n| Address capacity exhausted or permission denied | Report the blocker; do not delete resources, upgrade, or bypass restrictions. |\n\n## Complete DNS with a human handoff\n\nUse MailLogic's returned records and readiness rather than reconstructing DNS policy. Receiving needs ownership and MX readiness. Sending additionally needs the returned sending requirements, including valid DMARC. Free/no-entitlement users skip sending-only SPF/DKIM/DMARC work; paid receiving-only users do too. A full DNS mode is not sending intent.\n\nWhen automatic setup is available and authorized, call `begin_automatic_dns_setup` with explicit `forwarding`, `sending`, and `dmarc` booleans matching the proposed work. Verification is always included; forwarding selects MX; sending selects SPF/DKIM together; DMARC requires sending. Skip satisfied groups where possible. Explain any included changes to existing routing. Do not silently omit unmet DMARC from a sending-completion claim.\n\nPresent the returned private authorization URL unchanged. Do not fetch/follow it, automate consent, or share it elsewhere. The human opens, authenticates, and approves it. Preparation/approval does not establish DNS readiness. After the user returns, use `check_domain_dns`; do not automatically generate another authorization URL. There is no consent-session polling API.\n\nIf automatic setup is unavailable/unsupported or manual setup is preferred, present the returned record type, name/host, value, and priority. Preserve SPF `merge` and DMARC `preserve_or_create` semantics; do not blindly replace existing records. Explain MX routing consequences before changes. Unknown provider hints are advisory: a deliberate automatic attempt can validate fresh authority if desired, but do not loop on provider failures or use direct provider APIs. After external edits, deliberately check DNS. Preserve partial progress while propagation continues.\n\n## Optional sending setup\n\nOnly for requested sending: check entitlement and distinguish configuration readiness from current sending availability. If not entitled, explain the limitation and complete authorized receiving work; do not attempt billing/upgrade actions. Suspension, billing operations, or exhausted credits can block sending even when configured. An availability-only blocker need not prevent authorized configuration that the backend permits; never bypass a mutation denial.\n\nFor a new address on an entitled account, `create_email_account` with `smtp_enabled=true` can configure SMTP and issue one private setup email, avoiding a second mutation. For an existing address with SMTP disabled, use `enable_smtp`. If already enabled, reuse it; never call creation with default SMTP false as a way to resume.\n\nHave the user complete the password privately through the emailed setup link. Never request a password or private setup link in chat. Do not automatically call `request_password_setup` after creation/enablement or when submission is uncertain. Use it only for a deliberate replacement request, explaining that previous usable links are replaced and respecting cooldowns. Pending state does not prove email delivery; absence of pending state does not prove password completion.\n\n## Optional forwarding diagnostic\n\nUse `create_forwarding_test` only when the user wants verification/diagnosis, the exact route is authorized under applicable testing restrictions, and the address is eligible. Inspection of a route is not permission to send to it. Do not mine production data for test recipients or use an arbitrary email-send tool.\n\nBefore calling, retain the exact address, locale, and non-secret idempotency key in conversational state; then retain the returned test ID and replay expiry. After uncertainty, inspect setup as needed and deliberately recover with the identical address/locale/key within replay retention—never a fresh key. If the ID is known, use `get_forwarding_test`. Respect `poll_after_ms`, use bounded checks, and return pending rather than polling indefinitely. Lost key/ID is not permission to start another diagnostic.\n\nAcceptance/202 is only durable request acceptance. Queued/submitting/checking are pending. Confirmed means observed destination SMTP acceptance, not inbox placement, lasting forwarding health, or SMTP sending readiness. Preserve failure codes; failed/expired monitoring does not prove nondelivery. A 404 can reflect visibility or retention, not absence.\n\n## Resume and report\n\nKeep a concise conversational checkpoint: domain, intended address/destination, requested capabilities, completed milestones, outstanding human action, and any diagnostic key/ID/expiry. Do not store passwords or private links in a separate state file.\n\nFor unknown mutation outcomes, inspect before a deliberate retry and follow the tool's retry guidance. A matching observation does not attribute the prior write or prove its email was sent. For partial/persisted failures, preserve the resource and synchronization warnings; follow returned recovery actions rather than recreating it. Honor retry timing. Scope/capacity denials are blockers, not invitations to bypass controls. Do not automatically resend uncertain password emails or repeat authorization flows.\n\nReport these milestones separately, only as supported:\n\n- **Domain/ownership:** identity exists; ownership verified or still pending/revoked.\n- **Receiving DNS:** `forwarding_ready=true` at the reported observation time; not guaranteed delivery.\n- **Address configured:** exact intended active address and destination saved; disclose unresolved synchronization issues.\n- **Receiving setup complete:** ownership, receiving DNS, and intended address ready, without known unresolved setup/synchronization blockers. A forwarding test is optional.\n- **Forwarding test:** not requested, pending, confirmed destination SMTP acceptance, or ended without confirmation.\n- **Sending DNS/domain readiness:** `smtp_ready=true`; not password setup or SMTP authentication proof.\n- **Address SMTP:** enabled or still pending configuration.\n- **Private password handoff:** awaiting the human, or completed according to their report; never claim API-verified password completion/authentication.\n- **Current sending availability:** account sending state, including entitlement, suspension, billing, or credit blockers; configuration alone is insufficient.\n\nStop at the next required human action or blocker, with the specific resume step. Do not expand into general troubleshooting, logs, catch-all changes, address administration/deletion, replies, arbitrary sending, or billing management.\n"
}SHA-256 of public snapshot: 7d3d51ae67a51723ec446c38b61c117964b0b75ecc19c0bba369245b041dfb45