USRE41411E1 - Method and system for filtering electronic messages - Google Patents

Method and system for filtering electronic messages Download PDF

Info

Publication number
USRE41411E1
USRE41411E1 US11/448,579 US44857906A USRE41411E US RE41411 E1 USRE41411 E1 US RE41411E1 US 44857906 A US44857906 A US 44857906A US RE41411 E USRE41411 E US RE41411E
Authority
US
United States
Prior art keywords
sender
message
address
prompt
list
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
US11/448,579
Inventor
Christopher Alan Cobb
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
PHIL GOLDMAN
Google LLC
Original Assignee
AOL Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=25446245&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=USRE41411(E1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by AOL Inc filed Critical AOL Inc
Priority to US11/448,579 priority Critical patent/USRE41411E1/en
Assigned to BANK OF AMERICAN, N.A. AS COLLATERAL AGENT reassignment BANK OF AMERICAN, N.A. AS COLLATERAL AGENT SECURITY AGREEMENT Assignors: AOL ADVERTISING INC., AOL INC., BEBO, INC., GOING, INC., ICQ LLC, LIGHTNINGCAST LLC, MAPQUEST, INC., NETSCAPE COMMUNICATIONS CORPORATION, QUIGO TECHNOLOGIES LLC, SPHERE SOURCE, INC., TACODA LLC, TRUVEO, INC., YEDDA, INC.
Assigned to AOL INC. reassignment AOL INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AOL LLC
Assigned to PHIL GOLDMAN reassignment PHIL GOLDMAN NOTICE OF REVERSIONARY INTEREST Assignors: COBB, CHRISTOPHER A.
Assigned to MAILBLOCKS, INC. reassignment MAILBLOCKS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: THE GOLDMAN LIVING TRUST
Assigned to PHIL GOLDMAN reassignment PHIL GOLDMAN ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: COBB, CHRISTOPHER A.
Assigned to MBLX LLC reassignment MBLX LLC MERGER (SEE DOCUMENT FOR DETAILS). Assignors: MAILBLOCKS, INC.
Assigned to AMERICA ONLINE, INC. reassignment AMERICA ONLINE, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MBLX LLC
Assigned to AOL LLC reassignment AOL LLC CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: AMERICA ONLINE, INC.
Assigned to THE GOLDMAN LIVING TRUST reassignment THE GOLDMAN LIVING TRUST COURT ORDER Assignors: BY COURT ORDER SIGNED BY THE JUDGE ON 4/28/2004, AND FILED BY THE CLERK 05/07/2004, ON BEHALF OF PHILLIP Y. GOLDMAN A/K/A PHIL GOLDMAN (DECEASED)
Priority to US12/823,735 priority patent/USRE42702E1/en
Publication of USRE41411E1 publication Critical patent/USRE41411E1/en
Application granted granted Critical
Assigned to NETSCAPE COMMUNICATIONS CORPORATION, AOL INC, TRUVEO, INC, YEDDA, INC, TACODA LLC, SPHERE SOURCE, INC, MAPQUEST, INC, LIGHTNINGCAST LLC, GOING INC, AOL ADVERTISING INC, QUIGO TECHNOLOGIES LLC reassignment NETSCAPE COMMUNICATIONS CORPORATION TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS Assignors: BANK OF AMERICA, N A
Assigned to MARATHON SOLUTIONS LLC reassignment MARATHON SOLUTIONS LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AOL INC.
Assigned to BRIGHT SUN TECHNOLOGIES reassignment BRIGHT SUN TECHNOLOGIES ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MARATHON SOLUTIONS LLC
Assigned to GOOGLE INC. reassignment GOOGLE INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BRIGHT SUN TECHNOLOGIES
Anticipated expiration legal-status Critical
Assigned to GOOGLE LLC reassignment GOOGLE LLC CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: GOOGLE INC.
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21Monitoring or handling of messages
    • H04L51/212Monitoring or handling of messages using filtering or selective blocking

Definitions

  • the present invention relates generally to the receipt of electronic messages, via the Internet for example, and more particularly, to a system and method for filtering unsolicited electronic commercial messages.
  • a user can send messages to a receiver located virtually anywhere in the world.
  • email By using email, it may take only seconds for the sender's message to be received by a receiver on the other side of the world.
  • the receiver can read the sender's text immediately on the screen, respond to it right away, save it for later, print it, or quickly forward it to another receiver.
  • Messages a user receives can be organized into convenient electronic folders and saved for as long as the user wishes without taking up office space. Due to these advantages, email has become many people's principle means of communicating with the world.
  • a further function of electronic mail allows a user to create electronic mailing lists for sending notices to hundreds or even thousands of people at once. Due to the ease of sending electronic mail to a very large number of people, the number of mass mailings for unsolicited advertising has risen dramatically. Unlike advertisements through the U.S. Postal Service, it is not necessarily clear to the user that the message is for advertising purposes until the user opens and reads the message. Thus, the target of the unsolicited electronic commercial message must typically open the message, read a portion of it, then, after determining it to be unwanted “junk”, delete it. A user receiving several of these commercial messages can easily expend valuable time, resources and mental aggravation.
  • a junk e-mailer (commonly referred to as a “spammer”) benefits by contacting the largest and broadest group of recipients as possible—more recipients means more people who might be interested in the message—even if it also means a larger group of outraged recipients.
  • the present invention provides a system and method for filtering unsolicited electronic commercial messages.
  • a system and method according to the present invention for screening out unsolicited commercial messages comprises the steps of receiving a message from a sender, sending a prompt back to the sender, receiving a response to the prompt, and determining if the response is a proper response.
  • the sender address is a valid address. If the sender address is not a valid address, then it can be assumed that it is an unsolicited commercial message. However, if the sender address is valid, then a prompt is sent to the sender.
  • the prompt can be any question which can be answered by a person but typically not by a computer system. If a correct response to the prompt is received thereafter, then the message can be assumed not to be a mass mailed unsolicited commercial message, and accordingly is not filtered out. If incorrect, the message is filtered.
  • FIG. 1 is a block diagram of a computer system in which the present invention can reside.
  • FIG. 2 is a block diagram of a network in which the present invention can operate.
  • FIG. 3 is an example of a networking system in which the present invention can operate.
  • FIG. 4 is another example of a networking system in which the present invention can operate.
  • FIG. 5 is a diagram of a typical electronic message.
  • FIG. 6 is an example of a challenge and its components according to the present invention.
  • FIG. 7 is a flow diagram of a method according to the present invention.
  • the present invention relates to a system and method for screening out unsolicited commercial messages.
  • the following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements.
  • Various modifications to the preferred embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments.
  • the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.
  • the present invention is described in terms of a system which receives e-mail, it is to be understood that email is merely an example in which the present invention can be applied.
  • the present invention can also be applied to electronic messages in video form wherein unsolicited commercial messages can be sent via video.
  • the source list method requires a message sender to be on a list (either an acceptance or blocking list) in order to permit the filter to take action.
  • a message from an unknown sender (frequently a solicitor) cannot be discarded because it might be from, for example, a new business contact or a long-lost friend.
  • a solicitor can assure that junk messages will pass through a source list filter and come to rest in a temporary or miscellaneous category reserved for messages that are not actionable. Messages in this category must typically, at least briefly, be scanned by the recipient—a successful defeat of the filtering mechanism.
  • the second method has the potential of discarding wanted, as well as unwanted, messages.
  • Any keyword or phrase search (with the intention of identifying and dealing with particular message subject matters) will eventually discard a bona fide message that appears to be “junk” in nature. For example, searching and discarding all messages with the words “make money” in them might get rid of some junk messages, but it will also eventually discard a desired message such as a new business idea from a brother or sister that happens to use the same words or word patterns.
  • the flaws in this approach force most implementations to place incoming messages in a temporary holding category. And again the messages in this category will, at least briefly, be scanned by the recipient a success for the solicitor.
  • a feature of the present invention is the checking of incoming messages to verify that they include valid sender information. Any message which does not contain a valid sender address is assumed to be a junk email communication and is dealt with appropriately (generally deleted).
  • a sender address will depend on the specifics of whatever communication system is being used. On the Internet, for example, a sender address cannot contain certain characters (such as ‘control’ characters), must include an AT “@” symbol, and must be from a registered domain name. Each of these requirements (as well as others) can be checked. A sender address which violates any of them would be invalid.
  • Another feature of the present invention is the checking of incoming messages to verify that each message is properly addressed to the user (the recipient). For example, a message which is not addressed to the recipient will be assumed to be a junk email communication and dealt with appropriately (generally deleted).
  • the method according to the present invention will consider various appropriate recipient designations for the messaging system being used. In other words, it is possible that the recipient will receive a valid message that is not directly addressed to him. Instead, he might be a CC (carbon copy) recipient, or perhaps a BCC (blind carbon copy) recipient. There may be other possible message recipient designations. As long as the invention user's address is present on at least one of these recipient designations the message is considered valid. If the user's address is absent from all of these recipient groups the incoming message is considered junk email.
  • Yet another feature of the invention is that it prompts unrecognized email senders, for example, by returning their message and asking them a predetermined question or one of a set of predetermined questions:
  • a block of text is added to the beginning of an incoming email message from an unknown sender.
  • the sender's original message is preferably preserved.
  • This block of text is referred to as a Challenge and contains, among other elements, a prompt, such as a question similar to those above. It also contains an answer blank area where the sender is requested to place their response to the prompt.
  • the modified message is returned to the sender.
  • the sender must answer the Challenge (which includes the prompt) and send it back to the recipient.
  • the answers are checked for validity. If the answers are correct, the message is forwarded to the recipient. Otherwise the message is blocked and discarded.
  • FIG. 1 is a block diagram of a system in which the present invention can reside.
  • the computer system 10 is shown to include a display 12 , a keyboard 14 , a pointing device 16 , a processor 18 , a memory 20 , a disk drive 22 , and a Network interface 24 . These various components are shown to be coupled to a system bus 26 .
  • FIG. 2 is a block diagram of networking system with which the present invention can work.
  • the Internet system 50 is shown to include mail servers 52 a- 52 c which utilize the standard protocol of Simple Mail Transfer Protocol (SMTP).
  • a message 54 can be sent via one of the SMTP servers, such as the server 52 a.
  • the message may be passed through several servers before reaching its final destination, in this example, the server 52 c.
  • a mailbox 56 such as a Post Office Protocol box (POP) or Internet Message Access Protocol box (IMAP) where it is held pending retrieval by an Email Client Program 60 .
  • POP Post Office Protocol box
  • IMAP Internet Message Access Protocol box
  • the message can be filtered through the Message Filter Program 58 .
  • the Message Filter 58 can be located in various locations including between the Mailbox 56 and the user's Email Client Program 60 ; as part of mailbox servers such as Mailbox 56 , or in the Email Client Program 60 which actually processes the user's messages.
  • the Message Filter 58 according to the present invention is shown to be located between the Mailbox 56 and the Email Client Program 60 .
  • the message filter is shown incorporated into the Email Client Program.
  • FIG. 3 is an example of a networking system in which the present invention can operate.
  • Filtering Enabled Email Client Program 100 is shown communicating with a Network 110 that facilitates communication among other members of the network.
  • Filtering Enabled Email Client Program (FEECP) 100 is resident and actively run on a computer system illustrated in FIG. 1 which also provides the network connection.
  • FECP Filtering Enabled Email Client Program
  • Network 110 which connects a number of Users 101 a- 101 c.
  • Network 110 may be a network such as the Internet or a commercial email network, or it may be a 101 c an email system which communicates internally between users of a single computer system.
  • Users 101 a- 101 c are interconnected to this network by one or more links 103 over which each User 101 may send and receive electronic messages (email).
  • the Network 110 connects any number of computer systems 101 a- 101 c, each being able to facilitate at least one user.
  • Each user attaches to and interacts with the Network 110 (and other Users 101 ) by means of a device, generally a computer, that sends, receives, interprets, and acts upon the signals transmitted across the network.
  • a device generally a computer, that sends, receives, interprets, and acts upon the signals transmitted across the network.
  • Each user 101 therefore represents not only an individual, but also the computing devices and email client programs that allow them to communicate over network 110 .
  • These computers may vary greatly in their construction and manner of use.
  • each will have, at the minimum, rudimentary capabilities to compose, send, receive, and manipulated electronic messages over network 110 by way of an email client program.
  • Filtering Enable Email Client Program 100 (and the user(s) that use it) has the same characteristics and capabilities as normal Users 101 , but also implements the various part of the message filtering system of the present invention.
  • the system and method according to the present invention allows the user to reduce the amount of junk email received from the network (and hence other users).
  • There may be multiple users on the network that implement a Filtering Enabled Email Client Program 100 but this discussion will focus on only one such user for the sake of clarity.
  • FEECP 100 is primarily a software application.
  • Each of FEECP 100 's composite components ( 105 , 106 , 107 , 108 , 109 , 114 , 115 ) are likewise primarily software modules. As such, all of them utilize some combination of processing time, memory, long-term storage, video displays, input devices, pointing devices, and other common computer elements, components, systems, and/or processes.
  • the exact computing requirements necessary to execute FEECP 100 will vary, but can easily be determined by someone skilled in the art.
  • FEECP 100 resides and operates on a reasonably powerful and reasonably configured computing device necessary to execute and carry out the described invention and each of its components. An individual skilled in the art could easily specify such a machine and most modern computing devices available to average consumers currently meet these criteria.
  • the Mail Processor 104 is the main transmission and processing component that retrieves and/or accepts incoming messages and filters them appropriately. Each incoming message is examined and processed by this component according to the flow chart in FIG. 7 . During these steps, the Mail Processor 104 will utilize some or all of the secondary components of the FEECP 100 . These secondary components include an Acceptance List 105 , a Blocking List 115 , Repository 106 , General and Legal Notices 107 , Message Folders 108 (a.n), a System Log File 114 and a User Mail Interface 109 .
  • These secondary components include an Acceptance List 105 , a Blocking List 115 , Repository 106 , General and Legal Notices 107 , Message Folders 108 (a.n), a System Log File 114 and a User Mail Interface 109 .
  • Mail Processor 104 also handles the transmission of electronic messages. All messages arrive and are sent via link 103 , but the specific process involved will vary depending on the messaging platform. On the Internet (the platform for this preferred embodiment), incoming mail will typically be retrieved from a message storage device located on the Network 110 called a POP3 or IMAP server. When commanded (perhaps from the user or after a certain time interval), Mail Processor 104 will access one or more of these “mailbox” servers and retrieve the user's messages (if any). As these messages are retrieved, they are processed and filtered according to flow chart FIG. 7 .
  • Mail Processor 104 will contact an SMTP mail server.
  • This server is similar to a conventional post office and accepts outgoing mail for delivery. Any outgoing mail is transmitted to such a server by Mail Processor 104 . Note that outgoing mail does not require any sort of filtering action and is delivered directly.
  • Acceptance List 105 contains zero or more email addresses or address patterns in a list—maintained on a non-volatile storage device—that can be retrieved, edited and saved.
  • the Acceptance List 105 contains email sender addresses (and therefore email senders) that are permitted to communicate unimpeded with the recipient. Any incoming message with a sender address contained in or matching a pattern on this Acceptance List will be permitted to reach the recipient.
  • This list may contain individual entries, such as “John_Smith@aol.com” (an Internet style address) or patterns such as “[all]@aol.com”. This pattern could indicate that all messages from senders in the “aol.com” domain should be accepted and passed on to the recipient unimpeded.
  • a feature of the method according to the present invention is the automatic creation and maintenance of this Acceptance List. Under normal circumstances, this invention will add entries to the acceptance List based upon the filtering process outlined in flow diagram, FIG. 7 . It is an option, however, for the user to manually add or delete an address or address pattern on this list, which could be done using User Interface 109 .
  • the Blocking List 115 like the Acceptance List 105 , also contains zero or more email address or address patterns in a list—also maintained on a non-volatile storage device—that can be retrieved, edited and saved. This list, however, performs the opposite function—any message with a sender address contained in or matching a pattern on the Blocking List 115 is filtered and blocked from reaching the recipient.
  • This list may contain individual entries, such as “John_Smith@aol.com” (Internet style address) or patterns such as “[all]@aol.com”.
  • Blocking List 115 is not actively maintained by the filtering process described in FIG. 7 . Instead, the blocking list is manually edited by the user.
  • the recipient i.e.—the user of this invention
  • the manual entry of blocking addresses would occur through the use of the User Interface 109 .
  • any incoming messages from that sender would be filtered and discarded.
  • Blocking List 115 preferably takes precedence over the Acceptance List 105 . If a message sender's address exists on or matches patterns on both the blocking and acceptance list, the message is blocked. This is necessary in order to have ultimate blocking control over an unwanted message sender who gains admission to the Acceptance List 105 (by correctly answering a Challenge).
  • the Mail Processor 104 when composing a Challenge, the Mail Processor 104 needs a prompt to place into the Challenge (which the sender must then answer and return). This prompt is taken from component 106 which stores one or more prompts and the acceptable answers to each of those prompts.
  • the prompts (and answers) stored in 106 could be entered as part of a pre-built, or commercial release of a method and system according to the present invention. This practice, however, would allow a junk email sender to procure the fixed prompt list and create an automated program capable of recognizing and answering the limited prompts therein. Instead, a feature of the present invention is that each user himself enters prompts (and answers) in to the Repository 106 (by using User Interface 109 .) by having each user compose and enter their own prompts, the possible permutations are limited only by human imagination. In such a case, it would be extremely difficult, if at all possible, to automate the answering of Challenges because the variety of possible prompts would be too great.
  • the user specifies, via User Interface 109 , the command to enter a new prompt. They can then enter a free-form block of text. This block of text should, in some way, be able to elicit a predictable, printable response from a human.
  • the User Interface 109 would then allow entry of one or more acceptable responses for the prompt. At that point the user must enter at least one acceptable answer to the previously entered prompt. The user may enter multiple correct answers. Any response to the Challenge prompt that matches one of the answers entered is considered a “valid” and correct response. When matching a response to valid answers, the user has the option of enabling certain features. One of these features is case insensitivity. If enabled, all matches to the answer list are performed without regard to case. A second feature causes whitespace (spaces, tabs, linefeeds, etc.) to be ignored. If selected, all whitespace characters are removed from the beginning and trailing edges of the challenge prompt responses and all groupings of multiple, adjacent whitespace characters within the prompt are replaced by a single space. This is done before comparisons are made to the acceptable list.
  • the user of this system could enter the following text as a prompt: “How many wheels on a car?”. For the list of valid responses, the user could enter: “4”, “four”, “for”, and “fore” (“for” and “fore” help accommodate human error). The user could enable the case insensitivity and whitespace ignore options. In this situation, the following Challenge responses (using that question) would be considered valid: “4”, “4”, “FOUR”, “FOUR”, and “foRe”.
  • Each prompt stored in 106 is given a designated reference number (such as prompt 1, prompt 2, etc.)
  • the Mail Processor 104 includes the reference number of the prompts used into a specially delimited area of the Challenge. Therefore, when the Challenge is returned by the sender, it can be easily scanned to retrieve the prompt reference number without requiring the parsing of the Challenge text to match the complete prompt word for word. In this same way, the sender's answer can also be easily extracted from the Challenge because it too can be located in a specially delimited area of the message. For more information on the construction and processing of a challenge please see THE CHALLENGE.
  • the system and method according to the present invention also uses a General Notice 116 and a Legal Notice 107 (below).
  • the General Notice (primarily text) is stored, maintained, and retrieved from the General Notice Repository 107 which stores the Notice on a non-volatile storage device.
  • the General Notice 107 can be modified through the use of User Interface 109 .
  • the General Notice preferably is the first thing that a sender reads when their message is returned (with the included Challenge). It can be anything the user wants. It is suggested, however, that this information describe the reason the sender's mail has been returned (i.e. predicted upon a proper response to a Challenge) and the process that the sender must complete in order to reach the recipient (instructions on completing the Challenge prompt and Legal Notice).
  • an alternate contact means such as an address or fax number where the recipient can be reached. This would be valuable if the sender, for some reason such as technical difficulties, cultural differences, or language differences, had trouble correctly responding to the Challenge. In such a situation, they could use the auxiliary contact means to reach the recipient. It would be important, however, to cover the auxiliary contact means in the Legal Notice as well as the recipient's email address.
  • the system and method according to the present invention also uses a Legal Notice.
  • This Legal Notice is stored, maintained (via User Interface 109 ) and retrieved from the Legal Notice Repository 107 .
  • the Legal Notice provides a means of stating and enforcing a legal agreement between the sender and receiver. It is preferable to state, to the effect, that the recipient does not accept unsolicited commercial communications. It should define and give specific examples of such communications. It would further state that appropriate legal action will be taken against any individual or company that violates the ban. And it should describe the fees and charges that will be levied for violating the agreement and improperly utilizing the recipient's time and computing resources. Other terms and conditions could be added at the discretion of the system user and based upon appropriate legal guidelines. The content described herein is for example purposes only.
  • This Legal Notice like the Challenge prompt from 106 , must also be answered correctly by the sender in order for the Challenge to be valid. Unlike the prompt from 106 , however, the correct answer to the Legal Notice is always an affirmation. For example, after reading the Legal Notice as part of the Challenge, the user would be prompted to type the word “AGREE” in a designated blank. The Legal Notice should specify that typing “AGREE” signals an understanding and agreement to the terms of the notice. If the sender does not agree to the Legal Notice, their email communication will be filtered and blocked upon being returned to Mail Processor 104 .
  • Email messages resident in the Filtering Enabled Email Client Program 100 are stored in categorized Message Folders 108 (a . . . n). These Message Folders (and the messages contained within them) are stored on non-volatile storage and can be retrieved, created, manipulated, and stored through the use of User Interface 109 . The messages contained (and to be contained) within the Message Folders can also be manipulated by the Mail Processor 104 during the process outlined in FIG. 7 .
  • Each Message Folder 108 (a . . . n) can be a distinguishing namex—chosen by the user of the system. All messages relating to a particular topic are categorized and stored in a Message Folder with an appropriate designation. (For example, all messages from a grandmother might be stored in a Message Folder entitled “Grandma”.) A tidy user can create Message Folders for the main topic areas that cover his correspondence.
  • this system preferably has two special-purpose default message folders—“New” and “Deleted”.
  • Mail Processor 104 places all incoming email messages that are not filtered and not blocked into the “New” folder.
  • Mail Processor 104 places all incoming email messages that are filtered and blocked into the “Deleted” folder.
  • the filtering and blocking process is outlined in FIG. 7 .
  • the user of this system examines the “New” message folder to read and manipulate any new messages which may have arrived.
  • the user may choose to delete a new message (thus moving it into the “Deleted” folder) or save and categorize it by moving it to a user-created message folder (like “Grandma”). Or, the user may simply leave the message in the “New” folder.
  • Messages that are deleted are placed in the “Deleted” system message folder.
  • the “Deleted” system message folder By placing a message in this folder, it is not actually deleted. Essentially is becomes marked for deletion which will occur at some future event.
  • This temporary holding of deleted messages allows the user to correct an accidental deletion or recover a wrongly filtered incoming message. To do so, the user simply moves the desired message out of the “Deleted” folder into another message folder.
  • the permanent deletion of items in the “Deleted” message folder can be configured by the user to occur after various events including manually, after a time interval, and after a certain amount of “Deleted” email has been accumulated.
  • Every significant action that the Filtering Enabled Email Client Program 100 performs is preferably, at the option of the user, logged to the system Log File 114 . Each action would be noted in this log along with specific information to make the entry useful. For example, an incoming message from “John_Smith@aol.com” whose address is on a Blocking List might cause a log file entry such as:
  • the recording of this information is valuable, for example, in order to assist the user in determining whether certain messages are being blocked or deleted incorrectly.
  • the User Interface 109 allows the user to manipulate, access, configure, and otherwise interact with the Invention and its components.
  • the User Interface 109 consists of both a software and hardware component.
  • the hardware component includes an output display device (such as a video monitor) and one or more input devices (keyboard, mouse, etc.).
  • the software component presents information and options to the user (via the display) and receives, interprets, and act upon commands from the user (input via the keyboard or similar device).
  • Each of the Filtering Enabled Email Client Program 100 components interacts with the user via the User Interface 109 .
  • FIG. 4 is another example of a networking system in which the present invention can operate.
  • the Filtering Enabled Email Client Program 100 from FIG. 3 has been split into two separate programs—Message Filtering Program 100 a′ and Email Client Program 100 b′.
  • both of these programs are resident and run on an appropriate computer system, but the systems can be separate (i.e. two computers, one running each component).
  • the Message Filtering Program 100 a′ contains all message filtering components of the present invention.
  • the Email Client Program 100 b′ consists of a normal email client and does not have the ability to filter incoming messages according to the present invention.
  • the Email Client Program 100 b′ will retrieve messages through the Message Filtering Program 100 a′. While messages are being retrieved, the Message Filtering Program 100 a′ will challenge, block and delete all appropriate message according to the flow diagram in FIG. 4 . Incoming messages which are not blocked are allowed to pass through to the Email Client Program 100 b′. And, as before, outgoing messages are transmitted unimpeded.
  • both programs have a User Interface ( 109 a′ and 109 b′). This allows the use and configuration of each program separately.
  • Each program also has a Mail Processor ( 104 a′ and 104 b′).
  • Mail Processor 104 b′ only has the ability to send and receive email.
  • Mail Processor 104 a′ retains the ability to analyze and filter incoming messages as well as also having the ability to send and receive mail (which come from and go to the Email Client Program).
  • FIG. 4 work as described with regard to the system of FIG. 3 .
  • FIG. 5 shows an example Internet email message 201 .
  • This message is composed of a message header 202 and message body 203 .
  • the message body 203 contains the substance of the message and is the part which is intended for the message recipient. It will typically include text, but may also include files, pictures, sound, video, etc. depending on the particular messaging system being used.
  • the message header 202 contains information about the message and the message body (“meta” data). This information usually includes the message sender, the message recipient, the subject of the message, the length of the message, the time the message was composed, etc. Many other pieces of information and combinations are possible.
  • FIG. 6 shows the composition of a Challenge 301 .
  • the Challenge is a section of text which is preferably inserted in the body 203 of an email message 201 . Once inserted, this newly modified message is returned to the sender.
  • the challenge consists of a Header 305 , General Notice 302 , Legal Notice 303 and Prompt 304 .
  • the sender's original message in the message body 203 is retained.
  • the Challenge text is simply placed in the message, preferably placed before the body of the text of the original message. This preserves the sender's original message so the recipient may view it if and when the Challenge is answered properly.
  • the beginning of the Challenge contains a Header 305 .
  • the header is an Invention specific block of text that identifies the presence of this Invention and the version of the Invention software. Other possible elements could include a copyright notice, a phone number or Web site address in order to purchase or inquire about the Invention, etc.
  • a Sample Header is shown below:
  • This token is specifically constructed of certain text sequences that are highly unlikely to occur in a typical message unless placed there intentionally. This token can therefore be searched for to determine if a Message 201 contains a Challenge 301 . This token would not only indicate the presence of a Challenge in an incoming message, but would also indicate the version of the software used to create it. The inclusion of a version number in the Challenge Header 305 would allow a program utilizing the method and system of the present invention to recognize and account for any differences among its implementations.
  • the General Notice 302 (retrieved from 107 of FIG. 3 ) is placed next in the Challenge. This will inform the user why their message has been returned and what they must do in order to reach the recipient.
  • the Legal Notice 303 a (retrieved from 107 of FIG. 3 ) is place next in the Challenge. This serves to warn the sender that only certain messages are accepted by the recipient and that penalties will be charged for violation.
  • the Mail Processor 104 When composing the Challenge 301 , the Mail Processor 104 will insert a blank, affirmation entry field 303 b into the text after the Legal Notice 303 a.
  • This field like the header token, will be delimited by certain predetermined characters that are chosen because of their unlikely probability of occurring in an email message unless placed there on purpose.
  • the affirmation blank 303 b could be constructed as such:
  • the Mail Processor 104 can scan a response (to a Challenge) and determine if the sender has correctly entered a proper response, such as “Agree”.
  • Prompt 304 a is retrieved from the Prompt Repository 106 and placed next in the Challenge 301 .
  • the Mail Processor 104 will insert a blank entry field 304 b into the Challenge 301 after the prompt. The sender will be instructed to answer the prompt and enter their response in the Answer Blank 304 b.
  • the Answer Blank 304 b will be delimited by predetermined characters that have a low probability of occurring naturally in an email message.
  • the Answer Blank 304 b could be constructed as:
  • the answer blank is preferably constructed differently in order to differentiate the two for searching and retrieval purposes.
  • the Answer Blank 304 b delimiters would include the reference number of the prompt which was being asked. In this case, the number 4 embedded in the delimiters would notify the Mail Processor 104 that the answer in blank 304 b is in response to Prompt number 4 from the Prompt Repository 107 .
  • the reference number assists the Mail Processor 104 in evaluating and processing a returned Challenge. Without use of the prompt reference number, the Mail Processor would have to parse the specific prompt text and attempt to match it with the exact prompt in the Prompt Repository 106 . This would be very unreliable since the Internet (and other mail systems) have a tendency to slightly, or even dramatically, reformat a message as it passes from a sender to a receiver.
  • the Answer Blank 304 b Since the Answer Blank 304 b is small and the delimiters are specifically chosen for their relative uniqueness, it becomes very easy to scan the message body 203 and extract these delimiters (and the contents between them). By adding the prompt reference number to a portion of one of the delimiters, it also becomes easy to extract. Once the prompt reference number is known, the answer in the Answer Blank 304 b can easily be compared and evaluated for correctness.
  • the Internet is one such system that allows the insertion of additional information into a message header 202 .
  • Additional information should also be placed into the Message Header. This additional information would indicate the presence of a Challenge, the version of this Invention used to create the Challenge, the Reference Number of the Prompt used in the Challenge, etc.
  • FIG. 7 shows a flow diagram of the Mail Filtering Process.
  • Mail Processor 104 traverses this diagram for each incoming message 201 . Recall that outgoing message are also handled by the Mail Processor, but do not undergo a filtering process. Instead, they are simply delivered to the Network 110 via Link 103 .
  • the Mail Processor 104 begins at Start 401 . It begins the filtering process after a signal of some kind. This signal could be, for example, notification from the Network 110 (via Link 103 ) that new mail is incoming; an explicit command from the user; or perhaps, after a certain time interval such as once every hour.
  • the Mail Processor queries the Network 110 to determine if any mail is incoming.
  • State 410 is the trivial case where there is no incoming mail. In this case, the Mail Processor has nothing to do and will stop. The Mail Processor will reawaken and begin again at Start 401 after one of the previously mentioned signals. Incoming message. Is it Properly Addressed to Recipient? 412
  • the incoming message is checked to see if it is properly addressed to the recipient.
  • the recipient might be a primary designated recipient (such as “TO:”) or a secondary recipient (such as “CC:” (carbon copy) or “BCC:” (blind carbon copy).
  • Any message which is not properly addressed to the recipient will be assumed to be a junk email communication and dealt with appropriately (typically deleted).
  • the user can configure various parameters which determine whether an incoming message is “properly” addressed to the recipient depending on such conditions as whether the recipient's email address is present in the message's recipient fields, which recipient field(s) the recipient's address appears in, how many secondary recipient addresses (those not belonging to the user) are present in the message's recipient fields, and which message recipient fields contain those secondary addresses.
  • a user it is possible for a user to receive a message which is not addressed to them in any way.
  • a message does not contain the user's email address (or name) in any of the message's recipient fields.
  • Such fields may include TO (which generally indicates the main message recipients), CC (which generally indicates carbon copy recipients), or perhaps BCC (which generally indicates blind carbon copy recipients).
  • TO which generally indicates the main message recipients
  • CC which generally indicates carbon copy recipients
  • BCC which generally indicates blind carbon copy recipients
  • the Mail Processor will transfer the message to the “Deleted” Message Folder 108 x (x being a number between a . . . n). The Mail Processor then proceeds back to 405 and checks for another incoming message.
  • the Mail Processor extracts the sender's address from the Message and determines if the sender's address is present on Blocking List 115 .
  • the Mail Processor will transfer the message to the “Deleted” Message Folder 108 x (x being a number between a . . . n). The Mail Processor then proceeds back to 405 and checks for another incoming message.
  • the Mail Processor has already determined that the Sender of the incoming message is not present on the Blocking List.
  • the Mail Processor now checks to see if the incoming message sender's address is on Acceptance List 105 .
  • the message will be accepted by the Mail Processor 104 and placed in the “New” message folder (for example, message folder) 108 x (x being a variable indicating one of the message folders 108 ).
  • the message has not been accepted or blocked based on the sender's address.
  • the Mail Processor must now determine if the incoming message contains a Challenge. To do this, the Mail Processor 104 scans the message body 203 for the Header 305 token (“ ⁇ ##Efilter;V1.2##>”). If found, the incoming message contains a Challenge.
  • the Mail Processor can also scan the Message Header 202 in messaging systems (such as the Internet) that allow non-standard additions to the portion of a message.
  • the message sender will be Challenged in an attempt to exclude junk email (which this message could be).
  • the Mail Processor 104 uses some simple heuristics to determine if the message sender's address is valid. As mentioned before, on the Internet, it is possible to send a message that doesn't include a valid sender address.
  • Various heuristics can be applied to an email address to determine if it is valid. These heuristics will vary depending on the messaging standards of the medium of transmission. On the Internet, for example, an email address must contain the symbol ‘@’. An email address without this symbol is invalid.
  • the Message Sender's Address is Invalid 445
  • sender's address is determined to be invalid, it is useless to create and return a Challenge because it will simply “bounce back” and be returned as “address unknown”. Messages with invalid sender addresses are moved by the Mail Processor 104 to the “Deleted” Message Folder 108 x.
  • the Mail Processor 104 will compose a Challenge 301 and attach it to the beginning of the original incoming message. This newly modified message (also referred to in its entirety as a “Challenge”) is then be returned to the message sender (delivered by Mail Processor 104 to the Network 110 ).
  • the Mail Processor extracts the Legal Notice response (in 303 b) and the Prompt response (including prompt reference number) (in 304 b) and evaluates them to determine if they are valid or not. Both responses must be valid in order to pass the Challenge.
  • a useful feature, anticipated, but not implemented in the preferred embodiment would involve a modification of the Acceptance List 105 . Recall that this list includes addresses of all sender's whose email messages may pass through, unimpeded, to the recipient. By adding extra information to the Acceptance List, it would be possible to automatically categorize all incoming messages. For example, an entry in the Acceptance List allowing a grandmother to communicate with the recipient might consist of:
  • This modified Acceptance List entry might look like:
  • the first entry is the sender address (or address pattern) to accept.
  • the second entry is the Message Folder in which to place all messages from the respective sender. Acceptance list entries are automatically generated. The user simply adds a message folder designation.
  • the method and system according to the present invention could be configured to create and return a Challenge in the native language of whatever domain the message originated from.
  • messages can arrive from different domains which represent different countries.
  • An incoming message from the “.jp” domain would indicate Japan and an appropriate Challenge in Japanese could be created and returned. All parts of the Challenge could be tailored to the message origination location including the Legal Notice, General Notice and Prompt.
  • a method and system for filtering unsolicited electronic commercial messages has been disclosed.
  • Software written according to the present invention is to be stored in some form of computer readable medium, such as memory or CD ROM, or transmitted over a network, and executed by a processor.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The present invention provides a system and method for filtering unsolicited electronic commercial messages. A system and method according to the present invention for screening out unsolicited commercial messages comprises the steps of receiving a message from a sender, sending a challenge back to the sender, receiving a response to the challenge, and determining if the response is a proper response.

Description

FIELD OF THE INVENTION
The present invention relates generally to the receipt of electronic messages, via the Internet for example, and more particularly, to a system and method for filtering unsolicited electronic commercial messages.
BACKGROUND OF THE INVENTION
By taking advantage of the growing popularity of the Internet, a user can send messages to a receiver located virtually anywhere in the world. There are a number of advantages to sending messages via electronic mail (email) rather than through the U.S. Postal Service. By using email, it may take only seconds for the sender's message to be received by a receiver on the other side of the world. The receiver can read the sender's text immediately on the screen, respond to it right away, save it for later, print it, or quickly forward it to another receiver. Messages a user receives can be organized into convenient electronic folders and saved for as long as the user wishes without taking up office space. Due to these advantages, email has become many people's principle means of communicating with the world.
A further function of electronic mail allows a user to create electronic mailing lists for sending notices to hundreds or even thousands of people at once. Due to the ease of sending electronic mail to a very large number of people, the number of mass mailings for unsolicited advertising has risen dramatically. Unlike advertisements through the U.S. Postal Service, it is not necessarily clear to the user that the message is for advertising purposes until the user opens and reads the message. Thus, the target of the unsolicited electronic commercial message must typically open the message, read a portion of it, then, after determining it to be unwanted “junk”, delete it. A user receiving several of these commercial messages can easily expend valuable time, resources and mental aggravation.
Companies and individuals in the business of mass commercial emailing have shown a reluctance to stop their practice or refrain from contacting recipients who do not want to receive promotions. This business, like traditional junk mail, is profitable. Since the cost of sending emails is so low, a junk e-mailer (commonly referred to as a “spammer”) benefits by contacting the largest and broadest group of recipients as possible—more recipients means more people who might be interested in the message—even if it also means a larger group of outraged recipients.
Members of the electronic community have tried to create numerous roadblocks to stop spamming—some electronic, some legal, and some with a business focus. Unfortunately, the junk email sending community has generally adapted to and overcome each one.
An attempt to request the advertiser to stop soliciting the user is typically severely hindered since it is common practice for advertisers to either not provide a reply address or to make up a false reply address. Since some email systems (the Internet in particular) do not require a valid reply address nor a valid sender name, most ads can be repeatedly sent to thousands of people without giving the recipients a convenient method to request that they be taken off the advertiser's list. Spammers who do provide valid reply information are often unresponsive to requests to desist. Accordingly, thousands of email users must suffer through a barrage of unwanted email advertisements which typically must be opened in order to determine that it is an (unwanted) advertisement. In lieu of a valid email reply address, some of these unsolicited commercial messages will give a non toll-free number. In order to contact the advertiser, the user must pay for a phone call which may be long distance.
There is currently an attempt to address these issues of unsolicited commercial messages by legislative means. However, since it is relatively simple for an advertiser to access a server virtually anywhere in the world in order to send his unsolicited commercial message to anywhere else in the world, U.S. legislation may have, at best, a limited effect on the problem.
Some users have tried to avoid this problem by posting notices threatening to sue if unsolicited commercial messages are sent to them. However, since most unsolicited commercial messages are sent to thousands of people at a given time, it is quite likely that the advertisers would never see the notice.
Accordingly, what is needed is an effective system and method for filtering unsolicited electronic commercial messages. The present invention addresses such a need.
SUMMARY OF THE INVENTION
The present invention provides a system and method for filtering unsolicited electronic commercial messages. A system and method according to the present invention for screening out unsolicited commercial messages comprises the steps of receiving a message from a sender, sending a prompt back to the sender, receiving a response to the prompt, and determining if the response is a proper response.
According to the present invention, when an electronic message is received, unless the sender is part of a list of senders to accept messages from, it is determined if the sender address is a valid address. If the sender address is not a valid address, then it can be assumed that it is an unsolicited commercial message. However, if the sender address is valid, then a prompt is sent to the sender. The prompt can be any question which can be answered by a person but typically not by a computer system. If a correct response to the prompt is received thereafter, then the message can be assumed not to be a mass mailed unsolicited commercial message, and accordingly is not filtered out. If incorrect, the message is filtered.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of a computer system in which the present invention can reside.
FIG. 2 is a block diagram of a network in which the present invention can operate.
FIG. 3 is an example of a networking system in which the present invention can operate.
FIG. 4 is another example of a networking system in which the present invention can operate.
FIG. 5 is a diagram of a typical electronic message.
FIG. 6 is an example of a challenge and its components according to the present invention.
FIG. 7 is a flow diagram of a method according to the present invention.
DESCRIPTION OF THE INVENTION
The present invention relates to a system and method for screening out unsolicited commercial messages. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.
Although the present invention is described in terms of a system which receives e-mail, it is to be understood that email is merely an example in which the present invention can be applied. For instance, the present invention can also be applied to electronic messages in video form wherein unsolicited commercial messages can be sent via video.
In an attempt to solve some of the problems related to unsolicited commercial messages in the electronic medium, a message filter is currently available. However, it has been found that the conventional message filter is highly ineffective in screening out unsolicited commercial messages.
Conventional message filtering involves the use of a mail filter in an email recipient's local email system. Such a filter typically sorts incoming email for the recipient into categories determined by the recipient. The filter typically simply scans elements of each email message as it reaches the recipient and determines what category it should be placed in depending on certain criteria. One category is “discard”. Messages which the filter places in the discard category are automatically discarded, but in practice the direct deletion of messages via a filter is extremely risky. A perfect filter would catch and dispose of all junk messages and retain all non-junk messages, but such a filter has yet to be demonstrated. This imperfection is primarily caused by the inability of most filters to determine what constitutes “junk email”. For this reason, most filter designs take a different approach and move suspected junk messages to a temporary or miscellaneous holding category for review by the recipient before deletion. Invariably, desired messages are accidentally marked for deletion and junk messages slip through the filter. The user must typically manually correct these mistakes.
Conventional filters have had varying degrees of intelligence; some have simply worked with lists of mail addresses and have sorted messages according to the source of the message; others have used keywords provided by the recipient to sort; with others, finally, the filter observes how the recipient sorts his email and is then able to sort in a similar fashion (usually by utilizing a combination of the two previous methods—source lists or keyword/content searches).
Each of the message filtering methods has weaknesses that can and typically are exploited by junk email senders. The source list method requires a message sender to be on a list (either an acceptance or blocking list) in order to permit the filter to take action. A message from an unknown sender (frequently a solicitor) cannot be discarded because it might be from, for example, a new business contact or a long-lost friend. By constantly using new sender addresses, a solicitor can assure that junk messages will pass through a source list filter and come to rest in a temporary or miscellaneous category reserved for messages that are not actionable. Messages in this category must typically, at least briefly, be scanned by the recipient—a successful defeat of the filtering mechanism. The second method—keyword/content searching—has the potential of discarding wanted, as well as unwanted, messages. Any keyword or phrase search (with the intention of identifying and dealing with particular message subject matters) will eventually discard a bona fide message that appears to be “junk” in nature. For example, searching and discarding all messages with the words “make money” in them might get rid of some junk messages, but it will also eventually discard a desired message such as a new business idea from a brother or sister that happens to use the same words or word patterns. Again, the flaws in this approach force most implementations to place incoming messages in a temporary holding category. And again the messages in this category will, at least briefly, be scanned by the recipient a success for the solicitor.
It should be noted that there are some message filtering techniques that rely upon the sender to indicate the subject or target audience of their message. The recipient's filter can then look for and operate on these messages with the recipients best interests in mind. These can work successfully, for example, in a corporate environment where both the senders and recipients have a working relationship and an active interest in effectively using each other's time and communication resources wisely. For example, all incoming resumes might be marked as high priority for a human resources manager, but the sender would have to indicate, via a predetermined method, that the content of the message was a resume. The human resource recipient could then configure their email processing system to categorize and correctly handle these resumes. These techniques are ineffective, however, when the sender is not cooperative and uninterested in having their messages intercepted and screened by this mechanism. Most junk email senders on the Internet fall into this category. The business of sending junk email is typically profitable, legal, and effective. There is no incentive for such an individual or company to actively make it easier for recipients to discard or ignore their messages. Indeed, most spammers make money by emailing more individuals, not less. Any technique, therefore, that attempts to stop this flow of unwelcome messages, can not rely on the cooperation of the message senders. In fact, this group has shown the exact opposite tendency in actively pursuing means of circumventing any and all filtering techniques.
Even if these filtering techniques provided a reasonable means of relief from the junk email onslaught, they still suffer from the need to be actively maintained. For example, source lists must continually be updated as solicitors use new sender addresses. And keyword lists must be continually modified as solicitors send widely varying and extremely creative messages which resemble legitimate communications. In either case, the temporary holding category must typically be reviewed for mistakes and the filtering apparatus must be maintained. Junk email usually causes frustration because of the time wasted in dealing with it. The use of conventional message filters has simply traded one means of spending time with another with no net gain.
Accordingly, what is needed is an effective system and method for screening out unsolicited electronic commercial messages. The present invention addresses such a need.
A feature of the present invention is the checking of incoming messages to verify that they include valid sender information. Any message which does not contain a valid sender address is assumed to be a junk email communication and is dealt with appropriately (generally deleted).
The “validity” of a sender address will depend on the specifics of whatever communication system is being used. On the Internet, for example, a sender address cannot contain certain characters (such as ‘control’ characters), must include an AT “@” symbol, and must be from a registered domain name. Each of these requirements (as well as others) can be checked. A sender address which violates any of them would be invalid.
Another feature of the present invention is the checking of incoming messages to verify that each message is properly addressed to the user (the recipient). For example, a message which is not addressed to the recipient will be assumed to be a junk email communication and dealt with appropriately (generally deleted).
When determining whether an incoming message is actually addressed to the recipient, the method according to the present invention will consider various appropriate recipient designations for the messaging system being used. In other words, it is possible that the recipient will receive a valid message that is not directly addressed to him. Instead, he might be a CC (carbon copy) recipient, or perhaps a BCC (blind carbon copy) recipient. There may be other possible message recipient designations. As long as the invention user's address is present on at least one of these recipient designations the message is considered valid. If the user's address is absent from all of these recipient groups the incoming message is considered junk email.
Yet another feature of the invention is that it prompts unrecognized email senders, for example, by returning their message and asking them a predetermined question or one of a set of predetermined questions:
    • “What color is an orange?”
    • “What is the ocean made of?”
    • “Fire is not cold, it is ?”
    • “How many wheels on a car?”
    • “Muhammad Ali is a (a) boxer, (b) man, (c) horse, (d) airplane.
    • Choose all that apply.”
Most humans can answer these questions, but it would be an enormous task to do so with a computer. In order to communicate with the recipient, the sender must correctly answer the question they are asked.
Preferably a block of text is added to the beginning of an incoming email message from an unknown sender. The sender's original message is preferably preserved. This block of text is referred to as a Challenge and contains, among other elements, a prompt, such as a question similar to those above. It also contains an answer blank area where the sender is requested to place their response to the prompt. After adding the Challenge text to the original message, thereby creating a modified message, the modified message, is returned to the sender. The sender must answer the Challenge (which includes the prompt) and send it back to the recipient. Upon receiving a completed Challenge, the answers are checked for validity. If the answers are correct, the message is forwarded to the recipient. Otherwise the message is blocked and discarded.
Recall that many senders purposely make themselves unreachable. If they are not reachable, they will never receive the Challenge and their messages will automatically be discarded.
If, on the other hand, they provide accurate sender information they will be inundated by Challenges from users of this invention, in addition to vast quantities of undeliverable returned messages and other detritus. In order to reach users of this invention, the spammer must staff relatively large banks of people to answer these Challenges (because a computer cannot). The staff to sort through the incoming mess of messages and manually answer Challenges will cost money and hurt the profitability of the junk email business. Many in the business would likely choose to avoid this step by either not including a sender address or ignoring all returned email—in either case their unwanted transmissions do not reach a user of the method and system according to the present invention.
FIG. 1 is a block diagram of a system in which the present invention can reside. The computer system 10 is shown to include a display 12, a keyboard 14, a pointing device 16, a processor 18, a memory 20, a disk drive 22, and a Network interface 24. These various components are shown to be coupled to a system bus 26.
FIG. 2 is a block diagram of networking system with which the present invention can work. The Internet system 50 is shown to include mail servers 52a-52c which utilize the standard protocol of Simple Mail Transfer Protocol (SMTP). A message 54 can be sent via one of the SMTP servers, such as the server 52a. The message may be passed through several servers before reaching its final destination, in this example, the server 52c. Once the message is received by the destination receiver 52c, then it is typically sent to a mailbox 56, such as a Post Office Protocol box (POP) or Internet Message Access Protocol box (IMAP) where it is held pending retrieval by an Email Client Program 60. During message retrieval, the message can be filtered through the Message Filter Program 58. Note that the Message Filter 58 according to the present invention can be located in various locations including between the Mailbox 56 and the user's Email Client Program 60; as part of mailbox servers such as Mailbox 56, or in the Email Client Program 60 which actually processes the user's messages. In the example shown in FIG. 2, the Message Filter 58 according to the present invention is shown to be located between the Mailbox 56 and the Email Client Program 60. In the following figure (FIG. 3), the message filter is shown incorporated into the Email Client Program.
FIG. 3 is an example of a networking system in which the present invention can operate. Filtering Enabled Email Client Program 100 is shown communicating with a Network 110 that facilitates communication among other members of the network. Filtering Enabled Email Client Program (FEECP) 100 is resident and actively run on a computer system illustrated in FIG. 1 which also provides the network connection.
Filtering Enabled Email Client Program 100 communicates with Network 110 which connects a number of Users 101a-101c. Network 110 may be a network such as the Internet or a commercial email network, or it may be a 101c an email system which communicates internally between users of a single computer system. Users 101a-101c are interconnected to this network by one or more links 103 over which each User 101 may send and receive electronic messages (email).
The Network 110 connects any number of computer systems 101a-101c, each being able to facilitate at least one user. Each user attaches to and interacts with the Network 110 (and other Users 101) by means of a device, generally a computer, that sends, receives, interprets, and acts upon the signals transmitted across the network. Each user 101, therefore represents not only an individual, but also the computing devices and email client programs that allow them to communicate over network 110. These computers may vary greatly in their construction and manner of use. They may contain different configurations of logic processing software and may have different capabilities (for example, some may have email client mail filters like this invention and some may not.) For the sake of this discussion, each will have, at the minimum, rudimentary capabilities to compose, send, receive, and manipulated electronic messages over network 110 by way of an email client program.
Filtering Enable Email Client Program 100 (and the user(s) that use it) has the same characteristics and capabilities as normal Users 101, but also implements the various part of the message filtering system of the present invention. The system and method according to the present invention allows the user to reduce the amount of junk email received from the network (and hence other users). There may be multiple users on the network that implement a Filtering Enabled Email Client Program 100, but this discussion will focus on only one such user for the sake of clarity.
Filtering Enabled Email Client Program (FEECP) 100
As a whole, FEECP 100 is primarily a software application. Each of FEECP 100's composite components (105, 106, 107, 108, 109, 114, 115) are likewise primarily software modules. As such, all of them utilize some combination of processing time, memory, long-term storage, video displays, input devices, pointing devices, and other common computer elements, components, systems, and/or processes. The exact computing requirements necessary to execute FEECP 100 will vary, but can easily be determined by someone skilled in the art. In general, FEECP 100 resides and operates on a reasonably powerful and reasonably configured computing device necessary to execute and carry out the described invention and each of its components. An individual skilled in the art could easily specify such a machine and most modern computing devices available to average consumers currently meet these criteria.
The Mail Processor 104 is the main transmission and processing component that retrieves and/or accepts incoming messages and filters them appropriately. Each incoming message is examined and processed by this component according to the flow chart in FIG. 7. During these steps, the Mail Processor 104 will utilize some or all of the secondary components of the FEECP 100. These secondary components include an Acceptance List 105, a Blocking List 115, Repository 106, General and Legal Notices 107, Message Folders 108 (a.n), a System Log File 114 and a User Mail Interface 109.
As mentioned, Mail Processor 104 also handles the transmission of electronic messages. All messages arrive and are sent via link 103, but the specific process involved will vary depending on the messaging platform. On the Internet (the platform for this preferred embodiment), incoming mail will typically be retrieved from a message storage device located on the Network 110 called a POP3 or IMAP server. When commanded (perhaps from the user or after a certain time interval), Mail Processor 104 will access one or more of these “mailbox” servers and retrieve the user's messages (if any). As these messages are retrieved, they are processed and filtered according to flow chart FIG. 7.
To send a message on the Internet, Mail Processor 104 will contact an SMTP mail server. This server is similar to a conventional post office and accepts outgoing mail for delivery. Any outgoing mail is transmitted to such a server by Mail Processor 104. Note that outgoing mail does not require any sort of filtering action and is delivered directly.
Acceptance List 105 contains zero or more email addresses or address patterns in a list—maintained on a non-volatile storage device—that can be retrieved, edited and saved.
The Acceptance List 105 contains email sender addresses (and therefore email senders) that are permitted to communicate unimpeded with the recipient. Any incoming message with a sender address contained in or matching a pattern on this Acceptance List will be permitted to reach the recipient.
This list may contain individual entries, such as “John_Smith@aol.com” (an Internet style address) or patterns such as “[all]@aol.com”. This pattern could indicate that all messages from senders in the “aol.com” domain should be accepted and passed on to the recipient unimpeded.
A feature of the method according to the present invention is the automatic creation and maintenance of this Acceptance List. Under normal circumstances, this invention will add entries to the acceptance List based upon the filtering process outlined in flow diagram, FIG. 7. It is an option, however, for the user to manually add or delete an address or address pattern on this list, which could be done using User Interface 109.
The Blocking List 115, like the Acceptance List 105, also contains zero or more email address or address patterns in a list—also maintained on a non-volatile storage device—that can be retrieved, edited and saved. This list, however, performs the opposite function—any message with a sender address contained in or matching a pattern on the Blocking List 115 is filtered and blocked from reaching the recipient.
This list, just like the Acceptance List 105, may contain individual entries, such as “John_Smith@aol.com” (Internet style address) or patterns such as “[all]@aol.com”.
Unlike Acceptance List 105, the Blocking List 115 is not actively maintained by the filtering process described in FIG. 7. Instead, the blocking list is manually edited by the user.
If an email solicitor correctly answers a Challenge and reaches the recipient against his wishes, the recipient (i.e.—the user of this invention) can manually add the sender's address to Blocking List 115. (The manual entry of blocking addresses would occur through the use of the User Interface 109.) From that point forward, any incoming messages from that sender would be filtered and discarded.
Note that the Blocking List 115 preferably takes precedence over the Acceptance List 105. If a message sender's address exists on or matches patterns on both the blocking and acceptance list, the message is blocked. This is necessary in order to have ultimate blocking control over an unwanted message sender who gains admission to the Acceptance List 105 (by correctly answering a Challenge).
Referring now to the prompt and answer repository 106, when composing a Challenge, the Mail Processor 104 needs a prompt to place into the Challenge (which the sender must then answer and return). This prompt is taken from component 106 which stores one or more prompts and the acceptable answers to each of those prompts.
The prompts (and answers) stored in 106 could be entered as part of a pre-built, or commercial release of a method and system according to the present invention. This practice, however, would allow a junk email sender to procure the fixed prompt list and create an automated program capable of recognizing and answering the limited prompts therein. Instead, a feature of the present invention is that each user himself enters prompts (and answers) in to the Repository 106 (by using User Interface 109.) by having each user compose and enter their own prompts, the possible permutations are limited only by human imagination. In such a case, it would be extremely difficult, if at all possible, to automate the answering of Challenges because the variety of possible prompts would be too great.
When creating and entering a prompt, a user should arrive to pick a topic and level of difficulty that do not exceed the mental capabilities with those whom they expect to communicate. Choosing prompts that few people could answer will have the effect of unintentionally blocking desired communications. (Note—specialized or difficult prompts could have a beneficial effect. A user could choose questions of a very personal nature so only people very close to him would succeed in being able to correctly answer a Challenge and therefore communicate. This might be a desired approach for wealthy or famous people.)
To enter a prompt, the user specifies, via User Interface 109, the command to enter a new prompt. They can then enter a free-form block of text. This block of text should, in some way, be able to elicit a predictable, printable response from a human.
The User Interface 109 would then allow entry of one or more acceptable responses for the prompt. At that point the user must enter at least one acceptable answer to the previously entered prompt. The user may enter multiple correct answers. Any response to the Challenge prompt that matches one of the answers entered is considered a “valid” and correct response. When matching a response to valid answers, the user has the option of enabling certain features. One of these features is case insensitivity. If enabled, all matches to the answer list are performed without regard to case. A second feature causes whitespace (spaces, tabs, linefeeds, etc.) to be ignored. If selected, all whitespace characters are removed from the beginning and trailing edges of the challenge prompt responses and all groupings of multiple, adjacent whitespace characters within the prompt are replaced by a single space. This is done before comparisons are made to the acceptable list.
Other features are also conceivable. For example, it would be possible for the comparison mechanism to understand common misspellings of words and compensate before determining the validity of a response. Many of today's word processors have this ability.
Prompt and Answer Example:
The user of this system could enter the following text as a prompt: “How many wheels on a car?”. For the list of valid responses, the user could enter: “4”, “four”, “for”, and “fore” (“for” and “fore” help accommodate human error). The user could enable the case insensitivity and whitespace ignore options. In this situation, the following Challenge responses (using that question) would be considered valid: “4”, “4”, “FOUR”, “FOUR”, and “foRe”.
Each prompt stored in 106 is given a designated reference number (such as prompt 1, prompt 2, etc.) When composing a Challenge, the Mail Processor 104 includes the reference number of the prompts used into a specially delimited area of the Challenge. Therefore, when the Challenge is returned by the sender, it can be easily scanned to retrieve the prompt reference number without requiring the parsing of the Challenge text to match the complete prompt word for word. In this same way, the sender's answer can also be easily extracted from the Challenge because it too can be located in a specially delimited area of the message. For more information on the construction and processing of a challenge please see THE CHALLENGE.
There is a benefit to having multiple prompts in the Prompt Repository 106—it becomes possible to rotate or vary the prompt used for each Challenge. By having multiple prompts and rotating their use, it becomes difficult for a person or organization to catalog all the prompts used by a particular person and use this knowledge in an attempt to automate Challenge responses to that individual. For example, if a user of the Invention always used the question, “What color is an orange?”, a solicitation company could record the answer and automate mailings to that individual by programming software to automatically respond with “orange” to any Challenge from that individual. The use of a large prompt repository makes this unlikely.
General Notice Repository 116
Besides a Challenge prompt, the system and method according to the present invention also uses a General Notice 116 and a Legal Notice 107 (below). The General Notice (primarily text) is stored, maintained, and retrieved from the General Notice Repository 107 which stores the Notice on a non-volatile storage device. The General Notice 107 can be modified through the use of User Interface 109.
The General Notice preferably is the first thing that a sender reads when their message is returned (with the included Challenge). It can be anything the user wants. It is suggested, however, that this information describe the reason the sender's mail has been returned (i.e. predicted upon a proper response to a Challenge) and the process that the sender must complete in order to reach the recipient (instructions on completing the Challenge prompt and Legal Notice). In addition, it might be advisable to include an alternate contact means such as an address or fax number where the recipient can be reached. This would be valuable if the sender, for some reason such as technical difficulties, cultural differences, or language differences, had trouble correctly responding to the Challenge. In such a situation, they could use the auxiliary contact means to reach the recipient. It would be important, however, to cover the auxiliary contact means in the Legal Notice as well as the recipient's email address.
Legal Notice Repository 107
Besides the General Notice 116, the system and method according to the present invention also uses a Legal Notice. This Legal Notice is stored, maintained (via User Interface 109) and retrieved from the Legal Notice Repository 107. The Legal Notice provides a means of stating and enforcing a legal agreement between the sender and receiver. It is preferable to state, to the effect, that the recipient does not accept unsolicited commercial communications. It should define and give specific examples of such communications. It would further state that appropriate legal action will be taken against any individual or company that violates the ban. And it should describe the fees and charges that will be levied for violating the agreement and improperly utilizing the recipient's time and computing resources. Other terms and conditions could be added at the discretion of the system user and based upon appropriate legal guidelines. The content described herein is for example purposes only.
This Legal Notice, like the Challenge prompt from 106, must also be answered correctly by the sender in order for the Challenge to be valid. Unlike the prompt from 106, however, the correct answer to the Legal Notice is always an affirmation. For example, after reading the Legal Notice as part of the Challenge, the user would be prompted to type the word “AGREE” in a designated blank. The Legal Notice should specify that typing “AGREE” signals an understanding and agreement to the terms of the notice. If the sender does not agree to the Legal Notice, their email communication will be filtered and blocked upon being returned to Mail Processor 104.
Message Folders 108
Email messages resident in the Filtering Enabled Email Client Program 100 are stored in categorized Message Folders 108(a . . . n). These Message Folders (and the messages contained within them) are stored on non-volatile storage and can be retrieved, created, manipulated, and stored through the use of User Interface 109. The messages contained (and to be contained) within the Message Folders can also be manipulated by the Mail Processor 104 during the process outlined in FIG. 7.
Each Message Folder 108(a . . . n) can be a distinguishing namex—chosen by the user of the system. All messages relating to a particular topic are categorized and stored in a Message Folder with an appropriate designation. (For example, all messages from a grandmother might be stored in a Message Folder entitled “Grandma”.) A tidy user can create Message Folders for the main topic areas that cover his correspondence.
In addition to user created message folders, this system preferably has two special-purpose default message folders—“New” and “Deleted”. Mail Processor 104 places all incoming email messages that are not filtered and not blocked into the “New” folder. Mail Processor 104 places all incoming email messages that are filtered and blocked into the “Deleted” folder. The filtering and blocking process is outlined in FIG. 7.
The user of this system examines the “New” message folder to read and manipulate any new messages which may have arrived. The user may choose to delete a new message (thus moving it into the “Deleted” folder) or save and categorize it by moving it to a user-created message folder (like “Grandma”). Or, the user may simply leave the message in the “New” folder. These options (and others conceivably) are performed at the wish of the user via User Interface 109.
Messages that are deleted (either by the Mail Processor 104 or manually by the user) are placed in the “Deleted” system message folder. By placing a message in this folder, it is not actually deleted. Essentially is becomes marked for deletion which will occur at some future event. This temporary holding of deleted messages allows the user to correct an accidental deletion or recover a wrongly filtered incoming message. To do so, the user simply moves the desired message out of the “Deleted” folder into another message folder. The permanent deletion of items in the “Deleted” message folder can be configured by the user to occur after various events including manually, after a time interval, and after a certain amount of “Deleted” email has been accumulated.
Log File 114
Every significant action that the Filtering Enabled Email Client Program 100 performs is preferably, at the option of the user, logged to the system Log File 114. Each action would be noted in this log along with specific information to make the entry useful. For example, an incoming message from “John_Smith@aol.com” whose address is on a Blocking List might cause a log file entry such as:
    • “BLOCKED: ‘John_Smith@aol.com’ on Jul. 3, 1997 2:34 pm. Subject of message: ‘Real Estate Deal’”
The recording of this information is valuable, for example, in order to assist the user in determining whether certain messages are being blocked or deleted incorrectly.
User Interface 109
The User Interface 109 allows the user to manipulate, access, configure, and otherwise interact with the Invention and its components. The User Interface 109 consists of both a software and hardware component. The hardware component, at the minimum, includes an output display device (such as a video monitor) and one or more input devices (keyboard, mouse, etc.). The software component presents information and options to the user (via the display) and receives, interprets, and act upon commands from the user (input via the keyboard or similar device).
Each of the Filtering Enabled Email Client Program 100 components interacts with the user via the User Interface 109. Some examples of what the user can do:
Log File 114
    • Read the log file
    • Delete the log file
      Mail Processor 104
    • Change incoming message filtering options
    • Send outgoing mail
      Acceptance List 105 and Blocking List 115
    • Clear either or both lists
    • Add an address or address pattern to either list
    • View entries on either list
      Prompt & Answer Repository 106
    • View the prompts and answers currently entered
    • Edit prompts and/or answers currently entered
    • Enter new prompts and answers
    • Delete prompts and answers
      General Notice 116 and Legal Notice 107
    • View either or both notices
    • Modify either or both notices
      Message Folders 108(a . . . n)
    • View or Read mail in any of the a.n folders
    • Delete mail from a folder
    • Delete a folder
    • Create a new folder
    • Rename a folder
    • Move or Copy mail from one folder to another
This list only shows some of the functions possible via the User Interface 109. Anyone skilled in the art will immediately recognize numerous other capabilities, but these will not alter the basic principles outlined above.
FIG. 4 is another example of a networking system in which the present invention can operate. In this example, the Filtering Enabled Email Client Program 100 from FIG. 3 has been split into two separate programs—Message Filtering Program 100a′ and Email Client Program 100b′. As before, both of these programs are resident and run on an appropriate computer system, but the systems can be separate (i.e. two computers, one running each component).
The Message Filtering Program 100a′ contains all message filtering components of the present invention. The Email Client Program 100b′ consists of a normal email client and does not have the ability to filter incoming messages according to the present invention. During normal operation of FIG. 4, the Email Client Program 100b′ will retrieve messages through the Message Filtering Program 100a′. While messages are being retrieved, the Message Filtering Program 100a′ will challenge, block and delete all appropriate message according to the flow diagram in FIG. 4. Incoming messages which are not blocked are allowed to pass through to the Email Client Program 100b′. And, as before, outgoing messages are transmitted unimpeded.
In this figure, both programs have a User Interface (109a′ and 109b′). This allows the use and configuration of each program separately. Each program also has a Mail Processor (104a′ and 104b′). In this figure, Mail Processor 104b′ only has the ability to send and receive email. Mail Processor 104a′, however, retains the ability to analyze and filter incoming messages as well as also having the ability to send and receive mail (which come from and go to the Email Client Program).
Except for these differences, the components of FIG. 4 work as described with regard to the system of FIG. 3.
FIG. 5 shows an example Internet email message 201. This message is composed of a message header 202 and message body 203. The message body 203 contains the substance of the message and is the part which is intended for the message recipient. It will typically include text, but may also include files, pictures, sound, video, etc. depending on the particular messaging system being used. The message header 202 contains information about the message and the message body (“meta” data). This information usually includes the message sender, the message recipient, the subject of the message, the length of the message, the time the message was composed, etc. Many other pieces of information and combinations are possible.
FIG. 6 shows the composition of a Challenge 301. The Challenge is a section of text which is preferably inserted in the body 203 of an email message 201. Once inserted, this newly modified message is returned to the sender. The challenge consists of a Header 305, General Notice 302, Legal Notice 303 and Prompt 304.
During insertion of the Challenge into the sender's message, the sender's original message in the message body 203 is retained. The Challenge text is simply placed in the message, preferably placed before the body of the text of the original message. This preserves the sender's original message so the recipient may view it if and when the Challenge is answered properly.
Challenge
The beginning of the Challenge contains a Header 305. The header is an Invention specific block of text that identifies the presence of this Invention and the version of the Invention software. Other possible elements could include a copyright notice, a phone number or Web site address in order to purchase or inquire about the Invention, etc. A Sample Header is shown below:
    • <##Efilter;V1.2##> EFILTER Electronic Message Filtering System Copyright © 1997 High-Tech Industries.
    • For information about purchasing, contact 800-999-9999 or
    • http://www.acme.com
In this header, it is important to note the “<##Efilter;V1.2##>”. This will be referred to as a token and is similar to the Legal Answer Blank 303b and Prompt Answer Blank 304b delimiters.
This token is specifically constructed of certain text sequences that are highly unlikely to occur in a typical message unless placed there intentionally. This token can therefore be searched for to determine if a Message 201 contains a Challenge 301. This token would not only indicate the presence of a Challenge in an incoming message, but would also indicate the version of the software used to create it. The inclusion of a version number in the Challenge Header 305 would allow a program utilizing the method and system of the present invention to recognize and account for any differences among its implementations.
The General Notice 302 (retrieved from 107 of FIG. 3) is placed next in the Challenge. This will inform the user why their message has been returned and what they must do in order to reach the recipient.
The Legal Notice 303a (retrieved from 107 of FIG. 3) is place next in the Challenge. This serves to warn the sender that only certain messages are accepted by the recipient and that penalties will be charged for violation.
When composing the Challenge 301, the Mail Processor 104 will insert a blank, affirmation entry field 303b into the text after the Legal Notice 303a. This field, like the header token, will be delimited by certain predetermined characters that are chosen because of their unlikely probability of occurring in an email message unless placed there on purpose. For example, the affirmation blank 303b could be constructed as such:
    • “###>> <<###”
      The choice of three pound signs and then two greater than symbols (with the opposite at the end of the entry blank) would be extremely unlike to occur in a normal email message unless placed there on purpose.
The original sender of the message would be instructed to type the word “AGREE” in the entry space between the two delimiters thereby signaling their understanding and agreement to the Legal Notice.
    • “###>>AGREE<<###”
By searching for these delimiters (and what is contained between them), the Mail Processor 104 can scan a response (to a Challenge) and determine if the sender has correctly entered a proper response, such as “Agree”.
Rather than “agree”, another word or phrase or even a varying range of affirmative responses can be used. This could be set up similar to the Challenge prompt such that a different affirmative response is required for each Challenge. By doing this, it would become difficult for an email solicitor to automate the response to the Legal Notice.
Prompt 304a
Prompt 304a is retrieved from the Prompt Repository 106 and placed next in the Challenge 301.
As in the case of the Legal Notice Affirmation Blank 303b, the Mail Processor 104 will insert a blank entry field 304b into the Challenge 301 after the prompt. The sender will be instructed to answer the prompt and enter their response in the Answer Blank 304b. As also in the previous case (303b), the Answer Blank 304b will be delimited by predetermined characters that have a low probability of occurring naturally in an email message. For example, the Answer Blank 304b could be constructed as:
    • “##>>> <<<##4#”
Unlike the Legal Affirmation blank 303a, the answer blank is preferably constructed differently in order to differentiate the two for searching and retrieval purposes. Also unlike Legal Notice Answer Blank 303b, the Answer Blank 304b delimiters would include the reference number of the prompt which was being asked. In this case, the number 4 embedded in the delimiters would notify the Mail Processor 104 that the answer in blank 304b is in response to Prompt number 4 from the Prompt Repository 107.
The reference number assists the Mail Processor 104 in evaluating and processing a returned Challenge. Without use of the prompt reference number, the Mail Processor would have to parse the specific prompt text and attempt to match it with the exact prompt in the Prompt Repository 106. This would be very unreliable since the Internet (and other mail systems) have a tendency to slightly, or even dramatically, reformat a message as it passes from a sender to a receiver.
Since the Answer Blank 304b is small and the delimiters are specifically chosen for their relative uniqueness, it becomes very easy to scan the message body 203 and extract these delimiters (and the contents between them). By adding the prompt reference number to a portion of one of the delimiters, it also becomes easy to extract. Once the prompt reference number is known, the answer in the Answer Blank 304b can easily be compared and evaluated for correctness.
In addition to adding a reference number to each answer blank, it would also be beneficial to encrypt the reference number. Without encrypting the number, it becomes possible for an organization to catalog and record answers to specific prompt numbers for an individual. It is conceivable that a site might attempt to retrieve multiple prompts and answer pairs from an individual and record them. This organization could then sell or use this list for the purpose of automating Responses to that individual. By encrypting the reference number, prompt #4 might be used numerous times in a Challenge, but the result of encrypting “4” (which would be placed in the delimiter) would differ each time. It would be extremely difficult for a site to catalog the reference numbers from multiple Challenges.
Challenge Identifier (Optional) 306
In messaging systems that allow modification of the Message Header 202, it can be beneficial to include information in this section of the message. The Internet is one such system that allows the insertion of additional information into a message header 202.
When composing a challenge and modifying the incoming message, additional information should also be placed into the Message Header. This additional information would indicate the presence of a Challenge, the version of this Invention used to create the Challenge, the Reference Number of the Prompt used in the Challenge, etc.
There are at least two benefits to this approach.
    • (1) The header of a message is usually much more fixed in format than the message body 203. This makes it easier to search and locate, with precision, various important pieces of information mentioned above. And
    • (2) it is possible on the Internet, for example, to retrieve and process only the message header 202 without retrieving the message body 203. By doing this, the message may be evaluated and subsequently deleted (by the mechanisms described herein) without incurring the cost and time of downloading the entire message.
On the Internet, a sample Challenge Identifier 306 embedded in a Message Header 202 could resemble:
    • . . . [header information]
    • X-EFILTER: Challenge Present
    • X-EFILTER: Version=1.2
    • X-EFILTER: Prompt Number=4
    • . . . [additional header information]. . .
FIG. 7 shows a flow diagram of the Mail Filtering Process. Mail Processor 104 traverses this diagram for each incoming message 201. Recall that outgoing message are also handled by the Mail Processor, but do not undergo a filtering process. Instead, they are simply delivered to the Network 110 via Link 103.
Start 401
The Mail Processor 104 begins at Start 401. It begins the filtering process after a signal of some kind. This signal could be, for example, notification from the Network 110 (via Link 103) that new mail is incoming; an explicit command from the user; or perhaps, after a certain time interval such as once every hour.
Check For Incoming Message 405
After Start 401, the Mail Processor queries the Network 110 to determine if any mail is incoming.
No Incoming Message—Done 410
State 410 is the trivial case where there is no incoming mail. In this case, the Mail Processor has nothing to do and will stop. The Mail Processor will reawaken and begin again at Start 401 after one of the previously mentioned signals. Incoming message. Is it Properly Addressed to Recipient? 412
The incoming message is checked to see if it is properly addressed to the recipient. Note that the recipient might be a primary designated recipient (such as “TO:”) or a secondary recipient (such as “CC:” (carbon copy) or “BCC:” (blind carbon copy).
Any message which is not properly addressed to the recipient will be assumed to be a junk email communication and dealt with appropriately (typically deleted). The user can configure various parameters which determine whether an incoming message is “properly” addressed to the recipient depending on such conditions as whether the recipient's email address is present in the message's recipient fields, which recipient field(s) the recipient's address appears in, how many secondary recipient addresses (those not belonging to the user) are present in the message's recipient fields, and which message recipient fields contain those secondary addresses.
On the Internet, for example, it is possible for a user to receive a message which is not addressed to them in any way. In other words, such a message does not contain the user's email address (or name) in any of the message's recipient fields. Such fields may include TO (which generally indicates the main message recipients), CC (which generally indicates carbon copy recipients), or perhaps BCC (which generally indicates blind carbon copy recipients). There may be other possible message recipient fields. It is an option of the present invention to identify such incoming messages as junk email and deal with them appropriately.
On the Internet, for example, it is possible for a user to receive a message which is not solely addressed to them. This condition would exist if the message's recipient fields contained the user's address and also contained addresses of other (secondary) recipients. It is an option of the present invention to identify as junk email any incoming message which is not solely addressed to the recipient. It is also an option of the present invention to identify as junk email any incoming message which is not solely addressed to the recipient when the number of secondary recipients of the message exceeds a predetermined threshold (10 for example).
In other words, a user could select from the following example options (among others) when configuring this invention:
  • (1) Accept incoming email regardless of message's recipients.
  • (2) Accept incoming email only if I am one of the message's recipients.
  • (3) Accept incoming email only if I am the sole message recipient (no other recipients in the message's recipient fields).
  • (4) Accept incoming email only if I am one of the message's recipients and there are no more than N other message recipients.
  • (5) Accept incoming email only if I am the sole primary message recipient (i.e. my address is the only recipient address in the TO: recipient field).
  • (6) Accept incoming email only if I am a primary message recipient (i.e. my address is in the TO: recipient field) and there are no more than N other primary recipients.
    There are other possible combinations. Message Not Properly Addressed to Recipient 413
If the incoming message is not properly addressed to the recipient, the Mail Processor will transfer the message to the “Deleted” Message Folder 108x (x being a number between a . . . n). The Mail Processor then proceeds back to 405 and checks for another incoming message.
Determine if Sender is on Block List 415
If an incoming message is for the recipient, the Mail Processor extracts the sender's address from the Message and determines if the sender's address is present on Blocking List 115.
Sender's Address is on a Blocking List—Block Message 420
If the sender's Address is on Blocking List 115, it means that the user has specified that all messages from this sender are unwanted. The Mail Processor will transfer the message to the “Deleted” Message Folder 108x (x being a number between a . . . n). The Mail Processor then proceeds back to 405 and checks for another incoming message.
Sender not on Blocking List. Determine if on Acceptance List 425
The Mail Processor has already determined that the Sender of the incoming message is not present on the Blocking List. The Mail Processor now checks to see if the incoming message sender's address is on Acceptance List 105.
Sender's Address is on Acceptance List—Accept Message 430
If the sender's Address is listed on the Acceptance List, the message will be accepted by the Mail Processor 104 and placed in the “New” message folder (for example, message folder) 108x (x being a variable indicating one of the message folders 108).
Does Message Contain a Challenge? 435
The message has not been accepted or blocked based on the sender's address. The Mail Processor must now determine if the incoming message contains a Challenge. To do this, the Mail Processor 104 scans the message body 203 for the Header 305 token (“<##Efilter;V1.2##>”). If found, the incoming message contains a Challenge.
Note that the Mail Processor can also scan the Message Header 202 in messaging systems (such as the Internet) that allow non-standard additions to the portion of a message.
No Challenge Found in Message 440
If the incoming message does not contain a Challenge then the message is from a new, unrecognized sender that has never correctly answered a Challenge and/or never been placed on the Blocking List 115. In this situation, the message sender will be Challenged in an attempt to exclude junk email (which this message could be).
Before going through the trouble of composing and returning a Challenge, however, the Mail Processor 104 uses some simple heuristics to determine if the message sender's address is valid. As mentioned before, on the Internet, it is possible to send a message that doesn't include a valid sender address.
Various heuristics can be applied to an email address to determine if it is valid. These heuristics will vary depending on the messaging standards of the medium of transmission. On the Internet, for example, an email address must contain the symbol ‘@’. An email address without this symbol is invalid.
The Message Sender's Address is Invalid 445
If the sender's address is determined to be invalid, it is useless to create and return a Challenge because it will simply “bounce back” and be returned as “address unknown”. Messages with invalid sender addresses are moved by the Mail Processor 104 to the “Deleted” Message Folder 108x.
The Message Sender's Address Appears to be Valid 450
If the message sender's address has been determined to be valid (as best possible). The Mail Processor 104 will compose a Challenge 301 and attach it to the beginning of the original incoming message. This newly modified message (also referred to in its entirety as a “Challenge”) is then be returned to the message sender (delivered by Mail Processor 104 to the Network 110).
Message Contains Challenge. Is Response Correct? 460
If the incoming message contains a Challenge 301 the Mail Processor extracts the Legal Notice response (in 303b) and the Prompt response (including prompt reference number) (in 304b) and evaluates them to determine if they are valid or not. Both responses must be valid in order to pass the Challenge.
Response to Challenge is Invalid 465
If either the Prompt 304b or Legal Notice response 303b is invalid the message is blocked and placed in the “Deleted” Message Folder 108x.
Response to Challenge is Valid 470
If both the Prompt 304b and Legal Notice responses 303b are valid the message is accepted and placed in the “New” Message Folder 108x. In addition, the sender's address is entered into the Acceptance List 105. This assures that all future emails from this sender are accepted without the issuing of a Challenge (unless the Acceptance List 105 is cleared manually by the user, or unless the sender's address is subsequently added to the Blocking List 115).
Miscellaneous Variations
A useful feature, anticipated, but not implemented in the preferred embodiment would involve a modification of the Acceptance List 105. Recall that this list includes addresses of all sender's whose email messages may pass through, unimpeded, to the recipient. By adding extra information to the Acceptance List, it would be possible to automatically categorize all incoming messages. For example, an entry in the Acceptance List allowing a grandmother to communicate with the recipient might consist of:
    • “grandma@company.com”
By adding an additional piece of information to this list entry, we could automatically send all of grandma's email messages to the “Grandma” Message Folder 108x (assuming one exists). This modified Acceptance List entry might look like:
    • “grandma@company.com,Grandma”
The first entry is the sender address (or address pattern) to accept. The second entry is the Message Folder in which to place all messages from the respective sender. Acceptance list entries are automatically generated. The user simply adds a message folder designation.
It should be noted that it would be beneficial for some users of this Invention to included some or all elements of the Challenge in multiple languages. For example, the Legal Notice could consist of an English and Spanish version for a user that expects messages from a speaker of foreign languages. There is nothing in the design of this Invention that precludes the use of multiple language texts and Prompts.
Note also that the method and system according to the present invention could be configured to create and return a Challenge in the native language of whatever domain the message originated from. On the Internet, for example, messages can arrive from different domains which represent different countries. An incoming message from the “.jp” domain would indicate Japan and an appropriate Challenge in Japanese could be created and returned. All parts of the Challenge could be tailored to the message origination location including the Legal Notice, General Notice and Prompt.
A method and system for filtering unsolicited electronic commercial messages has been disclosed. Software written according to the present invention is to be stored in some form of computer readable medium, such as memory or CD ROM, or transmitted over a network, and executed by a processor.
Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.

Claims (65)

1. A method for filtering electronic messages, the method comprising:
receiving an electronic message from a sender, the electronic message including an address field containing a sender's address;
comparing the sender's address to a list of accepted senders;
applying a heuristic to the sender's address to determine if the sender's address is formatted according to a message standard of a messaging medium of transmission through which the electronic message is received in order to make a determination of whether the sender's address is valid or invalid;
analyzing the electronic message to determine whether the electronic message includes a first token that indicates that the electronic message is a reply to a first challenge message; and
sending a prompt second challenge message back to the sender if the sender's address is valid and if the sender's address is not contained in the list of accepted senders and if the electronic message does not include the first token, wherein the second challenge message includes a prompt is designed to be answered by a person and not a machine and wherein the second challenge message further includes a second token.
2. The method of claim 1, wherein the electronic message is an e-mail.
3. The method of claim 1, further comprising a step of determining if information regarding the sender is listed on a predetermined list, the predetermined list being defined before receiving the electronic message from the sender.
4. The method of claim 1, further comprising a step of not filtering out the message if information regarding the sender is listed on the list of accepted senders.
5. The method of claim 1, further comprising a step of comparing the sender's address to a list if of blocked addresses and filtering out the electronic message if information regarding the sender is listed on the list of blocked addresses.
6. The method of claim 1, further comprising a step of automatically adding information regarding the sender to a the list of accepted senders.
7. The method of claim 1, further comprising a step of determining if the received electronic message is properly addressed to a predetermined receiver recipient.
8. The method of claim 7, wherein a the received electronic message is filtered out if the received electronic message is not properly addressed to the predetermined receiver recipient.
9. The method of claim 1 additionally comprising a step of receiving a response to the prompt and adding the sender's address to the list of accepted senders if the response to the prompt is correct.
10. The method of claim 1 additionally comprising a step of receiving a response to the prompt and adding the sender's address to a list of blocked senders if the response to the prompt is incorrect.
11. The method of claim 10 additionally comprising a step of deleting the response if the response does not contain a correct answer to the prompt.
12. The method of claim 11 wherein the step of deleting the response comprises moving the response to a deleted messages folder.
13. The method of claim 1 wherein the sender's address field is a reply address field and the sender's address is a reply address for the sender.
14. The method of claim 1, wherein the step of additionally comprising a step of comparing the sender's address to a list of blocked senders, wherein the step of sending a prompt second challenge message back to the sender comprises sending a prompt second challenge message back to the sender only if the sender's address is not in the list of accepted senders and not in the list of blocked senders if the sender's address is valid, the sender's address is not contained in the list of accepted senders, the sender's address is not contained in the list of blocked senders and the electronic message does not include the first token.
15. The method of claim 14 additionally comprising a step of deleting the message if the sender's address is in the list of blocked senders.
16. The method of claim 1 additionally comprising a step of adding the sender's address to the list of accepted senders if the sender correctly responds to the prompt.
17. A system for filtering electronic messages, the system comprising:
means for receiving an electronic message from a sender;
means for determining that a return address of the sender is an accepted sender's address;
means for sending a prompt back to the sender if the return address is not an accepted sender's address, wherein the prompt is designed to be answered by a person and not a machine.
18. The system of claim 17, wherein the means for determining comprises means for determining if the address is listed on a list.
19. The system of claim 18, further comprising means for not filtering out the message if information regarding the sender is listed on the list of accepted senders.
20. The system of claim 18, further comprising means for filtering out the message if information regarding the sender is listed on a list of blocked senders.
21. The system of claim 17, further comprising means for adding information regarding the sender to a list.
22. The system of claim 17, further comprising means for determining if the received message is properly addressed to a predetermined receiver.
23. The system of claim 22, wherein the received message is filtered out if it is not properly addressed to the predetermined receiver.
24. A non-transitory computer readable medium containing program instructions for filtering electronic messages, the program instructions comprising:
receiving an electronic message from a sender, the electronic message including an address field containing a sender's address;
comparing the sender's address to a list of accepted senders;
applying a heuristic to the sender's address to determine if the sender's address is formatted according to a message standard of a messaging medium of transmission through which the electronic message is received to make a determination of whether the sender's address is valid or invalid;
analyzing the electronic message to determine whether the electronic message includes a first token that indicates that the electronic message is a reply to a first challenge message,
sending a prompt second challenge message back to the sender if the sender's address is valid and if the sender's address is not contained in the list of accepted senders and if the electronic message does not include the first token, wherein the second challenge message includes a prompt is designed to be answered by a person and not a machine and wherein the second challenge message further includes a second token.
25. The medium of claim 24 additionally comprising wherein the program instructions additionally comprise a step of receiving a response to the prompt and adding the sender's address to the list of accepted senders if the response to the prompt is correct.
26. The medium of claim 24 additionally comprising wherein the program instructions additionally comprise a step of receiving a response to the prompt and adding the sender's address to a list of blocked senders if the response to the prompt is incorrect.
27. The medium of claim 26 additionally comprising wherein the program instructions additionally comprise a step of deleting the response if the response does not contain a correct answer to the prompt.
28. The medium of claim 27 wherein the step of deleting the response comprises moving the response to a deleted messages folder.
29. The medium of claim 24 wherein the sender's address field is a reply address field and the sender's address is a reply address for the sender.
30. A method for filtering electronic messages, the method comprising:
receiving an electronic message from a sender, the message including a sender's address field containing an address of the sender;
comparing the sender's address to a list of accepted senders;
applying a heuristic to the sender's address to determine if the sender's address is formatted according to a message standard of a messaging medium of transmission through which the electronic message is received to make a determination of whether the sender's address is valid or invalid;
sending a challenge back to the sender if the sender's address is valid and if the sender's address is not in the list of accepted senders, wherein the challenge is designed to be answered by a person and not a machine, the challenge including a prompt and a legal notice designed to be answered by a person and not a machine.
31. The method of claim 30, wherein the challenge includes a prompt.
32. The method of claim 30, wherein the challenge includes a legal notice.
33. The method of claim 32 30, wherein the legal notice includes text which cannot be altered once the text is sent to the sender.
34. The method of claim 30, further comprising a step of automatically updating the list of accepted senders.
35. The method of claim 30, wherein the challenge includes a program version number.
36. The method of claim 30, further comprising a step of determining if the received electronic message is properly addressed to a predetermined receiver recipient.
37. The method of claim 36, wherein the received message is filtered out if it is not properly addressed to a predetermined receiver recipient.
38. The method of claim 1 additionally comprising:
receiving a response to the prompt of the second challenge message; and
automatically accepting the electronic message without filtering out the electronic message, if the received response includes:
the second token; and
a correct response to the prompt of the second challenge message.
39. The method of claim 1 additionally comprising:
receiving a response to the prompt of the second challenge message; and
automatically adding the sender's address to the list of accepted senders, if the received response includes:
the second token; and
a correct response to the prompt of the second challenge message.
40. The method of claim 1 additionally comprising:
receiving a response to the prompt of the second challenge message; and
automatically adding the sender's address to a list of blocked senders, if the received response includes:
the second token; and
an incorrect response to the prompt of the second challenge message.
41. The method of claim 1 additionally comprising:
receiving a response to the prompt of the second challenge message; and
automatically deleting the electronic message, if the received response includes:
the second token; and
an incorrect response to the prompt of the second challenge message.
42. The method of claim 1 wherein the second challenge message further includes a program version number.
43. The medium of claim 24 wherein the second challenge message further includes a program version number.
44. The medium of claim 24 wherein the electronic message is an e-mail.
45. The medium of claim 24 wherein the program instructions additionally comprise a step of determining if information regarding the sender is listed on a predetermined list, the predetermined list being defined before receiving the electronic message from the sender.
46. The medium of claim 24 wherein the program instructions additionally comprise a step of not filtering out the message if information regarding the sender is listed on the list of accepted senders.
47. The medium of claim 24 wherein the program instructions additionally comprise a step of comparing the sender's address to a list of blocked addresses and filtering out the electronic message if information regarding the sender is listed on the list of blocked addresses.
48. The medium of claim 24 wherein the program instructions additionally comprise a step of automatically adding information regarding the sender to the list of accepted senders.
49. The medium of claim 24 wherein the program instructions additionally comprise a step of determining if the received electronic message is properly addressed to a recipient.
50. The medium of claim 49 wherein the received electronic message is filtered out if the received electronic message is not properly addressed to the recipient.
51. The medium of claim 24 wherein the program instructions additionally comprise:
a step of comparing the sender's address to a list of blocked senders; and
wherein the step of sending a second challenge message back to the sender comprises sending a second challenge message back to the sender if the sender's address is valid, the sender's address is not contained in the list of accepted senders, the sender's address is not contained in the list of blocked senders and the electronic message does not include the first token.
52. The medium of claim 24 wherein the program instructions additionally comprise:
automatically accepting the electronic message without filtering out the electronic message, if the electronic message includes:
the first token that indicates that the electronic message is a reply to the first challenge message; and
a correct response to a prompt of the first challenge message.
53. The medium of claim 24 wherein the program instructions additionally comprise:
automatically adding the sender's address to the list of accepted senders, if the electronic message includes:
the first token that indicates that the electronic message is a reply to the first challenge message; and
a correct response to a prompt of the first challenge message.
54. The medium of claim 24 wherein the program instructions additionally comprise:
automatically adding the sender's address to a list of blocked senders, if the electronic message includes:
the first token that indicates that the electronic message is a reply to the first challenge message; and
an incorrect response to a prompt of the first challenge message.
55. The medium of claim 24 wherein the program instructions additionally comprise:
automatically deleting the electronic message, if the electronic message includes:
the first token that indicates that the electronic message is a reply to the first challenge message; and
an incorrect response to a prompt of the first challenge message.
56. The medium of claim 24 wherein the program instructions additionally comprise:
receiving a response to the prompt of the second challenge message; and
automatically accepting the electronic message without filtering out the electronic message, if the received response includes:
the second token; and
a correct response to the prompt of the second challenge message.
57. The medium of claim 24 wherein the program instructions additionally comprise:
receiving a response to the prompt of the second challenge message; and
automatically adding the sender's address to the list of accepted senders, if the received response includes:
the second token; and
a correct response to the prompt of the second challenge message.
58. The medium of claim 24 wherein the program instructions additionally comprise:
receiving a response to the prompt of the second challenge message; and
automatically adding the sender's address to a list of blocked senders, if the received response includes:
the second token; and
an incorrect response to the prompt of the second challenge message.
59. The medium of claim 24 wherein the program instructions additionally comprise:
receiving a response to the prompt of the second challenge message; and
automatically deleting the electronic message, if the received response includes:
the second token; and
an incorrect response to the prompt of the second challenge message.
60. The method of claim 30 additionally comprising:
receiving a response to the prompt and the legal notice of the second challenge message; and
automatically accepting the electronic message without filtering out the electronic message, if the received response is correct.
61. The method of claim 30 additionally comprising:
receiving a response to the prompt and the legal notice of the second challenge message; and
automatically adding the sender's address to the list of accepted senders, if the received response is correct.
62. The method of claim 30 additionally comprising:
receiving a response to the prompt and the legal notice of the second challenge message; and
automatically adding the sender's address to a list of blocked senders, if the received response is incorrect.
63. The method of claim 30 additionally comprising:
receiving a response to the prompt and the legal notice of the second challenge message; and
automatically deleting the electronic message, if the received response is incorrect.
64. A non-transitory computer readable medium containing program instructions for filtering electronic messages, the program instructions comprising:
a) receiving a first electronic message from a sender, the first electronic message including an address field containing a sender's address;
b) comparing the sender's address to a list of accepted senders;
c) comparing the sender's address to a list of blocked senders;
d) applying a heuristic to the sender's address to determine if the sender's address is formatted according to a message standard of a messaging medium of transmission through which the first electronic message is received in order to make a determination of whether the sender's address is valid or invalid;
e) analyzing the first electronic message to determine whether the first electronic message is properly addressed to one or more recipients in at least one recipient designation;
f) analyzing the first electronic message to determine whether the first electronic message includes a first token that indicates that the first electronic message is a reply to a challenge message;
g) sending a challenge message back to the sender via the sender's address if:
the sender's address is not contained in the list of accepted senders,
the sender's address is not contained in the list of blocked senders,
the sender's address is valid,
the first electronic message is properly addressed to one or more recipients in at least one recipient designation, and
the first electronic message does not include the first token,
wherein the challenge message includes a prompt designed to be answered by a person and not a machine and wherein the challenge message further includes a second token;
h) receiving a second electronic message from the sender that includes the second token, the second electronic message including an answer to the prompt in the challenge message;
i) analyzing the answer to the prompt to determine whether the answer to the prompt is correct;
k) sending the second electronic message to a message folder accessible by a user to view the second electronic message; and
j) automatically adding the sender's address to the list of accepted senders when the answer to the prompt in the challenge message is correct.
65. The medium of claim 64 wherein the program instructions additionally comprise filtering out the first electronic message when:
the sender's address is not contained in the list of blocked senders,
the sender's address is invalid, or
the first electronic message is not properly addressed to one or more recipients in at least one recipient designation.
US11/448,579 1997-08-26 2006-06-07 Method and system for filtering electronic messages Expired - Lifetime USRE41411E1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US11/448,579 USRE41411E1 (en) 1997-08-26 2006-06-07 Method and system for filtering electronic messages
US12/823,735 USRE42702E1 (en) 1997-08-26 2010-06-25 Method and system for filtering electronic messages

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US08/921,950 US6199102B1 (en) 1997-08-26 1997-08-26 Method and system for filtering electronic messages
US11/448,579 USRE41411E1 (en) 1997-08-26 2006-06-07 Method and system for filtering electronic messages

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US08/921,950 Reissue US6199102B1 (en) 1997-08-26 1997-08-26 Method and system for filtering electronic messages

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US08/921,950 Continuation US6199102B1 (en) 1997-08-26 1997-08-26 Method and system for filtering electronic messages

