Abstract
Beyond Apple's Hide My Email: Recipient-Controlled Delivery Authority for Gmail, iCloud Mail and Outlook
Abstract
A person gives an email address to a hotel, insurance, education or quotation form. The original business may keep it, and a lead-generation intermediary, affiliate or data broker may also acquire it. Several marketers can then email that address, sometimes from properly authenticated domains. This is a documented possible route to unwanted email, not a certain result of every lead form. Mail providers such as Gmail, iCloud Mail and Outlook assess sender authentication (SPF, DKIM, DMARC), content, reputation, complaints and recipient rules. Aliases such as Apple Hide My Email hide the permanent address and can be deactivated. None of these, by itself, lets the recipient define which sender may reach them, for what purpose, and with what delivery effect.
This disclosure analyses that gap and proposes pre-inbox enforcement. A governed delivery effect (inbox placement, forwarding, notification or priority treatment) stays non-effective until protected recipient-side authority verifies the sender, recipient, purpose, channel, freshness, nonce, quota and revocation status. Only then does it release a bounded, single-use communication capability. The email address or alias becomes a locator, not proof of authority to deliver. A transactional relationship (“send my receipt”) is kept separate from a marketing relationship (“send offers indefinitely”). Non-matching mail is rejected, deferred, quarantined or downgraded by policy. The same control applies to AI-agent outreach, where autonomous senders can contact many recipients at machine speed.
The analysis separates ordinary Apple iCloud+ Hide My Email aliases from Sign in with Apple private email relay, which already restricts registered sending domains. It also recognises Gmail’s and Outlook’s existing pre-inbox spam controls. The proposal is complementary to them. It needs trusted purpose evidence, careful handling of unknown legitimate senders, protection of every actual delivery path (SMTP/MTA, alias resolver, mailbox gateway, forwarding, notification), and measured latency and false-positive rates. It is a prospective engineering analysis. It does not claim deployment by Google, Apple or Microsoft, or demonstrated spam elimination.
Based on PCT/IB2026/056353, “Non-Bearer Capability-Validated Architecture for Pre-Effect Authorization of Communication, Payment Settlement, Data Export, and AI-Native Machine Operations”. The filing names SMTP and mailbox gateways, and recipient- and purpose-bound communication authority. To read the full PCT filing, search “Sangam Das” on WIPO PATENTSCOPE, or search PCT/IB2026/056353 (pctib2026056353).
Any mapping to named companies or products is AI-generated. Readers must cross-check it against the original PCT filing before drawing any conclusion. It is not an endorsement, validation or infringement statement.
License: CC BY-NC 4.0.
Keywords (26)
Gmail spam prevention; Apple Hide My Email; iCloud Mail; Outlook; email spam; unwanted email; lead generation; data brokers; lead-form data resale; email aliases; Sign in with Apple private relay; SMTP gateway; mail transfer agent; pre-inbox enforcement; recipient-authorized delivery; purpose-bound email; consent; SPF DKIM DMARC; sender authentication; anti-replay; non-bearer authority; email finality; marketing abuse; secure email gateway; AI-agent outreach; AI safety
https://zenodo.org/records/24334427
Creative Commons License

This work is licensed under a Creative Commons Attribution-Noncommercial 4.0 License
Recommended Citation
Das, Sangam Kumar, "AI Safety for Email: Stopping Spam and AI-Agent Outreach Before It Reaches Gmail, iCloud Mail and Outlook", Technical Disclosure Commons, (November 20, 2026)
https://www.tdcommons.org/dpubs_series/13171