THIRD-PARTY DOCUMENTED TRUST LINKAGES FOR EMAIL STREAMS

• US 20160142390A1
• Filed: 10/12/2015
• Published: 05/19/2016
• Est. Priority Date: 10/10/2014
• Status: Active Grant

• Current Assignee: Greg Kraios, Tim Draegen
• Original Assignee: Greg Kraios, Tim Draegen
• Inventors: Draegen, Tim, Kraios, Greg
• Granted Patent: US 10,897,460 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for establishing third-party documented trust linkages. In one aspect, a method includes receiving linkage context data from a sending user, creating a linkage context based on the linkage context data, sending the linkage context to the sending user, receiving linkage initiation data from the sending user, sending linkage initiation email based on the linkage initiation data to a recipient user, receiving confirmation opt-in data from the recipient user; and creating a trust linkage between the sending user and the recipient user, where the trust linkage allows the sending user to successfully send at least one future message stream and where the trust linkage allows the recipient user to successfully receive the at least one future message stream. Further aspects include testing trust linkages for processing message streams and destroying trust linkages to stop message streams.

Claims

1. A method for establishing a third-party documented trust linkage over a computer network, comprising the steps of:

receiving linkage context data from a sending user;

creating a linkage context based on the linkage context data;

sending the linkage context to the sending user;

receiving linkage initiation data from the sending user;

sending linkage initiation email based on the linkage initiation data to a recipient user;

receiving confirmation opt-in data from the recipient user; and

creating a trust linkage between the sending user and the recipient user,

wherein the trust linkage allows the sending user to successfully send at least one future message stream; and

wherein the trust linkage allows the recipient user to successfully receive the at least one future message stream.

2. The method of claim 1, further comprising the steps of:

receiving an email identifier from a mailbox provider;

testing the email identifier to the trust linkage;

calculating a verdict based on the testing step; and

sending the verdict to the mailbox provider;

wherein the verdict determines how the mailbox provider will process the at least one future message stream.

3. The method of claim 1, wherein:

the sending user comprises a plurality of sending users;

the recipient user comprises a plurality of recipient users; and

the trust linkage comprises a plurality of trust linkages.

4. The method of claim 2, wherein:

the email identifier comprises a plurality of email identifiers; and

the verdict comprises a plurality of verdicts.

5. The method of claim 2, wherein the verdict is considered subscribed wherein the email identifier is associated with the recipient user and wherein the recipient user has an existing trust linkage associated with the email identifier.

6. The method of claim 1, further comprising the step of:

creating a tokenized linkage context.

7. The method of claim 1, further comprising the step of:

creating a tokenized trust linkage.

8. The method of claim 1, further comprising the steps of:

receiving a request to destroy a trust linkage; and

destroying the trust linkage.

9. A system for establishing a third-party documented trust linkage system over a computer network configured to overate over a network using a server, a recipient user, and a sending user, comprising:

a server operating the third-party documented trust linkage system, the server adapted to communicate with a network;

wherein the server is configured to;

receive linkage context data from the sending user;

create a linkage context associated with the linkage context data;

send the linkage context to the sending user;

receive linkage initiation data from the sending user;

send linkage initiation email associated with the linkage initiation data to the recipient user;

receive confirmation opt-in data from the recipient user; and

create a trust linkage between the sending user and the recipient user,

wherein the trust linkage allows the sending user to successfully send at least one future message stream; and

wherein the trust linkage allows the recipient user to successfully receive the at least one future message stream.

10. The system of claim 9, wherein the server is further configured to:

receive an email identifier from a mailbox provider;

test the email identifier to the trust linkage;

calculate a verdict based on the testing step; and

send the verdict to the mailbox provider;

wherein the verdict determines how the mailbox provider will process the at least one future message stream.

11. The system of claim 9, wherein:

the sending user comprises a plurality of sending users;

the recipient user comprises a plurality of recipient users; and

the trust linkage comprises a plurality of trust linkages.

12. The system of claim 10, wherein:

the email identifier comprises a plurality of email identifiers; and

the verdict comprises a plurality of verdicts.

13. The system of claim 10, wherein the verdict is considered subscribed wherein the email identifier is associated with the recipient user and wherein the recipient user has an existing trust linkage associated with the email identifier.

14. The system of claim 10, wherein the server is further configured to:

provide a user interface to manage the trust linkage.

15. The system of claim 9, wherein the server is further configured to:

create a tokenized linkage context.

16. The system of claim 9, wherein the server is further configured to:

create a tokenized trust linkage.

17. The method of claim 9, wherein the server is further configured to:

receive a request to destroy a trust linkage; and

destroy the trust linkage.

18. A nontransitory, computer-readable medium having instructions stored thereon, which when executed by one or more computers, causes the one or more computers to:

receive linkage context data from a sending user;

create a linkage context based on the linkage context data;

send the linkage context to the sending user;

receive linkage initiation data from the sending user;

send linkage initiation email based on the linkage initiation data to a recipient user;

receive confirmation opt-in data from the recipient user; and

create a trust linkage between the sending user and the recipient user, wherein the trust linkage allows the sending user to successfully send at least one future message stream; and

wherein the trust linkage allows the recipient user to successfully receive the at least one future message stream.

19. The nontransitory, computer-readable medium of claim 18, wherein when executed by one or more computers, further causes the one or more computers to:

receive an email identifier from a mailbox provider;

test the email identifier to the trust linkage;

calculate a verdict based on the testing step; and

send the verdict to the mailbox provider;

wherein the verdict determines how the mailbox provider will process the at least one future message stream.