Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUSRE40804 E1
Publication typeGrant
Application numberUS 11/448,580
Publication dateJun 23, 2009
Filing dateJun 7, 2006
Priority dateAug 6, 1998
Fee statusPaid
Also published asUS6112227
Publication number11448580, 448580, US RE40804 E1, US RE40804E1, US-E1-RE40804, USRE40804 E1, USRE40804E1
InventorsJeffrey Nelson Heiner
Original AssigneeAol Llc
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Filter-in method for reducing junk e-mail
US RE40804 E1
Abstract
A method is provided for preventing the delivery of unwanted electronic mail messages to a destination client. An original electronic mail message is first received from a source client at a destination server. Next, a reply electronic mail message is sent from the destination server to the source client requesting the source client to complete a registration process to register the source client's electronic mail address with the destination server. The original electronic mail message is only sent from the destination server to the destination client when the source client properly registers the source client's electronic mail address.
Images(3)
Previous page
Next page
Claims(50)
1. A method for preventing the delivery of unwanted electronic mail messages to a destination client, said method comprising the steps of:
receiving an original electronic mail message from a source client at a destination server, said original electronic mail message including an email address for said source client;
comparing said electronic mail address of said source client to at least one of an accept list or a reject list of electronic mail addresses;
holding said original electronic mail message in a first memory that is distinct from a second memory where deleted messages are stored if said electronic mail address of said source client is not on at least one of said accept list or said reject list;
sending a reply electronic mail message from said destination server to said source client requesting that said source client complete a registration process, if said electronic mail address of said source client is not on at least one of said accept list or said reject list,
wherein said registration process comprises completing a form at an Internet address, and
wherein said form includes a query that is designed to be answered by a human rather than a machine;
monitoring thea response of said source client to said request to complete a registration process to determine whether said source client properly responds to said request; and
sending said original electronic mail message from said destination server to said destination client only if said source client properly responds to said request to complete a registration process.
2. The method for preventing the delivery of unwanted electronic mail messages according to claim 1, wherein said registration process comprises answering a question included in said reply electronic mail message.
3. The method for preventing the delivery of unwanted electronic mail messages according to claim 1, wherein said registration process comprises completing a form at an Internet address.
4. The method for preventing the delivery of unwanted electronic mail messages according to claim 1, wherein said registration process comprises following instructions via a telephone system.
5. A method for preventing the delivery of unwanted electronic mail messages to a destination client comprising the steps of:
receiving an original electronic mail message addressed to a destination client from a source client having an electronic mail address at a destination server;
comparing said electronic mail address of said source client to an accept list of electronic mail addresses;
sending said original electronic mail message to said destination client when said electronic mail address of said source client is on said accept list;
sending a reply electronic mail message from said destination server to said source client requesting that said source client complete a registration process when said electronic mail address of said source client is not on said accept list;
monitoring the response of said source client to said request to complete a registration process to determine whether said source client properly responds to said request; and
sending said original electronic mail message from said destination server to said destination client only if said source client properly responds to said request to complete a registration process.
6. The method for preventing the delivery of unwanted electronic mail messages according to claim 5, wherein said registration process comprises answering a question included in said reply electronic mail message.
7. The method for preventing the delivery of unwanted electronic mail messages according to claim 5, wherein said registration process comprises completing a form at an Internet address.
8. The method for preventing the delivery of unwanted electronic mail messages according to claim 5, wherein said registration process comprises following instructions via a telephone system.
9. The method for preventing the delivery of unwanted electronic mail messages according to claim 5, further including the steps of:
storing electronic mail addresses of clients to which said destination client has sent electronic mail messages; and
automatically updating said accept list to include said electronic mail addresses of clients to which said destination client has sent electronic mail messages.
10. The method for preventing the delivery of unwanted electronic mail messages according to claim 5, further including the steps of:
holding said original electronic mail message in a memory if said source client does not properly respond to said request to complete a registration process;
allowing said destination client to access said memory to determine the content of said original electronic mail message.
11. The method for preventing the delivery of unwanted electronic mail messages according to claim 5, further including the step of:
automatically adding said electronic mail address of said source client to said accept list if said source client properly responds to said request to complete a registration process.
12. A method for preventing the delivery of unwanted electronic mail messages to a destination client comprising the steps of:
receiving an original electronic mail message addressed to a destination client from a source client having an electronic mail address at a destination server;
comparing said electronic mail address of said source client to an accept list of electronic mail addressees;
sending said original electronic mail message to said destination client when said electronic mail address of said source client is on said accept list;
comparing said electronic mail address of said source client to a reject list of electronic mail addresses when said electronic address of said source client is not on said accept list;
deleting said original message when said electronic mail address of said source client is on said reject list;
holding said original electronic mail message in a first memory that is distinct from a second memory where deleted messages are stored if said electronic mail address of said source client is not on said accept list or said reject list;
sending a reply electronic mail message from said destination server to said source client requesting that said source client complete a registration process when said electronic mail address of said source client is not on said accept list or said reject list;
said registration process includes a query that is designed to be answered by a human rather than a machine;
monitoring the response of said source client to said request to complete a registration process to determine whether said source client properly responds to said request; and
sending said original electronic mail message from said destination server to said destination client only if said source client properly responds to said request to complete a registration process; and
deleting said original electronic mail message from said first memory when a predetermined period of time has lapsed without receiving a response to said request that said source client completed a registration process.
13. The method for preventing the delivery of unwanted electronic mail messages according to claim 12, wherein said registration process comprises answering a question included in said reply electronic mail message.
14. The method for preventing the delivery of unwanted electronic mail messages according to claim 12, wherein said registration process comprises completing a form at an Internet address.
15. The method for preventing the delivery of unwanted electronic mail messages according to claim 12, wherein said registration process comprises following instructions via a telephone system.
16. The method for preventing the delivery of unwanted electronic mail messages according to claim 12, further including the steps of:
storing electronic mail addresses of clients to which said destination client has sent electronic mail messages; and
automatically updating said accept list to include said electronic mail addresses of clients to which said destination client has sent electronic mail messages.
17. The method for preventing the delivery of unwanted electronic mail messages according to claim 12, further including the steps of:
holding said original electronic mail message in asaid first memory if said source client does not properly respond to said request to complete a registration process; and
allowing said destination client to access said first memory to determine the content of said original electronic mail message.
18. The method for preventing the delivery of unwanted electronic mail messages according to claim 12, further including the step of:
automatically adding said electronic mail address of said source client to said accept list if said source client properly responds to said request to complete a registration process.
19. The claim as recited in claim 1, further comprising comparing said electronic mail address of said source client to both an accept list and a reject list of electronic mail addresses.
20. The claim as recited in claim 1, further comprising sending said original electronic mail message to said destination client when said electronic mail address of said source client is on said accept list.
21. The claim as recited in claim 1, further comprising deleting said original electronic mail message, if said electronic mail address of said source client is on said reject list.
22. The claim as recited in claim 1, further comprising deleting said original electronic mail message from said first memory upon a preselected event.
23. The claim as recited in claim 1, wherein said preselected event is upon instruction from said destination client.
24. The claim as recited in claim 1, wherein said preselected event is when a predetermined period of time has lapsed without receiving a response to said request that said source client complete a registration process.
25. The claim as recited in claim 1, wherein said preselected event is exceeding a predetermined number of original electronic mail messages.
26. The claim as recited in claim 1, further comprising allowing said destination client to access said first memory to determine content of said original electronic mail message.
27. The claim as recited in claim 1, further comprising automatically adding said electronic mail address of said source client to said accept list if said source client properly responds to said request to complete a registration process.
28. The claim as recited in claim 1, further comprising adding said electronic mail address of said source client to said reject list.
29. The claim as recited in claim 12, further comprising deleting said original electronic mail message from said first memory upon a preselected event, wherein said preselected event is upon instruction from said destination client.
30. The claim as recited in claim 12, further comprising deleting said original electronic mail message from said first memory upon a preselected event, wherein said preselected event is exceeding a predetermined number of original electronic mail messages.
31. The claim as recited in claim 12, further comprising adding said electronic mail address of said source client to said reject list.
32. A method for preventing the delivery of unwanted electronic mail messages to a destination client, said method comprising the steps of:
receiving an original electronic mail message from a source client at a destination server, said original electronic mail message including an email address from said source client;
comparing said electronic mail address of said source client to at least one of an accept list or a reject list of electronic mail addresses;
holding said original electronic mail message in a first memory that is distinct from a second memory where deleted messages are stored if said electronic mail address of said source client is not on at least one of said accept list or said reject list;
sending a reply electronic mail message from said destination server to said source client requesting that said source client complete a registration process, if said electronic mail address of said source client is not on at least one of said accept list or said reject list;
said registration process includes a query that is designed to be answered by a human rather than a machine;
monitoring a response of said source client to said request to complete a registration process to determine whether said source client properly responds to said request;
sending said original electronic mail message from said destination server to said destination client if said source client properly responds to said request to complete a registration process; and
deleting said original electronic mail message from said first memory when a predetermined period of time has lapsed without receiving a response to said request that said source client complete a registration process.
33. The claim as recited in claim 32, further comprising comparing said electronic mail address of said source client to both an accept list and a reject list of electronic mail addresses.
34. The claim as recited in claim 32, further comprising sending said original electronic mail message to said destination client when said electronic mail address of said source client is on said accept list.
35. The claim as recited in claim 32, further comprising deleting said original electronic mail message, if said electronic mail address of said source client is on said reject list.
36. The claim as recited in claim 32, further comprising deleting said original electronic mail message from said first memory upon a preselected event, wherein said preselected event is upon instruction from said destination client.
37. The claim as recited in claim 32, further comprising deleting said original electronic mail message from said first memory upon a preselected event, wherein said preselected event is exceeding a predetermined number of original electronic mail messages.
38. The claim as recited in claim 32, further comprising allowing said destination client to access said first memory to determine content of said original electronic mail message.
39. The claim as recited in claim 32, further comprising automatically adding said electronic mail address of said source client to said accept list if said source client properly responds to said request to complete a registration process.
40. The claim as recited in claim 32, further comprising adding said electronic mail address of said source client to said reject list.
41. A method for preventing the delivery of unwanted electronic mail messages to a destination client, said method comprising the steps of:
receiving an original electronic mail message from a source client at a destination server, said original electronic mail message including an email address for said source client;
comparing said electronic mail address of said source client to at least one of an accept list or a reject list of electronic mail addresses;
holding said original electronic mail message in a first memory that is distinct from a second memory where deleted messages are stored if said electronic mail address of said source client is not on at least one of said accept list or said reject list;
allowing said destination client to access said first memory to determine content of said original electronic mail message;
sending a reply electronic mail message from said destination server to said source client requesting that said source client complete a registration process, if said electronic mail address of said source client is not on at least one of said accept list or said reject list;
said registration process includes a query that is designed to be answered by a human rather than a machine;
monitoring a response of said source client to said request to complete a registration process to determine whether said source client properly responds to said request; and
sending said original electronic mail message from said destination server to said destination client if said source client properly responds to said request to complete a registration process.
42. The claim as recited in claim 41, further comprising comparing said electronic mail address of said source client to both an accept list and a reject list of electronic mail addresses.
43. The claim as recited in claim 41, further comprising sending said original electronic mail message to said destination client when said electronic mail address of said source client is on said accept list.
44. The claim as recited in claim 41, further comprising deleting said original electronic mail message, if said electronic mail address of said source client is on said reject list.
45. The claim as recited in claim 41, further comprising deleting said original electronic mail message from said first memory upon a preselected event.
46. The claim as recited in claim 41, wherein said preselected event is upon instruction from said destination client.
47. The claim as recited in claim 41, wherein said preselected event is when a predetermined period of time has lapsed without receiving a response to said request that said source client complete a registration process.
48. The claim as recited in claim 41, wherein said preselected event is exceeding a predetermined number of original electronic mail messages.
49. The claim as recited in claim 41, further comprising automatically adding said electronic mail address of said source client to said accept list if said source client properly responds to said request to complete a registration process.
50. The claim as recited in claim 41, further comprising adding said electronic mail address of said source client to said reject list.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to methods used to reduce the amount of unwanted electronic mail (e-mail) received by a user of an e-mail service.

