Loop Token Email Loop Detection System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to effectively detect and prevent email loops, which can lead to unnecessary message generation and potential denial of service attacks, especially in high-volume email services like Salesforce.com, where auto-replies and out-of-office rules can create loops that degrade message serving services.

Innovation Solution

A method and apparatus for identifying message loops using a 'Loop Token' that tracks sender information and reply patterns across messages, allowing for the detection and interruption of loops by discarding inappropriate messages and blacklisting looping users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system sends outbound email notifications for every event, then complete information delivery is achieved, but email loops are generated causing service degradation

Engineering Contradiction:
Improveservice stabilityVSAvoidemail loops
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The system performs preliminary actions by adding loop tokens to outbound emails before they are sent, and by proactively detecting reply patterns that indicate potential loops. This allows the system to prevent loop formation before it causes service degradation, rather than reacting after loops have already formed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by monitoring inbound replies against stored loop token patterns, automatically identifying when replies form circular patterns. This feedback loop allows the system to detect and block problematic email sequences while maintaining legitimate communication, thus preserving service stability without generating harmful loops.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If auto-reply rules are enabled for all users, then individual user responsiveness is improved, but system-wide email loops increase

Engineering Contradiction:
Improveuser responsivenessVSAvoidmessage serving efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system applies local quality by enabling auto-reply functionality for individual users while simultaneously applying loop detection and blocking rules at the system level. This allows each user to maintain their auto-reply settings for personal responsiveness while the system collectively prevents loop formation through localized intervention on problematic messages.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The loop detection system acts as an intermediary between user auto-reply rules and the message serving infrastructure. It monitors and filters replies to prevent loop formation while allowing legitimate auto-replies to pass through, thus mediating between individual user needs for responsiveness and system-wide productivity requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of energy

If loop detection is implemented, then unnecessary messages are reduced, but system complexity increases

Engineering Contradiction:
Improveunnecessary message processingVSAvoiddetection system complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The system uses copying by creating simplified loop token representations of email threads and storing them for comparison. Instead of implementing complex real-time analysis of entire email histories, the system copies essential identifying information into tokens that can be quickly matched against incoming replies, reducing the computational complexity of loop detection while maintaining effectiveness.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system applies parameter changes by transforming complex email thread data into simplified loop token parameters that capture essential identifying information. This parameter transformation allows the system to detect loops by comparing simplified tokens rather than analyzing entire message histories, thereby reducing the complexity of the detection mechanism while still preventing unnecessary message processing.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9628412B2System and method for generic loop detection
Publication Date: 2017.04.18 SALESFORCE INC
  • US9628412B2 patent drawing
  • US9628412B2 patent drawing
  • US9628412B2 patent drawing

AI summary

A system and method for detecting generic loops is described. In one example, an inbound email is inspected for a loop token. If a loop token is found, then an event identification and a sender identification is extracted. The extracted sender identification and event identification is applied to a loop token record, and the inbound email is conditionally discarded based on the application to the loop token record.