This application is related to U.S. patent application Ser. No. 10/914,035, filed Aug. 6, 2004, entitled “Displaying Conversations in a Conversation-Based Email System,” which is incorporated by reference herein in its entirety. This application is also related to U.S. patent application Ser. No. 11/111,166, filed Apr. 20, 2005, entitled “System and Method for Targeting Information Based on Message Content,” which is incorporated by reference herein in its entirety.
The disclosed embodiments relate generally to providing information to computer users, and in particular, to provide information items to a computer user based on their popularity.
As with traditional advertising, online advertising seeks to provide advertisements to those individuals most likely to respond to the advertisement in a desired way, for example, by purchasing a product or service. One way advertisers target a user is to provide advertisements that are related to the content of a web page that the user is viewing. This application concerns additional methods and systems for targeting online advertisements to individuals so as to improve the likelihood that the individuals receiving the online advertisements will be sufficiently interested in the advertisements to click through links to the advertisements or associated content.
According to some embodiments, a method of selecting information items in connection with an electronic message is disclosed. The method includes selecting a plurality of information items satisfying a predefined popularity condition, each of the information items having an associated keyword, and identifying one or more of the selected information items whose associated keyword is found in the electronic message. In some embodiments, a set of candidate items are selected periodically based on their respective popularity metrics. The popularity metric of an information item may be its click-through rate during a predefined time period. Each candidate information item has one or more keywords and the number of the keywords found in the electronic message determines the item's relevancy to a user accessing the message. In some other embodiments, the method selects a subset of the information items using user geographical information associated with a user accessing the electronic message from a client and at least one of the selected information items is targeted to users at a location corresponding to the user geographical information.
For a better understanding of the nature and embodiments of the invention, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The client 102 can be any of a number of devices (e.g., a computer, an interne kiosk, a personal digital assistant, a cell phone, a gaming device, a desktop computer, or a laptop computer) and can include a client application 132, a client assistant 134, and/or client memory 136. The client application 132 can be a software application that permits a user to interact with the client 102 and/or network resources to perform one or more tasks. For example, the client application 132 can be a browser (e.g., Firefox) or other type of application that permits a user to search for, browse, and/or use resources (e.g., web pages and web services) on the client 102 and/or accessible via the communication network 104. The client assistant 134 can perform one or more tasks related to monitoring a user's activities with respect to the client application 132 and/or other applications, searching or browsing for resources (e.g., files) on the client 102, and processing information received from or being sent to information service 106. The client assistant 134 can be part of the client application 132, available as a plug-in to the client application 132 (provided, for example, from various on-line sources), or provided as a stand-alone program. The client assistant can be a web-based messaging application such as the client executable portion of the Google Gmail product. A client memory 136 can store system information and information about a user, among other things.
The communication network 104 can be any local area network (LAN) and/or wide area network (WAN), such as an intranet, an extranet, or the Internet. It is sufficient that the communication network 104 provides communication capability between the clients 102 and the information service 106. In some embodiments, the communication network 104 uses the HyperText Transport Protocol (HTTP) to transport information using the Transmission Control Protocol/Internet Protocol (TCP/IP). The HTTP permits client computers to access various resources available via the communication network 104. The various embodiments of the invention, however, are not limited to the use of any particular protocol. The term “resource” as used throughout this specification refers to any piece of information or service that is accessible via a Uniform Resource Locator (URL) and can be, for example, a web page, a document, an email message, an Instant Messaging (IM) message, a Short Message Service (SMS) message, a transcribed voice message, a database, an image, or a computational object.
The conversation engine 110 can respond to a variety of requests from the client assistant 134 related to messages and return conversation-based responses via its connection with the communication network 104. A conversation may include one or more relevant messages relating to a conversation topic. Various criteria can be used to determine which messages are parts of each distinct conversation. For example, an analysis can be made of the contents of messages received and/or sent by a user. Messages whose contents are found to be related can be grouped together. In another example, a thread identifier found in a message header can also be used to identify related messages. In a further example, a subject line in the message header can be used to identify related messages. The senders and recipients of the messages are participants in the conversation. All messages directed to a user of the information service 106 can be grouped into a plurality of conversations and presented to the user in a conversation-based format, individually or jointly. In a conversation list view, a user can see in a summary form a list of conversations in which the user participates. In a conversation view, the user can see in an expanded form one or more of messages associated with a particular conversation.
The information service 106 can create a snippet of a conversation or a message. A snippet provides a user with a preview of the contents of the conversation or message without the user having to open the conversation or the message. In a list of conversations, the snippet can be generated from the most recent message in the conversation. The snippet can also be extracted from the first message (i.e., the oldest message) in the conversation. The snippet can also be extracted from all the messages in the conversation according to predefined heuristic rules, e.g., listing a set of keywords appearing most frequently in the conversation. If the information service 106 is preparing a list of conversations in response to a search submitted by a user, the information service 106 can create a snippet for each conversation in the list, or for each conversation is a displayed portion of the list, the snippet including a portion of the conversation that matches user-submitted query terms. These snippets may be similar in one or more respects to snippets included in search results returned by a search engine, such as the Google search engine. In a conversation view, a snippet can be generated for one or more messages in the conversation.
The SMTP gateway 122 is also connected to the communication network 104. The SMTP gateway 122 can be directly involved in receiving and sending messages between the information service 106 and other email systems, messaging systems or information services. In some embodiments, the SMTP gateway 122, for example, transmits and receives messages using the simple mail transfer protocol (SMTP). The SMTP gateway 122 can receive a new message from the communication network 104 and send the message to conversation engine 110 for additional processing. Additionally, the SMTP gateway 122 can receive messages from the conversation engine 110 and then transmit (via the communication network 104) those messages to recipient addresses specified in the messages.
The one or more auxiliary services servers 120 can provide additional services to the conversation engine 110. In some embodiments, the auxiliary services servers 120 include a spam detection module 121 for detecting and processing spam, an attachment management module 123 for managing the storage and retrieval of documents attached to messages, and a geographical information module 125 for extracting user geographical information from a login or message access request.
For example, when the information service 106 receives a login request initiated by a user from a client 102, it extracts an IP address of the client from the login request. The IP address is typically a 32-bit digital number that uniquely identifies the client on the Internet. The information service 106 includes an IP-Geo mapping database 127. The IP-Geo mapping database 127 includes many entries, each entry mapping one or more IP addresses to a specific geographical location. For example, the entry “171.64.*.*→Stanford, Calif. 94305” indicates that any IP address whose first eight bits correspond to the decimal value “171” and second eight bits correspond to the decimal value “64” refers to a computer located at Stanford, Calif. 94305. The geographical information module 125 is responsible for converting the IP address of the client into the client user's geographical location. This geographical location is used subsequently by the advertisement server 128 and the information item server 130 for selecting one or more information items relevant to the user's geographical location. In some other embodiments, the service provided by the geographical information module 125 and the IP-Geo mapping database 127 may be delegated to a geographical information server that is connected to the information service 106. Upon receiving a login or message access request, the information service 106 forwards the IP address included in the request to the geographical information server. The geographical information server returns to the information service 106 the geographical location corresponding to the IP address.
As mentioned above, the conversation engine 110 can be connected to the targeted information processor 124. The targeted information processor 124 can provide geo-targeted and/or content-targeted information for display to a user at client 102. The targeted information processor 124 can provide, for example, advertisements and/or other information items related to the user's messages being handled by the conversation engine 110. In some embodiments, the messages include not only messages received by the user but also messages authored and sent by the user. In some other embodiments, the advertisements may be only related to a user's geographical location, not to the message content at all. This scenario may be appropriate in some special circumstances, e.g., when the user is on a business trip and away from the location where the user usually logs into his or her account. Advertisements are herein defined to include information items, or links to information items, that offer or promote products, services, events, companies, organizations, ideas or the like.
The targeted information processor 124 can be connected to popular keywords information 126. In some embodiments, the popular keywords information 126 includes a plurality of keywords associated with a set of advertisements deemed to be most popular by a group of users within a predefined time period. The popular keywords information can be used to determine whether there are any popular advertisements whose associated keyword(s) are found in a message being processed by the conversation engine 110. Similarly, popular advertisements may also have associated geographical locations, and a list of geographical locations associated with the popular advertisements may be compared with the user's current geographical location to determine whether there are any popular advertisements targeted at users at the same geographical location as the user. If no popular keyword is found in the message, and (optionally) no geographical location associated with popular advertisements matches the user's geographical location, there is no need for the targeted information processor 124 to launch request(s) for popular advertisements against the advertisement server 128 and/or the information item server 130. Otherwise, the targeted information processor 124 may obtain popular advertisements and other popular information items from advertisement server 128 and information item server 130, respectively.
As mentioned above, the client 102 can include client application 132 and client assistant 134. Client application 132 can provide a window to be displayed on a displaying device (e.g., a monitor) for rendering conversations and targeted information. The conversations, targeted information and messages in the conversations can be encoded using HyperText Markup Language (HTML), XML, or any other appropriate markup language or encoding scheme, and then rendered by the client application 132. When a user submits a request through client application 132 to the information service 106 to access messages stored in the user's account, the information service 106 identifies conversations in the user's account in accordance with the user's request and transfers them as well as a set of display instructions back to the client 102. Client assistant 134 can, in response, generate one or more forms in accordance with the display instructions, where each form can include information of some of the conversations. The forms can then be submitted to and rendered by client application 132. In another embodiment, client assistant 134 may alternatively exist and operate in the information service 106.
The information service 106 and client assistant 134 work in concert to allow a user to view, compose, send and/or search messages in the user's message account and to present the search results in a highly intuitive fashion. The information service 106 extracts information from a user's message account by processing messages received, sent and/or being composed by the user, and the client assistant 134 assists in rendering the information prepared by the information service 106. In other embodiments a different division of duties between the information service 106 and the client assistant 134 can be implemented. Because many of the tasks performed by the system can be performed by either the information service 106 or the client assistant 134 or by the two working together, these two components are sometimes herein referred to jointly as the “conversation system”.
The conversation system can provide at least two different views, including a conversation list view and a conversation view as mentioned briefly above. In a conversation list view, a plurality of conversations can be displayed where each conversation can be displayed in a summary form. For example, each conversation can be represented by a number of conversation elements. The conversation elements can include one or more of: a number indicating the number of messages in the conversation, a list of one or more of the identifiers or names of the senders of messages in the conversation, a conversation description (e.g., a subject line of the message), a date/time value of the conversation (e.g., a date/time value of the last received message in the conversation), and a snippet from one or more of the messages in the conversation. In one approach, each conversation can be represented as a single row in the conversation list view.
In a conversation view, one or more messages from a conversation can be displayed. Each message can be displayed in one of a number of various modes, for example an expanded mode, a compacted mode, or a compressed mode. In an expanded mode, the body of the message can be displayed along with, for example, header information including names or other identifiers of the sender and the recipients of the message, a date/time value indicative of when the message is received or sent, routing information, and other properties of the message. An expanded mode can be used, for example, for messages which are marked as “unread.” In a compacted mode, the message body can be hidden and a snippet from the message is provided in its place. The snippet can be chosen to occupy less space than the body. For example, a snippet can be chosen to occupy only one line in a display window. The compacted mode can be used for messages which have been read or marked as read. The compacted mode allows messages in a conversation to be displayed within the same window more densely than if the expanded mode were used. In a compressed mode, a message can be represented with a small bar. The small bar can contain no message information. The visual effect of such a mode can be that multiple compressed messages appear like the edges of cards in a deck of cards. A user can toggle between the various display modes by selecting a message or using various controls in the display window. It should be understood that the techniques described in this specification with reference to a conversation (as might be found in the Google Gmail product) can be equally used with any message system (e.g., Outlook or Thunderbird) where messages can be displayed in various views (and can include portions of messages) such as a message view or a thread view where related messages can be displayed.
In some embodiments, when a conversation is being displayed in the conversation view, additional, targeted information (sometimes herein called “informational items”) can be displayed in the display window. For example, one or more advertisements relevant to, or related to, one or more of the messages in the conversation can be displayed. In another example, one or more other types of information can be displayed. Such other information can include, but is not limited to news items or links to news items, map links, phone numbers, links to product information, stock prices or links to stock prices, links to weather forecasts, web page links, dictionary entries or links to dictionary entries, images or links to images, RSS feeds or links to RSS feeds, links to blog (web log) events, links to user polls, links to files or other content on the client 102, and other types of information.
RSS feeds can be content distributed from various sources on a network (e.g., the Internet). RDF Site Summary (RSS) (and sometimes, Real Simple Syndication) is an XML-based lightweight multi-purpose extensible metadata description and syndication format. RSS is typically used for distributing various types of content to a number of receivers simultaneously. News items can be news items from one or more sources. Blog events can be events generated from one or more web logs (blogs). User polls can be polls that the user may participate in which may come from a variety of sources. Stock prices can be stock prices of companies whose names or stock ticker symbols are mentioned in the conversation. Weather forecasts can be weather forecasts of locations like cities or states whose names are directly or indirectly referred to by a message in the conversation.
Before the identified messages are transferred back to the requesting client, the information service 106 needs to determine if there are any popular advertisements targeted at the identified messages or targets at the user's current geographical location (206). Within the information service 106, the targeted information processor 124 is typically responsible for determining whether there are any popular advertisements associated with a requested message by checking if any advertisement-related keyword is found in the message. Optionally, the targeted information processor 124 may also determine whether there are any popular advertisements associated with the user's geographical location (or alternately stated, that are targeted at users at the user's current geographical location).
If there is no matching keyword in the message, and (optionally) there are no popular advertisements targets at users at the user's geographical location, the information service 106 may finish the process by bypassing the remaining steps 208-212 as indicated by line 207 of
If there is any matching keyword in the message (206), the information service 106 performs operations 208, 210, 212 in order to obtain those targeted information items. Note that operation 206 may be delegated to the advertisement server 128 or the information item server 130 in some embodiments.
In order to obtain targeted information from the advertisement server 128 or the information item server 130, the information service 106 sends the user geographical information and the messages to the information servers (208). The information servers, e.g., the advertisement server 128, search through a pool of candidate information items for those items that are most relevant to the user geographical information and the message content. Subsequently, the information service 106 receives from the information servers a set of popular information items targeted at the user geographical information and/or the messages (210) and transfers these geo-targeted and/or content-targeted information items to the requesting client for display (212). A more thorough description of the process of identifying relevant information items is provided below in connection with
In order to display the information items on the client 102, the information service 106 may provide formatting information directing the display of the information obtained from the information servers. The obtained information is preferably displayed in a manner consistent with the user's expectation. For example, if the obtained information is associated with a conversation or a message in the conversation requested by the user, it is simultaneously displayed next to the requested conversation or message in a corresponding conversation view. If the obtained information items are associated with a message just sent by the user and the user expects to return to the conversation list view, the information items may be displayed at the top of the conversation list view in order to attract the user's attention. It will be understood by one skilled in the art that the aforementioned schemes of rendering the obtained information items in a display device are exemplary. Other rendering schemes may be used in other embodiments. Typically, the information items are displayed at a location within an application or browser window that is prominent, but consistent with the normal experience that users have with a particular information service.
In some embodiments, the task of identifying targeted information items is accomplished by, or primarily by the information service 106. For example, it is the targeted information processor 124 that is responsible for conducting semantic analysis of the message contents. The semantic analysis may include extracting concepts from the message contents, inferring from the concepts other relevant keywords, and grouping the concepts and keywords into categories. In these embodiments, the information servers 128, 130 are only responsible for choosing advertisements matching the concepts, keywords and categories.
However, in other embodiments, the information servers 128, 130 play a more significant role in the process of identifying targeted information items. In some embodiments, this process is divided into two sub-processes: (1) periodically identifying a set of keywords associated with the most popular advertisements under certain circumstances; and (2) selecting those advertisements and other information items whose associated keywords appear in the message. The one or more keywords associated with an advertisement may be the one or more keywords on which the provider of the advertisement has bid, as part of an auction process for determining placement of online advertisements. Keywords may be associated with other information items by automated content analysis or by human assignment of the keywords, or a combination of these techniques. Prior to further discussion of these two sub-processes, it is helpful to address the topic of how to measure the relevancy of an advertisement to a particular user.
In general, the relevancy of an on-line advertisement to a user viewing a web page or an email message depends on two factors: (1) how close the subject of the advertisement is to the web page or message content and (2) how likely the user is going to click the link to the advertisement when noticing its existence. The first factor can be measured, e.g., by the frequencies that keywords associated with the advertisement are found in the web page or message content. When the number or percentage of words within a message that match keywords associated with an advertisement or information item reaches a predetermined threshold, the advertisement or information item is deemed relevant to that message. In some embodiments, the relevancy of the keywords to the message can be measured by the number of unique keywords present in the message. The latter factor can be approximated by a popularity metric, such as the click-through rate of the advertisement during a predefined time period. The click-through rate of an advertisement is defined as the number of times that users clicked on links to the advertisement divided by the number of times that the advertisement was displayed to different users during a predefined time period. A shorthand version of this definition is “number of click-throughs divided by number of impressions,” where each “impression” is the display or presentation of an item to a user. An advertisement having a high click-through rate (CTR) is more likely to be clicked than one having a low click-through rate provided that other conditions of the two advertisements are relatively equal. In other words, the actual click-through rate of an advertisement is treated as a proxy for its predicted click-through rate for the purpose of determining its relevancy to a user. In some embodiments, this predicted click-through rate may be further modulated by the user's personal profile. For example, a user's age, gender, educational, income level, and known or stated interests may affect the relevancy of an advertisement to the user. Therefore, in order to select more relevant information items for a message, it is necessary to determine their respective predicted click-through rates.
The database 700 includes a set of information items 702, which may include advertisements and/or other types of information items. For ease of explanation, both advertisements and other information items are herein called information items. Each information item 702 includes content 704, keywords 706 associated with the information item and click-through information 708. Optionally, a subset of the information items include geo-targeting information 710. Optionally, other fields or types of information may also be stored with or associated with one or more of the information items. Content 704 may include text, graphics, links to URLs or other content storage locations. The content 704 of one or more of the items 702 may optionally be preformatted for display, for example by including HTML tags. Keywords 706 are one or more keywords used to identify or select information items. Keywords for advertisements, and perhaps other types of information items as well, may be associated with bids. Bids are used in an auction or similar process for determining advertisement or information item selection and placement. Alternately, or in addition, bids may be used to determine debits or credits to be applied to one or more financial accounts when predefined events occur with respect to the associated advertisements or information items.
Geo-targeting information 710, when provided for an information item or advertisement, may be used to limit the users who receive the information item or advertisement to users whose current location is consistent with the geo-targeting information 710 for that information item or advertisement. Geo-targeting information 710 for particular information items may specify geographic regions of different sizes, including large regions (e.g., Canada, or New York State), small regions (e.g., locations within 1000 yards of a particular address in New York City), and regions of any intermediate size, such as a county (e.g., Santa Clara County, California), a metropolitan area (e.g., “the Bay area of Northern California”), a city (e.g., Palo Alto, Calif.), or any other well defined geographic region that is suitable for use in geo-targeting. As explained elsewhere in this document, a user's current location may be determined by the current IP address of user, or may be determined using other positioning mechanisms (e.g., if the client 102 is a cell phone, the cell phone network for the client 102 may provide information about the user's current location). In some embodiments, information items or advertisements that do not have geo-targeting information associated with them are assumed to be targeted to all users.
Click-through rate (CTR) information 708 for an information item includes one more CTR values. In the simplest implementations, the CTR information 708 for an information item is a single value representing the click-through rate for the information items for a predefined period of time. In other implementations, separate CTR values may be provide for a plurality of time periods (e.g., the last month, the last week, etc.), and/or for a plurality of geographic regions, and/or for a plurality of categories of users, and/or other groupings of the CTR information for the information item.
From the candidate popular advertisements, the advertisement server extracts their respective keywords (304). Each advertisement may has an associated bid on one or more keywords. In some embodiments, an advertisement is not considered relevant to a message if (A) none of its associated keywords are found in the message, or (B) the current location of the user is outside the targeted geographical region associated with the advertisement. In these embodiments, when an advertisement include geo-targeting information, the advertisement is only considered relevant to a message if the client 102 receiving or sourcing the message is located within (or optionally nearby) the advertisement's targeted geographical region, and at least one of the keywords of the advertisement are found in the message.
The extracted keywords associated with the candidate popular advertisements are transferred to the information service (306). As mentioned earlier, the information service may use these keywords to determine whether a message contains any keywords in a proactive manner (206 of
In some embodiments, if the user's current location is unknown, operation 404 is skipped. In some embodiments, geographic information is not used to select advertisements, in which case operation 404 is not part of the advertisement selection process. Other uses of the user geographical information can be found in the co-pending U.S. patent application entitled “System and Method for Targeting Advertisements or Other Information Using User Geographical Information,” which is incorporated by reference herein in its entirety.
After selecting a group of popular advertisements, the process identifies a set of keywords associated with the group of advertisements (406). Next, the process determines whether any of the keywords are found in the message (408). If a keyword has a match in the message (408, Yes), an advertisement associated with the keyword are returned to the information service (410). If there is more than one advertisement associated with the same keyword, one or more of the advertisements (from the set of advertisements associated with the keyword found in the message) having the highest CTR are selected and returned to the information server. In some embodiments, the CTR used for selecting the most popular advertisements whose keyword(s) are found in the message is the most geographically specific CTR for each advertisement that is consistent with the user's current location. Thus, if an advertisement includes an overall CTR, a national CTR and a state CTR, all of which are applicable to the user's current location, the state CTR would be used.
If multiple keywords are found in the message, a predefined selection process may be used to determine which advertisements associated with those keywords are returned to the information service. For example, a round robin selection process may be used, in which the highest CTR advertisement (among the not-yet selected advertisements) for each matching keyword is selected, until a predefined maximum number of advertisements have been selected. Alternately, a relevancy metric may be computed for each candidate advertisement, and then the advertisements with the best (e.g., highest) relevancy metric are selected for return to the information service. The relevancy metric of an advertisement may be based on a number of factors, including one or more of the following factors: the number of keywords associated with the advertisement found in the message, the number of matching keywords in the message, the advertisement's click-through rate, the number of times the advertisement has previously been displayed to the user, whether the user has previously seen and clicked through the advertisement, and possibly other factors as well. In some embodiments, information corresponding to the relevancy metrics of the selected advertisements may be provided along with the selected advertisements, for use in determining the positioning or display order of the selected advertisements.
The order of operations in the process of identifying popular advertisements may differ in some embodiments. For instance, in some embodiments, filtering based on geo-targeting may be performed after using keyword matching to identify candidate advertisements. Thus, after identifying matching keywords, a set of candidate advertisements associated with the matching keywords is identified, and that set is then optionally filtered based on geo-targeting so as to produce a filtered set of candidate advertisements. Selection of advertisements from the filtered set can be based on a popularity metric, as described above. Furthermore, in some embodiments, the operations of geo-target filtering and selection of advertisements based on a popularity metric may be combined into a single operation (i.e., performed together instead of performed in sequence).
The processes described above with reference to
Note that the processes of
In some embodiments, the information service 106 includes the following elements, or a subset or superset of such elements: a conversation engine 110 for responding to a variety of requests from the client assistant 134 returning conversation-based responses; an updater engine 112 for updating a message database 118; a message index 114 containing index information for messages in the message database 118; a query engine 116 for performing various queries using the message index 114 and message database 118; an SMTP gateway 122 for sending and receiving messages; an auxiliary services server 120 for performing various auxiliary services; and an IP-Geo mapping database 127 for generating user geographical information.
The information service 106 can be connected to advertisement server 128 and/or information item server 130 via the communication interface 604. Advertisement server 128 can contain one or more advertisements 620. The advertisement server 128 can receive input and return advertisements that can be relevant to the input. The information item server 130 can include one or more information items 622. Similar to the advertisement server 128, the information server 130 can receive input and return informational items that can be relevant to the input.
Each of the above identified elements in
Although
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.
Number | Name | Date | Kind |
---|---|---|---|
3566153 | Spencer, Jr. | Feb 1971 | A |
5109509 | Katayama et al. | Apr 1992 | A |
5208748 | Flores et al. | May 1993 | A |
5216603 | Flores et al. | Jun 1993 | A |
5613108 | Morikawa | Mar 1997 | A |
5724521 | Dedrick | Mar 1998 | A |
5724571 | Woods | Mar 1998 | A |
5734837 | Flores et al. | Mar 1998 | A |
5740549 | Reilly et al. | Apr 1998 | A |
5761689 | Rayson et al. | Jun 1998 | A |
5832502 | Durham et al. | Nov 1998 | A |
5848397 | Marsh et al. | Dec 1998 | A |
5887133 | Brown et al. | Mar 1999 | A |
5905863 | Knowles et al. | May 1999 | A |
5913040 | Rakavy et al. | Jun 1999 | A |
5918014 | Robinson | Jun 1999 | A |
5948058 | Kudoh et al. | Sep 1999 | A |
5948061 | Merriman | Sep 1999 | A |
5959621 | Nawaz et al. | Sep 1999 | A |
5963205 | Sotomayor | Oct 1999 | A |
5987454 | Hobbs | Nov 1999 | A |
6014502 | Moraes | Jan 2000 | A |
6021427 | Spagna et al. | Feb 2000 | A |
6026368 | Brown et al. | Feb 2000 | A |
6029164 | Birrell et al. | Feb 2000 | A |
6044376 | Kurtzman, II | Mar 2000 | A |
6078914 | Redfern | Jun 2000 | A |
6085206 | Domini et al. | Jul 2000 | A |
6115709 | Gilmour et al. | Sep 2000 | A |
6134532 | Lazarus et al. | Oct 2000 | A |
6144944 | Kurtzman, II et al. | Nov 2000 | A |
6148332 | Brewer et al. | Nov 2000 | A |
6151596 | Hosomi | Nov 2000 | A |
6167382 | Sparks et al. | Dec 2000 | A |
6182063 | Woods | Jan 2001 | B1 |
6182098 | Selker | Jan 2001 | B1 |
6182122 | Berstis | Jan 2001 | B1 |
6185551 | Birrell et al. | Feb 2001 | B1 |
6269361 | Davis et al. | Jul 2001 | B1 |
6330589 | Kennedy | Dec 2001 | B1 |
6332127 | Bandera et al. | Dec 2001 | B1 |
6350066 | Bobo, II | Feb 2002 | B1 |
6356834 | Hancock et al. | Mar 2002 | B2 |
6381465 | Chern et al. | Apr 2002 | B1 |
6396513 | Helfman et al. | May 2002 | B1 |
6401075 | Mason et al. | Jun 2002 | B1 |
6408297 | Ohashi | Jun 2002 | B1 |
6421694 | Nawaz et al. | Jul 2002 | B1 |
6438564 | Morton et al. | Aug 2002 | B1 |
6449657 | Stanbach, Jr. et al. | Sep 2002 | B2 |
6493702 | Adar et al. | Dec 2002 | B1 |
6493703 | Knight et al. | Dec 2002 | B1 |
6505046 | Baker | Jan 2003 | B1 |
6507351 | Bixler | Jan 2003 | B1 |
6522875 | Dowling et al. | Feb 2003 | B1 |
6549957 | Hanson et al. | Apr 2003 | B1 |
6571279 | Herz et al. | May 2003 | B1 |
6587835 | Treyz et al. | Jul 2003 | B1 |
6594658 | Woods | Jul 2003 | B2 |
6594693 | Borwankar | Jul 2003 | B1 |
6606644 | Ford et al. | Aug 2003 | B1 |
6640239 | Gidwani | Oct 2003 | B1 |
6654735 | Eichstaedt et al. | Nov 2003 | B1 |
6665668 | Sugaya et al. | Dec 2003 | B1 |
6683627 | Ullmann et al. | Jan 2004 | B1 |
6708205 | Sheldon et al. | Mar 2004 | B2 |
6714975 | Aggarwal et al. | Mar 2004 | B1 |
6725228 | Clark et al. | Apr 2004 | B1 |
6732152 | Lockhart et al. | May 2004 | B2 |
6742042 | Holden et al. | May 2004 | B1 |
6745197 | McDonald | Jun 2004 | B2 |
6757740 | Parekh et al. | Jun 2004 | B1 |
6757889 | Ito | Jun 2004 | B1 |
6771291 | DiStefano, III | Aug 2004 | B1 |
6785869 | Berstis | Aug 2004 | B1 |
6788769 | Waites | Sep 2004 | B1 |
6820081 | Kawai et al. | Nov 2004 | B1 |
6834276 | Jensen et al. | Dec 2004 | B1 |
6847969 | Mathai et al. | Jan 2005 | B1 |
6847992 | Haitsuka et al. | Jan 2005 | B1 |
6889361 | Bates et al. | May 2005 | B1 |
6892196 | Hughes | May 2005 | B1 |
6947396 | Salmi | Sep 2005 | B1 |
6973481 | MacIntosh et al. | Dec 2005 | B2 |
6983139 | Dowling et al. | Jan 2006 | B2 |
6983311 | Haitsuka et al. | Jan 2006 | B1 |
6985882 | Del Sesto | Jan 2006 | B1 |
6993553 | Kaneko et al. | Jan 2006 | B2 |
6999941 | Agarwal | Feb 2006 | B1 |
7013263 | Isaka et al. | Mar 2006 | B1 |
7017173 | Armstrong et al. | Mar 2006 | B1 |
7031961 | Pitkow et al. | Apr 2006 | B2 |
7035903 | Baldonado | Apr 2006 | B1 |
7039599 | Merriman | May 2006 | B2 |
7043690 | Bates et al. | May 2006 | B1 |
7062572 | Hampton | Jun 2006 | B1 |
7069300 | Toyota et al. | Jun 2006 | B2 |
7089278 | Churchill et al. | Aug 2006 | B1 |
7107544 | Luke | Sep 2006 | B1 |
7120668 | Manber et al. | Oct 2006 | B2 |
7136875 | Anderson et al. | Nov 2006 | B2 |
7136915 | Rieger, III | Nov 2006 | B2 |
7139850 | Amemiya et al. | Nov 2006 | B2 |
7143135 | Smith et al. | Nov 2006 | B2 |
7171429 | Frieden et al. | Jan 2007 | B2 |
7188356 | Miura et al. | Mar 2007 | B1 |
7203727 | Suzuki et al. | Apr 2007 | B2 |
7243080 | Bhadra | Jul 2007 | B2 |
7328242 | McCarthy et al. | Feb 2008 | B1 |
7356772 | Brownholtz et al. | Apr 2008 | B2 |
7359936 | Gruen et al. | Apr 2008 | B2 |
7376714 | Gerken | May 2008 | B1 |
7383307 | Kirkland et al. | Jun 2008 | B2 |
7412437 | Moody et al. | Aug 2008 | B2 |
7421690 | Forstall et al. | Sep 2008 | B2 |
7433920 | Blagsvedt et al. | Oct 2008 | B2 |
7478414 | Glusker et al. | Jan 2009 | B1 |
7484175 | Kirkland | Jan 2009 | B2 |
7487112 | Barnes, Jr. | Feb 2009 | B2 |
7565534 | Starbuck et al. | Jul 2009 | B2 |
7584208 | Spivack et al. | Sep 2009 | B2 |
7584251 | Brown et al. | Sep 2009 | B2 |
7599852 | Bosarge et al. | Oct 2009 | B2 |
7643352 | Chen | Jan 2010 | B2 |
7668832 | Yeh et al. | Feb 2010 | B2 |
7693866 | Weaver et al. | Apr 2010 | B1 |
7707283 | Tsunoda et al. | Apr 2010 | B2 |
7716593 | Durazo et al. | May 2010 | B2 |
7730113 | Payette et al. | Jun 2010 | B1 |
7788326 | Buchheit et al. | Aug 2010 | B2 |
7827055 | Snodgrass et al. | Nov 2010 | B1 |
7903099 | Baluja | Mar 2011 | B2 |
7904510 | Anderson et al. | Mar 2011 | B2 |
7912904 | Buchheit et al. | Mar 2011 | B2 |
7953741 | Shih et al. | May 2011 | B2 |
7979501 | Coleman et al. | Jul 2011 | B1 |
8150924 | Buchheit et al. | Apr 2012 | B2 |
8327270 | Jones et al. | Dec 2012 | B2 |
20010016845 | Tribbensee | Aug 2001 | A1 |
20010042100 | Guedalia et al. | Nov 2001 | A1 |
20010047272 | Frietas et al. | Nov 2001 | A1 |
20010047294 | Rothschild | Nov 2001 | A1 |
20010054066 | Spitzer | Dec 2001 | A1 |
20020010775 | Rakavy et al. | Jan 2002 | A1 |
20020010794 | Stanbach, Jr. et al. | Jan 2002 | A1 |
20020032771 | Gledge | Mar 2002 | A1 |
20020046099 | Frengut et al. | Apr 2002 | A1 |
20020052925 | Kim et al. | May 2002 | A1 |
20020073156 | Newman | Jun 2002 | A1 |
20020078158 | Brown et al. | Jun 2002 | A1 |
20020078441 | Drake et al. | Jun 2002 | A1 |
20020083140 | Shin et al. | Jun 2002 | A1 |
20020087631 | Sharma | Jul 2002 | A1 |
20020094868 | Tuck et al. | Jul 2002 | A1 |
20020107735 | Henkin et al. | Aug 2002 | A1 |
20020116494 | Kocol | Aug 2002 | A1 |
20020165923 | Prince | Nov 2002 | A1 |
20020178225 | Madenberg et al. | Nov 2002 | A1 |
20020188689 | Michael | Dec 2002 | A1 |
20020188699 | Ullman et al. | Dec 2002 | A1 |
20020194229 | Decime et al. | Dec 2002 | A1 |
20030009385 | Tucciarone et al. | Jan 2003 | A1 |
20030020749 | Abu-Hakima et al. | Jan 2003 | A1 |
20030037140 | Aaltonen | Feb 2003 | A1 |
20030050916 | Ortega et al. | Mar 2003 | A1 |
20030055711 | Doherty | Mar 2003 | A1 |
20030069029 | Dowling et al. | Apr 2003 | A1 |
20030088554 | Ryan et al. | May 2003 | A1 |
20030093315 | Sato | May 2003 | A1 |
20030101065 | Rohall et al. | May 2003 | A1 |
20030110227 | O'Hagan | Jun 2003 | A1 |
20030135555 | Birrell et al. | Jul 2003 | A1 |
20030145285 | Miyahira et al. | Jul 2003 | A1 |
20030163537 | Rohall et al. | Aug 2003 | A1 |
20030167310 | Moody et al. | Sep 2003 | A1 |
20030177190 | Moody et al. | Sep 2003 | A1 |
20030191689 | Bosarge et al. | Oct 2003 | A1 |
20030195801 | Takakura et al. | Oct 2003 | A1 |
20030229607 | Zellweger et al. | Dec 2003 | A1 |
20030233419 | Beringer | Dec 2003 | A1 |
20040044735 | Hoblit | Mar 2004 | A1 |
20040048604 | Idei | Mar 2004 | A1 |
20040054737 | Daniell | Mar 2004 | A1 |
20040059712 | Dean et al. | Mar 2004 | A1 |
20040068435 | Braunzell | Apr 2004 | A1 |
20040078432 | Manber et al. | Apr 2004 | A1 |
20040083133 | Nicholas et al. | Apr 2004 | A1 |
20040083265 | Beringer | Apr 2004 | A1 |
20040098488 | Mayers | May 2004 | A1 |
20040133564 | Gross et al. | Jul 2004 | A1 |
20040153509 | Alcorn et al. | Aug 2004 | A1 |
20040181580 | Baranshamaje | Sep 2004 | A1 |
20040199589 | Keohane et al. | Oct 2004 | A1 |
20040199623 | Houri | Oct 2004 | A1 |
20040205141 | Goland | Oct 2004 | A1 |
20040210587 | Reysa | Oct 2004 | A1 |
20040260710 | Marston et al. | Dec 2004 | A1 |
20040260756 | Forstall et al. | Dec 2004 | A1 |
20040267700 | Dumais et al. | Dec 2004 | A1 |
20050004990 | Durazo et al. | Jan 2005 | A1 |
20050015394 | McKeeth | Jan 2005 | A1 |
20050033657 | Herrington et al. | Feb 2005 | A1 |
20050038861 | Lynn et al. | Feb 2005 | A1 |
20050050027 | Yeh et al. | Mar 2005 | A1 |
20050060310 | Tong et al. | Mar 2005 | A1 |
20050060643 | Glass et al. | Mar 2005 | A1 |
20050076051 | Carobus et al. | Apr 2005 | A1 |
20050076132 | Roberts et al. | Apr 2005 | A1 |
20050086598 | Marshall, III et al. | Apr 2005 | A1 |
20050091320 | Kirsch et al. | Apr 2005 | A1 |
20050102292 | Tamayo et al. | May 2005 | A1 |
20050108345 | Suzuki | May 2005 | A1 |
20050114781 | Brownholtz et al. | May 2005 | A1 |
20050130685 | Jenkin | Jun 2005 | A1 |
20050131715 | Trethewey | Jun 2005 | A1 |
20050131884 | Gross et al. | Jun 2005 | A1 |
20050137939 | Calabria et al. | Jun 2005 | A1 |
20050138002 | Giacobbe et al. | Jun 2005 | A1 |
20050144157 | Moody et al. | Jun 2005 | A1 |
20050144241 | Stata et al. | Jun 2005 | A1 |
20050149397 | Morgenstern et al. | Jul 2005 | A1 |
20050160107 | Liang | Jul 2005 | A1 |
20050165896 | Mooney | Jul 2005 | A1 |
20050177401 | Koeppel et al. | Aug 2005 | A1 |
20050182765 | Liddy | Aug 2005 | A1 |
20050187823 | Howes | Aug 2005 | A1 |
20050198173 | Evans | Sep 2005 | A1 |
20050198256 | Moody et al. | Sep 2005 | A1 |
20050216454 | Diab et al. | Sep 2005 | A1 |
20050216516 | Calistri-Yeh et al. | Sep 2005 | A1 |
20050222900 | Fuloria et al. | Oct 2005 | A1 |
20050222985 | Buchheit et al. | Oct 2005 | A1 |
20050223058 | Buchheit et al. | Oct 2005 | A1 |
20050223066 | Buchheit et al. | Oct 2005 | A1 |
20050262203 | Buchheit et al. | Nov 2005 | A1 |
20060020510 | Vest | Jan 2006 | A1 |
20060026046 | Yaron et al. | Feb 2006 | A1 |
20060026593 | Canning et al. | Feb 2006 | A1 |
20060031304 | Bagga et al. | Feb 2006 | A1 |
20060064346 | Steenstra et al. | Mar 2006 | A1 |
20060075445 | O'Kane | Apr 2006 | A1 |
20060080303 | Sargent et al. | Apr 2006 | A1 |
20060085434 | Mah et al. | Apr 2006 | A1 |
20060092920 | Karamchedu et al. | May 2006 | A1 |
20060123091 | Ho | Jun 2006 | A1 |
20060129455 | Shah | Jun 2006 | A1 |
20060129943 | Maguire | Jun 2006 | A1 |
20060149677 | Shahine et al. | Jul 2006 | A1 |
20060167747 | Goodman et al. | Jul 2006 | A1 |
20060179127 | Randall | Aug 2006 | A1 |
20060184617 | Nicholas et al. | Aug 2006 | A1 |
20060248209 | Chiu et al. | Nov 2006 | A1 |
20060259473 | Li et al. | Nov 2006 | A1 |
20060294084 | Patel et al. | Dec 2006 | A1 |
20070005715 | LeVasseur et al. | Jan 2007 | A1 |
20070033531 | Marsh | Feb 2007 | A1 |
20070047697 | Drewry et al. | Mar 2007 | A1 |
20070050372 | Boyle | Mar 2007 | A1 |
20070067404 | Brown et al. | Mar 2007 | A1 |
20070088801 | Levkovitz et al. | Apr 2007 | A1 |
20070088851 | Levkovitz et al. | Apr 2007 | A1 |
20070088852 | Levkovitz | Apr 2007 | A1 |
20070143411 | Costea et al. | Jun 2007 | A1 |
20070143428 | Kumar et al. | Jun 2007 | A1 |
20070157119 | Bishop | Jul 2007 | A1 |
20070198639 | Litwin et al. | Aug 2007 | A1 |
20070255791 | Bodlaender et al. | Nov 2007 | A1 |
20070294740 | Drake et al. | Dec 2007 | A1 |
20080022211 | Jones et al. | Jan 2008 | A1 |
20080147815 | Damm et al. | Jun 2008 | A1 |
20080275873 | Bosarge et al. | Nov 2008 | A1 |
20080313292 | Forstall et al. | Dec 2008 | A1 |
20100280903 | Barlin et al. | Nov 2010 | A1 |
20100299326 | Germaise | Nov 2010 | A1 |
20110264750 | Fabre et al. | Oct 2011 | A1 |
20120226760 | Lewis | Sep 2012 | A1 |
Number | Date | Country |
---|---|---|
0886228 | Dec 1998 | EP |
09-128407 (A) | May 1997 | JP |
2001-222477 | Aug 2001 | JP |
2002-359667 (A) | Dec 2002 | JP |
2003-030216 | Jan 2003 | JP |
2003-108278 (A) | Apr 2003 | JP |
WO 9721183 | Jun 1997 | WO |
WO 0023931 | Apr 2000 | WO |
WO 0054201 | Sep 2000 | WO |
WO 0161551 | Aug 2001 | WO |
WO 0163512 | Aug 2001 | WO |
WO 03058519 | Jul 2003 | WO |
WO 03067497 | Aug 2003 | WO |
Entry |
---|
AdForce, Inc., A Complete Guide to AdForce, Version 2.6, 1998, Chapter 6, p. 6-20 and 6-21. (Provided by Applicant). |
Bellotti, V et al., (2003), “Taking Email to Task: the design and evaluation of a task management centered email tool.” In Conference Proceedings on Human Factors in Computing Systems (CHI2003), pp. 345-352, Apr. 5-10, 2003, Fort Lauderdale, Florida. |
Bellotti, V. et al., “Taskmaster: recasting email as task management,” PARC, CSCW '02 Workshop on Redesigning Email for the 21st Century. |
Comer, D. and Peterson, L., “Conversation-Based Mail,” ACM Transactions on Computer Systems (TOCS) vol. 4, Issue 4, pp. 299-319, Nov. 1986. |
Flores, F. et al., “Computer Systems and the design of organizational interaction,” ACM Transactions on Information Systems., pp. 153-172, (1988). |
Shepherd, A. et al., “Strudel—an extensible electronic conversation toolkit,” Proceedings of the 1990 ACM Conference on Computer-supported Cooperative Work, Los Angeles, California, United States, pp. 93-104. |
Venolia, G., et al., “Supporting Email Workflow,”Technical Report MSR-TR-2001-88, Microsoft Corporation, 10 pages (Sep. 2001). |
Winograd, T., (1987), “A language/action perspective on the design of cooperative work,” Human-Computer Interaction, vol. 3 No. 1, pp. 3-30, (1987-1988). Earlier version presented at the Conference on Computer-supported Cooperative Work, Austin, pp. 203-220, Dec. 1986. |
Winograd, T., “Where the Action is,” pp. 256A-260, Byte, Dec. 1988. |
Zawinski, J., “Message Threading,” http://www.jwz.org/doc/threading.html, pp. 1-9 (1997-2002). |
AdForce, Inc., A Complete Guide to AdForce, Version 2.6, 1998. |
AdForce, Inc., S-1/A SEC Filing, May 6, 1999. |
AdKnowledge Campaign Manager: Reviewer's Guide, AdKnowledge, Aug. 1998. |
AdKnowledge Market Match Planner: Reviewer's Guide, AdKnowledge, May 1998. |
Ad-Star.com website archive from www. Archive.org, Apr. 12, 1997 and Feb. 1, 1997. |
95/001,073, Reexamination of Stone et al. |
95/001,061, Reexamination of Stone et al. |
95/001,069, Reexamination of Dean et al. |
95/001,068, Reexamination of Stone et al. |
Baseview Products, Inc., AdManagerPro Administration Manual v. 2.0, Dec. 1998. |
Baseview Products, Inc., ClassManagerPro Administration Manual v. 1.0.5, Feb. 1, 1997. |
Business Wire, “Global Network, Inc. Enters Into Agreement in Principle With Major Advertising Agency,” Oct. 4, 1999. |
Information Access Technologies, Inc., Aaddzz brochure, “The Best Way to Buy and Sell Web Advertising Space,” © 1997. |
Information Access Technologies, Inc., Aaddzz.com website archive from www. Archive.org, archived on Jan. 30, 1998. |
Zeff, R. et al., Advertising on the Internet, 2nd Ed., John Wiley & Sons, 1999. |
Dedrick, R., Interactive Electronic Advertising, IEEE, 1994. |
Dedrick, R., A Consumption Model for Targeted Electronic Advertising, Intel Architecture Labs, IEEE, 1995. |
Request for Reexamination of U.S. Patent No. 7,240,025 B2, Control No. 95/001,073, Jul. 30, 2008. |
Request for Reexamination of U.S. Patent No. 6,446,045 B1, Control No. 95/001,061, Jul. 7, 2008. |
Request for Reexamination of U.S. Patent No. 7,249,059 B2, Control No. 95/001,069, Jul. 21, 2008. |
Request for Reexamination of U.S. Patent No. 6,829,587 B2, Control No. 95/001,068, Jul. 14, 2008. |
Digital Envoy Press Releases, “Double click and Digital Envoy Partner to Offer Advanced Geo-Targeting Solutions,” Mar. 23, 2003, 2 pages. |
Friedman, N., “Dashboard,” Jul. 25, 2003, 24 pages. |
NetGravity AdServer AdMaster's Guide, Mar. 11, 1997, 59 pages. |
About Microsoft Word screen shot, May 28, 2007, 1 pg. |
Apple Computer Inc, Mail 1.3.3 Help: Checking Spelling in Email, Aug. 31, 2004, 1 pg. |
Apple Computer Inc., Mac mail utility screenshot (Aug. 18, 2004), 1 pg. |
Courter, Mastering Microsoft Office 2000—Professional Edition, p. 3. |
Courter, Mastering Microsoft Office 2000—Professional Edition, pp. 36-37 and 92-94. |
Gmail beta About Gmail, Apr. 20, 2004, 2 pgs. |
Gmail beta Sneak Peek of Conversation View, Apr. 20, 2004, 1 pg. |
Gmail beta Sneak Peek of Gmail Inbox, Apr. 20, 2004, 1 page. |
Google, European Search Report, EP 11172427.4, Dec. 21, 2011, 6 pgs. |
Google, IPRP, PCT/US2005/006826, Oct. 4, 2006, 4 pgs. |
Google, ISR/WO, PCT/US2005/006826, Jun. 26, 2006, 7 pgs. |
Google, ISR/WO, PCT/US2005/010137, Jun. 3, 2005, 4 pgs. |
Google, Notice of Acceptance, AU 2011203058, Jan. 6, 2012, 3 pgs. |
Google, Office Action, AU 2011201989, Apr. 12, 2012, 3 pgs. |
Google, Office Action, AU 2011201991, Mar. 8, 2012, 2 pgs. |
Google, Office Action, AU 2011201992, Aug. 16, 2012, 3 pgs. |
Google, Office Action, AU 2011201993, Feb. 28, 2012, 2 pgs. |
Google, Office Action, AU 2011201994, Mar. 8, 2012, 2 pgs. |
Google, Office Action, AU 2011203058, Oct. 31, 2011, 1 pg. |
Google, Office Action, CN 200580016413.8, Jul. 2, 2012, 3 pgs. |
Google, Office Action, CN 200580016413.8, Dec. 19, 2011, 3 pgs. |
Google, Office Action, JP 2010-275595, Jul. 6, 2012, 4 pgs. |
Google, Office Action, KR 2006-7022840, Jan. 26, 2012, 4 pgs. |
Google, Office Action, KR 2011-7017094, Sep. 26, 2011, 5 pgs. |
Google, Office Action, KR 2011-7017095, Sep. 29, 2011, 5 pgs. |
Google, Office Action, KR 2011-7017096, Oct. 4, 2011, 4 pgs. |
Google, Office Action, KR 2011-7017098, Oct. 4, 2011, 3 pgs. |
Google, Office Action, KR 2011-7017102, Oct. 4, 2011, 4 pgs. |
Google, Supplemental ESR, EP 05724384.2, Mar. 16, 2009, 5 pgs. |
Gorman, The Next Major Email Domain: Gmail.com, Jun. 2004, 6 pgs. |
Lawrence, Context and page analysis for improved web search, Oct. 31, 1998, 9 pgs. |
O'Hara, Easy Microsoft Office Outlook 2003, Sep. 18, 2003, 44 pgs. |
Resnick, Network Working Group, RFC 2822, 70 pgs, Apr. 2001. |
Russel, Special Edition Using Microsoft Office Outlook 2003, Sep. 25, 2003, 102 Pgs. |
Screenshot of reply to message in Lotus Notes 6.5, Aug. 6, 2007, 1 pg. |
Syroid, Outlook 2000 in a Nutshell, May 2, 2000, O'Reilly, pp. 1-66. |
Thies, Special Report: How to Prosper With The New Google, 2004, 17 pgs. |
Tobias, Dan's Mail Format Site, Feb. 2, 2009, 6 pgs. |
Tyson, Sams Teach Yourself Microsoft Outlook 2000 in 24 Hours, 1999, pp. 237. |