US20090144380A1 - Peer-to-peer email - Google Patents

Abstract

A peer-to-peer email system and methods are provided for distributed email distribution, prevention of SPAM, and efficient email storage. Each email client also serves as a node in the peer-to-peer system, relaying email messages and/or attachments. Large attachments may be transmitted directly from sender to receiver, and if the receiver is not online at the time the sender sends the attachment, the receiver can request the attachment from the sender at a later time.

Description

CROSS REFERENCE TO RELATED APPLICATIONS
• This application claims priority to U.S. Provisional Application Ser. No. 60/989,774, entitled PEER-TO-PEER EMAIL, filed Nov. 21, 2007. The contents of that application are incorporated herein by reference for all purposes.
BACKGROUND
• Existing email systems may be centrally controlled. Simple Mail Transport Protocol (“SMTP”) is the de facto standard used on the internet today. A first SMTP server (e.g., mail.yin.com) may receive email messages from SMTP clients (e.g., Microsoft® Outlook, Mozilla® Thunderbird) executing on computers in the first SMTP server's domain. The email messages may include one or more recipient email addresses (e.g., john @yang.net). The first SMTP server may route the received messages to a second SMTP server on the intended recipient's domain (e.g., mail.yang.net) using known systems such as the domain name system (“DNS”). After receiving the email message, the second SMTP server may deliver the email messages to the intended recipient's mailbox, which may be stored on the second SMTP server and made available to the intended recipient over the network.
• SMTP servers may be configured to restrict the size of attachments which may be sent with an email message. Other SMTP servers may limit the amount of storage space (i.e., the size of a mailbox) allocated to a user to store emails and attachments. Still other SMTP servers may not protect or offer the capability of protecting emails and attachments associated therewith from malicious or otherwise unintended recipients, either locally or while in transit over a computer network.
• In addition to the above, unsolicited advertising emails (“SPAM”) are ubiquitous on the Internet. It is estimated by some that as of 2007, 90 billion SPAM messages are sent every day, and that so-called “abusive email” accounts for up to 85% of incoming mail in a given email inbox.
• Finally, existing email systems exhibit various inefficiencies. For instance, centralized email server farms are estimated to consume over two billion dollars worth of energy annually around the world. In addition, current methods of encoding attachments involve the use of base64, which encodes attachments as 7-bit representations, rather than traditional 8-bit. Base64 introduces approximately 30% of overhead to each attachment sent. Some estimate that attachments make up 80% of email traffic on the Internet. CPU cycles are also required to perform this encoding on the sending user's computer, as well as perform the decoding on the recipient user's computer.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 depicts an example email system.
• FIGS. 2A-E depict an email transmission on a system where the sender and the intended recipient are both online simultaneously.
• FIGS. 3A-H depict an email transmission on a system where the intended recipient is offline.
• FIG. 4 depicts an example method of preventing unsolicited emails.
• FIG. 5 depicts a computer using webmail from a remote location to obtain a user's email from his or her computer.
DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS
• A Peer-to-Peer (“P2P”) email and social networking system is provided for use by a plurality of users to exchange emails and attachments. Such a system may be controlled by one or more central servers, or it may be controlled by decentralized services distributed over a mesh network. Such a mesh network may comprise a plurality of node computers, each running a P2P email client according to the present disclosure. Node computers may be alternatively referred to as “peers.” Emails may be stored in mailboxes residing on each node, rather than centrally located. The system may encrypt emails during transmission, and the emails may remain encrypted while stored at each node computer.
• In some embodiments, the system may allow the user of each node computer to configure her email client with the user's interests (e.g., kayaking). Those interests may be communicated to a central server or decentralized distributed service, where they may be associated with the user's email address, so that potential advertisers may search by interest type, and send solicited emails to users associated with the searched-for interest types.
• In other embodiments, the system may be configured to provide remote access to the user's local email when the user is away from her local computer. Such access may be provided via a webmail webpage interfacing via a secure tunnel to the user's local email store.
• FIG. 1 depicts an exampleP2P email system10 comprising node computers such assender20 andrecipient30.Sender20 may be a computer controlled by a first user intending to send an email message to arecipient30.Recipient30 likewise may be a computer controlled by a second user who is the intended recipient of the email message. Sender20 andrecipient30 may be connected by anetwork40.Sender20 may include anemail client22, alocal email store24, and anemail agent26.Recipient30 likewise may include anemail client32, alocal email store34, and anemail agent36.
• Network40 may be a local or wide-area computer network, including the Internet. TheP2P email system10 may be controlled by components onnetwork40, such as decentralizeddistributed services42 includingidentity manager44,presence manager46,delivery manager48, andcontact store49, as well ascache servers50. Thedistributed services42 will be described in further detail below. While decentralizeddistributed services42 are shown having the fourcomponents44,46,48 and49 as being separate, these components may alternatively reside on a single server, and there may be more than one server hosting one or more of these services. Moreover, additional services which are not shown (e.g., a gateway server for sending emails to traditional email domains) may also be included.
• Email clients22 and32 may include user interfaces resembling traditional email clients (e.g., Outlook, Thunderbird), and may be configured to allow a user to draft, send and receive P2P emails.Email clients22 and32 may further include interfaces allowing a user to select interests (e.g., kayaking, dating), which may be communicated to decentralizeddistributed services42 so that potential advertisers may communicate solicited emails toclients22 and32, as will be discussed further below.
• Local email stores24 and34 may be portions of memory (e.g., on a local hard drive) which may be used to store email messages and associated attachments. In other words,local email stores24 and34 may serve similar roles as mailboxes on traditional SMTP servers. Messages stored inlocal email stores24 and34 may be encrypted. The amount of space allocated to a user may be configured, and in some embodiments may be limited only by the computer's storage capabilities. In addition to emails and attachments,local mail stores24 and34 may store interest information (a.k.a. user metadata), user contacts (e.g., the user's friends residing on P2P email system and elsewhere), user profiles (e.g., photos available for viewing, whom may view the photos, personal information and to whom it is available), group membership (e.g., open or closed groups of users ofP2P email system10 having common interests/metadata/contacts) or the like. Interest information, contacts, profiles and other similar information may be configured by a user using email clients such as22 or32.
• Email agents26 and36 may be processes executing on node computers such assender20 orrecipient30 forming the P2P network. While a computer such assender20 orrecipient30 is connected tonetwork40 and is executing its email agent (26 or36), that computer may be considered ‘online’ for purposes of the P2P network and this discussion.
• Contact store49 may be a central server or servers, or it may be a service distributed among various nodes in theP2P email system10. It may contain information allowing peers onP2P email system10 to locate other peers, including information similar to that stored in local email stores described above like interest information, contacts, metadata, group membership, and the like. Peers may be searched atcontact store49 using various search values, such as interests, group membership, friendship networks, personal profiles, and the like. In some embodiments, users may synchronize information stored in theirlocal email stores24,34 such as metadata, profiles, and contacts with information contained incontact store49. In other embodiments wherecontact store49 is a service distributed among various nodes, there may be a central contact store (not shown) which is configured to synchronize all nodes on whichcontact store49 is contained.
• Cache servers50 may comprise one or more computers onnetwork40 which may be used as intermediate points in email communications between computers such assender20 andrecipient30.Cache servers50 may be configured to cache at least a portion of email messages, as well as attachments thereto. In some embodiments, each cache server may be a node computer, similar tosender20 orreceiver30, forming another peer on the P2P system. Additionally or alternatively,cache servers50 may be specialized computers maintained specifically for the purpose of caching emails. In some embodiments, cache servers may only cache attachments having a size smaller than a predetermined size (e.g., <50 Megabytes).
• A given email message in transition betweensender20 andrecipient30 may be stored at a number ofcache servers50 while awaiting delivery, providing redundancy and high availability of the email message torecipient30 in case some of the cache servers become unavailable (e.g., go offline). Moreover,cache servers50, which may simply be peers or node computers onP2P system10, may be configured to forward email messages to other intermediate peers closer to the recipient's destination. Additionally or alternatively, if a given cache server is going to go offline, it may forward copies of its stored pending email messages/attachments and/or notify the P2P email system of the email's new location.
• TheP2P email system10 will now be explained by example. An example email communication between twonode computers20 and30, which are online simultaneously, is shown inFIGS. 2A-E. Instep1 ofFIG. 2A,email client application22 submits an email message created by a first user to emailagent26. Instep2 ofFIG. 2B,email agent26 communicates withidentity manager44 to verify the recipient email address(es) contained in the email message, and to obtain one or more public keys corresponding to the verified email address(es). The public keys may be used byemail agent26 to encrypt the email message and/or any the message's attachments.
• Identity manager44 may take various forms. In some embodiments,identity manager44 may be a central database running a hash table or similar data structure for relating email addresses to public keys. In other embodiments,identity manager44 may be a distributed hash table (“DHT”), such as Content Addressable Network (“CAN”), Chord, Kademlia, Pastry, P-Grid, Tapestry or NeoNet, to name a few. DHTs are a class of decentralized distributed systems that provide a lookup service similar to a hash table. They are well-known in the art, and therefore need not be described further here. Email addresses such as the recipient email address may comprise the names of the hash table, and the value(s) corresponding to each name may be one or more public keys. Email agents such as36 each may possess private keys usable to decrypt messages encrypted with the one or more public keys.
• Instep3 ofFIG. 2C,sender email agent26 may communicate withpresence manager46 to determine whetherrecipient30 is online. Ifrecipient30 is online,sender email agent26 may obtain recipient's network address (e.g., IP address).
• Presence manager46 may be a central server configured to track the presence of email clients and make that information available to email agents such as26 and36. Presence manager may be a central server or decentralized service, implementing various protocols, such as the Extensible Messaging and Presence Protocol (“XMPP”), for real-time or near-real-time presence information. Jabber Instant Messaging and Presence technology is based on XMPP, and may be used in some embodiments aspresence manager46.
• Oncesender email agent26 has obtained the network address ofrecipient30 frompresence manager46,sender email agent26 may transmit the email message and any attachments thereto directly torecipient email agent36 instep4 ofFIG. 2D. Whenrecipient email agent36 receives the email message, instep5 ofFIG. 2D, it may store the email message (which may remain encrypted) and attachments thereto inlocal email store34.
• When the user ofrecipient30 executesemail client32 to check her email, instep6 ofFIG. 2E,recipient email client32 may communicate withlocal email store34 to obtain all recipient's email messages, including the newest message just received, as well as any attachments thereto. If the messages are encrypted,email client32 may use its private key, corresponding to the public key described above, to decrypt messages.
• The above discussion describes an email transmission where bothsender20 andrecipient30 are online simultaneously. However, there is no guarantee thatrecipient30 will be online at themoment sender30 transmits an email message.FIGS. 3A-H and the following discussion describe one possible way an email may be transmitted betweensender20 andrecipient30 under such a scenario.
• Instep100 shown inFIG. 3A, similar to step1 ofFIG. 2A,email client application22 submits an email message created by a user to emailagent26. Similar to step2 inFIG. 2B, instep102 ofFIG. 3B,email agent26 connects toidentity manager44 to verify the recipient email addresses contained in the email message, and to obtain public keys corresponding to the verified email addresses. And again, instep104 inFIG. 3C,sender email agent26 communicates withpresence manager46 to determine whetherrecipient30 is online.
• In the previous example,recipient30 was online, and therefore available to receive the email message and attachments directly fromsender20. However, in this example,recipient30 is offline. Therefore, instep106 ofFIG. 3D,sender email agent24 may communicate the message body of the email message and any attachments having a size less than a predetermined amount tocache servers50 residing onnetwork40. In some embodiments, attachments having sizes greater than the predetermined amount may remain stored locally onsender20. Instep108 ofFIG. 3E,sender email agent26 may notifydelivery manager48 that there are pending messages stored innetwork40, as well as where those pending message may be located (e.g., on whichcache servers50 the message is cached).
• In some embodiments,delivery manager48 may be a central server configured to store information regarding pending P2P email messages stored innetwork40. In other embodiments,delivery manager48 may be a decentralized service such as a DHT or other similar distributed systems.
• In some embodiments wheredelivery manager48 is a DHT, the names may be recipient email addresses, and the values associated therewith may include information necessary forrecipient email agent36 to obtain pending email messages fromnetwork40. Such information may include address information associated withparticular cache servers50 having cached copies of the pending email. The address information may be a network address of theparticular cache servers50 storing the pending emails, or, if each cache server is merely another node similar to20 or30, the address information may be an email address associated with each node.
• In other embodiments, each email message or attachment may have a unique Universal Resource Name (“URN”).Recipient email agent36 may be notified of any URNs associated with email messages or attachments destined forrecipient30. Adelivery manager48 implementing a DHT may use URNs related to pending email messages and attachments as names, and the value(s) associated with each URN may be a Universal Resource Locator (“URL”). The URL may indicate where the email message/attachment identified by a URN may be found, as well as what method may be used to obtain the message/attachment (e.g, ftp://www.yin.comlattachment.jpg indicates that the file ‘attachment.jpg’ may be obtained from the domain yin.com using the ftp protocol).
• Accordingly, whenrecipient30 comes online, instep110 ofFIG. 3F,recipient email agent36 may communicate withdelivery manager48 to determine whether there are pending email messages onnetwork40 which are intended forrecipient30 and to identify one ormore cache servers50 where those messages are located. In some embodiments,recipient email agent36 may next communicate withpresence manager44 to determine which of the identified nodes are currently online and those nodes' network addresses.
• Next, instep112 ofFIG. 3G, recipient local email store34 (or alternatively, recipient email agent36) may communicate with the identified nodes of thecache servers50 to retrieve message bodies and attachments having a size less than the predetermined amount described above.
• Attachments larger than the predetermined size may be obtained from theoriginal sender30, assumingsender30 is currently online. Ifsender20 is not currently online,recipient30 may periodically querypresence manager46 so that whensender20 comes back online,recipient30 may then obtain the large attachment directly fromsender20.
• In some embodiments, wherelocal email store34 oremail agent36 must download multiple emails fromcache servers50, it may prioritize which emails/attachments will be retrieved first. For instance, anemail client32 may provide an interface for a user to edit contacts and sort them by various criterion (e.g., degrees of separation of friendship, age, etc.). Using this priority information,email client32 oragent36 may retrieve emails/attachments in the order of which its contacts have been sorted by the user. This priority information may be synchronized withcontact store49 when convenient.
• When the user of recipient device wishes to read the received message(s), he or she may userecipient email client32 to view email messages, including newly received messages, stored inlocal email store34 instep108 ofFIG. 3H.
• In some embodiments,sender20 may be configured to verify thatrecipient30 received the email address. For instance,recipient email agent36 may send an acknowledgement tosender20 once recipientlocal email store34 has received and stored the entirety of the email and any attachments thereto. Additionally or alternatively,Sender20 may queryrecipient30 to determine whetherrecipient30 received the message. In some embodiments,recipient30 may notify one of the services in decentralized distributed services42 (e.g., delivery manager48) that a message having a particular URN has been delivered. In such a case,sender20 may verify that the message was received by communicating with theservices42.
• In the P2P email system disclosed herein, some embodiments may be configured to prevent unsolicited email and/or provide users with emails related to topics of interest. Turning toFIG. 4, instep200, anadvertiser62 of a particular interest (e.g., a kayak manufacturer) may communicate with decentralized distributedservices42 to upload advertisement information, which may include metadata such as keywords (e.g., kayak) as well as advertising emails and/or attachments.Email client22 may include an interface including alist60 of selectable interests. A user ofemail client22 may choose one or more interests fromlist60 in step202, and those choices may be communicated to decentralized distributed services42 (e.g., to delivery manager48) instep204. In step206,email agent26 may “pull” down the advertisements uploaded byadvertiser62 instep200. Note that becausesender20 indicated interest in kayaks, the email sent in step206 is not unsolicited.
• In some embodiments, advertisers such as62 may be charged a fee for each of their advertisement emails “pulled” from thesystem10. Additionally or alternatively, a ratings system similar to those used in television (e.g., Nielsen ratings, which are based on the habits of home TV viewers) may be implemented to ascertain how much a given advertisement is “pulled,” for purposes of charging advertisers such as62.
• In another aspect, a user who is away from her computer containing her P2P emails may nevertheless wish to access those emails. In traditional email systems (e.g., SMTP), such a user may have access to a webmail interface, which may comprise a HTML page which the user may access with a web browser. The user may enter her login information (e.g., a username and password), and upon successful authentication, the webpage may direct the user's web browser to a second webpage which allows the user to view, manipulate, and create/send new email messages. This second web page may obtain email data from and interface with the same mail server (containing the user's mailbox) which the user would normally log into with her local computer.
• Webmail access similarly may be possible in some embodiments of the disclosedP2P email system10. Referring toFIG. 5, a user may be away from hercomputer20, but may wish to access email on herlocal email store24 using aremote computer70. A central server or one of the decentralized distributed services42 (such as delivery manager48) may include a webmail service. Instep300, the user may connect to the webmail service executing on decentralized distributedservices42 and provide login credentials to a login webpage. Upon successful authentication, the user may be redirected to a second webpage giving the user email access. Instead of communicating with the user's mailbox on a central SMTP server, however, instep302, the second webpage may communicate with the user'slocal email store24 through asecure tunnel72 to the user'scomputer20.
• Although the above examples only describe the exchange of email messages between two node computers onP2P system10, those skilled in the art will understand that communications may occur between any number of node computers. Moreover, communications may occur between a node computer onP2P system10 and a traditional email system (e.g., hotmail, gmail, etc.).
• For example, one of the decentralized distributed services (e.g., a separate gateway server which is not shown) may be identified as a mail exchanger (MX) in a DNS. The Gateway server therefore may receive email messages/attachments sent from traditional email systems, destined for a recipient residing on the disclosedP2P email system10, and communicate those messages to the appropriate recipients using the above-described methods (depending on whether the user is online or offline).
• Likewise, if a user on a node computer ofP2P email system10 desires to send an email message to an outside traditional email address, the user may communicate the message and any attachments to the gateway server. The gateway server may forward the message to the appropriate SMTP server using MX records in the DNS. In some embodiments,identity manager44 may be configured with an index of domains that are part ofP2P email system10. Whensender20 verifies the email address, such as instep2 inFIG. 2B or step102 inFIG. 3B,identity manager44 may determine whether the recipient email address(es) are within theP2P email system10. If so, the process may proceed as described above. If a recipient email address is destined for an outside domain unrelated to theP2P email system10, however,sender20 may be required to forward the email and any attachments to the gateway server for delivery to the outside domain.
• In another aspect of the disclosure, theP2P email system10 may provide efficient attachment distribution. In some instances, instead of using base64 to encode attachments to 7-bit representations, theP2P email system10 may determine the URLs of attachments and make those URLs available through decentralized distributedservices42. For instance, assumesender20 sends an email message including a large attachment (i.e., too large to be stored on cache servers50) torecipient30. Also assumerecipient30 is online simultaneously withsender20. The email received byrecipient30 may not include the large attachment, encoded using Base64 or otherwise. Instead, the email received byrecipient30 may include a hyperlink (URL) to a location onsender20 containing the large attachment, so thatrecipient30 may initiate a connection tosender20 and download the large attachment directly (e.g., using FTP, HTTP, BitTorrent, or other well-known transfer protocols). The initiation of the file transfer may not require intervention by the user ofrecipient30. Instead,recipient email client32 may be configured to automatically initiate the transfer when the user opens the email or attachment.
• Accordingly, while embodiments have been particularly shown and described with reference to the foregoing disclosure, many variations may be made therein. The foregoing embodiments are illustrative, and no single feature or element is essential to all possible combinations that may be used in a particular application. Where the disclosure recites “a” or “a first” element or the equivalent thereof, such disclosure includes one or more such elements, neither requiring nor excluding two or more such elements. Further, ordinal indicators, such as first, second or third, for identified elements are used to distinguish between the elements, and do not indicate or imply a required or limited number of such elements, and do not indicate a particular position or order of such elements unless otherwise specifically stated.

