IP Library Granted Patent US 7,469,292
Granted Patent B2
US 7,469,292 · App. 11/015,066 · Granted Dec 23, 2008

Managing electronic messages using contact information

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,469,292
App. No.
11/015,066
Granted
Dec 23, 2008
Kind
B2
Abstract

A system may include an electronic messaging management application that may access contact information. The contact information may include information maintained by one or more system users. The electronic messaging management application may determine how to process an incoming electronic message using at least a portion of the contact information. The electronic messaging management application may determine whether to send a challenge-response message to a sender of an electronic message using at least a portion of the contact information.

Claims (51)

1. A system for managing the delivery of an electronic message, the system comprising:

a data storage device comprising at least one computer-readable medium;

system contact information stored on the data storage device, the system contact information including user contact information for a plurality of users, the user contact information identifying one or more contacts;

an electronic messaging management module configured to access the system contact information and configured to determine whether a challenge-response process should be initiated at least in part based upon the accessed system contact information;

the electronic messaging management module further configured to perform the following:

determine whether the system contact information includes at least one non-rejected contact for the sender;

determine whether the sender has exceeded an activity limit;

determine whether the system contact information includes a minimum number of contacts for the sender; and

determine whether the number of rejected contacts in the system contact information exceeds a threshold; and

the electronic messaging management module further configured to deliver the electronic message to an inbox of a recipient specified in the electronic message if;

the sender is included in at least one non-rejected contact for the system contact information;

the sender has not exceeded an activity limit;

the system contact information includes a minimum number of contacts for the sender; and

the number of rejected contacts in the system contact information does not exceed a threshold.

2. The system of claim 1 , wherein the user contact information for the plurality of users comprises one or more contact data structures embodied on a computer-readable medium and wherein the electronic messaging management module is further configured to determine an amount of information for the sender of the electronic message that is stored in the contact data structures.

3. The system of claim 1 , wherein the electronic messaging management module is further configured to

determine whether the system contact information includes at least one rejected contact for the sender

4. The system of claim 1 , wherein the user contact information for the plurality of users comprises one or more contact data structures embodied on a computer-readable medium and including data manually entered by a user.

5. The system of claim 1 , wherein a recipient user is associated with the electronic message and wherein the electronic messaging management module is further configured to identify at least one contact chain for the recipient user and determine a length of the at least one contact chain for the recipient user.

6. The system of claim 1 , wherein a recipient user is associated withthe electronic message and wherein the electronic messaging management module is furtherconfigured to identify at least one contact chain for the recipient user and calculate a strengthvalue for at least one link in the at least one contact chain for the recipient user.

7. The system of claim 1 , wherein a recipient user is associated withthe electronic message and wherein the electronic messaging management module is furtherconfigured to identify at least one contact chain for the recipient user and calculate an averagestrength value for two or more links in the at least one contact chain for the recipient user.

8. The system of claim 1 , wherein a recipient user is associated withthe electronic message and wherein the electronic messaging management module is furtherconfigured to identify at least one contact chain for the recipient user and calculate a totalstrength value for two or more links in the at least one contact chain for the recipient user.

9. A method for processing an electronic messagereceived within a computing system, the method comprising:

identifying a sender of the electronic message;

identifying, from a set of system contact information comprising contactinformation associated with a plurality of system users, any contact informationassociated with the sender of the electronic message; and

using the contact information associated with the sender to determine whether achallenge-response message should be sent to the sender, wherein using the contactinformation comprises:

determining whether the system contact information includes at least onenon-rejected contact for the sender; and

determining whether the system contact information comprises an amountof information about the sender of the electronic message stored on one or morecontact data structures embodied on a computer-readable medium, the amount ofinformation about the sender being information other than information included inan addressing portion of the electronic message that has been added to the one ormore contact data structures by at least one of the plurality of users: and issuing a challenge-response message when the one or more contact datastructures do not contain information other than information included in an addressingportion of the electronic message.

10. The method of claim 9 , wherein using the contactinformation comprises one or more of:

determining whether the system contact information includes at least one rejectedcontact for the sender;

determining whether the sender has exceeded an activity limit;

determining whether the system contact information includes a minimum numberof contacts for the sender; and