Publications (1)

Publication Number Publication Date
USRE41411E1 true USRE41411E1 (en) 2010-06-29

Family

ID=25446245

Family Applications (3)

Application Number Title Priority Date Filing Date
US08/921,950 Ceased US6199102B1 (en) 1997-08-26 1997-08-26 Method and system for filtering electronic messages
US11/448,579 Expired - Lifetime USRE41411E1 (en) 1997-08-26 2006-06-07 Method and system for filtering electronic messages
US12/823,735 Expired - Lifetime USRE42702E1 (en) 1997-08-26 2010-06-25 Method and system for filtering electronic messages

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US08/921,950 Ceased US6199102B1 (en) 1997-08-26 1997-08-26 Method and system for filtering electronic messages

Family Applications After (1)

Application Number Title Priority Date Filing Date
US12/823,735 Expired - Lifetime USRE42702E1 (en) 1997-08-26 2010-06-25 Method and system for filtering electronic messages

Country Status (2)

Country Link
US (3) US6199102B1 (en)
WO (1) WO1999010817A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070249374A1 (en) * 2006-04-21 2007-10-25 Lucent Technologies Inc. Method for controlling delivery of short messages in wireless network
US20090030989A1 (en) * 2007-07-25 2009-01-29 International Business Machines Corporation Enterprise e-mail blocking and filtering system based on user input
US20130144674A1 (en) * 2011-12-01 2013-06-06 Samsung Electronics Co. Ltd. System and method for providing mobile advertising services