Claims (14)

1. A storage medium, readable by a first processor of a first computer system, having embodied therein a first computer program of commands executable by the first processor, the program being adapted to be executed to:

transmit a user identifier to a presence manager, the user identifier identifying a user to which an outgoing email message is to be delivered;

receive from the presence manager an indication of whether the user identified by the user identifier is currently online;

where the user is currently online, receive from the presence manager a network address of the user, and transmit the outgoing email message to the network address; and

where the user is not currently online, transmit the outgoing email message to a first cache computer system and transmit to a delivery manager the user identifier, an email identifier uniquely identifying the outgoing email message, and a network address associated with the first cache computer system;

2. The storage medium ofclaim 1, in which the first computer program is further adapted to be executed to:

transmit the user identifier to an identity manager;

receive from the identity manager a public key associated with the user identifier; and

encrypt the outgoing email message with the public key prior to transmitting the outgoing email message.

3. The storage medium ofclaim 1, in which the first computer program is further adapted to be executed to:

determine whether an attachment associated with the outgoing email message has a size that is less than a predetermined size;

where the size of the attachment is less than the predetermined size, transmit the attachment to a second cache computer system and transmit to a delivery manager the email identifier and a network address associated with the second cache computer system;

where the size of the attachment is greater than the predetermined size, provide to the user identified by the user identifier network access to the attachment.