2. Related Art

The problem of unwanted, i.e. “junk,” e-mail is well known and has received considerable attention. However, some background is thought to be of help in understanding the problem and the solutions that have been previously used or proposed, as well as the basic e-mail process. Referring to FIG. 1, there is shown the conventional process of sending e-mail messages from a source client 10 to a destination client 40. After the source client 10 composes an e-mail message, the message is sent from the source client 10 to a source simple mail transfer protocol (SMTP) server 20. The source SMTP server 20 sends the e-mail message to a destination SMTP server 30, which then sends the e-mail message to the destination client 40. A major drawback in the conventional process is the ever increasing amount of junk e-mail messages received by the destination clients 40. Such junk e-mail messages include advertisements for numerous goods and services. Users of e-mail systems have been spending an increasing amount of time separating their regular e-mail messages from unwanted e-mail messages.

Attempts have been made to reduce the number of junk e-mail messages received by the destination clients. Some methods require the source client to add descriptive information to the e-mail message so that the destination SMTP server can prevent undesired e-mail messages from being sent to the destination client. These methods are basically ineffective because the senders of junk e-mail messages will not add the descriptive information which will allow destination clients to block the junk e-mail messages.

Filter-out methods have also been developed. With such filter-out methods, a database of known sources (source clients) of junk e-mail messages is compiled. The destination SMTP server compares the source client's e-mail address to the e-mail addresses in the database and does not sent undesired e-mail messages to the destination client. These methods have also proven to be ineffective because the development of robotic delivery programs. These robotic delivery programs sent out thousands of junk e-mail messages and create nonexistent source client e-mail addresses. Thus, when one source client e-mail address is blocked, a new address is created. As a consequence, the database of known sources of junk e-mail messages can not keep up with changing e-mail addresses created by the robotic delivery programs.

