Third-Party Trust Linkages for Email Sender Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mailbox providers lack a means to determine if an email sender has permission from the recipient to send messages and if this permission has been revoked, leading to issues with malware and unsolicited commercial email distribution.

Innovation Solution

A trust-based email system that facilitates verifiable consent-based filtering through the creation, testing, and management of trust linkages between email senders and recipients, using a system that verifies the authenticity of email streams and directs or discards messages based on subscription status.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If mailbox providers perform basic filtering decisions, then email delivery control is improved, but the ability to determine sender permission independently deteriorates

Engineering Contradiction:
Improveemail delivery controlVSAvoidsender permission verification
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a third-party trust documentation system that acts as an intermediary between senders and mailbox providers. This system issues and verifies trust links that document sender permission, allowing mailbox providers to make filtering decisions with reliable permission verification without needing to independently determine consent. The trust documentation serves as the mediator that bridges the gap between delivery control needs and permission verification reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If email distribution is made inexpensive and wide, then email accessibility is improved, but malware and unsolicited commercial email distribution worsens

Engineering Contradiction:
Improveemail distribution efficiencyVSAvoidmalware and spam distribution
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent implements preliminary action by requiring senders to obtain and document trust permission before distributing email. The trust documentation system records sender authorization in advance, creating a verifiable permission trail that mailbox providers can check. This preliminary documentation prevents malware and unsolicited commercial email from being distributed widely, as unauthorized senders cannot obtain the necessary trust links, while still allowing legitimate email distribution to proceed efficiently.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If mailbox providers lack independent permission determination means, then system complexity is reduced, but trust verification capability deteriorates

Engineering Contradiction:
Improvepermission determination systemVSAvoidpermission verification accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent introduces a third-party trust documentation system that acts as an intermediary between senders and mailbox providers. This system issues and verifies trust links that document sender permission, allowing mailbox providers to make filtering decisions with reliable permission verification without needing to independently determine consent. The trust documentation serves as the mediator that bridges the gap between delivery control needs and permission verification reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10897460B2Third-party documented trust linkages for email streams
Publication Date: 2021.01.19 DRAEGEN TIM
  • US10897460B2 patent drawing
  • US10897460B2 patent drawing
  • US10897460B2 patent drawing

AI summary

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.