# US 2019/0379660 A1 · Domain-based Isolated Mailboxes

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0379660 A1
- Document ID: US20190379660A1
- Status: Published application
- Kind: A1
- Application number: 16/544,941
- Filed: 2019-08-20
- Published: 2019-12-12
- Earliest claimed: 2018-08-21
- Inventors: VIRUTHAGIRI THIRUMAVALAVAN
- Web page: https://patentgrep.com/patent/US20190379660A1

## CPC

- H04L 63/0869: {for achieving mutual authentication (cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273)}
- H04W 12/084: using delegated authorisation, e.g. open authorisation [OAuth] protocol
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- H04L 51/046: Interoperability with other network applications or services
- H04L 51/212: using filtering or selective blocking
- H04L 51/42: Mailbox-related aspects, e.g. synchronisation of mailboxes
- H04L 51/48: Message addressing, e.g. address format or anonymous messages, aliases
- H04L 63/0414: {during transmission, i.e. party's identity is protected against eavesdropping, e.g. by using temporary identifiers, but is known to the other party or parties involved in the communication}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/126: {the source of the received data}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods are provided for reducing email spam without wasting network bandwidth. The system contains two groups of boxes. Domboxes and Mailboxes. (a) Domboxes should be used only for non-conversational mails. E.g. website/app mails. Each Dombox has a disposable email address and associated with a primary domain. The primary domain can authorize additional domains in the DNS. We primarily rely on the SPF record for validating Dombox mails. (b) Mailboxes are designed to accept only conversational mails. Conversational Mails can be termed as Human-to-Human, Mailbox-to-Mailbox or MX-to-MX mails. We pull the MX record from the Envelope Domain and verify whether it's really originating from one of the MX servers. Spammer is a Human. Since we accept only MX record verified mails, spammers need registered domains to send spam. Additional checks can be performed with the help of Domain registration date, Spam Filters, Challenge/Response etc.

## Claims

### Claim 1

A method for providing isolated mail address via authentication, the method comprising:
under control of a system of an identity provider,
registering an auth-client application for a service by a service administrator of the service;
under control of a system of the service,
displaying an auth-button of the identity provider for the auth-client application on the service;
under control of a server of the identity provider,
receiving a request from the service to authorize a release of protected data of a user who has requested access to the service, the request initiated by the user by clicking the auth-button;
responsive to receiving the request, authenticating the user;
responsive to authenticating the user, receiving a permission from the user, the permission authorizing the release of protected data of the user;
responsive to authorizing the release, creating an email address;
associating the email address with the user;
associating the email address with at least one of:
the service;
a primary domain of the service; or
the auth-client application;
releasing the protected data of the user to the service, wherein the released data comprises the email address; and
under control of a mail handling server,
receiving an electronic mail from an external source to the email address; and
validating the electronic mail by performing one or more checks using information extracted from the electronic mail to determine whether or not the electronic mail is allowed for the email address;
wherein the information extracted from at least one of:
envelope part of the electronic mail; or p2 message part of the electronic mail;
wherein the validating step comprises loading a configuration for the email address using an information associated with the email address;
wherein the configuration comprises one or more domains authorized by an entity of the service to send one or more electronic mail to the email address;
wherein the entity is a human.

### Claim 2 (depends on 1)

The method of claim 1, wherein performing one or more checks comprises:
extracting an envelope domain from the electronic mail; and
comparing at least a part of the envelope domain with the primary domain.

### Claim 3 (depends on 1)

The method of claim 1, wherein performing one or more checks comprises:
extracting an envelope domain from the electronic mail; and
comparing at least a part of the envelope domain with said one or more domains.

### Claim 4 (depends on 1)

The method of claim 1, wherein the validating step requires at least one of the following to allow the electronic mail:
at least a part of an envelope domain of the electronic mail to match the primary domain; or
at least a part of an envelope domain of the electronic mail to match at least one of the envelope domains.

### Claim 5 (depends on 1)

The method of claim 1, wherein the validating step requires mandatory pass for Sender Policy Framework (SPF) to allow the electronic mail.

### Claim 6 (depends on 1)

The method of claim 1, wherein the validating step requires mandatory pass for Sender Alias Domains (SAD) to allow the electronic mail.

### Claim 7 (depends on 1)

The method of claim 1, wherein the identity provider forces said one or more domains to configure SPF record.

### Claim 8 (depends on 1)

The method of claim 1, wherein the system of the identity provider performs an SPF record DNS lookup on a domain provided by the service administrator to check whether or not the domain is compatible with mandatory pass requirement.

### Claim 9 (depends on 8)

The method of claim 8, wherein the SPF record DNS lookup performed after receiving an electronic mail from the domain to a randomly generated email address.

### Claim 10 (depends on 1)

The method of claim 1, wherein the email address can be deleted by the user.

### Claim 11 (depends on 1)

The method of claim 1, wherein the email address can be made inactive by the user without deleting the email address.

### Claim 12 (depends on 1)

The method of claim 1, wherein the email address is associated with a plurality of auth-client applications.

### Claim 13 (depends on 1)

The method of claim 1, wherein the email address accepts one or more email s from a plurality of domains, at least one domain of the plurality of domains is verified by the service administrator.

### Claim 14 (depends on 1)

The method of claim 1, wherein the primary domain requires domain verification.

### Claim 15 (depends on 1)

The method of claim 1, wherein the auth-client application is associated with the primary domain.

### Claim 16 (depends on 1)

The method of claim 1, wherein the released data is a minimal insensitive data.

### Claim 17 (depends on 1)

The method of claim 1, wherein the auth-button is displayed adjacent to a button that groups all other authentication methods.

### Claim 18 (depends on 1)

The method of claim 1, wherein the auth-button is displayed in a first position.

### Claim 19 (depends on 1)

The method of claim 1, wherein the displaying of the auth-button on the service is mandatory when at least one third-party identity provider auth-button is displayed on the service.

### Claim 20 (depends on 1)

The method of claim 1, wherein said one or more domains comprises at least one domain not owned by the service.