SUMMARY OF THE INVENTION

According to the invention, a method for preventing delivery of unwanted electronic mail is provided which overcomes the problems of prior art methods discussed above. The method of the invention thwarts conventional robotic delivery programs and, in preferred implementations, includes features which will counteract the anticipated use of more sophisticated robotic delivery systems.

In accordance with a first preferred embodiment of the invention, a method for preventing the delivery of unwanted electronic mail messages to a destination client is provided which comprises the steps of: receiving an original electronic mail message from a source client at a destination server; sending a reply electronic mail message from the destination server to the source client requesting that the source client complete a registration process; monitoring the response of the source client to the request to complete a registration process to determine whether the source client properly responds to the request; and sending the original electronic mail message from the destination server to the destination client only if the source client properly responds to the request to complete a registration process.

In another preferred embodiment, a method for preventing the delivery of unwanted electronic mail messages to a destination client is provided which comprises the steps of: receiving an original electronic mail message addressed to a destination client from a source client having an electronic mail address at a destination server; comparing the electronic mail address of the source client to an accept list of electronic mail addresses; sending the original electronic mail message to the destination client when the electronic mail address of the source client is on the accept list; sending a reply electronic mail message from the destination server to the source client requesting that the source client complete a registration process when the electronic mail address of the source client is not on the accept list; monitoring the response of the source client to the request to complete a registration process to determine whether the source client properly responds to the request; and sending the original electronic mail message from the destination server to the destination client only if the source client properly responds to the request to complete a registration process.

In accordance with yet another preferred embodiment of the invention, a method for preventing the delivery of unwanted electronic mail messages to a destination client is provided which comprises the steps of: receiving an original electronic mail message addressed to a destination client from a source client having an electronic mail address at a destination server; comparing the electronic mail address of the source client to an accept list of electronic mail addresses; sending the original electronic mail message to the destination client when the electronic mail address of the source client is on the accept list; comparing the electronic mail address of the source client to a reject list of electronic mail addresses when the electronic address of the source client is not on the accept list; deleting the original message when the electronic mail address of the source client is on the reject list; sending a reply electronic mail message from the destination server to the source client requesting that the source client complete a registration process when the electronic mail address of the source client is not on the reject list; monitoring the response of the source client to the request to complete a registration process to determine whether the source client properly responses to the request; and sending the original electronic mail message from the destination server to the destination client only if the source client properly responds to the request to complete a registration process.

