Managing digital message sending via proxy digital mailboxes

Abstract

A technique for managing digital messages to and from a proxy message address. The system receives a message directed to a specific destination address. The system replaces any source address included in the message with a proxy address. When the system receives a reply to the message, the reply is directed to the proxy address. The system analyzes the message data to identify a target address for the reply message. The system identifies contextual data associated with the reply message. The system transmits the reply message and the contextual data to the target address.

Description

[Technical Field]

[0001] Incorporation by Reference, Disclaimer The following applications are incorporated herein by reference: Application No. 18 / 299,641, filed April 12, 2023; Application No. 63 / 416,351, filed October 14, 2022. Applicant hereby waives any disclaimer of claim scope or prosecution history in the parent application and notifies the USPTO that the claims in this application may be broader than any claims in the parent application.

[0002] Technical Field The present disclosure relates to managing the transmission of digital messages through proxy mailboxes, and in particular to analyzing message content, including metadata and content within the messages, to identify recipients for digital messages directed to a proxy mailbox. [Background technology]

[0003] background Companies use a global email mailbox to send messages to and receive messages from customers. Typically, one or more users with permission can view messages in the global email mailbox. However, the email mailbox receives a large volume of emails, and users may have difficulty determining which emails apply to them. Users may miss opportunities or upset customers by failing to respond to emails in a timely manner. Additionally, when users receive a large volume of emails, they may find it difficult to remember the context associated with a particular email. For example, a recruiter may handle 10 different candidates, 4 active customers, 20 or more opportunities related to other recruiters or the overall recruiting company. When reading candidate emails, the recruiter may find it difficult to remember the qualifications of a particular candidate or the requirements for a particular position.

[0004] The approaches described in this section are approaches that could be pursued, but not necessarily approaches that have been previously conceived or pursued. Thus, unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section. Summary of the Invention

[0005] Embodiments are illustrated by way of example, and not by way of limitation, in the accompanying drawings, in which: It should be noted that references to "an" or "one" embodiment in this disclosure do not necessarily refer to the same embodiment, but rather mean at least one. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 illustrates a system according to one or more embodiments. [Figure 2A] FIG. 2 illustrates an example set of operations for managing the sending of digital messages through a proxy mailbox, according to one or more embodiments. [Figure 2B] FIG. 2 illustrates an example set of operations for managing the sending of digital messages through a proxy mailbox, according to one or more embodiments. [Figure 3] FIG. 2 illustrates an example set of operations for identifying multiple digital message recipients for a digital message sent to a proxy mailbox, according to one or more embodiments. [Figure 4] FIG. 1 illustrates one exemplary embodiment. [Figure 5] FIG. 1 is a block diagram illustrating a computer system according to one or more embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0007] Detailed Description In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding. One or more embodiments may be practiced without these specific details. Features described in one embodiment may be combined with features described in a different embodiment. In some instances, well-known structures and devices are described with reference to block diagram form in order to avoid unnecessarily obscuring the present invention.

[0008] 1. Overview 2. System Architecture 3. Analysis of digital message content to manage digital message transmission via proxy mailboxes 4. Analysis of digital messages to proxy mailboxes to identify multiple recipients 5. Exemplary Embodiments 6. Computer Networks and Cloud Networks 7. Miscellaneous, Extensions 8. Hardware Overview

