Patent application number | Description | Published |
20090006564 | HIGH AVAILABILITY TRANSPORT - A system provides high availability electronic message forwarding. When an electronic message is communicated to a first server, a copy of the electronic message is maintained at a second server. The electronic message is maintained on both servers until the electronic message is successfully communicated to a third server. After the message is delivered to the third server, the electronic message is removed from both the first server and the second server. If the first server fails to communicate the electronic message to the third server, the second server does so. | 01-01-2009 |
20100185735 | EXTENSIBILITY FOR HOSTED MESSAGING SERVERS - Architecture for messaging server extensibility without the need to update or make changes to the messaging server by routing selected messages to a remote location for processing by custom code or third-party code. The messaging server routes the selected messages based server analysis of the messages and in view of configuration data (or conditions) for routing messages. The remote location processes the message and can instruct the messaging server to accept, reject, or redirect the message. Additionally, the remote location can modify the message and instruct the messaging server to process the modified message. The hosted organization can configure triggers to have the messaging server call to a web service with the messages, which extends the functionality of the messaging server. | 07-22-2010 |
20100306323 | DETAILED END-TO-END LATENCY TRACKING OF MESSAGES - Latency information is collected for each message as it moves through an organization. The latency information includes latency information for components processing the message. When the message is routed to the next server within the organization, the collected latency information for the server sending the message is included with the message. The collected latency information is written to a message tracking log when it either is delivered within the organization or when the message leaves the organization. The message tracking log may then be viewed such that the collected latency information may be viewed and analyzed. | 12-02-2010 |
20100318613 | SOCIAL GRAPHING FOR DATA HANDLING AND DELIVERY - Architecture that enables data handling according to types of social relationships. A social graph is used to categorize the types of the social relationships of the tagged messaging users. The social graph can include social relationship categories for friends, family, coworkers, and blocked individuals of the recipient, for example. The social graph can also include metadata related to the tagged users. The metadata defines the social relationship of the tagged users to the recipient. Delivery of messages to the recipient from the tagged messaging users is managed based on the social graph. Delivery management can include blocking messages, allowing the messages through, or delivering the messages with high or low priority, for example. Email messages can be delivered to respective email locations based on the social graph. User information can be imported and/or mined from external sources to augment the social graph. | 12-16-2010 |
20100325215 | MESSAGE REQUIREMENTS BASED ROUTING OF MESSAGES - Architecture for enabling messages to be routed between network servers based on message requirements related to version, capabilities, and features, for example. The message requirements designate delivery over a transport path compatible with the message requirements. The message requirements can include a particular version or other features related to different software applications that require compatibility in message handling. Routing information is maintained related to a transport server or other network transport entity compatible with the message requirements and through which the message can be routed. The message is routed to the compatible transport server for delivery to the destination while avoiding delivery to transport servers incompatible with the message requirements. | 12-23-2010 |
20110289581 | TRUSTED E-MAIL COMMUNICATION IN A MULTI-TENANT ENVIRONMENT - Trusted e-mail communication may be provided. A message source organization may be validated. When a message is received from the validated message source organization for a recipient organization, a determination may be made as to whether the recipient organization supports an attribution data extension. If so, the message may be transmitted to the recipient organization with an attribution element associated with the message source organization. | 11-24-2011 |
20120150964 | Using E-Mail Message Characteristics for Prioritization - Message prioritization may be provided. First, a message may be received and a priority level may be calculated for the message. If the message is not rejected for having a priority lower than a predetermined threshold, the message may be placed in a first priority queue. Next, the message may be de-queued from the first priority queue based upon the calculated priority level for the message. Distribution group recipients corresponding to the message may then be expanded and the priority level for the message may be re-calculated based upon the expanded distribution group recipients. Next, the message may be placed in a second priority queue. The message may then be de-queued from the second priority queue based upon the re-calculated priority level for the message and delivered. | 06-14-2012 |
20120159514 | CONDITIONAL DEFERRED QUEUING - Conditional deferred queuing may be provided. Upon receiving a message, one or more throttle conditions associated with the message may be identified. A lock associated with the throttle condition may be created on the message until the throttle condition is satisfied. Then, the lock on the message may be removed and the message may be delivered. | 06-21-2012 |
20130238715 | ENABLING COMMUNICATION BETWEEN SOURCE AND TARGET MAIL TRANSFER AGENTS - A system is provided for enabling a source MTA to communicate with a target MTA via an SMTP proxy using SMTP commands for transmitting email messages in a networked environment. An email message may be received by a source mail transport agent (MTA) and the source MTA may route the incoming email message to a target MTA via an SMTP proxy. The SMTP proxy may serve as an intermediary proxy server for enabling the source MTA to communicate with an external and internal target MTA. The SMTP proxy may connect to a target MTA via a connection command, and the SMTP proxy may implement custom SMTP commands to communicate additional information about the source MTA to the target MTA. The system may additionally enable the SMTP proxy to perform actions designated by the SMTP commands and to communicate the result of the SMTP proxy's actions back to the source MTA. | 09-12-2013 |
20130238718 | STORING AND PARTITIONING EMAIL MESSAGING DATA - A system is provided for storing messaging data at a mail transport agent in a network environment. An email message may be transmitted over a network from a sender client to a recipient server through a plurality of mail transport agents (MTA). An MTA may receive an email message and may store messaging data for the email message in a data store associated with the MTA. The MTA may partition the messaging data into generations representing a defined time frame for the date and time that an email message was received. The MTA may enable a search operation to be performed on the stored generations for retrieving and replaying messaging data to a downstream recipient server. The MTA may continually clean the data store by deleting from the data store a generation of data that has expired and outlived the predefined hold period. | 09-12-2013 |
20130238719 | OPTIMIZED ROUTING FOR PROXY USE - A system is provided for applying optimized selection to route an email message over a network to a recipient mailbox. An email message may be enabled to be transmitted through a plurality of servers to a destination recipient mailbox server. An external message transfer agent may receive the email message using Simple Mail Transfer Protocol (SMTP) and may transmit the received email message to a proxy transport server. The proxy transport server may apply a selection for an optimal store-and-forward (SAF) transport server to which to route the email message. The selection may provide for identifying available SAF transport servers, organizing the SAF transport servers into server groups, and selecting the optimal SAF transport server belonging to a server group where a recipient mailbox server is located. The proxy transport server may transmit the email message to the SAF transport server for delivering the message to the recipient mailbox. | 09-12-2013 |
20130262589 | COMMUNICATING PER-RECIPIENT DELIVERY STATUSES OF MULTI-RECIPIENT MESSAGES IN MULTILINE SIMPLE MAIL TRANSFER PROTOCOL RESPONSES - A simple mail transfer protocol (“SMTP”) computer fails to deliver a multi-recipient e-mail to another SMTP computer. The SMTP computer generates a multi-line SMTP response including a per-recipient delivery status for each recipient of the multi-recipient e-mail message. The multi-line SMTP response may include a line for each recipient of the e-mail message. The multi-line SMTP response alternatively may include a line only for recipients for which delivery of the e-mail message has failed. | 10-03-2013 |
20130268600 | TRANSFERRING MESSAGE CONTEXT INFORMATION USING EXTENDED SIMPLE MAIL TRANSFER PROTOCOL BINARY DATA CHUNKING - A client computer sends an extended simple mail transfer protocol extended hello command to a server computer. In response, the server computer sends an advertisement to the client computer to identify a capability to receive message context information. The client computer, in turn, analyzes the capability advertisement to determine if it has any blobs associated with the capability identified in the capability advertisement to send. If the client computer has one or more blobs to send, the client computer sends a parameter in a MAIL command to the server computer specifying that the client computer will utilize the capability identified in the capability advertisement and specifying an order in which to expect the blobs if the client computer intends to send more than one blob. The client computer sends the blob(s) to the server computer after receiving an indication that the server computer is ready to receive the blob(s). | 10-10-2013 |
20140372548 | OPTIMIZED ROUTING FOR PROXY USE - A system is provided for applying optimized selection to route an email message over a network to a recipient mailbox. An email message may be enabled to be transmitted through a plurality of servers to a destination recipient mailbox server. An external message transfer agent may receive the email message using Simple Mail Transfer Protocol (SMTP) and may transmit the received email message to a proxy transport server. The proxy transport server may apply a selection for an optimal store-and-forward (SAF) transport server to which to route the email message. The selection may provide for identifying available SAF transport servers, organizing the SAF transport servers into server groups, and selecting the optimal SAF transport server belonging to a server group where a recipient mailbox server is located. The proxy transport server may transmit the email message to the SAF transport server for delivering the message to the recipient mailbox. | 12-18-2014 |
20150067069 | ENFORCING RESOURCE QUOTA IN MAIL TRANSFER AGENT WITHIN MULTI-TENANT ENVIRONMENT - An application such as a mail transfer agent (MTA) enforces a resource quota within a multi-tenant environment. An email associated with a tenant is managed based on decisions evaluating the email against a queue quota and an association between the email and an email storm. The email is also managed based on another decision evaluating the email against a processing quota. In addition, the email is managed based on a cross MTA aggregate of usage information associated with the first, second, and third decisions. | 03-05-2015 |