Preferred implementations for the registration process include: answering a question included in the reply electronic mail message; completing a form at an Internet address; and following instructions via a telephone system.

Other features and advantages of the invention will be set forth in, or apparent from, the following detailed description of the preferred embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1, which was discussed above, is a schematic block diagram of a conventional e-mail system.

FIG. 2 is a flow chart illustrating a method of blocking junk e-mail messages in accordance with a preferred embodiment of the invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Referring to FIG. 2, there are shown the basic steps in a method of reducing the amount of junk e-mail received by a user of an e-mail service in accordance with a preferred embodiment of the invention. In a first step 60, a source client composes an e-mail message and the message is sent to the source SMTP server. Then, in step 70, the source SMTP server sends the e-mail message to the destination SMTP server. In step 80, the destination SMTP server compares the source client's e-mail address to an accept list. The accept list contains the e-mail addresses of source clients from which the destination client wishes to receive e-mail messages. In one implementation, the accept list is automatically updated to include the e-mail addresses of clients to which the destination client has sent e-mail messages. In all implementations, if the source client's e-mail address is on the accept list, the destination SMTP server sends the e-mail message to the destination client, as indicated in step 90. In step 100, if the source client's e-mail address is not on the accept list, the destination SMTP server determines if the source client's e-mail address is on a reject list. The reject list may contain e-mail addresses of known sources of junk e-mail and any e-mail address from which the destination client wishes not to accept e-mail. If the source client's e-mail address is on the reject list, the e-mail message is deleted by the destination SMTP server, as indicated in step 110. In an alternative embodiment, the e-mail message is held in a memory which is accessible by the destination client when the source client's e-mail address is on the reject list.

If the source client is not on the reject list, the destination SMTP server holds the e-mail message in memory and requests that the source client proceed with a registration process, as indicated in step 120. There are many different ways in which the source client can register its e-mail address. In one advantageous implementation, the destination SMTP server sends a reply message to the source client and requests that the source client send back a reply message. When the destination SMTP server receives the reply message, the original e-mail message is “filtered-in” and released to the destination client. However, if the original message is junk e-mail produced by a robotic delivery program, the destination SMTP server will never receive a response to its reply message because the source client e-mail address does not exist.

As robotic delivery programs become more sophisticated, it will become necessary to make the registration process more complex. For example, the destination SMTP server can send a reply message to the source client with instructions or a question that only a human can follow or answer, respectively. The registration process is successfully completed when the source client responds correctly. In a preferred implementation, each destination client is allowed to compose their own question and answer or instructions, in order to maximize the amount of effort required by a source of junk e-mail to send messages to multiple destination clients. In general, it will be cost prohibitive for the source of junk e-mail messages to go through and response to each destination SMTP server reply message. In other embodiments, the registration process is completed by filling out an Internet web page form or by following instructions via a telephone system. Although these embodiments have particular benefit, those skilled in the art will appreciate that there are many different ways in which the registration process can be performed. One advantage of including such a registration process is that it requires the source client to make an effort to filter-in a desired message, instead of requiring the destination client to filter-out undesired messages.

In step 130, the destination SMTP server determines whether the source client properly registered its e-mail address within a predetermined time period. The length of the predetermined time period may be selected either by the destination client or the destination SMTP server. If the e-mail address is properly registered, the original e-mail message is sent to the destination client and the source client's e-mail address is added to the accept list, as indicated in step 150. At any time, the destination client can add e-mail addresses and remove e-mail addresses from the accept and reject lists. Therefore, if the source client does properly register its e-mail address and the destination client wishes to not receive any more e-mail messages from that source client, the destination client can remove that entry from the accept list and add it to the reject list.

In the illustrated embodiment, if the registration process is not successfully completed within the predetermined period of time, the destination SMTP server holds the original e-mail message in a memory, as indicated in step 140. The destination client may access the e-mail messages stored in the memory. The destination SMTP server may delete the e-mail messages from the memory when a preselected event occurs, i.e., when instructed to do so by the destination client, or when a predetermined time period has lapsed, or when the memory is full or when a predetermined number of e-mail messages has been exceeded. Either the destination SMTP server, or the destination client can determine the manner in which the e-mail messages will be deleted from the memory.

In another embodiment (not shown), the destination SMTP server automatically deletes the original e-mail message if the registration process is not completed within the predetermined period of time.

One of ordinary skill in the art will appreciate that the software necessary to carry out the present invention may operate either from the destination server or the destination client.