[0009] 1. Overview One or more embodiments include a digital message management platform for contextual routing of messages using proxy addresses. The digital message management platform manages one-to-n and n-to-n communications incorporating proxy addresses for uniform messaging, user privacy, and message management. In one example, outbound messages from various users associated with the digital message management platform are sent with the same proxy address as the source address (replacing the user's address). When a reply message is received, the digital message management platform identifies an appropriate recipient from the set of users associated with the digital message management platform based on contextual data determined from the message, message metadata, and / or the source of the reply message.

[0010] Identifying appropriate recipients from the set of users for contextual routing may include identifying the initial user that sent the outbound message, identifying users that were included in the initial outbound message, identifying users that may contribute to the conversation, and / or identifying users that the system determines should be replicated in the conversation based on inclusion criteria.

[0011] According to one or more embodiments, the contextual data used to route the message may include, for example, personal information about the writer of the reply message and information about the subject matter with which the writer of the reply message is associated. The system provides the contextual information along with the reply message to the initial source address.

[0012] In one or more embodiments, the digital message management platform augments inbound and / or outbound messages with supplemental information that may be useful to the message recipient. In one example, the digital message management platform forwards a message from a candidate to a recruiter. Before forwarding the message, the digital message management platform queries a database for hiring manager notes associated with the candidate. The system appends the notes to the message before forwarding the message to the recruiter. The recruiter can then process and / or respond to the candidate's message taking the hiring manager notes into account.

[0013] According to one or more embodiments, the system determines when a reply message should be sent to an address other than the initial source address. For example, the initial source message may be "to:Bob@domain2.xxy" and "cc:Lucy@domain1.xxy." The system sends the initial message to the addresses Bob@domain2.xxy and Lucy@domain1.xxy. When the system receives a reply from Bob@domain2.xxy that omits Lucy@domain1.xxy as a destination address, the system determines whether to also send the reply message to Lucy@domain1.xxy. For example, the system may apply rules specifying whether (a) an initial digital message from the source address included Lucy@domain1.xxy as a destination address, and (b) a reply message to the initial digital message did not include Lucy@domain1.xxy; then, the system modifies the destination address associated with the reply address to include the destination address Lucy@domain1.xxy.

[0014] According to one or more embodiments, a digital message management platform provides contextual notification and / or display of messages from a shared mailbox. For example, a user may send a message from the email address of the shared mailbox and may receive a message in the shared mailbox. When the message is received at the address associated with the shared mailbox, the digital message management platform identifies one or more recipients who have access to the shared mailbox based on contextual data, message metadata, and / or the source of the message determined from the message. The system may perform notification operations such as (a) sending a notification to a particular communication platform, such as email, instant message, or text, that a message in the shared mailbox is associated with the recipient; (b) tagging the message in the shared mailbox with the name of the recipient associated with the message; and / or (c) categorizing the messages in the shared mailbox according to user. For example, the shared mailbox may include a separate header for each user who has access to the shared mailbox. Under each header, the system may display messages that the system determines are relevant to the particular user. Additionally or alternatively, users may access email messages through a particular application. A particular application may access the shared mailbox and display for a user only messages from the shared mailbox associated with the particular user. The system may display the shared mailbox in a manner that hides messages that are determined to be associated with other users and that the particular user does not have permission to view.

[0015] One or more embodiments provide for selectively anonymizing messages via a digital message management platform. For example, a user may generate a message to an external address. The message generation graphical user interface (GUI) may include radio buttons for (a) showing / hiding the source address and (b) showing / hiding the source sender name. For example, a user may hide the source address but show the source name. The recipient sees the email from the proxy email address or shared email address and the sender name. Alternatively, the user may hide both the source address and the sender name. The recipient sees the email from the proxy email address or shared email address with the sender name omitted. Additionally or alternatively, the message generation GUI may include radio buttons for showing the sender name and / or address for recipients within the same organization as the sender (e.g., recipients with the same email domain) and hiding the sender name and / or address for recipients outside the organization.

[0016] One or more embodiments described and / or claimed herein may not be included in this summary section.

[0017] 2. System Architecture FIG. 1 illustrates a system 100 according to one or more embodiments. As shown in FIG. 1, system 100 includes a digital communication management platform 110 and a data repository 130. In one or more embodiments, system 100 may include more or fewer components than those illustrated in FIG. 1. The components illustrated in FIG. 1 may be local or remote from one another. The components illustrated in FIG. 1 may be implemented in software and / or hardware. Each component may be distributed across multiple applications and / or machines. Multiple components may be combined into one application and / or machine. Operations described with respect to one component may instead be performed by another component.

[0018] One or more clients 102, 104 communicate with a digital communication management platform 110 to send and receive digital messages, such as electronic mail (email). The digital communication management platform 110 sends digital messages to and receives digital messages from one or more destination devices 120. For example, a client 102 associated with a first digital message address 103 may connect to a user interface, such as interface 119, of the digital communication management platform 110 to send a digital message to the destination device 120. A user associated with a digital message address 121 may access the destination device 120 to send a digital message to a proxy address 112-115.

[0019] According to one or more embodiments, clients 102 and 104 are associated with one or more devices, such as a personal computer, a laptop, or a mobile device. A user associated with address 103 or 105 may communicate with digital communication management platform 110 via any device. For example, a user associated with address 103 may open an application on a workstation to access cloud-based digital communication management platform 110 managed in-house by a company. Additionally or alternatively, a user associated with address 103 may access digital communication management platform 110 by entering a uniform resource locator (URL) into a web browser from any one of a personal computer, laptop, and mobile phone. Additionally or alternatively, digital communication management platform 110 may be implemented, at least in part, as an application downloadable to a client device. A user associated with address 103 or 105 may connect with the application to send and receive messages. The application may communicate with cloud-based resources to perform functions for sending, receiving, storing, and analyzing digital messages.

[0020] According to one or more embodiments, the system includes an automatic message generator 106. The automatic message generator 106 may generate messages associated with one or more clients 102, 104 without user input from a user associated with the client 102, 104. For example, a recruiting application may match employment opportunities with candidates associated with the client 102. The recruiting application may generate an email message to each candidate with a link to one or more employment opportunities without user input from the client 102. When the digital communication management platform 110 sends a message to a user associated with the address 121, the proxy mailbox manager 111 may specify the job mailbox address 112 as the source address. When the user associated with the address 121 replies to the message, the digital communication management platform 110 may identify the client 102 as associated with the reply message, even though the initial message was generated by the automatic message generator 106 and sent from the anonymized address 112, and the candidate replied to the anonymized address 112.

[0021] Digital communication management platform 110 includes a proxy mailbox manager 111, a contextual data search engine 118, a digital communication processing engine 117, and an interface 119. In one or more embodiments, interface 119 refers to hardware and / or software configured to facilitate communication between a user and digital communication management platform 110. Interface 119 renders user interface elements and receives input via user interface elements. Examples of interfaces include a graphical user interface (GUI), a command line interface (CLI), a tactile interface, and a voice command interface. Examples of user interface elements include check boxes, radio buttons, drop-down lists, list boxes, buttons, toggles, text fields, date and time selectors, command lines, sliders, pages, and forms.

[0022] In one embodiment, different components of interface 119 are specified in different languages. The behavior of user interface elements is specified in a dynamic programming language such as JavaScript. The content of user interface elements is specified in a markup language such as HyperText Markup Language (HTML) or XML User Interface Language (XUL). The layout of user interface elements is specified in a style sheet language such as Cascading Style Sheets (CSS). Alternatively, interface 119 is specified in one or more other languages, such as Java, C, or C++.

[0023] According to one embodiment, interface 119 includes a graphical user interface element that allows a user to selectively anonymize a message. For example, a user may use address 103 to generate a message to external address 121. Interface 119 may provide client 102 with a GUI that includes user-selectable radio buttons to (a) show / hide the source address and (b) show / hide the source sender name. The GUI may also include radio buttons to allow a user to selectively show their name and address to other users within the same organization, such as a user whose address includes "domain1." When a user selects the interface element to hide the source address, proxy mailbox manager 111 replaces the source address "name1@domain1" with a corresponding proxy address, such as "recruiting@domain1." Proxy mailbox manager 111 includes the name associated with the address "name1@domain1" in the message. For example, a recipient may select "name1@domain1" in the address line.<recruiting@domain1> If the user selects the interface element to hide both the username and the source address, the proxy mailbox manager 111 replaces the source address "name1@domain1" with the corresponding proxy address, such as "recruiting@domain1". The proxy mailbox manager 111 also omits from the message the name associated with the address "name1@domain1". For example, if the recipient ...<recruiting@domain1> " can be seen.

[0024] Proxy mailbox manager 111 stores messages associated with one or more proxy mailboxes 134. In the embodiment shown in FIG. 1, proxy mailboxes 134 include a recruiting mailbox associated with address 112, a support mailbox associated with address 113, an information mailbox associated with address 114, and a sales mailbox associated with address 115. Each proxy mailbox may be associated with one or more clients, such as users or employees. For example, an organization may include 10 recruiters. The recruiting mailbox associated with address 112 may manage messages from and to the 10 recruiters. Similarly, an organization may include 50 customer support representatives. The support mailbox associated with address 113 may manage messages from and to the 50 customer support representatives. For example, proxy mailbox manager 111 receives a message directed to proxy address 112, identifies a specific address 103 or 105 associated with the message, and generates a message including the message content for transmission to the specific address 103 or 105 identified as associated with the message.

[0025] The proxy mailbox manager 111 includes a proxy mailbox configuration analysis engine 116. The proxy mailbox configuration analysis engine 116 analyzes the proxy mailbox configuration 131 to identify rules for storing and sending messages. For example, the proxy mailbox configuration 131 may specify the client 102 or 104 to which a message should be sent. The proxy mailbox configuration 131 may specify conditions under which the proxy mailbox manager 111 should generate a message. For example, the proxy mailbox configuration analysis engine 116 may determine that if the message is personal in nature based on semantic content, the proxy mailbox manager 111 should send the message to the recipient without generating a message from the proxy mailbox address. In contrast, the proxy mailbox configuration analysis engine 116 may determine that if the message is business-related based on semantic content, the proxy mailbox manager 111 should generate a message including the message content with the proxy mailbox address as the source address. The proxy mailbox configuration 131 may specify that any message sent from address 103 should be carbon copied (cc'd) to address 105. Proxy mailbox configuration 131 may specify that any message sent to address 103 should be carbon-copied to address 105. Proxy mailbox configuration 131 may specify that the proxy mailbox manager should generate a message to address 103 and carbon-copy it to address 105 when (a) a received message is a reply to a message originating from address 103, and (b) a message originating from address 103 is carbon-copied to address 105.

[0026] Digital communication processing engine 117 analyzes received digital communications to identify actions that should be interpreted as associated with the communications. For example, digital communication processing engine 117 analyzes digital communications received from clients 102 and 104 and automatic message generator 106 to identify proxy mailboxes from which messages should be sent. Digital communication processing engine 117 analyzes digital communications received from external addresses, such as address 121, that are directed to proxy addresses 112, 113, 114, or 115 to identify addresses 103 or 105 to which messages should be sent.

[0027] The digital communication processing engine 117 analyzes digital communications by analyzing the content within the communication and / or the metadata transmitted with or associated with the communication. For example, message content may include an item identification number within the text of the message, a name within the text of the message, a timestamp associated with the message, a source address (such as an email address) from which the message was sent, or an IP address or MAC address associated with the device from which the message was sent. Metadata may include data files not visible within the message that contain data associated with the message. For example, metadata may identify the sender of the message, the sender's address, the recipients of the message, the priority of the message, and time data associated with the message.

[0028] The contextual data search engine 118 identifies contextual data 133 associated with the digital message based on the message content and / or metadata associated with the message. For example, the contextual data search engine 118 may search for employment opportunities, resumes, and related documents associated with the employment candidate based on identifying the employment candidate as the sender of the digital message. The proxy mailbox manager 111 may send the contextual information along with the digital message to the recruiter associated with the address 103. According to one or more embodiments, the system uses at least some of the contextual data to perform contextual routing of the message. In other words, the system identifies one or more target addresses for routing the message based on the identified contextual data.

[0029] For example, the contextual data search engine 118 may query a database for hiring manager notes associated with the candidate. The proxy mailbox manager 111 adds the notes to the message before sending the message to the recruiter. The recruiter can then process and / or respond to the candidate's message taking the hiring manager notes into account.

[0030] In one or more embodiments, digital communication management platform 110 refers to hardware and / or software configured to receive digital communications, analyze the content of the digital communications, identify contextual data associated with the digital communications, and perform the operations described herein to generate digital communications. Example operations for managing the transmission of digital messages through proxy mailboxes based on content associated with received messages are described below with reference to Figures 2A, 2B, and 3.

[0031] In one embodiment, the digital communication management platform 110 is implemented on one or more digital devices. The term "digital device" generally refers to any hardware device that includes a processor. A digital device may refer to a physical device or a virtual machine that runs applications. Examples of digital devices include computers, tablets, laptops, desktops, netbooks, servers, web servers, network policy servers, proxy servers, generic machines, specific function hardware devices, hardware routers, hardware switches, hardware firewalls, hardware network address translators (NATs), hardware load balancers, mainframes, televisions, content receivers, set-top boxes, printers, mobile handsets, smartphones, personal digital assistants ("PDAs"), wireless receivers and / or transmitters, base stations, communication management devices, routers, switches, controllers, access points, and / or client devices.

[0032] Additional embodiments and / or examples of computer networks are described below in Section 6 entitled "Computer Networks and Cloud Networks."

[0033] In one or more embodiments, data repository 130 is any type of storage unit and / or device for storing data (e.g., a file system, a database, a collection of tables, or any other storage mechanism). Furthermore, data repository 130 may include multiple different storage units and / or devices. The multiple different storage units and / or devices may or may not be of the same type, or may or may not be located in the same physical location. Furthermore, data repository 130 may be implemented on or execute on the same computing system as digital communication management platform 110. Alternatively, or in addition, data repository 130 may be implemented or execute on a computing system separate from digital communication management platform 110. Data repository 130 may be communicatively coupled to digital communication management platform 110 via a direct connection or via a network.

[0034] The information describing proxy mailbox configuration 131, message metadata 132, and contextual data 133 may be implemented across any of the components in system 100. However, this information is shown in data repository 130 for clarity and illustration.

[0035] In one or more embodiments, a tenant (e.g., client 102 and / or client 104) is a user associated with a company, organization, enterprise, or other entity that has access to a shared computing resource, such as digital communication management platform 110.

[0036] 3. Analysis of digital message content to manage digital message transmission via proxy mailboxes 2A and 2B illustrate an example set of operations for managing digital message transmission to and from a proxy mailbox according to one or more embodiments. One or more of the operations illustrated in FIG. 2A and 2B may be modified, rearranged, or omitted altogether. Thus, the particular sequence of operations illustrated in FIG. 2A and 2B should not be construed as limiting the scope of one or more embodiments.

[0037] The system receives a message from a source address destined for an external address (operation 202). The source address is an address associated with a proxy mailbox. For example, a company may maintain a proxy mailbox. An employee of the company may have access to the proxy mailbox to send messages to addresses outside the company. The source address may be associated with the employee. In one or more embodiments, one proxy mailbox is associated with multiple users. For example, multiple employees may send messages from the same proxy mailbox. In one exemplary embodiment in which the proxy mailbox is managed in a cloud environment, a user may log in from a desktop computer or other computer to a software platform associated with one or more servers in the cloud environment. The platform may provide the user with a graphical user interface (GUI) for creating and / or receiving messages.

[0038] According to one or more embodiments, the received message is from the same domain as the proxy mailbox. For example, a user associated with email address ABC@domain1.xxy may have access to the proxy mailbox proxy@domain1.xxy. Users not associated with an email address that matches the proxy mailbox domain may not have access to the proxy mailbox.

[0039] According to one embodiment, the message is an automatically generated message that is generated without user input. For example, the system may identify three candidates who meet the qualifications for a job posting. The system may generate automated message request information, such as a resume, cover letter, writing sample, or transcript.

[0040] The system determines whether the user has selected address anonymization for the message (operation 204). For example, when the source of the message is the user, the system may provide the user with a GUI that includes selectable radio buttons for showing / hiding the source address. The selectable radio buttons may include options for showing / hiding the source address from all destination addresses or for selectively showing / hiding the source address. For example, the user may select a button to show the source address from other addresses with the same domain and to hide the source address from any addresses outside the domain. The selection to show / hid the source address may be selected by the user when creating the message, or may be stored in a predetermined setting for the system to apply to all messages created within a particular electronic messaging application.

[0041] According to one or more embodiments, the system determines whether to replace a source address with a proxy address by determining that the source address is associated with a permission level that allows a user associated with the source address to access a proxy mailbox. If the source address is not associated with the corresponding permission level, the system may refrain from replacing the source address with a proxy address. According to another example, the system may identify a source application from which the message is received. The system may determine whether to replace the source address with a proxy address based on the source application. For example, if a user generates and sends a message from one type of application, such as an email application in a web browser or an email service associated with an office application suite of applications, the system may refrain from replacing the source address with a proxy address. On the other hand, if a user generates and sends a message using an application or browser plug-in associated with a proxy email platform, the system may replace the source address with a proxy address. According to yet another exemplary embodiment, the system may analyze account configuration settings to determine whether to replace the source address with a proxy address. For example, an account configuration setting may specify that the system should replace the source address with a proxy address when email is directed to an address in one set of addresses, but should not replace the source address with a proxy address when email is directed to any other address. An account configuration setting may specify that the system should replace the source address with a proxy address when a user selects a particular icon in the GUI, but should not replace the source address with a proxy address when the user does not select the icon.

[0042] Based on detecting a selection to anonymize the source address, the system replaces the source address of the digital message with a proxy address (operation 206). For example, if the message is received from address ABC@domain1.xxy, the system replaces the address with proxy address proxy@domain1.xxy. Replacing the address may include generating a new message that includes the proxy address. The new message includes the message content included in the received digital message.

[0043] The system stores the source address data associated with the message (operation 208). For example, if the source address is replaced with a proxy address, the system may store the source address as metadata in a digital file attached to the message. The metadata does not appear in the address line of the message or in the content of the message.

[0044] According to one embodiment, the system includes an automatic digital message generator. For example, the system may automatically generate messages to notify job applicants of the next step in an interview process, to notify business or sales prospects of an event or sales opportunity, and to notify customers of an event. The automatic digital message generator may not have a designated address. Upon receiving a digital message from the automatic digital message generator, the system assigns a proxy address to the digital message. The system may further identify a source address to be associated with the digital message. For example, the automatic digital message generator may generate a reminder message for a client associated with a particular account. The system may identify the source address associated with the account and store the source address as metadata in the generated digital message, which includes the proxy address as the source address in the digital message.

[0045] The system determines whether source name anonymization is selected (operation 210). For example, a recruiter may send an initial message to a prospect from a proxy email address. However, the recruiter may choose to keep their name in the email header to add a personal element to the message. Alternatively, a user may choose to omit their name from the message. For example, a customer support team may be assisting a particular customer. Members of the team may send messages without identifying themselves as senders.

[0046] Based on a determination that the user has selected source name anonymization, the system omits the user's name from the message (operation 212). For example, the system may include only an email address in the "from" portion of the message. According to one embodiment, the system may remove the username from the signature portion. For example, the system may detect whether the user has configured their email account to automatically include the user's name in a "signature" with every message. Based on detecting the user's selection to anonymize the source name, the system may omit the user's name from the address portion of the message and remove the username from the signature portion of the message.

[0047] Based on a determination that the user refrained from selecting source name anonymization, the system includes the user's name in the message (operation 214). For example, the system may include the user's name associated with the proxy email address, such as "John Johnson@proxyaddress1.xyz."

[0048] The system sends the message to the external address with the proxy address displayed as the source address of the message (operation 216). In one example where the digital message is an email address, the system lists the proxy address in the "from:" field and the external address in the "to:" field. The system refrains from displaying the original source address.

[0049] The system receives a message from an external address that is addressed to the proxy address (operation 218).

[0050] The system analyzes the received message to perform contextual routing for the message (operation 220). In particular, the system identifies contextual data that informs the system to which one or more target addresses the system should route the message. The target address is an address that is different from the proxy address. In particular, when multiple users associated with multiple different digital message addresses have access to a proxy mailbox, the system analyzes the received message to identify a specific target address from among the multiple different digital message addresses to which the system attempts to send the message. According to one embodiment, the system identifies the message as a reply to a message sent from a proxy address. The system may analyze stored metadata associated with a reply to the message to identify the target address. According to another exemplary embodiment, the system analyzes metadata sent with the message to identify the target address. According to yet another embodiment, the system analyzes message content, such as an item ID number included in the message content, to identify the target address. For example, the subject of the message may include the text "Re:Matter:ZZXX11 Employment Opportunity." The system may identify entry ZZXX11 as being associated with two target addresses, ABC@domain1.xxy and DEF@domain1.xxy.

[0051] The system generates a message directed to the target address that includes the message content of the received message (operation 222). For example, if a message directed to the address "recruiting@domain1.xxy" includes the text "I'm interested in this opportunity!", the system generates a message directed to the target address ABC@domain1.xxy that includes the text "I'm interested in this opportunity!".

[0052] According to one or more embodiments, the system identifies contextual data associated with a message. For example, the system may identify a user associated with the external address based on the external address ggpyz@domain3.xxy. The system may identify documents previously submitted by the user, such as a resume, employment cover letter, or application. The system may identify employee-generated data, such as a customer support ticket, qualification or interview notes, or any other employee-generated data stored in association with the user. The system may include the contextual data with the generated message. For example, the system may include the document as an attachment attached to the message. Additionally or alternatively, the system may include a hyperlink in the content of the message that directs the employee to contextual data, such as a previously submitted application.

[0053] According to one embodiment, the system replaces the external address with the proxy address in messages to the target address (operation 224). For example, an employee accessing an electronic mailbox associated with the address ABC@domain1.xxy will see a message from the proxy address recruiting@domain1.xxy.

[0054] The system may modify the contents of the message to include identifying information associated with the external address (operation 226). The identifying information may include, for example, the external email address, the name of the user associated with the external email address, and matters associated with the user. According to one exemplary embodiment, when an employee replies to a message, such as by selecting a "Reply" messaging function, the system may identify the external address associated with the message even if the address in the "from:" field of the digital message is a proxy address. In other words, both employees and external users may reply to a message from a proxy address. The system generates a substitute message in each case directed to the specific target address (e.g., the employee address or the address associated with the external user).

[0055] According to one or more embodiments, the system includes a file or link to data associated with the external email address. For example, when a job applicant responds to a message, the system may modify the response to include a link to the applicant's profile associated with the external address. Additionally or alternatively, the system may attach a data file to the message, such as a resume in the case of a job applicant, before sending the message to the target user.

[0056] 2B, dashed lines associated with operations 224 and 226 indicate that particular operations may alternatively not be performed by the system. In particular, according to an alternative embodiment, the system may generate a message to the target address while leaving the external address in the "from:" field of the message.

[0057] Having generated at least one message destined for the target address, the system sends the message to the target address (operation 228).

[0058] As illustrated in Figures 2A and 2B, the system manages digital messages sent to and from a proxy mailbox. The system replaces the source address of the outgoing message with the proxy address. An external user receiving the message sees the message from the proxy address instead of the specific user's address. The system analyzes the message received at the proxy mailbox to generate a message to a target address associated with the specific user. The system further identifies contextual data associated with the external user based on the digital message data included in the received message and provides the data to an internal user associated with the target address.

[0059] 4. Analysis of digital messages to proxy mailboxes to identify multiple recipients 3 illustrates an exemplary set of operations for identifying a recipient for a digital message to a proxy mailbox according to one or more embodiments. One or more of the operations illustrated in FIG. 3 may be modified, rearranged, or omitted all together. Thus, the particular sequence of operations illustrated in FIG. 2 should not be construed as limiting the scope of one or more embodiments.

[0060] The system receives a first message from a source address (operation 302). The message is directed to a first destination address and a second destination address. For example, a user within a company (an "internal user") may generate an email to an external user and carbon copy (cc) another employee of the company in the message.

[0061] The system generates a second message from the proxy address to at least the first destination address containing the content of the original message (operation 304). For example, as described above with respect to FIG. 2A, when a message is received from the address ABC@domain1.xxy, the system replaces the address with the proxy address proxy@domain1.xxy. According to one embodiment, the system replaces the source address with the proxy address in messages to both the first and second destination addresses. According to one or more alternative embodiments, the system may determine, for each destination address associated with the digital message, whether to replace the source address with the proxy address. For example, the system may analyze the domains of multiple destination addresses associated with the digital message. If one domain is the same as the source address, the system may refrain from replacing the source address with the proxy address. In other words, if the destination address is within the same organization (and therefore has the same domain) as the sending address, the system does not replace the sending address with the proxy address. If the domain of the destination address is different from the domain of the source address, the system replaces the source address with the proxy address. Thus, any address outside the particular organization may see the proxy address instead of the employee's personal address. In the exemplary embodiment shown in Figure 3, the system determines that the second message should be addressed to both the first and second destination addresses.

[0062] The system sends the second message to the first and second destination addresses (operation 306).

[0063] The system receives a third message from the first destination address directed to the proxy address (operation 308). As described above with respect to Figure 2A, the message may be a reply to the message sent from the proxy address.

[0064] The system analyzes the third message to perform contextual routing for the third message (operation 310). As described above with respect to FIG. 2B, the system may analyze content within the message text, content within the subject field of the message, and / or metadata associated with the message to determine to which target address to route the third message.

[0065] In the exemplary embodiment shown in Figure 3, the system determines that the third message is a reply to the second message. The system further determines that the second message corresponds to the first message addressed to the first destination address and the second destination address.

[0066] Therefore, the system generates a fourth message directed to the source address, operation 312. In the fourth message, the system includes the contents of the third message.

[0067] The system further determines that the third message does not include the second destination address as a destination address for the third message. Based on the determination that (a) the third message is associated with the first message and (b) the third message does not include the second address as a destination address, the system determines whether to include the second destination address as a destination for the fourth message.

[0068] The system may apply specific rules to determine whether to include a second destination address as a destination for the fourth message. According to one embodiment, the rules may specify that if a second message includes both (a) the first destination address and (b) the second destination address in the "to:" or "cc:" field, any response from the first destination address be sent to the second destination address, even if the response does not include the second destination address among the destination addresses of the message. According to another embodiment, the rules may specify that any message directed from a proxy address to a source address must also be sent to the second destination address. Alternatively, the rules may specify that a message directed to a proxy address that does not include the second destination address will not be sent to the second destination address, even if the message is a reply to an initial message that included the second destination address as a destination for the message. According to one exemplary embodiment, rules for determining whether to send a "reply" type message to additional addresses in addition to the initial address may be configured by a user and stored by the system.

[0069] According to one or more embodiments, in addition to identifying users who were included in the initial outbound message, the system may identify users who may contribute to the conversation and / or identify users that the system determines should be replicated in the conversation based on inclusion criteria. For example, a rule may implement contextual routing of messages to a particular address by specifying that any message containing the item ID "ZZYY11" should be sent to the particular address along with any other identified messages.

[0070] 3, the system applies a rule that specifies that if the second message includes both (a) the first destination address and (b) the second destination address in the "to:" or "cc:" fields, any response from the first destination address is sent to the second destination address, even if the response does not include the second destination address among the destination addresses of the message. Thus, when generating the fourth message in operation 312, the system includes the second destination address as a destination for the fourth message.

[0071] The system sends a fourth message to the source address and the second destination address (operation 314).

[0072] 5. Exemplary Embodiments Detailed examples are described below for clarity. The components and / or operations described below should be understood as specific examples that may not be applicable to certain embodiments. Therefore, the components and / or operations described below should not be construed as limiting the scope of any of the claims.

[0073] FIG. 4 illustrates a recruiting platform 402 that utilizes an email manager 404 to send and receive emails. The recruiting application sends an email to a candidate (operation 408). The recruiting application includes an email generator that generates automated emails associated with employment opportunities that match the candidate's qualifications. The automated email generator generates the email. The email manager 404 assigns a proxy email address, "careers@vision.xyz," as the source email address for the email (operation 410). According to the exemplary embodiment illustrated in FIG. 4, the email generator accesses pre-stored messages to be sent to candidates without requiring a recruiter to enter message content. For example, a recruiter may be presented with an interface containing a set of applicants who appear to meet the preliminary qualifications for a particular job posting. The recruiter may select three applicants. The email generator automatically generates messages to send to the three applicants, without further recruiter input, and requests additional information from the applicants to advance to the next stage of the interview process. As another example, the email generator may match the requirements of a newly posted job to applicant profiles stored in the recruiting platform. Based on detecting a potential match, the email generator generates an email to potential candidates informing them of the job posting and providing a link whereby the potential candidates can apply to the job posting.

[0074] In addition to the automatic email generator, recruiters can use the recruiting platform 402 to generate emails. The email manager 404 replaces the source email address from the sender's email address to a proxy email address (e.g., from "John Johnson@vision.xyz" to "careers@vision.xyz").

[0075] The candidate 406 replies to the email from the recruitment application (operation 412). Because the candidate's email is a reply type email, the email is directed to the proxy mailbox "careers@vision.xyz."

[0076] The email manager 404 receives the reply message and uses contextual information associated with the reply message to identify the recruiter associated with the reply message (operation 414). For example, a recruiting firm may have three recruiters. Each recruiter may be associated with a particular job opportunity and / or a particular candidate. The system analyzes message data, such as content within the email or metadata associated with the email, to identify the particular recruiter. The content may include a job posting number associated with the particular recruiter, an applicant name associated with the particular recruiter, or a message identification (ID) number associated with the source message to which the candidate 406 is replying. The system sends the reply message to the email inbox of the particular recruiter (operation 416).

[0077] The system also identifies contextual data associated with the candidate and / or employment opportunities the candidate has expressed an interest in. For example, the system may include in the email to the recruiter a resume and a list of previous and / or pending employment opportunities to which the candidate has applied.

[0078] The recruiter responds to the candidate's reply email (operation 418). For example, the recruiter may request an updated resume, cover letter, or work product to complete an application for a job opportunity. The system receives the email generated by the recruiter. Based on predetermined settings, the system sends the recruiter's email message to the candidate without changing the sender email to a proxy address and without removing the recruiter's name from the email (operation 420). For example, the system may detect the recruiter's selection of a radio icon in a graphical user interface for generating email messages, indicating that the recruiter wants their email address to remain visible to the candidate 406. Additionally, or alternatively, the system may apply predetermined rules that specify when to or not to replace the recruiter's email address with a proxy email address. A rule may specify that the system should not replace the recruiter's email address with a proxy email address when the recruiter is replying to a candidate's email.

[0079] 6. Computer Networks and Cloud Networks In one or more embodiments, a computer network provides connectivity among a set of nodes. The nodes may be local and / or remote from one another. The nodes are connected by a set of links. Examples of links include coaxial cable, unshielded twisted cable, copper cable, optical fiber, and virtual links.

[0080] A subset of nodes implements computer networks. Examples of such nodes include switches, routers, firewalls, and network address translators (NATs). Another subset of nodes uses computer networks. Such nodes (also called "hosts") may run client processes and / or server processes. A client process makes a request for a computing service (such as running a particular application and / or storing a particular amount of data). A server process responds by performing the requested service and / or returning corresponding data.

[0081] A computer network may be a physical network including physical nodes connected by physical links. A physical node is any digital device. A physical node may be a specific function hardware device, such as a hardware switch, a hardware router, a hardware firewall, and a hardware NAT. Additionally or alternatively, a physical node may be a generic machine configured to run various virtual machines and / or applications that perform respective functions. A physical link is a physical medium connecting two or more physical nodes. Examples of links include coaxial cable, unshielded twisted cable, copper cable, and optical fiber.

[0082] A computer network may be an overlay network. An overlay network is a logical network implemented on top of another network (e.g., a physical network). Each node in the overlay network corresponds to a respective node in the underlying network. Thus, each node in the overlay network is associated with both an overlay address (for addressing the overlay node) and an underlay address (for addressing the underlay node that implements the overlay node). An overlay node may be a digital device and / or a software process (e.g., a virtual machine, an application instance, or a thread). The links connecting overlay nodes are implemented as tunnels through the underlay network. The overlay nodes at each end of the tunnel treat the underlay multi-hop path between them as a single logical link. Tunneling is performed by encapsulation and decapsulation.

[0083] In some embodiments, a client may be local to and / or remote from a computer network. A client may access a computer network over a private network or another computer network, such as the Internet. A client may communicate a request to a computer network using a communication protocol, such as Hypertext Transfer Protocol (HTTP). The request is communicated through an interface, such as a client interface (e.g., a web browser), a program interface, or an application programming interface (API).

[0084] In one embodiment, a computer network provides connectivity between clients and network resources. The network resources include hardware and / or software configured to run server processes. Examples of network resources include processors, data storage, virtual machines, containers, and / or software applications. The network resources are shared among multiple clients. The clients request computing services from the computer network independently of one another. The network resources are dynamically allocated to requests and / or clients on an on-demand basis. The network resources allocated to each request and / or client may be scaled up or down based on, for example, (a) the computing services requested by a particular client, (b) the aggregated computing services requested by a particular tenant, and / or (c) the aggregated computing services requested from the computer network. Such a computer network may be referred to as a "cloud network."

[0085] In one embodiment, a service provider offers a cloud network to one or more end users. Various service models can be implemented by the cloud network, including, but not limited to, Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), and Infrastructure-as-a-Service (IaaS). In SaaS, the service provider offers end users the ability to use the service provider's applications running on the network resources. In PaaS, the service provider offers end users the ability to deploy custom applications on the network resources. The custom applications can be created using programming languages, libraries, services, and tools supported by the service provider. In IaaS, the service provider offers end users the ability to configure the processing, storage, network, and other basic computing resources provided by the network resources. Any arbitrary application, including an operating system, can be deployed on the network resources.

[0086] In some embodiments, a computer network may implement various deployment models, including, but not limited to, private clouds, public clouds, and hybrid clouds. In a private cloud, network resources are configured for exclusive use by a specific group of one or more entities (the term "entity" as used herein refers to a company, organization, person, or other entity). The network resources may be local to and / or remote from the facilities of the specific group of entities. In a public cloud, cloud resources are configured for multiple entities (also called "tenants" or "customers") that are independent of each other. The computer network and its network resources are accessed by clients corresponding to different tenants. Such a computer network may be referred to as a "multi-tenant computer network." Several tenants may use the same specific network resources at different times and / or the same time. The network resources may be local to and / or remote from the tenant's facilities. In a hybrid cloud, the computer network includes a private cloud and a public cloud. An interface between the private cloud and the public cloud enables data and application portability. Data stored in the private cloud and data stored in the public cloud may be exchanged through the interface. Applications implemented in the private cloud and applications implemented in the public cloud may have dependencies on each other, and calls from applications in the private cloud to applications in the public cloud (and vice versa) may be made through interfaces.

[0087] In some embodiments, tenants of a multi-tenant computer network are independent of one another. For example, the business or operations of one tenant may be separate from the business or operations of another tenant. Different tenants require different network requirements for the computer network. Examples of network requirements include processing speed, amount of data storage, security requirements, performance requirements, throughput requirements, latency requirements, resilience requirements, Quality of Service (QoS) requirements, tenant isolation, and / or consistency. The same computer network may need to implement different network requirements required by different tenants.

[0088] In one or more embodiments, in a multi-tenant computer network, tenant isolation may be implemented to ensure that applications and / or data of different tenants are not shared with each other. Various tenant isolation approaches may be used.

[0089] In one embodiment, each tenant is associated with a tenant ID. Each network resource in a multi-tenant computer network is tagged with a tenant ID. A tenant is granted access to a particular network resource only if the tenant and the particular network resource are associated with the same tenant ID.

[0090] In one embodiment, each tenant is associated with a tenant ID. Each application implemented by the computer network is tagged with a tenant ID. Additionally or alternatively, each data structure and / or dataset stored by the computer network is tagged with a tenant ID. A tenant is granted access to a particular application, data structure, and / or dataset only if the tenant and the particular application, data structure, and / or dataset are associated with the same tenant ID.

[0091] As one example, each database implemented by a multi-tenant computer network may be tagged with a tenant ID. Only the tenant associated with the corresponding tenant ID may access the data in a particular database. As another example, each entry in a database implemented by a multi-tenant computer network may be tagged with a tenant ID. Only the tenant associated with the corresponding tenant ID may access the data in a particular entry. However, a database may be shared by multiple tenants.

[0092] In one embodiment, the subscription list indicates which tenants are authorized to access which applications. For each application, a list of tenant IDs of tenants authorized to access the application is stored. A tenant is granted access to a particular application only if the tenant's tenant ID is included in the subscription list corresponding to the particular application.

[0093] In one embodiment, network resources (such as digital devices, virtual machines, application instances, and threads) corresponding to different tenants are isolated in tenant-specific overlay networks maintained by a multi-tenant computer network. As an example, packets from any source device in a tenant overlay network can be transmitted only to other devices within the same tenant overlay network. An encapsulation tunnel is used to prevent any transmission from a source device in a tenant overlay network to a device in another tenant overlay network. In particular, a packet received from a source device is encapsulated within an outer packet. The outer packet is transmitted from a first encapsulation tunnel endpoint (communicating with a source device in the tenant overlay network) to a second encapsulation tunnel endpoint (communicating with a destination device in the tenant overlay network). The second encapsulation tunnel endpoint decapsulates the outer packet to obtain the original packet transmitted by the source device. The original packet is transmitted from the second encapsulation tunnel endpoint to a destination device in the same specific overlay network.

[0094] 7. Miscellaneous, Extensions Embodiments are directed to systems having one or more devices that include a hardware processor and are configured to perform any of the operations described herein and / or recited in any of the claims below.

[0095] In an embodiment, a non-transitory computer-readable storage medium includes instructions that, when executed by one or more hardware processors, result in the performance of any of the operations described herein and / or recited in any of the claims.

[0096] Any combination of the features and functions described herein may be used in accordance with one or more embodiments. In the foregoing specification, the embodiments are described with reference to numerous specific details that may vary from implementation to implementation. Accordingly, the specification and drawings should be regarded in an illustrative rather than a restrictive sense. The only exclusive indicator of the scope of the invention, and what is intended by the applicant to be the scope of the invention, is the literal equivalent range of the set of claims issuing from this specification, in the specific form in which such claims issue, including any subsequent amendments.

[0097] 8. Hardware Overview According to one embodiment, the techniques described herein for managing the transmission of digital messages via a proxy mailbox are implemented by one or more special-purpose computing devices. The special-purpose computing devices may be hardwired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or network processing units (NPUs) persistently programmed to perform the techniques, or may include one or more general-purpose hardware processors programmed to perform the techniques according to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices may combine custom hardwired logic, ASICs, FPGAs, or NPUs with custom programming to achieve the techniques. The special-purpose computing devices may be desktop computer systems, portable computer systems, handheld devices, networking devices, or any other devices incorporating hardwired and / or program logic to implement the techniques.

[0098] 5 is a block diagram illustrating a computer system 500 in which an embodiment of the present invention may be implemented. Computer system 500 includes a bus 502 or other communication mechanism for communicating information, and a hardware processor 504 coupled with bus 502 for processing information. Hardware processor 504 may be, for example, a general-purpose microprocessor.

[0099] Computer system 500 also includes a main memory 506, such as a random access memory (RAM) or other dynamic storage device, coupled to bus 502 for storing information and instructions executed by processor 504. Main memory 506 may also be used for storing temporary variables or other intermediate information during execution of instructions executed by processor 504. Such instructions, when stored on a non-transitory storage medium accessible to processor 504, render computer system 500 a special-purpose machine customized to perform the operations specified in the instructions.

[0100] Computer system 500 further includes a read-only memory (ROM) 508 or other static storage device coupled to bus 502 for storing static information and instructions for processor 504. A storage device 510, such as a magnetic disk or optical disk, is provided and coupled to bus 502 for storing information and instructions.

[0101] Computer system 500 may be coupled via bus 502 to a display 512, such as a cathode ray tube (CRT), for displaying information to a computer user. An input device 514, including alphanumeric and other keys, is coupled to bus 502 for communicating information and command selections to processor 504. Another type of user input device is a cursor control 516, such as a mouse, trackball, or cursor direction keys, for communicating directional information and command selections to processor 504 and for controlling cursor movement on display 512. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify a position in a plane.

[0102] Computer system 500 may implement the techniques described herein using customized hardwired logic, one or more ASICs or FPGAs, firmware, and / or program logic that, in combination with the computer system, makes or programs computer system 500 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 500 in response to processor 504 executing one or more sequences of one or more instructions contained in main memory 506. Such instructions may be read into main memory 506 from another storage medium, such as storage device 510. Execution of the sequences of instructions contained in main memory 506 causes processor 504 to perform the process steps described herein. In alternative embodiments, hardwired circuitry may be used in place of or in combination with software instructions.

[0103] The term "storage medium" as used herein refers to any non-transitory medium that stores data and / or instructions that cause a machine to operate in a specific manner. Such storage media may include non-volatile media and / or volatile media. Non-volatile media include, for example, optical or magnetic disks, such as storage device 510. Volatile media include dynamic memory, such as main memory 506. Common forms of storage media include, for example, floppy disks, flexible disks, hard disks, solid-state drives, magnetic tape, or any other magnetic data storage medium, CD-ROMs, any other optical data storage medium, any physical medium with a pattern of holes, RAM, PROM, and EPROM, flash EPROM, NVRAM, any other memory chip or cartridge, content addressable memory (CAM), and ternary content addressable memory (TCAM).

[0104] Storage media is distinct from but may be used in conjunction with transmission media. Transmission media involves transmitting information between storage media. For example, transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise bus 502. Transmission media can also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.

[0105] Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 504 for execution. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer may load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 500 may receive the data on the telephone line and use an infrared transmitter to convert the data to an infrared signal. An infrared detector can receive the data carried in the infrared signal and appropriate circuitry can place the data on bus 502. Bus 502 carries the data to main memory 506, from which processor 504 retrieves and executes the instructions. The instructions received by main memory 506 may optionally be stored on storage device 510 either before or after execution by processor 504.

[0106] Computer system 500 also includes a communication interface 518 coupled to bus 502. The communication interface 518 provides a two-way data communication coupling to a network link 520 that is connected to a local network 522. For example, communication interface 518 may be an Integrated Services Digital Network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 518 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, communication interface 518 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0107] Network link 520 typically provides data communication through one or more networks to other data devices. For example, network link 520 may provide a connection through local network 522 to a host computer 524 or to data equipment operated by an Internet Service Provider (ISP) 526. ISP 526 in turn provides data communication services through the world-wide packet data communication network now commonly referred to as the "Internet" 528. Local network 522 and Internet 528 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 520 and through communication interface 518, which carry the digital data to and from computer system 500, are exemplary forms of transmission media.