4. The storage medium ofclaim 1, in which the first computer program is further adapted to be executed to:

receive as input an interest identifier identifying an interest;

transmit the interest identifier to the delivery manager; and

receive emails relating to the interest.

5. The storage medium ofclaim 1, in which the first computer program is further adapted to be executed to:

connect to the delivery manager using a secure tunnel protocol; and

transmit email data to the delivery manager for delivery to a user of the first computer system that is currently using a second computer system different than the first computer system to access data on an email store on the first computer system.

6. The storage medium ofclaim 1, in which the first computer program is further adapted to be executed to:

transmit to the delivery manager a request for pending email messages intended for delivery to a first user of the first computer system;

receive an email identifier identifying an incoming email message intended for delivery to the first user;

receive a network address associated with a second cache computer system where the incoming email message is stored;

receive from the second cache system the incoming email message; and

store the incoming email message locally.

7. The storage medium ofclaim 6, in which the first computer program is further adapted to be executed to:

determine whether the incoming email message includes an associated attachment;

where an attachment associated with the incoming email message has a size that is less than a predetermined size, receive the attachment from a third cache computer system; and

where the attachment associated with the incoming email message has a size that is greater than the predetermined size, receive from the attachment from a computer system from which the incoming email message was sent.

8. The storage medium ofclaim 1, in which the first computer program is further adapted to be executed to:

receive an email message intended for delivery to a second user using a second computer system different from the first computer system, the email message being from a third user of a third computer system different from the first and second computer systems;

receive a request for the email message intended for delivery to the second user; and

transmit the email message intended for delivery to the second user to the second computer system.

9. A storage medium, readable by a first processor of a first computer system, having embodied therein a first computer program of commands executable by the first processor, the program being adapted to be executed to:

transmit to a delivery manager a request for pending email messages intended for delivery to a first user of the first computer system;

receive an email identifier identifying an incoming email message intended for delivery to the first user;

receive a network address associated with a first cache computer system where the incoming email message is stored;

receive from the first cache system the incoming email message; and

store the incoming email message locally.

10. The storage medium ofclaim 9, in which the first computer program is further adapted to be executed to:

determine whether the incoming email message includes an associated attachment;

where an attachment associated with the incoming email message has a size that is less than a predetermined size, receive the attachment from a second cache computer system; and

where the attachment associated with the incoming email message has a size that is greater than the predetermined size, receive from the attachment from a computer system from which the incoming email message was sent.

11. The storage medium ofclaim 9, in which the first computer program is further adapted to be executed to:

receive an email message intended for delivery to a second user using a second computer system different from the first computer system, the email message being from a third user of a third computer system different from the first and second computer systems;