Families Citing this family (369)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6266664B1 (en) * 1997-10-01 2001-07-24 Rulespace, Inc. Method for scanning, analyzing and rating digital information content
US8412778B2 (en) * 1997-11-25 2013-04-02 Robert G. Leeds Junk electronic mail detector and eliminator
JP3087710B2 (en) * 1997-11-29 2000-09-11 ブラザー工業株式会社 Facsimile machine
US6782510B1 (en) * 1998-01-27 2004-08-24 John N. Gross Word checking tool for controlling the language content in documents using dictionaries with modifyable status fields
US6219694B1 (en) * 1998-05-29 2001-04-17 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device having a shared electronic address
US6438585B2 (en) * 1998-05-29 2002-08-20 Research In Motion Limited System and method for redirecting message attachments between a host system and a mobile data communication device
US6925483B1 (en) * 1998-06-25 2005-08-02 Cisco Technology, Inc. System for characterizing information from an information producer
US7275082B2 (en) * 1998-07-15 2007-09-25 Pang Stephen Y F System for policing junk e-mail messages
US6112227A (en) 1998-08-06 2000-08-29 Heiner; Jeffrey Nelson Filter-in method for reducing junk e-mail
US6546416B1 (en) * 1998-12-09 2003-04-08 Infoseek Corporation Method and system for selectively blocking delivery of bulk electronic mail
US7073129B1 (en) 1998-12-18 2006-07-04 Tangis Corporation Automated selection of appropriate information based on a computer user's context
US9183306B2 (en) 1998-12-18 2015-11-10 Microsoft Technology Licensing, Llc Automated selection of appropriate information based on a computer user's context
US7225229B1 (en) * 1998-12-18 2007-05-29 Tangis Corporation Automated pushing of computer user's context data to clients
US6801223B1 (en) * 1998-12-18 2004-10-05 Tangis Corporation Managing interactions between computer users' context models
US7779015B2 (en) * 1998-12-18 2010-08-17 Microsoft Corporation Logging and analyzing context attributes
US6920616B1 (en) 1998-12-18 2005-07-19 Tangis Corporation Interface for exchanging context data
US6842877B2 (en) 1998-12-18 2005-01-11 Tangis Corporation Contextual responses based on automated learning techniques
US6791580B1 (en) * 1998-12-18 2004-09-14 Tangis Corporation Supplying notifications related to supply and consumption of user context data
US6513046B1 (en) * 1999-12-15 2003-01-28 Tangis Corporation Storing and recalling information to augment human memories
US8181113B2 (en) * 1998-12-18 2012-05-15 Microsoft Corporation Mediating conflicts in computer users context data
US7046263B1 (en) * 1998-12-18 2006-05-16 Tangis Corporation Requesting computer user's context data
US6654787B1 (en) * 1998-12-31 2003-11-25 Brightmail, Incorporated Method and apparatus for filtering e-mail
US6732149B1 (en) * 1999-04-09 2004-05-04 International Business Machines Corporation System and method for hindering undesired transmission or receipt of electronic messages
US6999955B1 (en) 1999-04-20 2006-02-14 Microsoft Corporation Systems and methods for estimating and integrating measures of human cognitive load into the behavior of computational applications and services
US6415304B1 (en) * 1999-04-20 2002-07-02 Microsoft Corporation Waiting prior to engaging in action for enhancement of automated service
AUPQ030299A0 (en) * 1999-05-12 1999-06-03 Sharinga Networks Inc. A message processing system
DE19922300A1 (en) * 1999-05-14 2000-11-16 Alcatel Sa Device for automatic processing of incoming electronic mail (= email)
US8874244B2 (en) * 1999-05-19 2014-10-28 Digimarc Corporation Methods and systems employing digital content
US6816274B1 (en) * 1999-05-25 2004-11-09 Silverbrook Research Pty Ltd Method and system for composition and delivery of electronic mail
US7346605B1 (en) 1999-07-22 2008-03-18 Markmonitor, Inc. Method and system for searching and monitoring internet trademark usage
US6449657B2 (en) 1999-08-06 2002-09-10 Namezero.Com, Inc. Internet hosting system
US7853989B2 (en) * 2000-02-08 2010-12-14 Katsikas Peter L System for eliminating unauthorized electronic mail
WO2001016695A1 (en) * 1999-09-01 2001-03-08 Katsikas Peter L System for eliminating unauthorized electronic mail
JP2001077993A (en) * 1999-09-03 2001-03-23 Ricoh Co Ltd Communication terminal device, facsimile machine and method for controlling them
EP1087321A1 (en) * 1999-09-24 2001-03-28 Alcatel A method of manipulating an already sent E-Mail and a corresponding server
AU7745000A (en) 1999-09-30 2001-04-30 United States Postal Service Systems and methods for authenticating an electronic message
US7797543B1 (en) 1999-09-30 2010-09-14 United States Postal Service Systems and methods for authenticating an electronic message
US6662230B1 (en) * 1999-10-20 2003-12-09 International Business Machines Corporation System and method for dynamically limiting robot access to server data
US6832321B1 (en) * 1999-11-02 2004-12-14 America Online, Inc. Public network access server having a user-configurable firewall
US6549972B1 (en) * 1999-11-22 2003-04-15 International Business Machines Corporation Method and system for providing control accesses between a device on a non-proprietary bus and a device on a proprietary bus
US7249175B1 (en) * 1999-11-23 2007-07-24 Escom Corporation Method and system for blocking e-mail having a nonexistent sender address
US6832245B1 (en) 1999-12-01 2004-12-14 At&T Corp. System and method for analyzing communications of user messages to rank users and contacts based on message content
US6999993B1 (en) * 1999-12-15 2006-02-14 Microsoft Corporation Methods and systems for end-users extensible electronic mail
US6460050B1 (en) * 1999-12-22 2002-10-01 Mark Raymond Pace Distributed content identification system
US7136634B1 (en) * 1999-12-22 2006-11-14 Nokia Corporation System and method for displaying information included in predetermined messages automatically
US7072942B1 (en) * 2000-02-04 2006-07-04 Microsoft Corporation Email filtering methods and systems
US7822977B2 (en) * 2000-02-08 2010-10-26 Katsikas Peter L System for eliminating unauthorized electronic mail
US6691156B1 (en) * 2000-03-10 2004-02-10 International Business Machines Corporation Method for restricting delivery of unsolicited E-mail
AU2001245808A1 (en) * 2000-03-17 2001-10-03 United States Postal Service Methods and systems for providing a secure electronic mailbox
JP2001268120A (en) * 2000-03-17 2001-09-28 Fujitsu Ltd Packet communication system
US7644274B1 (en) * 2000-03-30 2010-01-05 Alcatel-Lucent Usa Inc. Methods of protecting against spam electronic mail
US6826609B1 (en) 2000-03-31 2004-11-30 Tumbleweed Communications Corp. Policy enforcement in a secure data file delivery system
US7464153B1 (en) * 2000-04-02 2008-12-09 Microsoft Corporation Generating and supplying user context data
AU2001249768A1 (en) * 2000-04-02 2001-10-15 Tangis Corporation Soliciting information based on a computer user's context
US7428576B2 (en) * 2000-05-16 2008-09-23 Hoshiko Llc Addressee-defined mail addressing system and method
US6839760B1 (en) * 2000-06-02 2005-01-04 International Business Machines Corporation Method for preventing deep linking into a web site
US20040073617A1 (en) 2000-06-19 2004-04-15 Milliken Walter Clark Hash-based systems and methods for detecting and preventing transmission of unwanted e-mail
US8244809B2 (en) * 2000-06-20 2012-08-14 United States Postal Service System and methods for electronic message content identification
SE519317C2 (en) * 2000-07-07 2003-02-11 Ericsson Telefon Ab L M Method and communication device for blocking unwanted traffic in a data communication system
US7007008B2 (en) * 2000-08-08 2006-02-28 America Online, Inc. Category searching
US7359951B2 (en) 2000-08-08 2008-04-15 Aol Llc, A Delaware Limited Liability Company Displaying search results
US7047229B2 (en) * 2000-08-08 2006-05-16 America Online, Inc. Searching content on web pages
US7225180B2 (en) * 2000-08-08 2007-05-29 Aol Llc Filtering search results
US7546351B1 (en) 2000-08-17 2009-06-09 Mxgo Methods and systems for filtering, sorting, and dispatching messages to wired and wireless devices
US7058582B2 (en) * 2000-09-19 2006-06-06 Irn, Inc. Method for performing programming by plain text requests
US7127490B1 (en) * 2000-09-25 2006-10-24 Omnesys Technologies, Inc. Method and apparatus for content based routing of messages
WO2002033541A2 (en) * 2000-10-16 2002-04-25 Tangis Corporation Dynamically determining appropriate computer interfaces
WO2002039356A1 (en) * 2000-11-01 2002-05-16 Mark Landesmann System and method for granting deposit-contingent e-mailing rights
US7725546B2 (en) * 2000-11-01 2010-05-25 Buyerleverage System and method for granting deposit-contingent e-mailing rights
US7379972B2 (en) * 2000-11-01 2008-05-27 Buyerleverage E-Mail Solutions Llc System and method for granting deposit-contingent e-mailing rights
US8719326B2 (en) 2003-08-18 2014-05-06 S.F. Ip Properties 14 Llc Adaptive data transformation engine
US6778941B1 (en) * 2000-11-14 2004-08-17 Qualia Computing, Inc. Message and user attributes in a message filtering method and system
US7174453B2 (en) 2000-12-29 2007-02-06 America Online, Inc. Message screening system
US8219620B2 (en) 2001-02-20 2012-07-10 Mcafee, Inc. Unwanted e-mail filtering system including voting feedback
US20020120853A1 (en) * 2001-02-27 2002-08-29 Networks Associates Technology, Inc. Scripted distributed denial-of-service (DDoS) attack discrimination using turing tests
JP2005506604A (en) * 2001-03-22 2005-03-03 チュン マイケル Methods and systems for email, internet goals and direct marketing, and email banners
US20020147734A1 (en) * 2001-04-06 2002-10-10 Shoup Randall Scott Archiving method and system
US7779481B2 (en) * 2001-04-12 2010-08-17 United States Postal Service Systems and methods for electronic postmarking of data including location data
US6826729B1 (en) * 2001-06-29 2004-11-30 Microsoft Corporation Gallery user interface controls
US20030023736A1 (en) * 2001-07-12 2003-01-30 Kurt Abkemeier Method and system for filtering messages
US7647376B1 (en) 2001-07-26 2010-01-12 Mcafee, Inc. SPAM report generation system and method
US7016939B1 (en) * 2001-07-26 2006-03-21 Mcafee, Inc. Intelligent SPAM detection system using statistical analysis
JP2003046576A (en) * 2001-07-27 2003-02-14 Fujitsu Ltd Message delivery system, message delivery management server, message distribution management program, and computer-readable recording medium with the program recorded thereon
US7216114B2 (en) * 2001-08-09 2007-05-08 International Business Machines Corporation Transfer of mail folders between e-mail users
EP1286513B1 (en) * 2001-08-14 2005-10-19 Hewlett-Packard Company Message broker
US20030037102A1 (en) * 2001-08-14 2003-02-20 Philippe Eckert Message broker
US20030046144A1 (en) * 2001-08-28 2003-03-06 International Business Machines Corporation System and method for anonymous message forwarding and anonymous voting
US8255235B2 (en) * 2001-09-07 2012-08-28 United States Postal Service Item tracking and anticipated delivery confirmation system method
US7774711B2 (en) 2001-09-28 2010-08-10 Aol Inc. Automatic categorization of entries in a contact list
US7433923B2 (en) * 2001-10-03 2008-10-07 Reginald Adkins Authorized email control system
US7254709B1 (en) 2001-10-23 2007-08-07 Avanza Technologies, Inc. Managed information transmission of electronic items in a network environment
US20060036701A1 (en) * 2001-11-20 2006-02-16 Bulfer Andrew F Messaging system having message filtering and access control
WO2003048960A1 (en) * 2001-11-30 2003-06-12 A New Voice, Inc. Method and system for contextual prioritization of unified messages
US7039949B2 (en) * 2001-12-10 2006-05-02 Brian Ross Cartmell Method and system for blocking unwanted communications
US7054907B1 (en) * 2001-12-26 2006-05-30 Bellsouth Intellectual Property Corporation Systems and methods for blocking delivery of an electronic communication
JP2003248727A (en) * 2002-02-22 2003-09-05 Fujitsu Ltd Bedside communication system
GB0204589D0 (en) 2002-02-27 2002-04-10 Gordano Ltd Filtering E-mail messages
US7096498B2 (en) * 2002-03-08 2006-08-22 Cipher Trust, Inc. Systems and methods for message threat management
US8578480B2 (en) 2002-03-08 2013-11-05 Mcafee, Inc. Systems and methods for identifying potentially malicious messages
US7124438B2 (en) 2002-03-08 2006-10-17 Ciphertrust, Inc. Systems and methods for anomaly detection in patterns of monitored communications
US8132250B2 (en) * 2002-03-08 2012-03-06 Mcafee, Inc. Message profiling systems and methods
US20060015942A1 (en) * 2002-03-08 2006-01-19 Ciphertrust, Inc. Systems and methods for classification of messaging entities
US7870203B2 (en) 2002-03-08 2011-01-11 Mcafee, Inc. Methods and systems for exposing messaging reputation to an end user
US7693947B2 (en) 2002-03-08 2010-04-06 Mcafee, Inc. Systems and methods for graphically displaying messaging traffic
US7694128B2 (en) * 2002-03-08 2010-04-06 Mcafee, Inc. Systems and methods for secure communication delivery
US7458098B2 (en) * 2002-03-08 2008-11-25 Secure Computing Corporation Systems and methods for enhancing electronic communication security
US8561167B2 (en) * 2002-03-08 2013-10-15 Mcafee, Inc. Web reputation scoring
US6941467B2 (en) * 2002-03-08 2005-09-06 Ciphertrust, Inc. Systems and methods for adaptive message interrogation through multiple queues
US7903549B2 (en) 2002-03-08 2011-03-08 Secure Computing Corporation Content-based policy compliance systems and methods
US20030196116A1 (en) * 2002-04-15 2003-10-16 Todd Troutman Electronic mail blocking system
US20030200267A1 (en) * 2002-04-22 2003-10-23 Garrigues James F. Email management system
AUPS193202A0 (en) * 2002-04-23 2002-05-30 Pickup, Robert Barkley Mr A method and system for authorising electronic mail
US20030204569A1 (en) * 2002-04-29 2003-10-30 Michael R. Andrews Method and apparatus for filtering e-mail infected with a previously unidentified computer virus
US7606920B2 (en) * 2002-05-17 2009-10-20 Sony Computer Entertainment America Inc. Method and apparatus for controlling communication ports for an online session of a multi-user application by associating each of the ports with a protocol and designating an active port
US20030220978A1 (en) * 2002-05-24 2003-11-27 Rhodes Michael J. System and method for message sender validation
GB2407735A (en) * 2002-05-28 2005-05-04 Alan H Teague Message processing based on address patterns and automated management and control of contact aliases
US7139801B2 (en) * 2002-06-14 2006-11-21 Mindshare Design, Inc. Systems and methods for monitoring events associated with transmitted electronic mail messages
US7516182B2 (en) * 2002-06-18 2009-04-07 Aol Llc Practical techniques for reducing unsolicited electronic messages by identifying sender's addresses
US7310660B1 (en) 2002-06-25 2007-12-18 Engate Technology Corporation Method for removing unsolicited e-mail messages
US8046832B2 (en) * 2002-06-26 2011-10-25 Microsoft Corporation Spam detector with challenges
US7113977B1 (en) * 2002-06-26 2006-09-26 Bellsouth Intellectual Property Corporation Blocking electronic mail content
US7408664B2 (en) * 2002-06-26 2008-08-05 Ricoh Company, Ltd. Harassment mail reception suppressing network facsimile
US20080046592A1 (en) * 2002-06-26 2008-02-21 Research In Motion Limited System and Method for Pushing Information Between a Host System and a Mobile Data Communication Device
US8924484B2 (en) * 2002-07-16 2014-12-30 Sonicwall, Inc. Active e-mail filter with challenge-response
US7908330B2 (en) * 2003-03-11 2011-03-15 Sonicwall, Inc. Message auditing
US7539726B1 (en) * 2002-07-16 2009-05-26 Sonicwall, Inc. Message testing
US8396926B1 (en) * 2002-07-16 2013-03-12 Sonicwall, Inc. Message challenge response
US20080058013A1 (en) * 2002-07-29 2008-03-06 Research In Motion Limited System and Method for Pushing Information from a Host System to a Mobile Data Communication Device
US7899867B1 (en) * 2002-07-31 2011-03-01 FaceTime Communications, Inc, SpIM blocking and user approval techniques for real-time messaging networks
WO2004015583A1 (en) * 2002-08-09 2004-02-19 Burlington Communications, Inc. System and method for controlling access to an electronic message recipient
US20040093414A1 (en) * 2002-08-26 2004-05-13 Orton Kevin R. System for prevention of undesirable Internet content
US7673058B1 (en) 2002-09-09 2010-03-02 Engate Technology Corporation Unsolicited message intercepting communications processor
US7490128B1 (en) 2002-09-09 2009-02-10 Engate Technology Corporation Unsolicited message rejecting communications processor
US7716351B1 (en) 2002-09-09 2010-05-11 Engate Technology Corporation Unsolicited message diverting communications processor
US20040054733A1 (en) * 2002-09-13 2004-03-18 Weeks Richard A. E-mail management system and method
DE10243243B4 (en) * 2002-09-17 2005-01-27 T-Mobile Deutschland Gmbh Method for the receiver-side automatic treatment of unwanted electronic mail in communication networks
US7010565B2 (en) * 2002-09-30 2006-03-07 Sampson Scott E Communication management using a token action log
US8051172B2 (en) * 2002-09-30 2011-11-01 Sampson Scott E Methods for managing the exchange of communication tokens
US6804687B2 (en) * 2002-09-30 2004-10-12 Scott E. Sampson File system management with user-definable functional attributes stored in a token action log
US7472163B1 (en) * 2002-10-07 2008-12-30 Aol Llc Bulk message identification
US20080261633A1 (en) 2002-10-22 2008-10-23 Research In Motion Limited System and Method for Pushing Information from a Host System to a Mobile Data Communication Device
GB2396028A (en) * 2002-11-04 2004-06-09 Townsites Co Uk Ltd Email filtering method
KR100508118B1 (en) * 2002-11-18 2005-08-11 엘지전자 주식회사 Method for automatic processing the spam SMS message
US20040111480A1 (en) * 2002-12-09 2004-06-10 Yue Jonathan Zhanjun Message screening system and method
AU2003293501A1 (en) 2002-12-13 2004-07-09 Wholesecurity, Inc. Method, system, and computer program product for security within a global computer network
US20040122918A1 (en) * 2002-12-19 2004-06-24 Eastman Kodak Company System and method of sharing images
US7640336B1 (en) 2002-12-30 2009-12-29 Aol Llc Supervising user interaction with online services
US7263614B2 (en) 2002-12-31 2007-08-28 Aol Llc Implicit access for communications pathway
US7533148B2 (en) * 2003-01-09 2009-05-12 Microsoft Corporation Framework to enable integration of anti-spam technologies
US7305445B2 (en) * 2003-01-28 2007-12-04 Microsoft Corporation Indirect disposable email addressing
US7620691B1 (en) 2003-02-10 2009-11-17 Aol Llc Filtering electronic messages while permitting delivery of solicited electronics messages
US7406502B1 (en) 2003-02-20 2008-07-29 Sonicwall, Inc. Method and system for classifying a message based on canonical equivalent of acceptable items included in the message
US8266215B2 (en) * 2003-02-20 2012-09-11 Sonicwall, Inc. Using distinguishing properties to classify messages
US7299261B1 (en) * 2003-02-20 2007-11-20 Mailfrontier, Inc. A Wholly Owned Subsidiary Of Sonicwall, Inc. Message classification using a summary
US7249162B2 (en) 2003-02-25 2007-07-24 Microsoft Corporation Adaptive junk message filtering system
US7707564B2 (en) * 2003-02-26 2010-04-27 Bea Systems, Inc. Systems and methods for creating network-based software services using source code annotations
US7219148B2 (en) * 2003-03-03 2007-05-15 Microsoft Corporation Feedback loop for spam prevention
US20040243847A1 (en) * 2003-03-03 2004-12-02 Way Gregory G. Method for rejecting SPAM email and for authenticating source addresses in email servers
US7543053B2 (en) * 2003-03-03 2009-06-02 Microsoft Corporation Intelligent quarantining for spam prevention
US20050080857A1 (en) * 2003-10-09 2005-04-14 Kirsch Steven T. Method and system for categorizing and processing e-mails
US20040181581A1 (en) * 2003-03-11 2004-09-16 Michael Thomas Kosco Authentication method for preventing delivery of junk electronic mail
US7398315B2 (en) 2003-03-12 2008-07-08 Workman Nydegger Reducing unwanted and unsolicited electronic messages by preventing connection hijacking and domain spoofing
US7552176B2 (en) * 2003-03-12 2009-06-23 Microsoft Corporation Reducing unwanted and unsolicited electronic messages by exchanging electronic message transmission policies and solving and verifying solutions to computational puzzles
ATE402454T1 (en) * 2003-03-12 2008-08-15 Microsoft Corp METHOD AND CALCULATOR PROGRAM FOR REDUCING UNWANTED AND UNSOLICITED ELECTRONIC REPORTS
US7185015B2 (en) 2003-03-14 2007-02-27 Websense, Inc. System and method of monitoring and controlling application files
US7529754B2 (en) 2003-03-14 2009-05-05 Websense, Inc. System and method of monitoring and controlling application files
US8005899B2 (en) 2003-03-19 2011-08-23 Message Level Llc System and method for detecting and filtering unsolicited and undesired electronic messages
US20040249895A1 (en) * 2003-03-21 2004-12-09 Way Gregory G. Method for rejecting SPAM email and for authenticating source addresses in email servers
US7613776B1 (en) 2003-03-26 2009-11-03 Aol Llc Identifying and using identities deemed to be known to a user
US8606860B2 (en) * 2003-03-31 2013-12-10 Affini, Inc. System and method for providing filtering email messages
US20040193691A1 (en) * 2003-03-31 2004-09-30 Chang William I. System and method for providing an open eMail directory
US7856477B2 (en) * 2003-04-04 2010-12-21 Yahoo! Inc. Method and system for image verification to prevent messaging abuse
US7290033B1 (en) * 2003-04-18 2007-10-30 America Online, Inc. Sorting electronic messages using attributes of the sender address
US20040221016A1 (en) * 2003-05-01 2004-11-04 Hatch James A. Method and apparatus for preventing transmission of unwanted email
US7483947B2 (en) * 2003-05-02 2009-01-27 Microsoft Corporation Message rendering for identification of content features
US7590695B2 (en) * 2003-05-09 2009-09-15 Aol Llc Managing electronic messages
US20050108340A1 (en) * 2003-05-15 2005-05-19 Matt Gleeson Method and apparatus for filtering email spam based on similarity measures
US20040236838A1 (en) * 2003-05-24 2004-11-25 Safe E Messaging, Llc Method and code for authenticating electronic messages
US7653698B2 (en) 2003-05-29 2010-01-26 Sonicwall, Inc. Identifying e-mail messages from allowed senders
US7657599B2 (en) * 2003-05-29 2010-02-02 Mindshare Design, Inc. Systems and methods for automatically updating electronic mail access lists
US7272853B2 (en) * 2003-06-04 2007-09-18 Microsoft Corporation Origination/destination features and lists for spam prevention
US20050015452A1 (en) * 2003-06-04 2005-01-20 Sony Computer Entertainment Inc. Methods and systems for training content filters and resolving uncertainty in content filtering operations
US8145710B2 (en) * 2003-06-18 2012-03-27 Symantec Corporation System and method for filtering spam messages utilizing URL filtering module
US7711779B2 (en) * 2003-06-20 2010-05-04 Microsoft Corporation Prevention of outgoing spam
US7519668B2 (en) * 2003-06-20 2009-04-14 Microsoft Corporation Obfuscation of spam filter
US8533270B2 (en) 2003-06-23 2013-09-10 Microsoft Corporation Advanced spam detection techniques
US7739602B2 (en) 2003-06-24 2010-06-15 Aol Inc. System and method for community centric resource sharing based on a publishing subscription model
US9715678B2 (en) * 2003-06-26 2017-07-25 Microsoft Technology Licensing, Llc Side-by-side shared calendars
US20040266402A1 (en) * 2003-06-30 2004-12-30 Schavitz Mary J. Apparatus and method for message control on a wireless communication device
US7707255B2 (en) 2003-07-01 2010-04-27 Microsoft Corporation Automatic grouping of electronic mail
US20050005249A1 (en) * 2003-07-01 2005-01-06 Microsoft Corporation Combined content selection and display user interface
US7392249B1 (en) * 2003-07-01 2008-06-24 Microsoft Corporation Methods, systems, and computer-readable mediums for providing persisting and continuously updating search folders
US8799808B2 (en) * 2003-07-01 2014-08-05 Microsoft Corporation Adaptive multi-line view user interface
US7716593B2 (en) * 2003-07-01 2010-05-11 Microsoft Corporation Conversation grouping of electronic mail records
US7841940B2 (en) * 2003-07-14 2010-11-30 Astav, Inc Human test based on human conceptual capabilities
US7562119B2 (en) * 2003-07-15 2009-07-14 Mindshare Design, Inc. Systems and methods for automatically updating electronic mail access lists
ITRM20030353A1 (en) * 2003-07-17 2005-01-18 Diego Angelo Tomaselli METHOD FOR ANTI-SPAM MANAGEMENT OF E-MAIL MESSAGES.
US20050015455A1 (en) * 2003-07-18 2005-01-20 Liu Gary G. SPAM processing system and methods including shared information among plural SPAM filters
US7814545B2 (en) 2003-07-22 2010-10-12 Sonicwall, Inc. Message classification using classifiers
US7627635B1 (en) 2003-07-28 2009-12-01 Aol Llc Managing self-addressed electronic messages
US8892673B1 (en) * 2003-08-08 2014-11-18 Radix Holdings, Llc Hybrid challenge-response
US8645697B1 (en) 2003-08-08 2014-02-04 Radix Holdings, Llc Message authorization
US8275838B2 (en) * 2003-08-14 2012-09-25 International Business Machines Corporation Conditioned delivery of electronic mail
US8321512B2 (en) * 2003-08-22 2012-11-27 Geobytes, Inc. Method and software product for identifying unsolicited emails
US20050044155A1 (en) * 2003-08-22 2005-02-24 David Kaminski Method of authorizing email senders
US20050044156A1 (en) * 2003-08-22 2005-02-24 David Kaminski Verified registry
US20050044154A1 (en) * 2003-08-22 2005-02-24 David Kaminski System and method of filtering unwanted electronic mail messages
US20050060643A1 (en) * 2003-08-25 2005-03-17 Miavia, Inc. Document similarity detection and classification system
US7835294B2 (en) 2003-09-03 2010-11-16 Gary Stephen Shuster Message filtering method
AU2003244552B1 (en) * 2003-09-04 2004-04-29 New Millenium Solutions Pty Ltd Method and system for blocking unwanted e-mail
US20050055404A1 (en) * 2003-09-04 2005-03-10 Information Processing Corporation E-mail server registry and method
US7451487B2 (en) 2003-09-08 2008-11-11 Sonicwall, Inc. Fraudulent message detection
US20050055415A1 (en) * 2003-09-08 2005-03-10 Spectaris, Llc Two-tier email filtering
US8271588B1 (en) 2003-09-24 2012-09-18 Symantec Corporation System and method for filtering fraudulent email messages
US20050076220A1 (en) * 2003-10-02 2005-04-07 Xiao Quan Zhang Method and System for Using a Point System to Deliver Advertisement Emails and to Stop Spam
WO2005034537A1 (en) * 2003-10-08 2005-04-14 Three B Technologies Pty Ltd Method and system for authorising short message service (sms) messages
US20050081051A1 (en) * 2003-10-09 2005-04-14 International Business Machines Corporation Mitigating self-propagating e-mail viruses
US7715059B2 (en) * 2003-10-22 2010-05-11 International Business Machines Corporation Facsimile system, method and program product with junk fax disposal
US7395314B2 (en) * 2003-10-28 2008-07-01 Mindshare Design, Inc. Systems and methods for governing the performance of high volume electronic mail delivery
KR20050048890A (en) * 2003-11-20 2005-05-25 (주)솔메이즈 Mail system for kids
US7660857B2 (en) * 2003-11-21 2010-02-09 Mindshare Design, Inc. Systems and methods for automatically updating electronic mail access lists
US20050125667A1 (en) * 2003-12-09 2005-06-09 Tim Sullivan Systems and methods for authorizing delivery of incoming messages
US7548968B1 (en) 2003-12-10 2009-06-16 Markmonitor Inc. Policing internet domains
WO2005062843A2 (en) 2003-12-19 2005-07-14 America On Line, Inc Community messaging lists for authorization to deliver electronic messages
US20050193130A1 (en) * 2004-01-22 2005-09-01 Mblx Llc Methods and systems for confirmation of availability of messaging account to user
US7076347B2 (en) * 2004-01-23 2006-07-11 General Motors Corporation Brake booster vacuum sensor diagnostic
US7693943B2 (en) 2004-01-23 2010-04-06 International Business Machines Corporation Classification of electronic mail into multiple directories based upon their spam-like properties
US8886727B1 (en) * 2004-01-27 2014-11-11 Sonicwall, Inc. Message distribution control
US8224902B1 (en) * 2004-02-04 2012-07-17 At&T Intellectual Property Ii, L.P. Method and apparatus for selective email processing
US9471712B2 (en) 2004-02-09 2016-10-18 Dell Software Inc. Approximate matching of strings for message filtering
US8856239B1 (en) 2004-02-10 2014-10-07 Sonicwall, Inc. Message classification based on likelihood of spoofing
US7469292B2 (en) * 2004-02-11 2008-12-23 Aol Llc Managing electronic messages using contact information
US8799164B2 (en) 2004-02-26 2014-08-05 David C Reardon Financial transaction system with integrated electronic messaging, control of marketing data, and user defined charges for receiving messages
US8346660B2 (en) * 2004-02-26 2013-01-01 David C. Reardon System and method for two-way transfer of funds and electronic content between summa account users with gathering of behavioral metrics and management of multiple currencies and escrow accounts
US7873572B2 (en) * 2004-02-26 2011-01-18 Reardon David C Financial transaction system with integrated electronic messaging, control of marketing data, and user defined charges for receiving messages
US20090119159A1 (en) * 2007-10-31 2009-05-07 David C. Reardon System and Method for Transferring Funds to Recipients of Electronic Messages
US20050192819A1 (en) * 2004-02-27 2005-09-01 Smith Michael D. Method and system for reducing unsolicited messages using variable pricing and conditional redemption
US8214438B2 (en) * 2004-03-01 2012-07-03 Microsoft Corporation (More) advanced spam detection features
US20050204006A1 (en) * 2004-03-12 2005-09-15 Purcell Sean E. Message junk rating interface
US20050204005A1 (en) * 2004-03-12 2005-09-15 Purcell Sean E. Selective treatment of messages based on junk rating
US8595146B1 (en) 2004-03-15 2013-11-26 Aol Inc. Social networking permissions
DK1733532T3 (en) * 2004-03-30 2008-11-03 Imencro Software Sa Filters and methods for filtering electronic messages
US7747860B2 (en) 2004-05-04 2010-06-29 Message Level, Llc System and method for preventing delivery of unsolicited and undesired electronic messages by key generation and comparison
US7941490B1 (en) 2004-05-11 2011-05-10 Symantec Corporation Method and apparatus for detecting spam in email messages and email attachments
AU2005247504B2 (en) * 2004-05-25 2008-12-18 Reflexion Networks, Inc. A system and method for controlling access to an electronic message recipient
US7664819B2 (en) * 2004-06-29 2010-02-16 Microsoft Corporation Incremental anti-spam lookup and update service
US7343624B1 (en) 2004-07-13 2008-03-11 Sonicwall, Inc. Managing infectious messages as identified by an attachment
US9154511B1 (en) 2004-07-13 2015-10-06 Dell Software Inc. Time zero detection of infectious messages
US7904517B2 (en) * 2004-08-09 2011-03-08 Microsoft Corporation Challenge response systems
US7660865B2 (en) * 2004-08-12 2010-02-09 Microsoft Corporation Spam filtering with probabilistic secure hashes
US8146016B2 (en) 2004-08-16 2012-03-27 Microsoft Corporation User interface for displaying a gallery of formatting options applicable to a selected object
US7895531B2 (en) * 2004-08-16 2011-02-22 Microsoft Corporation Floating command object
US9015621B2 (en) 2004-08-16 2015-04-21 Microsoft Technology Licensing, Llc Command user interface for displaying multiple sections of software functionality controls
US8117542B2 (en) 2004-08-16 2012-02-14 Microsoft Corporation User interface for displaying selectable software functionality controls that are contextually relevant to a selected object
US7703036B2 (en) 2004-08-16 2010-04-20 Microsoft Corporation User interface for displaying selectable software functionality controls that are relevant to a selected object
US8255828B2 (en) 2004-08-16 2012-08-28 Microsoft Corporation Command user interface for displaying selectable software functionality controls
US7500265B2 (en) * 2004-08-27 2009-03-03 International Business Machines Corporation Apparatus and method to identify SPAM emails
US8037123B2 (en) 2004-08-27 2011-10-11 Microsoft Corporation Securely and efficiently extending data processing pipeline functionality
CA2484509C (en) * 2004-09-14 2009-04-21 Jean-Louis Vill Method and system for filtering electronic messages
US7747966B2 (en) * 2004-09-30 2010-06-29 Microsoft Corporation User interface for providing task management and calendar information
US20150195231A1 (en) * 2004-09-30 2015-07-09 Nahush Mahajan System and Method for Avoiding Loops in Automatic Message Processing
US20080086532A1 (en) * 2004-10-04 2008-04-10 Brian Cunningham Method for the Verification of Electronic Message Delivery and for the Collection of Data Related to Electronic Messages Sent with False Origination Addresses
US8180834B2 (en) 2004-10-07 2012-05-15 Computer Associates Think, Inc. System, method, and computer program product for filtering messages and training a classification module
US8635690B2 (en) 2004-11-05 2014-01-21 Mcafee, Inc. Reputation based message processing
US20060168009A1 (en) * 2004-11-19 2006-07-27 International Business Machines Corporation Blocking unsolicited instant messages
US7756933B2 (en) * 2004-12-13 2010-07-13 Collactive Ltd. System and method for deterring rogue users from attacking protected legitimate users
US20060161989A1 (en) * 2004-12-13 2006-07-20 Eran Reshef System and method for deterring rogue users from attacking protected legitimate users
BE1016369A5 (en) * 2004-12-22 2006-09-05 Underside S P R L Undesired electronic mail i.e. spam, reception detecting and distribution preventing method for computer management system, involves storing mail address, after request of address authentication and when authentication is not obtained
US7603422B2 (en) * 2004-12-27 2009-10-13 Microsoft Corporation Secure safe sender list
US7599993B1 (en) 2004-12-27 2009-10-06 Microsoft Corporation Secure safe sender list
US20060149820A1 (en) * 2005-01-04 2006-07-06 International Business Machines Corporation Detecting spam e-mail using similarity calculations
US8087068B1 (en) 2005-03-08 2011-12-27 Google Inc. Verifying access to a network account over multiple user communication portals based on security criteria
US7590698B1 (en) 2005-03-14 2009-09-15 Symantec Corporation Thwarting phishing attacks by using pre-established policy files
US7650383B2 (en) * 2005-03-15 2010-01-19 Aol Llc Electronic message system with federation of trusted senders
JP2008538267A (en) * 2005-03-17 2008-10-16 マーク・イー・ディロン System, method, and apparatus for capturing a large volume of distributed electronic messages
US7647381B2 (en) * 2005-04-04 2010-01-12 Aol Llc Federated challenge credit system
US8135778B1 (en) 2005-04-27 2012-03-13 Symantec Corporation Method and apparatus for certifying mass emailings
US20060272006A1 (en) * 2005-05-27 2006-11-30 Shaohong Wei Systems and methods for processing electronic data
US7937480B2 (en) * 2005-06-02 2011-05-03 Mcafee, Inc. Aggregation of reputation data
US8010609B2 (en) 2005-06-20 2011-08-30 Symantec Corporation Method and apparatus for maintaining reputation lists of IP addresses to detect email spam
US7739337B1 (en) 2005-06-20 2010-06-15 Symantec Corporation Method and apparatus for grouping spam email messages
US20070026372A1 (en) * 2005-07-27 2007-02-01 Huelsbergen Lorenz F Method for providing machine access security by deciding whether an anonymous responder is a human or a machine using a human interactive proof
US7930353B2 (en) * 2005-07-29 2011-04-19 Microsoft Corporation Trees of classifiers for detecting email spam
EP1922631B1 (en) 2005-08-09 2015-04-15 Message Level, LLC System and method for preventing delivery of unsolicited and undesired electronic messages by key generation and comparison
US8239882B2 (en) 2005-08-30 2012-08-07 Microsoft Corporation Markup based extensibility for user interfaces
US8689137B2 (en) * 2005-09-07 2014-04-01 Microsoft Corporation Command user interface for displaying selectable functionality controls in a database application
US9542667B2 (en) * 2005-09-09 2017-01-10 Microsoft Technology Licensing, Llc Navigating messages within a thread
US8627222B2 (en) 2005-09-12 2014-01-07 Microsoft Corporation Expanded search and find user interface
US8874477B2 (en) 2005-10-04 2014-10-28 Steven Mark Hoffberg Multifactorial optimization system and method
US20070088793A1 (en) * 2005-10-17 2007-04-19 Landsman Richard A Filter for instant messaging
WO2007045049A1 (en) * 2005-10-21 2007-04-26 Boxsentry Pte Limited Electronic message authentication
US8065370B2 (en) 2005-11-03 2011-11-22 Microsoft Corporation Proofs to filter spam
US20070180034A1 (en) * 2006-02-02 2007-08-02 Ditroia John Method and system for filtering communication
US8572381B1 (en) * 2006-02-06 2013-10-29 Cisco Technology, Inc. Challenge protected user queries
US8601160B1 (en) 2006-02-09 2013-12-03 Mcafee, Inc. System, method and computer program product for gathering information relating to electronic content utilizing a DNS server
EP1999613A4 (en) 2006-02-14 2014-08-06 Message Level Llc Method for predelivery verification of an intended recipient of an electronic message and dynamic generation of message content upon verification
US20070226804A1 (en) * 2006-03-22 2007-09-27 Method and system for preventing an unauthorized message
US9727989B2 (en) 2006-06-01 2017-08-08 Microsoft Technology Licensing, Llc Modifying and formatting a chart using pictorially provided chart elements
US8605090B2 (en) * 2006-06-01 2013-12-10 Microsoft Corporation Modifying and formatting a chart using pictorially provided chart elements
US7680891B1 (en) 2006-06-19 2010-03-16 Google Inc. CAPTCHA-based spam control for content creation systems
US8023927B1 (en) 2006-06-29 2011-09-20 Google Inc. Abuse-resistant method of registering user accounts with an online service
US9177293B1 (en) * 2006-07-21 2015-11-03 Cousins Intellectual Properties Llc Spam filtering system and method
US7519674B2 (en) * 2006-09-01 2009-04-14 Nuxo Technologies, Inc. Method and apparatus for filtering electronic messages
US20080065729A1 (en) * 2006-09-08 2008-03-13 Pitney Bowes Incorporated Method and system for service provider to be compensated for delivering e-mail messages while reducing amount of unsolicited e-mail messages
US8180835B1 (en) 2006-10-14 2012-05-15 Engate Technology Corporation System and method for protecting mail servers from mail flood attacks
US20080104181A1 (en) * 2006-10-26 2008-05-01 Tal Golan Electronic mail processing system
JP2008139926A (en) * 2006-11-30 2008-06-19 Database Consultants Corp Email server apparatus and email server program
US8224905B2 (en) 2006-12-06 2012-07-17 Microsoft Corporation Spam filtration utilizing sender activity data
US7949716B2 (en) 2007-01-24 2011-05-24 Mcafee, Inc. Correlation and analysis of entity attributes
US8763114B2 (en) 2007-01-24 2014-06-24 Mcafee, Inc. Detecting image spam
US7779156B2 (en) * 2007-01-24 2010-08-17 Mcafee, Inc. Reputation based load balancing
US8214497B2 (en) 2007-01-24 2012-07-03 Mcafee, Inc. Multi-dimensional reputation scoring
US8179798B2 (en) * 2007-01-24 2012-05-15 Mcafee, Inc. Reputation based connection throttling
GB0702763D0 (en) * 2007-02-13 2007-03-21 Skype Ltd Messaging system and method
US8725597B2 (en) * 2007-04-25 2014-05-13 Google Inc. Merchant scoring system and transactional database
US8762880B2 (en) 2007-06-29 2014-06-24 Microsoft Corporation Exposing non-authoring features through document status information in an out-space user interface
US8201103B2 (en) * 2007-06-29 2012-06-12 Microsoft Corporation Accessing an out-space user interface for a document editor program
US8484578B2 (en) 2007-06-29 2013-07-09 Microsoft Corporation Communication between a document editor in-space user interface and a document editor out-space user interface
US8185930B2 (en) * 2007-11-06 2012-05-22 Mcafee, Inc. Adjusting filter or classification control settings
US8045458B2 (en) * 2007-11-08 2011-10-25 Mcafee, Inc. Prioritizing network traffic
US20090138711A1 (en) * 2007-11-21 2009-05-28 Dennis Heimbigner Sender Email Address Verification Using Reachback
US8160975B2 (en) * 2008-01-25 2012-04-17 Mcafee, Inc. Granular support vector machine with random granularity
US9588781B2 (en) 2008-03-31 2017-03-07 Microsoft Technology Licensing, Llc Associating command surfaces with multiple active components
US8589503B2 (en) 2008-04-04 2013-11-19 Mcafee, Inc. Prioritizing network traffic
US9665850B2 (en) * 2008-06-20 2017-05-30 Microsoft Technology Licensing, Llc Synchronized conversation-centric message list and message reading pane
US8402096B2 (en) * 2008-06-24 2013-03-19 Microsoft Corporation Automatic conversation techniques
US20110081018A1 (en) * 2008-08-14 2011-04-07 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Obfuscating reception of communiqué affiliated with a source entity
US20100042667A1 (en) * 2008-08-14 2010-02-18 Searete Llc, A Limited Liability Corporation Of The State Of Delaware System and method for transmitting illusory identification characteristics
US8730836B2 (en) * 2008-08-14 2014-05-20 The Invention Science Fund I, Llc Conditionally intercepting data indicating one or more aspects of a communiqué to obfuscate the one or more aspects of the communiqué
US20110093806A1 (en) * 2008-08-14 2011-04-21 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Obfuscating reception of communiqué affiliated with a source entity
US20110110518A1 (en) * 2008-08-14 2011-05-12 Searete Llc Obfuscating reception of communiqué affiliated with a source entity in response to receiving information indicating reception of the communiqué
US20110166972A1 (en) * 2008-08-14 2011-07-07 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Conditionally obfuscating one or more secret entities with respect to one or more billing statements
US20100042669A1 (en) * 2008-08-14 2010-02-18 Searete Llc, A Limited Liability Corporation Of The State Of Delaware System and method for modifying illusory user identification characteristics
US8850044B2 (en) * 2008-08-14 2014-09-30 The Invention Science Fund I, Llc Obfuscating identity of a source entity affiliated with a communique in accordance with conditional directive provided by a receiving entity
US20110041185A1 (en) * 2008-08-14 2011-02-17 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Obfuscating identity of a source entity affiliated with a communiqué directed to a receiving user and in accordance with conditional directive provided by the receiving user
US20110131409A1 (en) * 2008-08-14 2011-06-02 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Conditionally intercepting data indicating one or more aspects of a communiqué to obfuscate the one or more aspects of the communiqué
US20110107427A1 (en) * 2008-08-14 2011-05-05 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Obfuscating reception of communiqué affiliated with a source entity in response to receiving information indicating reception of the communiqué
US8583553B2 (en) 2008-08-14 2013-11-12 The Invention Science Fund I, Llc Conditionally obfuscating one or more secret entities with respect to one or more billing statements related to one or more communiqués addressed to the one or more secret entities
US20100039218A1 (en) * 2008-08-14 2010-02-18 Searete Llc, A Limited Liability Corporation Of The State Of Delaware System and method for transmitting illusory and non-illusory identification characteristics
US9659188B2 (en) * 2008-08-14 2017-05-23 Invention Science Fund I, Llc Obfuscating identity of a source entity affiliated with a communiqué directed to a receiving user and in accordance with conditional directive provided by the receiving use
US20110166973A1 (en) * 2008-08-14 2011-07-07 Searete Llc Conditionally obfuscating one or more secret entities with respect to one or more billing statements related to one or more communiqués addressed to the one or more secret entities
US20110161217A1 (en) * 2008-08-14 2011-06-30 Searete Llc Conditionally obfuscating one or more secret entities with respect to one or more billing statements
US8929208B2 (en) * 2008-08-14 2015-01-06 The Invention Science Fund I, Llc Conditionally releasing a communiqué determined to be affiliated with a particular source entity in response to detecting occurrence of one or more environmental aspects
US9641537B2 (en) * 2008-08-14 2017-05-02 Invention Science Fund I, Llc Conditionally releasing a communiqué determined to be affiliated with a particular source entity in response to detecting occurrence of one or more environmental aspects
US8626848B2 (en) * 2008-08-14 2014-01-07 The Invention Science Fund I, Llc Obfuscating identity of a source entity affiliated with a communiqué in accordance with conditional directive provided by a receiving entity
US20100318595A1 (en) * 2008-08-14 2010-12-16 Searete Llc, A Limited Liability Corporation Of The State Of Delaware System and method for conditionally transmitting one or more locum tenentes
KR20100034637A (en) * 2008-09-24 2010-04-01 삼성전자주식회사 The data transmitting method in image forming apparatus and the image forming apparatus for performing the method
US9046983B2 (en) 2009-05-12 2015-06-02 Microsoft Technology Licensing, Llc Hierarchically-organized control galleries
US20110128906A1 (en) * 2009-11-27 2011-06-02 Nokia Corporation Method and apparatus for selectively receiving communication
US20110225076A1 (en) * 2010-03-09 2011-09-15 Google Inc. Method and system for detecting fraudulent internet merchants
US8621638B2 (en) 2010-05-14 2013-12-31 Mcafee, Inc. Systems and methods for classification of messaging entities
US8516062B2 (en) 2010-10-01 2013-08-20 @Pay Ip Holdings Llc Storage, communication, and display of task-related data
US8918467B2 (en) * 2010-10-01 2014-12-23 Clover Leaf Environmental Solutions, Inc. Generation and retrieval of report information
US9589254B2 (en) 2010-12-08 2017-03-07 Microsoft Technology Licensing, Llc Using e-mail message characteristics for prioritization
US20120215863A1 (en) * 2011-02-17 2012-08-23 Prolifiq Software Inc. Dedicated message channel
US20130054316A1 (en) * 2011-08-22 2013-02-28 Microsoft Corporation Managing presentation of commercial communications including electronic mail and advertisements
US8396935B1 (en) * 2012-04-10 2013-03-12 Google Inc. Discovering spam merchants using product feed similarity
US9306879B2 (en) 2012-06-08 2016-04-05 Apple Inc. Message-based identification of an electronic device
US9811830B2 (en) 2013-07-03 2017-11-07 Google Inc. Method, medium, and system for online fraud prevention based on user physical location data
US20150172320A1 (en) * 2013-12-17 2015-06-18 Khalifa University of Science, Technology, and Research Method and devices for access control
DE102014003520A1 (en) * 2014-03-16 2015-09-17 Tobias Rückert Method and system for processing an electronic message
US9928465B2 (en) 2014-05-20 2018-03-27 Oath Inc. Machine learning and validation of account names, addresses, and/or identifiers
US9462011B2 (en) * 2014-05-30 2016-10-04 Ca, Inc. Determining trustworthiness of API requests based on source computer applications' responses to attack messages
US10148606B2 (en) * 2014-07-24 2018-12-04 Twitter, Inc. Multi-tiered anti-spamming systems and methods
US9871884B2 (en) * 2014-09-30 2018-01-16 Xiaomi Inc. Method and device for transferring messages
US10057237B2 (en) * 2015-02-17 2018-08-21 Ca, Inc. Provide insensitive summary for an encrypted document
US10061930B2 (en) * 2016-08-11 2018-08-28 International Business Machines Corporation Strong confirmation mechanism for manipulation of sensitive configuration data
US10372927B2 (en) 2016-08-11 2019-08-06 International Business Machines Corporation Strong confirmation mechanism for manipulation of sensitive configuration data
US10657182B2 (en) * 2016-09-20 2020-05-19 International Business Machines Corporation Similar email spam detection

