Enterprise Email Routing via MX Record Storage Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current email routing systems in administrative domains are resource-intensive due to the need for proprietary internal routing protocols that require additional processing of mail messages, which can be inefficient and costly.
Innovation Solution
A system and method that repurpose standard MX records for internal email routing within an enterprise email system, allowing direct delivery of mail to storage servers by hiding SMTP protocol fields and using MX records to identify storage locations, thereby simplifying and enhancing email routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proprietary internal routing protocols are used to route mail within ESP architecture, then mail routing accuracy is improved, but processing resource consumption increases
Solution Approach 1:
The patent extracts the routing decision logic from complex proprietary protocols and embeds it directly into the MX record data structure itself. The MX record contains embedded routing information that directly specifies the target mail storage location, eliminating the need for separate routing protocol processing steps while maintaining accurate mail delivery.
Solution Approach 2:
The patent makes the MX record serve multiple functions: it continues to provide the standard mail exchange target but additionally embeds routing protocol logic and storage location identification within the same record structure. This multi-functional approach eliminates the need for separate proprietary routing protocols while maintaining routing accuracy.
2Reliability
If additional processing steps are added to ensure accurate mail delivery, then mail routing reliability is improved, but system complexity increases
Solution Approach 1:
The patent merges the routing protocol functionality with the existing MX record structure. Instead of adding separate processing steps, the routing logic is combined into the MX record itself, which contains both the target mail server information and the embedded routing protocol instructions for direct storage location delivery.
Solution Approach 2:
The MX record structure is designed to be self-sufficient, containing all necessary routing information and storage location identification within the record itself. This self-service approach eliminates the need for external proprietary routing protocols or additional processing steps, reducing system complexity while maintaining delivery accuracy.
3Use of energy by moving object
If standard MX records are used for internal routing, then processing resources are reduced, but routing flexibility is limited
Solution Approach 1:
The patent introduces dynamic routing capabilities within the MX record by embedding protocol-specific routing information that can adapt to different storage locations and routing scenarios. This allows the static MX record structure to dynamically handle various routing situations without requiring additional processing resources or complex proprietary protocols.
Solution Approach 2:
The patent utilizes parameter changes within the MX record structure to encode different routing scenarios and storage location identifiers. By varying the parameter values within the MX record, the system achieves routing flexibility for different mail delivery situations while maintaining the simple standard MX record format and avoiding additional processing overhead.
Data Source
AI summary
A system and method for providing email using a flexible routing technique based on MX records. The method includes the steps of creating an MX record for a user, the MX record identifying a storage location for the user within the system; and routing mail within the enterprise email system using the information contained in the MX record. A system may include an inbound mail transfer agent coupled to an external network and an internal network; user email data storage having an address within the internal network; a user location database server containing a unique user token identifying a storage location for user email data in the user email data storage; and an internal DNS server including MX records for storage domains on the internal network.