determining whether the number of rejected contacts in the system contactinformation exceeds a threshold.

11. The method of claim 9 , wherein a recipient system user isassociated with the electronic message and wherein using the contact information comprisesidentifying at least one contact chain for the recipient system user and determining a length ofthe at least one contact chain for the recipient system user.

12. The method of claim 9 , wherein a recipient system user isassociated with the electronic message and wherein using the contact information comprisesidentifying at least one contact chain for the recipient system user and calculating a strengthvalue for at least one link in the at least one contact chain for the recipient system user.

13. The method of claim 9 , wherein a recipient system user isassociated with the electronic message and wherein using the contact information comprisesidentifying at least one contact chain for the recipient system user and calculating an averagestrength value for two or more links in the at least one contact chain for the recipient systemuser.

14. The method of claim 9 , wherein a recipient system user isassociated with the electronic message and wherein using the contact information comprisesidentifying at least one contact chain for the recipient system user and calculating a total strengthvalue for two or more links in the at least one contact chain for the recipient system user.

15. The method of claim 9 , wherein the contact information comprises data stored in one or more event data structures.

16. A method for communicating an electronic messagewithin a computing system, the method comprising:

receiving a challenge-response message;

the challenge-response message sent from a computing system that

identified, from a set of system contact information comprising contactinformation associated with a plurality of system users, contact informationassociated with a sender of the electronic message; and

used the contact information associated with the sender to determine thatthe challenge-response message should be sent, the use of the contact informationcomprising determining a length of a contact chain between the sender of theelectronic message and a recipient user identified in the electronic message, thelength of the contact chain comprising one or more links of system users betweenthe sender and the recipient user, and identifying a link limit away from therecipient user on which to base use of contact information:

using only the contact information associated with the system usersbetween the recipient user and the link limit to perform two or more of:

determining whether the system contact information includes atleast one non-rejected contact for the sender;

determining whether the system contact information includes atleast one rejected contact for the sender;

determining whether the sender has exceeded an activity limit;

determining whether the system contact information includes aminimum number of contacts for the sender; and

determining whether the number of rejected contacts in the systemcontact information exceeds a threshold.

17. The method of claim 16 , further comprising transmitting the challenge-response message to the sender of the electronic message.

18. The method of claim 16 , further comprising transmitting a response to the challenge-response message.

Assignments (8)
CHANGE OF NAME Recorded Dec 20, 2021
From: FACEBOOK, INC.
To: META PLATFORMS, INC.
Reel/Frame 058961/0436 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 3, 2012
From: AOL INC.
To: FACEBOOK, INC.
Reel/Frame 028487/0466 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS Recorded Nov 16, 2010
From: BANK OF AMERICA, N A
To: AOL INC; AOL ADVERTISING INC; GOING INC; LIGHTNINGCAST LLC; MAPQUEST, INC; NETSCAPE COMMUNICATIONS CORPORATION; QUIGO TECHNOLOGIES LLC; SPHERE SOURCE, INC; TACODA LLC; TRUVEO, INC; YEDDA, INC
Reel/Frame 025323/0416 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 31, 2009
From: AOL LLC
To: AOL INC.
Reel/Frame 023720/0509 →
SECURITY AGREEMENT Recorded Dec 14, 2009
From: AOL INC.; AOL ADVERTISING INC.; BEBO, INC.; ICQ LLC; GOING, INC.; LIGHTNINGCAST LLC; MAPQUEST, INC.; NETSCAPE COMMUNICATIONS CORPORATION; QUIGO TECHNOLOGIES LLC; SPHERE SOURCE, INC.; TACODA LLC; TRUVEO, INC.; YEDDA, INC.
To: BANK OF AMERICAN, N.A. AS COLLATERAL AGENT
Reel/Frame 023649/0061 →
CHANGE OF NAME Recorded Nov 12, 2008
From: AMERICA ONLINE, INC.
To: AOL LLC
Reel/Frame 021825/0362 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 7, 2005
From: MBLX LLC
To: AMERICA ONLINE, INC.
Reel/Frame 016030/0888 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2005
From: LANDSMAN, RICHARD A.; SULLIVAN, TIMOTHY THOMAS; LOGUE, JAY DARE
To: MBLX LLC
Reel/Frame 015659/0992 →