| Patent application number | Description | Published |
|---|
| 20090006531 | CLIENT REQUEST BASED LOAD BALANCING - A method for balancing load in a network system, having a plurality of clients initiating transactions with a plurality of servers. For each transaction a host name associated with one or more servers capable of completing the transaction is specified. The client initiates a request to resolve the host name and a plurality of IP addresses are returned. The client randomly communicates with one of the IPs identified as capable of completing the transaction and reports on the success of the transaction. If multiple attempts to the same IP fail, the IP is removed from service by the client. | 01-01-2009 |
| 20100174788 | HONORING USER PREFERENCES IN EMAIL SYSTEMS - In a distributed email system, user preferences respected more effectively by presenting messages marked for deletion to secondary messaging servers having access to user preferences. Messages marked for deletion by inbound servers are presented to secondary level servers having access to user white lists and the choice of whether to delete the suspect message is made by the secondary server. | 07-08-2010 |
| 20100175103 | REACTIVE THROTTLING OF INBOUND MESSAGES AND RANGES - A method for throttling inbound email messages in an enterprise email system including a plurality of inbound mail servers and at least one management server is provided. Policies defining message event limits for each unique sender are applied to messaging events from the unique sender at each inbound server. Feedback from each of the inbound mail servers to the management server is provided. When events from a unique sender exceed a threshold, as determined by the management server using the feedback, an alert is generated and a new, more restrictive policy for the unique sender is created. The more restrictive policy is broadcast the more restrictive policy to each of the inbound mail servers. | 07-08-2010 |
| 20100205259 | EMAIL MANAGEMENT BASED ON USER BEHAVIOR - Methods for assisting email users manage email messages received in an email account. An event is triggered by an action performed by an email user with respect to an email message in an email account. The event identifies an entity associated with the email message (e.g., sender address, domain, keyword, etc.). A determination is made whether to assist the user manage their email based on a heuristic. The heuristic assigns weights based on prior events associated with the same entity to determine whether the user is interested in receiving emails from the sender. Based on the heuristics, the method may add the sender to the user's block-list or unsubscribe the user from a mailing list. | 08-12-2010 |
| 20100251362 | DYNAMIC SPAM VIEW SETTINGS - A method of displaying email messages to a user is provided. Spam classification information and meta data is associated with email messages received for a user. Email message summary information is displayed in a user interface based on whether the meta data associated with the message meets or exceeds a threshold display level for the summary information. The user provides input via the user interface which is an indication to change the threshold display level and the change is dynamically displayed. | 09-30-2010 |
| 20100332601 | REAL-TIME SPAM LOOK-UP SYSTEM - A system and method of managing unsolicited email sent to an email system over a network. Email messages are received at an message at an inbound mail transfer agent. A determination is made as to whether the email message is suspected to be an unsolicited suspect message. One or more queries for additional information on one or more characteristics of the message is initiated. Determinations are made based on replies to the queries before issuing a message accepted for delivery indication to a sending server. | 12-30-2010 |
| 20110138062 | RECIPROCAL PUBLIC TRUST RELATIONSHIP - Publicly accessible linking information is to establish a trusted relationship between reciprocally linked entities controlling web resources, such as websites or web logs. A method of establishing a trust relationship between two entities identifying a user-installed link to a second web resource in a first web resource. Next, the method determines when a reciprocal link is made in the second web resource directed to the first web resource and creates a trust relationship between the entities based on the reciprocal link. | 06-09-2011 |
| 20110191832 | RESCUING TRUSTED NODES FROM FILTERING OF UNTRUSTED NETWORK ENTITIES - Network entities controlling a set of nodes may vary by trustworthiness, such as tolerance for nodes that send spam, distribute malware, or perform denial-of-service attacks. A device receiving such activities may identify a trust rating of the network entity and apply appropriately stringent filtering (such as spam evaluation) to activities received from nodes controlled by the network entity. However, a poor trust rating of a network entity may subject a legitimate node controlled by the network entity to inefficiently or unfairly stringent activity filtering. Instead, the device may evaluate the activities of a particular node, assign a trust rating to the node, and if the trust rating of the node is higher than the trust rating of the network entity, apply less stringent activity filtering to the activities of the node, thereby “rescuing” the node from the more stringent activity filtering applied to the other nodes of the network entity. | 08-04-2011 |
| 20110191847 | ACTIVITY FILTERING BASED ON TRUST RATINGS OF NETWORK ENTITIES - The filtering of activities generated by nodes of a network while interacting with a device may be performed by evaluating the desirability of the activities (e.g., a spam or not-spam determination of email messages sent by the node) and assigning a trust rating to the node. However, nodes are often identified by network address, and an operator of a node sending undesirable activities may reassign the network address of the node in order to avoid heavy filtering. Instead, nodes may be identified as being controlled by a network entity (e.g., an autonomous system identified in a border gateway protocol routing table.) The network entity is assigned a network entity trust rating based on the trust ratings of the nodes controlled thereby, and an appropriate level of activity filtering based on the network entity trust rating may be selected for subsequent activities received from all nodes controlled by the network entity. | 08-04-2011 |