Although the invention has been described in detail with respect to preferred embodiments thereof, it will be apparent to those skilled in the art that variations and modifications can be effected in these embodiments without departing from the spirit and scope of the invention.

Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US4977520Feb 3, 1988Dec 11, 1990Ibm Corp.Method to facilitate a reply to electronic meeting invitation in an interactive multi-terminal system employing electronic calendars
US5040141Nov 23, 1987Aug 13, 1991Hitachi, Ltd.Method for administrating reply mail in electronic mail system
US5093918Dec 22, 1988Mar 3, 1992International Business Machines CorporationSystem using independent attribute lists to show status of shared mail object among respective users
US5159673Mar 11, 1992Oct 27, 1992Square D CompanyApparatus for networking programmable logic controllers to host computers
US5204961Jun 25, 1990Apr 20, 1993Digital Equipment CorporationComputer network operating with multilevel hierarchical security with selectable common trust realms and corresponding security protocols
US5245532Jun 12, 1989Sep 14, 1993International Business Machines CorporationElectronic mail follow-up system
US5283856Oct 4, 1991Feb 1, 1994Beyond, Inc.Event-driven rule-based messaging system
US5319776Sep 29, 1992Jun 7, 1994Hilgraeve CorporationIn transit detection of computer virus with safeguard
US5333266Mar 27, 1992Jul 26, 1994International Business Machines CorporationMethod and apparatus for message handling in computer systems
US5377354Jun 8, 1993Dec 27, 1994Digital Equipment CorporationMethod and system for sorting and prioritizing electronic mail messages
US5423042Oct 23, 1992Jun 6, 1995International Business Machines CorporationRemote procedure execution
US5448734May 26, 1994Sep 5, 1995International Business Machines CorporationSelective distribution of messages using named pipes
US5471519Feb 26, 1993Nov 28, 1995Bellsouth CorporationCommunications monitoring and control system
US5473671Mar 11, 1994Dec 5, 1995At&T Corp.Selective screening of incoming calls for cellular telephone systems
US5539828May 31, 1994Jul 23, 1996Intel CorporationApparatus and method for providing secured communications
US5548789Mar 13, 1995Aug 20, 1996Canon Kabushiki KaishaMessage communication processing apparatus for selectively converting storing and transmitting messages of different lengths
US5600799Oct 5, 1995Feb 4, 1997National Semiconductor CorporationStatus batching and filtering in a media access control/host system interface unit
US5604803Jun 3, 1994Feb 18, 1997Sun Microsystems, Inc.Method and apparatus for secure remote authentication in a public network
US5608786Feb 13, 1995Mar 4, 1997Alphanet Telecom Inc.Communication system
US5619648 *Nov 30, 1994Apr 8, 1997Lucent Technologies Inc.For locating expertise in a messaging system in a computer system
US5627764Jun 9, 1993May 6, 1997Banyan Systems, Inc.Automatic electronic messaging system with feedback and work flow administration
US5630123Sep 28, 1994May 13, 1997I2 Technologies, Inc.Software system utilizing a filtered priority queue and method of operation
US5632018Sep 13, 1993May 20, 1997Fujitsu LimitedElectronic mail system
US5655079May 22, 1995Aug 5, 1997Hitachi, Ltd.Data processing system and data transmission and processing method
US5721779Aug 28, 1995Feb 24, 1998Funk Software, Inc.Apparatus and methods for verifying the identity of a party
US5734903May 13, 1994Mar 31, 1998Apple Computer, Inc.System and method for object oriented message filtering
US5742668Jun 6, 1995Apr 21, 1998Bell Communications Research, Inc.Communication system
US5742769May 6, 1996Apr 21, 1998Banyan Systems, Inc.Directory with options for access to and display of email addresses
US5781857Jun 28, 1996Jul 14, 1998Motorola, Inc.Method of establishing an email monitor responsive to a wireless communications system user
US5796840Oct 4, 1995Aug 18, 1998Intel CorporationApparatus and method for providing secured communications
US5826022 *Apr 5, 1996Oct 20, 1998Sun Microsystems, Inc.Method and apparatus for receiving electronic mail
US5832227Dec 14, 1993Nov 3, 1998The Commonwealth Of Australia Of Anzak ParkMethod for providing message document security by deleting predetermined header portions and attaching predetermined header portions when seal is validly associated with message or document
US5835722Jun 27, 1996Nov 10, 1998Logon Data CorporationComputer running under a multi-tasking environment
US5859967Jul 9, 1996Jan 12, 1999Faxsav IncorporatedMethod and system for relaying communications from authorized users
US5884033May 15, 1996Mar 16, 1999Spyglass, Inc.Internet filtering system for filtering data transferred over the internet utilizing immediate and deferred filtering actions
US5893911Apr 17, 1996Apr 13, 1999Neon Software, Inc.Method for defining and applying rules for message distribution for transaction processing in a distributed application
US5909589Nov 12, 1996Jun 1, 1999Lance T. ParkerInternet based training
US5917489Jan 31, 1997Jun 29, 1999Microsoft CorporationSystem and method for creating, editing, and distributing rules for processing electronic messages
US5930479 *Oct 21, 1996Jul 27, 1999At&T CorpCommunications addressing system
US5937162Sep 24, 1996Aug 10, 1999Exactis.Com, Inc.Method and apparatus for high volume e-mail delivery
US5999600Oct 14, 1997Dec 7, 1999Samsung Electronics Co., Ltd.Facsimile mail system and method for controlling the same
US5999932Jan 13, 1998Dec 7, 1999Bright Light Technologies, Inc.System and method for filtering unsolicited electronic mail messages using data matching and heuristic processing
US5999967Aug 17, 1997Dec 7, 1999Sundsted; ToddElectronic mail filtering by electronic stamp
US6014634Aug 4, 1997Jan 11, 2000Supermarkets Online, Inc.System and method for providing shopping aids and incentives to customers through a computer network
US6023723 *Dec 22, 1997Feb 8, 2000Accepted Marketing, Inc.Method and system for filtering unwanted junk e-mail utilizing a plurality of filtering mechanisms
US6052709 *Dec 23, 1997Apr 18, 2000Bright Light Technologies, Inc.Apparatus and method for controlling delivery of unsolicited electronic mail
US6055510Oct 24, 1997Apr 25, 2000At&T Corp.Method for performing targeted marketing over a large computer network
US6057841Dec 21, 1998May 2, 2000Microsoft CorporationSystem and method for processing electronic messages with rules representing a combination of conditions, actions or exceptions
US6092101Jun 16, 1997Jul 18, 2000Digital Equipment CorporationMethod for filtering mail messages for a plurality of client computers connected to a mail service system
US6154765Mar 18, 1999Nov 28, 2000Pasocs LlcDistributed digital rule processor for single system image on a clustered network and method
US6173322Jun 5, 1997Jan 9, 2001Silicon Graphics, Inc.Network request distribution based on static rules and dynamic performance data
US6182118Oct 27, 1997Jan 30, 2001Cranberry Properties LlcSystem and method for distributing electronic messages in accordance with rules
US6189026Jun 16, 1997Feb 13, 2001Digital Equipment CorporationTechnique for dynamically generating an address book in a distributed electronic mail system
US6195698Apr 13, 1998Feb 27, 2001Compaq Computer CorporationMethod for selectively restricting access to computer systems
US6199102Aug 26, 1997Mar 6, 2001Christopher Alan CobbMethod and system for filtering electronic messages
US6199106Sep 14, 1998Mar 6, 2001Juno Online Services, Inc.Electronic mail system with advertising
US6205432Nov 16, 1998Mar 20, 2001Creative Internet Concepts, LlcBackground advertising system
US6237027Jun 10, 1997May 22, 2001Sony CorporationElectronic mail system, computer device, and remote notification method
US6373950Jun 17, 1996Apr 16, 2002Hewlett-Packard CompanySystem, method and article of manufacture for transmitting messages within messages utilizing an extensible, flexible architecture
US6393465May 29, 1998May 21, 2002Nixmail CorporationJunk electronic mail detector and eliminator
US6421709Jul 7, 1999Jul 16, 2002Accepted Marketing, Inc.E-mail filter and method thereof
US6484197Feb 11, 1999Nov 19, 2002International Business Machines CorporationFiltering incoming e-mail
US6546416 *Dec 9, 1998Apr 8, 2003Infoseek CorporationMethod and system for selectively blocking delivery of bulk electronic mail
US6625257Jul 31, 1998Sep 23, 2003Toyota Jidosha Kabushiki KaishaMessage processing system, method for processing messages and computer readable medium
US6678704Apr 25, 2001Jan 13, 2004Oracle International CorporationMethod and system for controlling recovery downtime by maintaining a checkpoint value
US6883095Dec 19, 2000Apr 19, 2005Singlesigon. Net Inc.System and method for password throttling
US7194515 *Apr 3, 2003Mar 20, 2007Google Inc.Method and system for selectively blocking delivery of bulk electronic mail
US7383433Jun 7, 2002Jun 3, 2008Sun Microsystems, Inc.Trust spectrum for certificate distribution in distributed peer-to-peer networks
US20020199095May 22, 2002Dec 26, 2002Jean-Christophe BandiniMethod and system for filtering communication
US20050081059Aug 9, 2004Apr 14, 2005Bandini Jean-Christophe DenisMethod and system for e-mail filtering
DE19708856A1Mar 5, 1997Sep 10, 1998Bosch Gmbh RobertDigital component test method for broadband communication
EP0463252A1Jun 28, 1990Jan 2, 1992International Business Machines CorporationMessage handling in data processing apparatus
EP0651533A2Jul 22, 1994May 3, 1995Sun Microsystems, Inc.Method and apparatus for privacy and authentication in a mobile wireless network
EP0686327A1Dec 14, 1993Dec 13, 1995The Commonwealth Of AustraliaMessage document security
EP0721268A2Nov 17, 1995Jul 10, 1996International Business Machines CorporationMethod and apparatus for automatic e-mail response to a third party
EP0725523A2Dec 6, 1995Aug 7, 1996International Business Machines CorporationTransaction message routing in digital communications networks
EP0760565A1Aug 28, 1995Mar 5, 1997Feldbau, OfraApparatus and method for authenticating the dispatch and contents of documents
EP0883271A2Apr 14, 1998Dec 9, 1998Hewlett-Packard CompanyMethod and system for managing data service systems
WO1994006236A2Aug 24, 1993Mar 17, 1994Bellsouth CorpPersonal number communications system
WO1996009714A1Sep 19, 1995Mar 28, 1996Bell Communications ResPersonal communications internetworking
WO1996024213A1Jan 24, 1996Aug 8, 1996Freemark Communications IncSystem and method for providing end-user free email
WO1997014234A2Sep 25, 1996Apr 17, 1997Netspeak CorpPoint-to-point internet protocol
WO1997020423A1Nov 27, 1996Jun 5, 1997Bell Communications ResA system and method for automatically screening and directing incoming calls
WO1997023082A1Dec 13, 1996Jun 26, 1997At & T CorpGuest mail: communicating electronic messages between disparate messaging systems
WO1997024825A2Dec 20, 1996Jul 10, 1997Martin BrabandMethod and microcomputer system for the automatic, secure and direct transmission of data
WO1997026709A1Jan 16, 1997Jul 24, 1997Pocketscience IncElectronic messaging system and method
WO1998037675A1Feb 18, 1998Aug 27, 1998Verifone IncA system, method and article of manufacture for secure digital certification of electronic commerce
WO1999010817A1Aug 26, 1998Mar 4, 1999Cobb Christopher AlanA method and system for filtering electronic messages
WO2001016695A1Aug 25, 2000Mar 8, 2001Peter L KatsikasSystem for eliminating unauthorized electronic mail
WO2002077768A2Mar 22, 2002Oct 3, 2002Michael ChungMethods and systems for electronic mail, internet target and direct marketing, and electronic mail banner
WO2003044617A2Oct 3, 2002May 3, 2003Reginald AdkinsAuthorized email control system
Non-Patent Citations
Reference
1A Way to Stop Spam Messages [online] [retrieved on Apr. 25, 2003]. Retrieved from the Internet http://groups.google.com/groups?q=%B%22sender%22=2Bspam&start=10&hl=en&lr . . . (4 pages).
2Andrew Leonard, SpamBomers, Sep. 1997, 7 pages, Salon Magazine + about 21st + newsletter.
3AOL Fights to Ban Junk Email, by Rose Aguilar [online] [retrieved on Nov. 3, 1998]. Retrieved from the Internet http://www.news.com/News/Item/0.4.3106.00.htm (3 pages).
4Article entitled "Pricing Via Processing or Combatting Junk Mail," by Cynthia Dwork and Moni Naor, IBM Research Division and Department of Applied Mathematics and Computer Science, Weizmann Institute of Science (12 pages).
5Article entitled "Spam!, " by Lorrie Faith Cranor and Brian A. LaMacchia, Aug. 1998, Communications of the ACM, vol. 41, No. 8, pp. 74-83.
6Article entitled "Verification of a Human in the Loop or Identification Via the Turing Test, " dated Sep. 13, 1996, by Moni Naor, Department of Applied Mathematics and Computer Science, Weizmann Institute of Science (6 pages).
7Cementing Online Partnerships and Improving User Experience, RSA Security, retrived online May 17, 2006, 7 pages, www.rsasecurity.com.
8Chinese Abstract for CN 1117680, published Feb. 28, 1996.
9CNET News.com staff, ISP: Internet Spam Provider, Feb. 18, 1997, 2 pages, CNET News.com.
10Cole-Gomolski, Barb, Adoption of S/Mime Still lagging, May 11, 1998, 4 pages, http://www.computerworld.com/home/features.nsf/.
11Controlling E-Mail Spam, online, retrieved on Mar. 28, 2003, 5 pages, retrieved from the Internet http://spam.abuse.net/adminhelp/mail.shtml.
12Cynthia Dwork, Fighting Spam May be Easier Than You Think, 1992, 30 pages, presentation given in Crypto.
13Cynthia Dwork, Fighting Spam: The Science, 2004, pp. 3-4, M. Farach-Colton (Ed.): Latin 2004, LNCS 2976, Springer-Verlag Berlin.
14D. J. Berstein, Variable Envelope Return Paths, Feb. 1, 1997, 2 pages, http://cr.yp.to/proto/verp.txt.
15David A. Wheeler, Countering Spam with Ham-Authenicated Email and the Guarded Email Protocol, Draft: First version Dec. 8, 2002; Released Apr. 2, 2003, 28 pages, dwheeler@dwheeler.com.
16Dealing with Unsolicited Commercial Email (UCE, "email spam") Copyright 2003, 2005 Public Access Network Corporation [online] [retrieved on Jun. 6, 2006]. Retrieved from the Internet http://www.panix.com.com/uce.html (3 pages).
17Document entitled "IMAP/POP Authorize Extension for Simple Challenge/Response, " dated Sep. 1997, by J. Klensin, R. Catoe, P. Krumviede (5 pages).
18Douglas G. Henke, All Hail Emperor Lewis ?, online, Feb. 20, 1997, 2 pages, retrived Apr. 25, 2003, retrived from the internet http://groups.google.com/groups.
19Ed Foster, The Gripe Line Threatening legal action may be the quickeest way off a junk e-mailer's list, Info World Info Quote, Sep. 9, 1996, 2 pages, vol. 18, Issue 37, http://www.infoworld.com/egi-bin/siplayArchives.pl?.
20Filter for mail not addressed to you, by Bob Jameson, Dated Aug. 19, 1997 [online] [retrieved on Nov. 3, 1998]. Retrieved from the internet http://www/zdnet.com/anchordesk/talkback/talkback-35298.html (1 page).
21Foiling Spam with an Email Password System [online]retrieved on Jun. 28, 2004 . Retrieved from the Internet http://www.uwasa.fi/~ts/info/spamfoil.html (10 pages).
22How to make SURE a human is sending you mail (was Re: Random e-mails) [online]. Retrieved from the Internet http://groups.google.com/group/news.admini.net-abuse.usenet/msg/e601783e8f40c545?d. . . (2 pages).
23Janet Kornblum, Programmer Writes Spam Bomb, Aug. 6, 1997, 2 pages, CNET News.com.
24Julian Byrne, New Improved EZSPAM! Was: My Spamblock. . ., online, Jan. 28, 1997, 4 pages, retrieved Apr. 25, 2003, retrived from the internet, http://groups.google.com/groups.
25MailCircuits's Email HandShake Verification and Spam Filter Process [online] copyright 1996-2003,MailCircuit.com. Retrieved from the Internet http://www.mailcircuit.com/filter.htm ( 2 pages).
26Mihir Bellare et al., Does Parallel Repition Lower the Error in Computationally Sound Protocols?, 24 pages, Proceedings of the 38th Symposium on Foundations of Computer Science, IEEE.
27MIT LCS, Applied Security Reading Group, by Email Sit and Kevin Fu, 2 pages, updated May 5, 2003 on the Internet http://www.pdocs.lcs,mit.edu/asrg.
28My Spamblock; Was: Thwarting UCE address culling programs [online] [retrieved on Apr. 28, 2003]. Retrieved from the Internet http://www.google.com/groups?hl=en&lr=lie=UTF-8&oe=UTF-8selm=32E1A4FD.41C. . . (2 pages).
29NAGS Spam Filter [online], Oct. 30, 1997. Retrieved from the Internet http://www.nags.org/spamfilter.html (11 pages).
30P. Resnick, RFC28822, Apr. 2001, 51 Pages, Qualcom Incorporated, http:rfc.net/rfc2822.html.
31Public Access Networks Corporation, Responding to Unsolicited Commercial Email (UCE, "email spam"), Feb. 25, 1997, 5 pages, http:www.panix.com/uce.html.
32Showing Full Headers of a Message, Nov. 6, 1998, 3 pages, http:/www.panix.com/headers.html.
33Stop Junk E-mail [online] [retrieved on Nov. 4, 1998]. Retrieved from the Internet http://www.crl.com/~michaelp/stopjunkmail.html (1 page).
34The Penny Black Project, online, retrieved on May 8, 2006, 2 pages, retrieved from the Internet http://research.microsoft.com/research/sv/PennyBlack.
35Tim Richardson, Simple Notes on Internet Security and Email, Jun. 28, 1999, 2 pages, http://www.timirichardson.net/security.html.
36To Mung or Not to Mung, Ronald F. Guilmette, Dated Jul. 24, 1997 [online] [retrieved on Apr. 25, 2003]. Retrieved from the Internet http://groups.google.com/groups?q=TheDeadbolt=tm=%2Bspam&hl=en&lr=&ie=UTF-8. . . (2 pages).
37Unsolicited Bulk Email: Mechanisms for Control, by Paul Hoffman and Dave Crocker, Internet Mail Consortium Report UBE-SOL, IMCR-005, Oct. 13, 1997 (31 pages).
38Unsolicited Bulk Email: Mechanisms for Control, by Paul Hoffman and Dave Crocker, Internet Mail Consortium Report UBE-SOL, IMCR-008, revised May 4, 1998 (16 pages).
Classifications
U.S. Classification709/203, 709/205, 709/204, 709/202, 709/206
International ClassificationG06Q10/00, G06F15/16, H04L12/58
Cooperative ClassificationH04L51/12, G06Q10/107, H04L12/585
European ClassificationG06Q10/107, H04L51/12, H04L12/58F
Legal Events
DateCodeEventDescription
Jul 3, 2012ASAssignment
Effective date: 20120614
Owner name: FACEBOOK, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL INC.;REEL/FRAME:028487/0466
Feb 1, 2012FPAYFee payment
Year of fee payment: 12
Nov 16, 2010ASAssignment
Owner name: AOL INC, VIRGINIA
Owner name: MAPQUEST, INC, COLORADO
Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416
Effective date: 20100930
Owner name: TACODA LLC, NEW YORK
Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416
Owner name: YEDDA, INC, VIRGINIA
Owner name: AOL ADVERTISING INC, NEW YORK
Effective date: 20100930
Owner name: NETSCAPE COMMUNICATIONS CORPORATION, VIRGINIA
Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416
Owner name: QUIGO TECHNOLOGIES LLC, NEW YORK
Owner name: TRUVEO, INC, CALIFORNIA
Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416
Owner name: GOING INC, MASSACHUSETTS
Owner name: SPHERE SOURCE, INC, VIRGINIA
Effective date: 20100930
Owner name: LIGHTNINGCAST LLC, NEW YORK
Jan 22, 2010ASAssignment
Owner name: AMERICA ONLINE, INC., VIRGINIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MBLX LLC;REEL/FRAME:023834/0612
Effective date: 20050331
Owner name: AOL LLC, VIRGINIA
Free format text: CHANGE OF NAME;ASSIGNOR:AMERICA ONLINE, INC.;REEL/FRAME:023834/0648
Effective date: 20060403
Owner name: MAILBLOCKS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VIRTUAL GATE TECHNOLOGIES, LLC;REEL/FRAME:023834/0456
Effective date: 20020930
Owner name: MBLX LLC, CALIFORNIA
Free format text: MERGER;ASSIGNOR:MAILBLOCKS, INC.;REEL/FRAME:023834/0567
Effective date: 20041101
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEINER, JEFFREY NELSON;REEL/FRAME:023834/0510
Effective date: 20021002
Dec 31, 2009ASAssignment
Owner name: AOL INC., VIRGINIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL LLC;REEL/FRAME:023720/0509
Effective date: 20091204
Owner name: AOL INC.,VIRGINIA
Dec 14, 2009ASAssignment
Owner name: BANK OF AMERICAN, N.A. AS COLLATERAL AGENT, TEXAS
Free format text: SECURITY AGREEMENT;ASSIGNORS:AOL INC.;AOL ADVERTISING INC.;BEBO, INC.;AND OTHERS;REEL/FRAME:023649/0061
Effective date: 20091209
Owner name: BANK OF AMERICAN, N.A. AS COLLATERAL AGENT,TEXAS