Citations (80)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4977520A (en) 1988-02-03 1990-12-11 Ibm Corp. Method to facilitate a reply to electronic meeting invitation in an interactive multi-terminal system employing electronic calendars
US5040141A (en) 1986-11-25 1991-08-13 Hitachi, Ltd. Method for administrating reply mail in electronic mail system
EP0463252A1 (en) 1990-06-28 1992-01-02 International Business Machines Corporation Message handling in data processing apparatus
US5093918A (en) * 1988-12-22 1992-03-03 International Business Machines Corporation System using independent attribute lists to show status of shared mail object among respective users
US5159673A (en) 1990-03-22 1992-10-27 Square D Company Apparatus for networking programmable logic controllers to host computers
US5204961A (en) 1990-06-25 1993-04-20 Digital Equipment Corporation Computer network operating with multilevel hierarchical security with selectable common trust realms and corresponding security protocols
US5245532A (en) 1988-06-16 1993-09-14 International Business Machines Corporation Electronic mail follow-up system
US5283856A (en) 1991-10-04 1994-02-01 Beyond, Inc. Event-driven rule-based messaging system
WO1994006236A2 (en) 1992-08-26 1994-03-17 Bellsouth Corporation Personal number communications system
US5319776A (en) 1990-04-19 1994-06-07 Hilgraeve Corporation In transit detection of computer virus with safeguard
US5333266A (en) 1992-03-27 1994-07-26 International Business Machines Corporation Method and apparatus for message handling in computer systems
US5377354A (en) * 1989-08-15 1994-12-27 Digital Equipment Corporation Method and system for sorting and prioritizing electronic mail messages
EP0651533A2 (en) 1993-11-02 1995-05-03 Sun Microsystems, Inc. Method and apparatus for privacy and authentication in a mobile wireless network
US5423042A (en) 1992-10-23 1995-06-06 International Business Machines Corporation Remote procedure execution
US5448734A (en) 1991-09-30 1995-09-05 International Business Machines Corporation Selective distribution of messages using named pipes
US5471519A (en) 1993-02-26 1995-11-28 Bellsouth Corporation Communications monitoring and control system
US5473671A (en) 1994-03-11 1995-12-05 At&T Corp. Selective screening of incoming calls for cellular telephone systems
EP0686327A1 (en) 1992-12-14 1995-12-13 The Commonwealth Of Australia Message document security
WO1996009714A1 (en) 1994-09-19 1996-03-28 Bell Communications Research, Inc. Personal communications internetworking
EP0721268A2 (en) 1995-01-05 1996-07-10 International Business Machines Corporation Method and apparatus for automatic e-mail response to a third party
US5539828A (en) 1994-05-31 1996-07-23 Intel Corporation Apparatus and method for providing secured communications
EP0725523A2 (en) 1995-01-05 1996-08-07 International Business Machines Corporation Transaction message routing in digital communications networks
WO1996024213A1 (en) 1995-02-01 1996-08-08 Freemark Communications, Inc. System and method for providing end-user free email
US5548789A (en) 1991-01-24 1996-08-20 Canon Kabushiki Kaisha Message communication processing apparatus for selectively converting storing and transmitting messages of different lengths
US5600799A (en) 1990-04-27 1997-02-04 National Semiconductor Corporation Status batching and filtering in a media access control/host system interface unit
US5604803A (en) 1994-06-03 1997-02-18 Sun Microsystems, Inc. Method and apparatus for secure remote authentication in a public network
US5608786A (en) 1994-12-23 1997-03-04 Alphanet Telecom Inc. Unified messaging system and method
EP0760565A1 (en) 1995-08-28 1997-03-05 Feldbau, Ofra Apparatus and method for authenticating the dispatch and contents of documents
US5619648A (en) * 1994-11-30 1997-04-08 Lucent Technologies Inc. Message filtering techniques
WO1997014234A2 (en) 1995-09-25 1997-04-17 Netspeak Corporation Point-to-point internet protocol
US5627764A (en) 1991-10-04 1997-05-06 Banyan Systems, Inc. Automatic electronic messaging system with feedback and work flow administration
US5630123A (en) 1994-09-28 1997-05-13 I2 Technologies, Inc. Software system utilizing a filtered priority queue and method of operation
US5632018A (en) 1993-01-18 1997-05-20 Fujitsu Limited Electronic mail system
WO1997020423A1 (en) 1995-11-29 1997-06-05 Bell Communications Research, Inc. A system and method for automatically screening and directing incoming calls
WO1997023082A1 (en) 1995-12-15 1997-06-26 At & T Corp. Guest mail: communicating electronic messages between disparate messaging systems
WO1997024825A2 (en) 1995-12-29 1997-07-10 Tixi.Com Gmbh Telecommunication Systems Method and microcomputer system for the automatic, secure and direct transmission of data
WO1997026709A1 (en) 1996-01-18 1997-07-24 Pocketscience, Inc. Electronic messaging system and method
US5655079A (en) 1989-07-31 1997-08-05 Hitachi, Ltd. Data processing system and data transmission and processing method
US5721779A (en) 1995-08-28 1998-02-24 Funk Software, Inc. Apparatus and methods for verifying the identity of a party
US5734903A (en) 1994-05-13 1998-03-31 Apple Computer, Inc. System and method for object oriented message filtering
US5742769A (en) 1996-05-06 1998-04-21 Banyan Systems, Inc. Directory with options for access to and display of email addresses
US5781857A (en) 1996-06-28 1998-07-14 Motorola, Inc. Method of establishing an email monitor responsive to a wireless communications system user
WO1998037675A1 (en) 1997-02-19 1998-08-27 Verifone, Inc. A system, method and article of manufacture for secure digital certification of electronic commerce
DE19708856A1 (en) 1997-03-05 1998-09-10 Bosch Gmbh Robert Digital component test method for broadband communication
US5826022A (en) 1996-04-05 1998-10-20 Sun Microsystems, Inc. Method and apparatus for receiving electronic mail
US5835722A (en) 1996-06-27 1998-11-10 Logon Data Corporation System to control content and prohibit certain interactive attempts by a person using a personal computer
EP0883271A2 (en) 1997-04-15 1998-12-09 Hewlett-Packard Company Method and system for managing data service systems
US5859967A (en) * 1996-07-09 1999-01-12 Faxsav Incorporated Method and system for relaying communications from authorized users
US5884033A (en) 1996-05-15 1999-03-16 Spyglass, Inc. Internet filtering system for filtering data transferred over the internet utilizing immediate and deferred filtering actions
US5893911A (en) 1996-04-17 1999-04-13 Neon Software, Inc. Method for defining and applying rules for message distribution for transaction processing in a distributed application
US5909589A (en) * 1996-11-12 1999-06-01 Lance T. Parker Internet based training
US5917489A (en) 1997-01-31 1999-06-29 Microsoft Corporation System and method for creating, editing, and distributing rules for processing electronic messages
US5930479A (en) * 1996-10-21 1999-07-27 At&T Corp Communications addressing system
US5937162A (en) 1995-04-06 1999-08-10 Exactis.Com, Inc. Method and apparatus for high volume e-mail delivery
US5999600A (en) 1996-10-14 1999-12-07 Samsung Electronics Co., Ltd. Facsimile mail system and method for controlling the same
US5999967A (en) * 1997-08-17 1999-12-07 Sundsted; Todd Electronic mail filtering by electronic stamp
US6014634A (en) 1995-12-26 2000-01-11 Supermarkets Online, Inc. System and method for providing shopping aids and incentives to customers through a computer network
US6073142A (en) 1997-06-23 2000-06-06 Park City Group Automated post office based rule analysis of e-mail messages and other data objects for controlled distribution in network environments
US6092101A (en) 1997-06-16 2000-07-18 Digital Equipment Corporation Method for filtering mail messages for a plurality of client computers connected to a mail service system
US6112227A (en) * 1998-08-06 2000-08-29 Heiner; Jeffrey Nelson Filter-in method for reducing junk e-mail
US6173322B1 (en) 1997-06-05 2001-01-09 Silicon Graphics, Inc. Network request distribution based on static rules and dynamic performance data
US6182118B1 (en) 1995-05-08 2001-01-30 Cranberry Properties Llc System and method for distributing electronic messages in accordance with rules
US6189026B1 (en) 1997-06-16 2001-02-13 Digital Equipment Corporation Technique for dynamically generating an address book in a distributed electronic mail system
WO2001016695A1 (en) 1999-09-01 2001-03-08 Katsikas Peter L System for eliminating unauthorized electronic mail
US6373950B1 (en) 1996-06-17 2002-04-16 Hewlett-Packard Company System, method and article of manufacture for transmitting messages within messages utilizing an extensible, flexible architecture
US6393465B2 (en) 1997-11-25 2002-05-21 Nixmail Corporation Junk electronic mail detector and eliminator
WO2002077768A2 (en) 2001-03-22 2002-10-03 Michael Chung Methods and systems for electronic mail, internet target and direct marketing, and electronic mail banner
US6484197B1 (en) 1998-11-07 2002-11-19 International Business Machines Corporation Filtering incoming e-mail
US20020199095A1 (en) 1997-07-24 2002-12-26 Jean-Christophe Bandini Method and system for filtering communication
WO2003044617A2 (en) 2001-10-03 2003-05-30 Reginald Adkins Authorized email control system
US20040236835A1 (en) 2003-05-24 2004-11-25 Blankenship Mark H. Direct mail manager for tracking customer attributes
US20040243698A1 (en) 2003-05-24 2004-12-02 Blankenship Mark H. Tracking purchaser attributes
US20040243676A1 (en) 2003-05-24 2004-12-02 Blankenship Mark H. Message manager for tracking customer attributes
US20050015481A1 (en) 2003-05-24 2005-01-20 Blankenship Mark H. Register manager for tracking customer attributes
US20050015482A1 (en) 2003-05-24 2005-01-20 Blankenship Mark H. Attachment manager for tracking customer attributes
US20050076220A1 (en) 2003-10-02 2005-04-07 Xiao Quan Zhang Method and System for Using a Point System to Deliver Advertisement Emails and to Stop Spam
US20050081059A1 (en) 1997-07-24 2005-04-14 Bandini Jean-Christophe Denis Method and system for e-mail filtering
US6883095B2 (en) 2000-12-19 2005-04-19 Singlesigon. Net Inc. System and method for password throttling
US7383433B2 (en) 2001-07-31 2008-06-03 Sun Microsystems, Inc. Trust spectrum for certificate distribution in distributed peer-to-peer networks
US7512788B2 (en) 2002-12-10 2009-03-31 International Business Machines Corporation Method and apparatus for anonymous group messaging in a distributed messaging system

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6023723A (en) 1997-12-22 2000-02-08 Accepted Marketing, Inc. Method and system for filtering unwanted junk e-mail utilizing a plurality of filtering mechanisms
US6052709A (en) 1997-12-23 2000-04-18 Bright Light Technologies, Inc. Apparatus and method for controlling delivery of unsolicited electronic mail
US5999932A (en) 1998-01-13 1999-12-07 Bright Light Technologies, Inc. System and method for filtering unsolicited electronic mail messages using data matching and heuristic processing
US6195698B1 (en) 1998-04-13 2001-02-27 Compaq Computer Corporation Method for selectively restricting access to computer systems
JP3942267B2 (en) 1998-04-21 2007-07-11 東芝テック株式会社 E-mail system

