Domain Email Forwarding
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only guide, but it describes changing domain mail routing that can receive password-reset emails and potentially all mail for a domain.
Before installing or using this skill, make sure you own the domain, forward mail only to an inbox you control, review existing MX records, test forwarding before relying on it, and remove or narrow forwarding after account recovery if it was only temporary.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken DNS or forwarding change could prevent mail from reaching the intended mailbox or route messages to the wrong destination.
The skill instructs the user to modify DNS/email-routing records, which is expected for domain forwarding but can redirect or break domain email if applied to the wrong domain or with conflicting records.
Add MX records at your registrar's DNS settings
Only make these changes for domains you own, review existing MX records first, verify the destination address, and keep a note of the original settings so they can be restored.
Whoever controls the forwarding destination may receive password resets or verification codes for accounts tied to that domain address.
The skill is explicitly about routing sensitive account-recovery messages. This is purpose-aligned, but those messages can grant access to third-party accounts.
receive verification codes, password resets, and other emails
Forward only to an inbox you control and secure with strong authentication; remove or narrow forwarding after recovery if it is no longer needed.
All mail for the domain, including unexpected or sensitive messages, may arrive in the chosen destination inbox.
Catch-all forwarding intentionally broadens delivery from one address to every address at the domain, which can amplify the impact of a misconfiguration.
Enable "Catch-all" to forward ALL addresses at the domain to one inbox
Prefer a single-address rule when possible; use catch-all only temporarily or when you truly need all domain mail routed to one mailbox.