receive a request for the email message intended for delivery to the second user; and

transmit the email message intended for delivery to the second user to the second computer system.

12. A peer-to-peer email system comprising first, second and third node computer systems used by first, second and third users, respectively, a delivery manager computer system, and a presence manager computer system:

wherein the presence manager computer system is configured to:

receive a request on behalf of the first node for an online status of the second node;

transmit to the first node an indication that the second node is not currently online; and

wherein the first node is configured to:

request from the presence manager an indication of whether the second node is currently online;

receive an indication that the second node is not currently online;

transmit an email message intended for delivery to the second user to the third node;

transmit to the delivery manager a user identifier identifying the second user, an email identifier uniquely identifying the email message intended for delivery to the second user, and a network address associated with the third node.

13. The peer-to-peer email system ofclaim 12, wherein the delivery manager computer system is configured to:

receive the user identifier, email identifier and network address from the first node;

receive a request from the second node for pending email messages intended for delivery to the second user;

transmit the email identifier and the network address to the second node.

14. The peer-to-peer email system ofclaim 12, further comprising an identity manager configured to:

receive a request from the first node for a public key associated with the second user;

transmit to the first node the public key associated with the second user;

wherein the first node is further configured to encrypt the email message intended for delivery to the second user prior to transmitting the email message.

Images