Automated Blocked-Originator List Management for Messaging Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing email systems face inefficiencies when their blocked-address lists become full, requiring users to manually delete entries to make room for new blocks, which can lead to the delivery of malicious emails.
Innovation Solution
A list management module automatically detects when the blocked-originator list is full and uses entry removal rules to delete the least relevant entries, allowing new entries to be added without user intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a blocked-address list is used to prevent malicious emails, then security against spam and phishing is improved, but the list size is limited and requires manual management when full
Solution Approach 1:
The system automatically manages the blocked-address list by detecting when it is full, identifying entries to remove based on activity criteria, and executing removals without user intervention. This self-service mechanism eliminates manual list management while maintaining security effectiveness.
Solution Approach 2:
The system dynamically adjusts the composition of the blocked-address list by changing which entries are present based on activity criteria such as message frequency and recency. This allows the list to adapt to changing threat patterns while maintaining optimal size.
2Reliability
If the blocked-address list is made larger to block more malicious emails, then security coverage is improved, but the system complexity and management burden increase
Solution Approach 1:
The patent replaces manual mechanical list management with an automated computer-implemented system that uses algorithms to monitor list size, evaluate entry criteria, and perform removals. This substitution reduces system complexity by automating what would otherwise require complex user intervention protocols.
3Ease of operation
If manual scanning and deletion of blocked addresses is required, then user control over the list is maintained, but user time is wasted and effectiveness may be compromised
Solution Approach 1:
The system performs self-service by automatically monitoring its own state, evaluating entries against predefined criteria, and executing removals without requiring user time or intervention. This eliminates the time loss associated with manual list management while preserving the effectiveness of blocked address management.
Solution Approach 2:
The system continuously monitors the blocked-address list state and message traffic patterns, using this feedback to automatically determine when removals are needed and which entries to remove. This feedback loop replaces manual user assessment with automated decision-making.
4Device complexity
If the blocked-address list is kept static to simplify management, then system simplicity is maintained, but adaptability to new threats is reduced
Solution Approach 1:
The system transitions from a static blocked-address list to a dynamic one that automatically adjusts its composition based on real-time message traffic analysis. Entries are automatically removed when they meet inactivity criteria, allowing the list to adapt to changing threat patterns without manual intervention or increased complexity.
Data Source
AI summary
Managing a blocked-originator list for a messaging application, including: detecting, by a list management module, a list management initiation event for a blocked-originator list, the blocked-originator list including a plurality of originators from which incoming messages are blocked; determining a number of entries in a blocked-originator list; determining a maximum number of entries in the blocked-originator list; determining whether the number of entries in the blocked-originator list is equal to the maximum number of entries in the blocked-originator list; and responsive to determining that the number of entries in the blocked-originator list is equal to the maximum number of entries in the blocked-originator list: deleting an entry from the blocked-originator list in dependence upon entry removal rules; and adding the new entry to the blocked-originator list.