[0108] Computer system 500 can send messages and receive data, including program code, through the network(s), network link 520 and communication interface 518. In the Internet example, a server 530 might transmit a requested code for an application program through Internet 528, ISP 526, local network 522 and communication interface 518.

[0109] The received code may be executed by processor 504 as it is received, and / or stored in storage device 510, or other non-volatile storage for later execution.

[0110] In the foregoing specification, embodiments of the invention have been described with reference to numerous specific details that may vary from implementation to implementation. Accordingly, the specification and drawings should be regarded in an illustrative rather than a restrictive sense. The sole and exclusive indicator of the scope of the invention, and what is intended by the applicant to be the scope of the invention, is the literal equivalent range of the set of claims issuing from this specification in the specific form in which such claims issue, including any subsequent amendments.

Claims

1. A non-transitory computer-readable medium containing instructions that, when executed by one or more hardware processors, cause the performance of operations, said operations including: The digital message management application includes receiving a first message from a first address directed to a second address, the first message including message content, the operation comprising: The digital message management application generates a second message including the message content of the first message, the second message identifying (a) a proxy address as a source address of the second message, the proxy address being associated with a plurality of source addresses, and (b) the second address as a destination address of the second message, the operation comprising: the digital message management application sending the second message from the proxy address to the second address; receiving, by the digital message management application, from the second address, a third message corresponding to a response to the second message, the third message being directed to the proxy address; analyzing the third message by the digital message management application to identify a correlation between the third message and the first address; the digital message management application generating a fourth message including the message content of the third message, the fourth message identifying the first address as a destination address of the fourth message, the operations comprising: The non-transitory computer-readable medium includes the digital message management application sending the fourth message to the first address.

