Shared Mail Transfer Agent Pool for Email Sending
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mass email sending systems face challenges in efficiently managing IP addresses and mail transfer agent instances, leading to over-provisioning of resources, limited email sending capacity, and increased complexity due to the need for large numbers of private IP addresses, which affects scalability and performance.
Innovation Solution
Implementing a shared pool of mail transfer agent instances and proxy virtual machines that serve as egresses for public sending network addresses, allowing MTA instances to dynamically determine the source IP address for each email, thereby reducing the number of required MTA instances and private IP addresses needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If dedicated pools of MTA instances are allocated to each user to handle peak email sending load, then email sending capacity is ensured, but resource over-provisioning occurs and device complexity increases
Solution Approach 1:
The patent merges previously separate dedicated MTA pools into a single shared pool that serves all users. The shared pool dynamically allocates MTA instances based on real-time demand, eliminating the need for each user to have their own dedicated pool. This consolidation reduces resource over-provisioning while maintaining email sending capacity through dynamic load balancing and on-demand instance allocation.
Solution Approach 2:
The shared MTA pool is designed to serve multiple users simultaneously with different email sending requirements. The system provides universal service by dynamically assigning MTA instances to any user who needs them, rather than dedicating specific instances to specific users. This multi-functional approach allows the same pool of resources to handle varying workloads from different users efficiently.
2Productivity
If the number of MTA instances is increased to handle peak concurrent loads, then email sending performance is improved, but resource utilization efficiency decreases
Solution Approach 1:
The system implements dynamic MTA instance allocation where the number of active MTA instances adjusts automatically based on real-time email sending demand. During peak loads, more instances are activated to maintain performance; during low-utilization periods, instances are deactivated or reassigned. This dynamic approach ensures high performance when needed while optimizing resource utilization efficiency by eliminating idle capacity.
Solution Approach 2:
The shared MTA pool maintains continuous readiness to handle email sending requests from any user. Instead of having static dedicated pools that may sit idle, the system ensures continuous useful action by dynamically allocating instances to users who actively need them. This eliminates periods of non-useful action (idle resources) while maintaining the capability to handle peak loads continuously.
3Ease of operation
If each MTA instance has as many private IP addresses as there are public sending IP addresses, then network address translation is enabled, but the number of private IP addresses becomes very large exceeding network switch capacity
Solution Approach 1:
The patent extracts the private IP address management from individual MTA instances and consolidates it at the shared pool level. Instead of each MTA instance having its own set of private IP addresses mapped to public sending IP addresses, the system maintains a centralized mapping in the shared pool. This extraction dramatically reduces the total number of private IP addresses needed while preserving network address translation capability through the centralized mapping mechanism.
Solution Approach 2:
The shared MTA pool acts as an intermediary between internal private IP addresses and external public sending IP addresses. The pool maintains the mapping between private and public addresses and handles the network address translation centrally. This intermediary approach eliminates the need for each MTA instance to have direct private IP address mappings, reducing the overall number of private IP addresses required while maintaining full NAT functionality.
Data Source
AI summary
A method by an email sending system to send emails from different public sending network addresses. The method includes receiving, by a load balancer, an email that is to be sent by the email sending system, sending, by the load balancer, the email to a mail transfer agent (MTA) instance from a plurality of MTA instances, wherein each of the MTA instances has access to configuration data that indicates which proxy virtual machines (VMs) serve as egresses for which public sending network addresses, determining, by the MTA instance, a public sending network address to send the email from, determining, by the MTA instance based on consulting the configuration data, a proxy VM that serves as an egress for the public sending network address, and sending, by the MTA instance, the email to the proxy VM for sending to its destination from the public sending network address.