Patent Citations (84)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5040141A (en) 1986-11-25 1991-08-13 Hitachi, Ltd. Method for administrating reply mail in electronic mail system
US4977520A (en) 1988-02-03 1990-12-11 Ibm Corp. Method to facilitate a reply to electronic meeting invitation in an interactive multi-terminal system employing electronic calendars
US5245532A (en) 1988-06-16 1993-09-14 International Business Machines Corporation Electronic mail follow-up system
US5093918A (en) * 1988-12-22 1992-03-03 International Business Machines Corporation System using independent attribute lists to show status of shared mail object among respective users
US5655079A (en) 1989-07-31 1997-08-05 Hitachi, Ltd. Data processing system and data transmission and processing method
US5377354A (en) * 1989-08-15 1994-12-27 Digital Equipment Corporation Method and system for sorting and prioritizing electronic mail messages
US5159673A (en) 1990-03-22 1992-10-27 Square D Company Apparatus for networking programmable logic controllers to host computers
US5319776A (en) 1990-04-19 1994-06-07 Hilgraeve Corporation In transit detection of computer virus with safeguard
US5600799A (en) 1990-04-27 1997-02-04 National Semiconductor Corporation Status batching and filtering in a media access control/host system interface unit
US5204961A (en) 1990-06-25 1993-04-20 Digital Equipment Corporation Computer network operating with multilevel hierarchical security with selectable common trust realms and corresponding security protocols
EP0463252A1 (en) 1990-06-28 1992-01-02 International Business Machines Corporation Message handling in data processing apparatus
US5548789A (en) 1991-01-24 1996-08-20 Canon Kabushiki Kaisha Message communication processing apparatus for selectively converting storing and transmitting messages of different lengths
US5448734A (en) 1991-09-30 1995-09-05 International Business Machines Corporation Selective distribution of messages using named pipes
US5283856A (en) 1991-10-04 1994-02-01 Beyond, Inc. Event-driven rule-based messaging system
US5627764A (en) 1991-10-04 1997-05-06 Banyan Systems, Inc. Automatic electronic messaging system with feedback and work flow administration
US5333266A (en) 1992-03-27 1994-07-26 International Business Machines Corporation Method and apparatus for message handling in computer systems
WO1994006236A2 (en) 1992-08-26 1994-03-17 Bellsouth Corporation Personal number communications system
US5423042A (en) 1992-10-23 1995-06-06 International Business Machines Corporation Remote procedure execution
EP0686327A1 (en) 1992-12-14 1995-12-13 The Commonwealth Of Australia Message document security
US5832227A (en) 1992-12-14 1998-11-03 The Commonwealth Of Australia Of Anzak Park Method for providing message document security by deleting predetermined header portions and attaching predetermined header portions when seal is validly associated with message or document
US5632018A (en) 1993-01-18 1997-05-20 Fujitsu Limited Electronic mail system
US5471519A (en) 1993-02-26 1995-11-28 Bellsouth Corporation Communications monitoring and control system
EP0651533A2 (en) 1993-11-02 1995-05-03 Sun Microsystems, Inc. Method and apparatus for privacy and authentication in a mobile wireless network
US5473671A (en) 1994-03-11 1995-12-05 At&T Corp. Selective screening of incoming calls for cellular telephone systems
US5734903A (en) 1994-05-13 1998-03-31 Apple Computer, Inc. System and method for object oriented message filtering
US5796840A (en) * 1994-05-31 1998-08-18 Intel Corporation Apparatus and method for providing secured communications
US5539828A (en) 1994-05-31 1996-07-23 Intel Corporation Apparatus and method for providing secured communications
US5604803A (en) 1994-06-03 1997-02-18 Sun Microsystems, Inc. Method and apparatus for secure remote authentication in a public network
US5742668A (en) 1994-09-19 1998-04-21 Bell Communications Research, Inc. Electronic massaging network
WO1996009714A1 (en) 1994-09-19 1996-03-28 Bell Communications Research, Inc. Personal communications internetworking
US5630123A (en) 1994-09-28 1997-05-13 I2 Technologies, Inc. Software system utilizing a filtered priority queue and method of operation
US5619648A (en) * 1994-11-30 1997-04-08 Lucent Technologies Inc. Message filtering techniques
US5608786A (en) 1994-12-23 1997-03-04 Alphanet Telecom Inc. Unified messaging system and method
EP0721268A2 (en) 1995-01-05 1996-07-10 International Business Machines Corporation Method and apparatus for automatic e-mail response to a third party
EP0725523A2 (en) 1995-01-05 1996-08-07 International Business Machines Corporation Transaction message routing in digital communications networks
WO1996024213A1 (en) 1995-02-01 1996-08-08 Freemark Communications, Inc. System and method for providing end-user free email
US5937162A (en) 1995-04-06 1999-08-10 Exactis.Com, Inc. Method and apparatus for high volume e-mail delivery
US6182118B1 (en) 1995-05-08 2001-01-30 Cranberry Properties Llc System and method for distributing electronic messages in accordance with rules
US5721779A (en) 1995-08-28 1998-02-24 Funk Software, Inc. Apparatus and methods for verifying the identity of a party
EP0760565A1 (en) 1995-08-28 1997-03-05 Feldbau, Ofra Apparatus and method for authenticating the dispatch and contents of documents
WO1997014234A2 (en) 1995-09-25 1997-04-17 Netspeak Corporation Point-to-point internet protocol
WO1997020423A1 (en) 1995-11-29 1997-06-05 Bell Communications Research, Inc. A system and method for automatically screening and directing incoming calls
WO1997023082A1 (en) 1995-12-15 1997-06-26 At & T Corp. Guest mail: communicating electronic messages between disparate messaging systems
US6014634A (en) 1995-12-26 2000-01-11 Supermarkets Online, Inc. System and method for providing shopping aids and incentives to customers through a computer network
WO1997024825A2 (en) 1995-12-29 1997-07-10 Tixi.Com Gmbh Telecommunication Systems Method and microcomputer system for the automatic, secure and direct transmission of data
WO1997026709A1 (en) 1996-01-18 1997-07-24 Pocketscience, Inc. Electronic messaging system and method
US5826022A (en) 1996-04-05 1998-10-20 Sun Microsystems, Inc. Method and apparatus for receiving electronic mail
US5893911A (en) 1996-04-17 1999-04-13 Neon Software, Inc. Method for defining and applying rules for message distribution for transaction processing in a distributed application
US5742769A (en) 1996-05-06 1998-04-21 Banyan Systems, Inc. Directory with options for access to and display of email addresses
US5884033A (en) 1996-05-15 1999-03-16 Spyglass, Inc. Internet filtering system for filtering data transferred over the internet utilizing immediate and deferred filtering actions
US6373950B1 (en) 1996-06-17 2002-04-16 Hewlett-Packard Company System, method and article of manufacture for transmitting messages within messages utilizing an extensible, flexible architecture
US5835722A (en) 1996-06-27 1998-11-10 Logon Data Corporation System to control content and prohibit certain interactive attempts by a person using a personal computer
US5781857A (en) 1996-06-28 1998-07-14 Motorola, Inc. Method of establishing an email monitor responsive to a wireless communications system user
US5859967A (en) * 1996-07-09 1999-01-12 Faxsav Incorporated Method and system for relaying communications from authorized users
US5999600A (en) 1996-10-14 1999-12-07 Samsung Electronics Co., Ltd. Facsimile mail system and method for controlling the same
US5930479A (en) * 1996-10-21 1999-07-27 At&T Corp Communications addressing system
US5909589A (en) * 1996-11-12 1999-06-01 Lance T. Parker Internet based training
US5917489A (en) 1997-01-31 1999-06-29 Microsoft Corporation System and method for creating, editing, and distributing rules for processing electronic messages
US6057841A (en) 1997-01-31 2000-05-02 Microsoft Corporation System and method for processing electronic messages with rules representing a combination of conditions, actions or exceptions
WO1998037675A1 (en) 1997-02-19 1998-08-27 Verifone, Inc. A system, method and article of manufacture for secure digital certification of electronic commerce
DE19708856A1 (en) 1997-03-05 1998-09-10 Bosch Gmbh Robert Digital component test method for broadband communication
EP0883271A2 (en) 1997-04-15 1998-12-09 Hewlett-Packard Company Method and system for managing data service systems
US6173322B1 (en) 1997-06-05 2001-01-09 Silicon Graphics, Inc. Network request distribution based on static rules and dynamic performance data
US6092101A (en) 1997-06-16 2000-07-18 Digital Equipment Corporation Method for filtering mail messages for a plurality of client computers connected to a mail service system
US6189026B1 (en) 1997-06-16 2001-02-13 Digital Equipment Corporation Technique for dynamically generating an address book in a distributed electronic mail system
US6073142A (en) 1997-06-23 2000-06-06 Park City Group Automated post office based rule analysis of e-mail messages and other data objects for controlled distribution in network environments
US20050081059A1 (en) 1997-07-24 2005-04-14 Bandini Jean-Christophe Denis Method and system for e-mail filtering
US20020199095A1 (en) 1997-07-24 2002-12-26 Jean-Christophe Bandini Method and system for filtering communication
US5999967A (en) * 1997-08-17 1999-12-07 Sundsted; Todd Electronic mail filtering by electronic stamp
US6393465B2 (en) 1997-11-25 2002-05-21 Nixmail Corporation Junk electronic mail detector and eliminator
US6112227A (en) * 1998-08-06 2000-08-29 Heiner; Jeffrey Nelson Filter-in method for reducing junk e-mail
US6484197B1 (en) 1998-11-07 2002-11-19 International Business Machines Corporation Filtering incoming e-mail
WO2001016695A1 (en) 1999-09-01 2001-03-08 Katsikas Peter L System for eliminating unauthorized electronic mail
US6883095B2 (en) 2000-12-19 2005-04-19 Singlesigon. Net Inc. System and method for password throttling
WO2002077768A2 (en) 2001-03-22 2002-10-03 Michael Chung Methods and systems for electronic mail, internet target and direct marketing, and electronic mail banner
US7383433B2 (en) 2001-07-31 2008-06-03 Sun Microsystems, Inc. Trust spectrum for certificate distribution in distributed peer-to-peer networks
WO2003044617A2 (en) 2001-10-03 2003-05-30 Reginald Adkins Authorized email control system
US7512788B2 (en) 2002-12-10 2009-03-31 International Business Machines Corporation Method and apparatus for anonymous group messaging in a distributed messaging system
US20040243676A1 (en) 2003-05-24 2004-12-02 Blankenship Mark H. Message manager for tracking customer attributes
US20050015482A1 (en) 2003-05-24 2005-01-20 Blankenship Mark H. Attachment manager for tracking customer attributes
US20050015481A1 (en) 2003-05-24 2005-01-20 Blankenship Mark H. Register manager for tracking customer attributes
US20040243698A1 (en) 2003-05-24 2004-12-02 Blankenship Mark H. Tracking purchaser attributes
US20040236835A1 (en) 2003-05-24 2004-11-25 Blankenship Mark H. Direct mail manager for tracking customer attributes
US20050076220A1 (en) 2003-10-02 2005-04-07 Xiao Quan Zhang Method and System for Using a Point System to Deliver Advertisement Emails and to Stop Spam