2. The operation (a) identifying a user corresponding to the second address and / or (b) identifying contextual information corresponding to either the third message; sending the context information with the fourth message to the first address; The non-transitory computer-readable medium of claim 1 , further comprising:

3. The context information is User profile, Employment data associated with the user; and a previous communication between the first address and the second address; 3. The non-transitory computer-readable medium of claim 2, comprising at least one of:

4. The digital message management application generating the second message comprises: replacing the second address with the proxy address as the destination address of the second message; storing metadata in the second message; 2. The non-transitory computer-readable medium of claim 1, wherein the metadata identifies a first address as a source of the first message.

5. The non-transitory computer-readable medium of claim 1 , wherein the first, second, third, and fourth messages are electronic mail (email) messages.

6. 2. The non-transitory computer-readable medium of claim 1, wherein analyzing the third message to identify the correlation between the third message and the first address comprises analyzing metadata in the third message, the metadata including information identifying the first address.

7. generating the fourth message includes: assigning the proxy address as the source address of the fourth message; modifying the content of the third message to include identification information associated with the second address; 10. The non-transitory computer-readable medium of claim 1, comprising:

8. The operation receiving, by the digital message management application, a fifth message from the second address directed to the proxy address; analyzing the fifth message to identify a correlation between the fifth message and the first address; in response to determining that the fifth message does not satisfy a forwarding criterion for forwarding the fifth message to the first address; refraining from forwarding the fifth message to the first address; The non-transitory computer-readable medium of claim 1 , further comprising:

9. The operation The digital message management application may further include receiving a fifth message from a third address directed to the second address, the fifth message including fifth message content, the operation comprising: The digital message management application further includes generating a sixth message including the fifth message content of the fifth message, the sixth message identifying (a) the proxy address as the source address of the sixth message, and (b) the second address as the destination address of the sixth message, the operation further comprising:

10. The non-transitory computer-readable medium of claim 1, further comprising the digital message management application sending the sixth message from the proxy address to the second address.

10. The operation The digital message management application may further include receiving a seventh message from the second address corresponding to a response to the sixth message, the seventh message being directed to the proxy address, the seventh message including seventh message content, and the operation further comprising: analyzing the seventh message by the digital message management application to identify a correlation between the seventh message and the third address; the digital message management application generating an eighth message including the seventh message content of the seventh message, the eighth message identifying the third address as the destination address of the eighth message, the operations further comprising:

10. The non-transitory computer-readable medium of claim 9, further comprising the digital message management application sending the eighth message to the third address.

11. A non-transitory computer-readable medium containing instructions that, when executed by one or more hardware processors, cause the performance of operations, said operations including: A digital message management application includes receiving a first message from a first address, the first message being directed to a second address and a third address, the first message including first message content, the operations including: The digital message management application includes generating a second message including the first message content, the second message (a) identifying a proxy address as a source address of the second message, the proxy address being associated with a plurality of source addresses, and (b) identifying the second address as a destination address of the second message, the operation comprising: the digital message management application sending the second message from the proxy address to the second address; receiving, by the digital message management application, from the second address, a third message corresponding to a response to the second message, the third message being directed to the proxy address; analyzing the third message to identify a correlation between the third message and the first and third addresses; In response to (a) identifying a correlation between the second message and the first and third addresses, and (b) determining that the second message does not include the third address as a destination address, adding the third address as a destination for the second message; the digital message management application sending the second message to the first address and the third address; 1. A non-transitory computer-readable medium comprising:

12. 16. The non-transitory computer-readable medium of claim 15, wherein the second message further identifies the third address as a destination address of the second message.

13. 16. The non-transitory computer-readable medium of claim 15, wherein the digital message management application sends the second message from the proxy address to the second address and the third address.

14. The operation analyzing a set of addresses associated with the source address; 16. The non-transitory computer-readable medium of claim 15, wherein based on a determination that the second destination address is within a set of addresses associated with the source address, the second destination address is added as a destination for the second message.

15. A method comprising the operations of any one of claims 1 to 14.

16. A system including at least one device including a hardware processor, said system configured to perform the operations of any one of claims 1 to 14.

17. A system comprising means for performing the operations of any one of claims 1 to 14.

Images