Non-Patent Citations (46)

* Cited by examiner, † Cited by third party
Title
A Way to Stop Spasm Messages [online ] [retrieved on Apr. 25, 2003]. Retrieved from the Internet http://groups.google.com/groups?=%B%22sender%22+%2Bspam&start+10&hl+en&lr. . . (4 pages).
Andrew Leonard, SpamBomers, Sep. 1997, 7 pages, Salon Magazine+ about 21st + newsletter.
AOL 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).
Article 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), 1996.
Article 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).
Cementing Online Partnerships and Improving User Experience, RSA Security, retrived online May 17, 2006, 7 pages, www.rsasecurity.com.
Chinese Abstract for CN 1117680, published Feb. 28, 1996.
CNET News.com staff, ISP: Internet Spam Provider, Feb. 18, 1997, 2 pages, CNET News.com.
Cole-Gomolski, Barb, Adoption of S/MIME still lagging, May 11, 1998, 4 pages, http://www.computerworld.com/home/features.nsf/. . .
Controlling E-Mail Spam, online, retrieved on Mar. 28, 2003, 5 pages, retrieved from the Internet http://spam.abuse.net/adminhelp/mail.shtml.
Cynthia Dwork, Fighting Spam May be Easier Than You Think, 1992, 30 pages, presentation given in Crypto.
Cynthia Dwork, Fighting Spam: The Science, 2004, pp. 3-4, M. Farach-Colton (Ed.): Latin 2004, INCS 2976, Springer-Verlag, Berlin.
D.J. Berstein, Variable Envelope Return Paths, Feb. 1, 1997, 2 pages, http://cr.yp.to/proto/verp.txt.
David A. Wheller, 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.
Dealing with Unsolicited Commercial Email (UCE, "email spam"), 2005 Public Access Networks Corporation, online, retrieved on Jun. 6, 2006, 3 pages, retrieved from the Internet http://www.panix.com/uce.html, Copyright 2003.
Douglas G. Henke, All Hail Emperior Lewis?, online, Feb. 20, 1997, 2 pages, retrived Apr. 25, 2003, retrived from the internet http://groups.google.com/groups.
Ed 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?. . .
Foiling Spam with an Email Password System, online, retrieved on Jun. 28, 2004, 10 pages, retrieved from the Internet, http://www.uwasa.fi/~ts/info/spamfoil.html.
Foiling Spam with an Email Password System, online, retrieved on Jun. 28, 2004, 10 pages, retrieved from the Internet, http://www.uwasa.fi/˜ts/info/spamfoil.html.
How 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), posted Nov. 15, 1996.
http://www.crl.com~michaelp/stopjunkmail.html, Nov. 1996. *
http://www.crl.com˜michaelp/stopjunkmail.html, Nov. 1996. *
http://www.news.com/News/Item/0,4,106,00.html, Sep. 1996. *
http://www.panix.com/uce.html, Feb. 1997. *
http://www.zdnet.com/anchordesk/talkback/talkback_35298.html, Aug. 1997. *
J. Klensin et al., IMAP/POP Authorize Extension for Simple Challenge/Response, Sep. 1997, 5 pages.
Jameson, Bob, Filter for mail not addressed to you, Jesse Berst's Anchor Desk, Sep. 6, 1996, 3 pages, http://www.news.com/News/Item/0.43106.00.html.
Janet Kornblum, Programmer Writes Spam Bomb, Aug. 6, 1997, 2 pages, CNET News.com.
Julian 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.
Lorrie Faith Crano et al, Spam!, Aug. 1998, pp. 74-83, Communications of the ACM, vol. 41, No. 8.
MailCircuit's Email HandShake Verification and Spam Filter Process [online] copyright 1996-2003, MailCircuit.com. Retrieved from the Internet http://www.mailcircuit.com/filter.html (2 pages).
Michael's Stop Junk E-Mail, Stop Junk E-Mail, Nov. 17, 1996, 2 pages, http:/www.crl.com/-michaelp/stopjunkmail.html.
Mihir Bellare et al., Does Parallel Repition Lower the Error in Computationally Sound Protocols?, 1997, 24 pages, Proceedings of the 38th Symposium on Foundations of Computer Science, IEEE.
MIT 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/.
My Spamblock; Was: Thwarting UCE address culling programs [online] [retrieved on Apr. 28, 2003]. Retrieved from the Internet http://www.google.com/groups? hl=en&1r=Iie=UTF-8&oe=UTF-8&selm+32E1A4FD.41C. . . (2 pages).
NAGS Spam Filter, 11 pages, http://www.nags.org/spamfilter.html.
P. Resnick, RFC28822, Apr. 2001, 51 Pages, Qualcom Incorporated, http:rfc.net/rfc2822.html.
Paul Hoffman et al., Unsolicited Bulk Email: Mechanisms for Control, Internet Mail Consortium Report UBE-SOL, IMCR-005, Oct. 13, 1997, 31 pages.
Paul Hoffman et al., Unsolicited Bulk Email: Mechanisms for Control, Internet Mail Consortium Report UBE-SOL, IMCR-2008, revised May 4, 1998, 16 pages.
Public Access Networks Corporation, Responding to Unsolicited Commercial Email (UCE, "email spam"), Feb. 25, 1997, 5 pages, http:www.panix.com/uce.html.
Qualcomm mInc. "Eudora MailPro Version for 3.0 for Windows User Manual", Jun. 1997, 198 pages. *
Showing Full Headers of a Message, Nov. 6, 1998, 3 pages, http:/www.panix.com/headers.html.
Simpson, W. "Request for Comments (RFC) 1994: PPP Challenge Handshake Authentication Protocol (CHAP)", published by Network Working Group, Aug. 1996, 14 pages. *
The Penny Black Project, online, retrieved on May 8, 2006, 2 pages, retrieved from the Internet http://research.microsoft.com/research/sv/PennyBlack/.
Tim Richardson, Simple Notes on Internet Security and Email, Jun. 28, 1999, 2 pages, http:/www.timrichardson.net/security.html.
To 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=The+Deadbolt+tm+%2Bspam&hl+en&lr=&ie+UTF-8. . . (2 pages).

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070249374A1 (en) * 2006-04-21 2007-10-25 Lucent Technologies Inc. Method for controlling delivery of short messages in wireless network
US9363105B2 (en) * 2006-04-21 2016-06-07 Alcatel Lucent Method for blocking spam short messages in wireless network
US20090030989A1 (en) * 2007-07-25 2009-01-29 International Business Machines Corporation Enterprise e-mail blocking and filtering system based on user input
US8082306B2 (en) * 2007-07-25 2011-12-20 International Business Machines Corporation Enterprise e-mail blocking and filtering system based on user input
US20130144674A1 (en) * 2011-12-01 2013-06-06 Samsung Electronics Co. Ltd. System and method for providing mobile advertising services
US11068940B2 (en) 2011-12-01 2021-07-20 Samsung Electronics Co., Ltd. System and method for providing mobile advertising services

Also Published As

Publication number Publication date
USRE42702E1 (en) 2011-09-13
US6199102B1 (en) 2001-03-06
WO1999010817A1 (en) 1999-03-04

Similar Documents

Publication Publication Date Title
USRE41411E1 (en) Method and system for filtering electronic messages
US9503406B2 (en) Active e-mail filter with challenge-response
US7516182B2 (en) Practical techniques for reducing unsolicited electronic messages by identifying sender&#39;s addresses
RU2381551C2 (en) Spam detector giving identification requests
US7257564B2 (en) Dynamic message filtering
KR101203331B1 (en) Url based filtering of electronic communications and web pages
US8646043B2 (en) System for eliminating unauthorized electronic mail
RU2378692C2 (en) Lists and features of sources/addressees for preventing spam messages
US20030236845A1 (en) Method and system for classifying electronic documents
US20030212745A1 (en) Selective multi-step email message marketing
Pelletier et al. Adaptive filtering of spam
US20050044160A1 (en) Method and software product for identifying unsolicited emails
CN114143282A (en) Mail processing method, device, equipment and storage medium
US20020147783A1 (en) Method, device and e-mail server for detecting an undesired e-mail
KR100473051B1 (en) Automatic Spam-mail Dividing Method
WO2006051434A1 (en) A method and system for preventing reception of unwanted electronic messages, such as spam-mails
JP2004523012A (en) A system to filter out unauthorized email
Paganini ASK: Active Spam Killer.
CA2423654A1 (en) Method and apparatus for identification and classification of correspondents sending electronic messages
Schryen The empirical analysis of the abuse of e-mail addresses placed on the Internet
CA2420812A1 (en) Method and apparatus for identification and classification of correspondents sending electronic messages
Wang et al. Using Header Session Messages to Filter-out Junk E-mails
Cottereau A peer-to-peer architecture for collaborative spam filtering
Chiarella An Analysis of Spam Filters
Tung et al. PISA Anti-Spam Project Group

Legal Events

Date Code Title Description
AS Assignment

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

Free format text: SECURITY AGREEMENT;ASSIGNORS:AOL INC.;AOL ADVERTISING INC.;BEBO, INC.;AND OTHERS;REEL/FRAME:023649/0061

Effective date: 20091209

AS Assignment

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

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL LLC;REEL/FRAME:023720/0509

Effective date: 20091204

AS Assignment

Owner name: THE GOLDMAN LIVING TRUST,CALIFORNIA

Free format text: COURT ORDER;ASSIGNOR:BY COURT ORDER SIGNED BY THE JUDGE ON 4/28/2004, AND FILED BY THE CLERK 05/07/2004, ON BEHALF OF PHILLIP Y. GOLDMAN A/K/A PHIL GOLDMAN (DECEASED);REEL/FRAME:023833/0247

Effective date: 20040428

Owner name: AOL LLC,VIRGINIA

Free format text: CHANGE OF NAME;ASSIGNOR:AMERICA ONLINE, INC.;REEL/FRAME:023833/0408

Effective date: 20060403

Owner name: AMERICA ONLINE, INC.,VIRGINIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MBLX LLC;REEL/FRAME:023833/0205

Effective date: 20050331

Owner name: MBLX LLC,CALIFORNIA

Free format text: MERGER;ASSIGNOR:MAILBLOCKS, INC.;REEL/FRAME:023833/0186

Effective date: 20041101

Owner name: MAILBLOCKS, INC.,CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:THE GOLDMAN LIVING TRUST;REEL/FRAME:023833/0149

Effective date: 20040617

Owner name: PHIL GOLDMAN,CALIFORNIA

Free format text: NOTICE OF REVERSIONARY INTEREST;ASSIGNOR:COBB, CHRISTOPHER A.;REEL/FRAME:023833/0087

Effective date: 20020726

Owner name: PHIL GOLDMAN,CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COBB, CHRISTOPHER A.;REEL/FRAME:023833/0047

Effective date: 20020715

AS Assignment

Owner name: YEDDA, INC, VIRGINIA

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: 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

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

Effective date: 20100930

Owner name: SPHERE SOURCE, INC, VIRGINIA

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: QUIGO TECHNOLOGIES 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

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

Effective date: 20100930

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: LIGHTNINGCAST 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

Effective date: 20100930

Owner name: GOING INC, MASSACHUSETTS

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: AOL ADVERTISING INC, NEW YORK

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: AOL INC, VIRGINIA

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

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

CC Certificate of correction
FPAY Fee payment

Year of fee payment: 12

AS Assignment

Owner name: MARATHON SOLUTIONS LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL INC.;REEL/FRAME:028911/0969

Effective date: 20120614

AS Assignment

Owner name: BRIGHT SUN TECHNOLOGIES, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MARATHON SOLUTIONS LLC;REEL/FRAME:030091/0483

Effective date: 20130312

XAS Not any more in us assignment database

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MARATHON SOLUTIONS LLC;REEL/FRAME:030091/0483

AS Assignment

Owner name: BRIGHT SUN TECHNOLOGIES, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MARATHON SOLUTIONS LLC;REEL/FRAME:031900/0494

Effective date: 20130312

AS Assignment

Owner name: GOOGLE INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BRIGHT SUN TECHNOLOGIES;REEL/FRAME:033074/0009

Effective date: 20140128

AS Assignment

Owner name: GOOGLE LLC, CALIFORNIA

Free format text: CHANGE OF NAME;ASSIGNOR:GOOGLE INC.;REEL/FRAME:044101/0610

Effective date: 20170929