US20130339462A1 - Pre-Send Evaluation of E-Mail Communications - Google Patents
Pre-Send Evaluation of E-Mail Communications Download PDFInfo
- Publication number
- US20130339462A1 US20130339462A1 US13/971,109 US201313971109A US2013339462A1 US 20130339462 A1 US20130339462 A1 US 20130339462A1 US 201313971109 A US201313971109 A US 201313971109A US 2013339462 A1 US2013339462 A1 US 2013339462A1
- Authority
- US
- United States
- Prior art keywords
- mail message
- recipient
- response
- distribution list
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000004891 communication Methods 0.000 title claims abstract description 16
- 238000011156 evaluation Methods 0.000 title description 3
- 230000004044 response Effects 0.000 claims description 37
- 230000008520 organization Effects 0.000 claims description 18
- 238000000034 method Methods 0.000 claims description 17
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 claims 3
- 229910052799 carbon Inorganic materials 0.000 claims 3
- JLYFCTQDENRSOL-VIFPVBQESA-N dimethenamid-P Chemical compound COC[C@H](C)N(C(=O)CCl)C=1C(C)=CSC=1C JLYFCTQDENRSOL-VIFPVBQESA-N 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 4
- 238000013500 data storage Methods 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 239000000344 soap Substances 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 241000699670 Mus sp. Species 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/60—Business processes related to postal services
-
- H04L51/12—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/212—Monitoring or handling of messages using filtering or selective blocking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
Definitions
- an e-mail message Due to the asynchronous nature of e-mail systems, it is possible for an e-mail message to not be successfully delivered to the intended recipient.
- the unsuccessful delivery of an e-mail message can occur for many reasons. For example, the e-mail message may be too large for the recipient's mailbox, or the recipient's mailbox may be full.
- embarrassing and costly mistakes can be made when composing e-mail messages.
- a private e-mail may be inadvertently sent to a large audience, or confidential material may be inadvertently sent to external recipients.
- the present disclosure relates to a systems and methods for validating the content of an e-mail message during the composition of the message and alerting a user of attributes associated with the message before the e-mail message is sent.
- the server receives notification when certain compose events occur.
- This notification is presented to the user.
- the notification can take the form of a mail tip which alerts to user to attributes associated with the message.
- FIG. 1 is an illustration of an example e-mail communication system.
- FIG. 2 is an illustration of an example banner for a mailbox full event.
- FIG. 3 is an illustration of an example banner for a recipient who is out-of-office.
- FIG. 4 is an illustration of example client interfaces.
- FIG. 5 is an illustration of example modules of an e-mail server.
- FIG. 6 is an illustration of example communication between example client interfaces and example modules of an e-mail server.
- FIG. 7 is an illustration of example information sources in an e-mail system.
- FIG. 8 is an illustration of an example flowchart for a server to validate the content of an e-mail message during the composition of the message.
- FIG. 9 is an illustration of an example flowchart for a client receiving validation of the content of an e-mail message during the composition of the message.
- the present application is directed to systems and methods for validating the content of an e-mail message during the composition of the message, before the message is sent to its intended recipients.
- FIG. 1 shows an example system 100 for validating the content of an e-mail message.
- the system includes one or more client devices 110 , a central-access e-mail server 120 , and information sources 130 .
- a client device 110 may be a desktop device such as a personal computer or a mobile device such as a personal digital assistant.
- the client device 110 is a computer system, such as a desktop computer, laptop computer, personal data assistant, or cellular device.
- the client 110 can include input/output devices, a central processing unit (“CPU”), a data storage device, and a network device.
- CPU central processing unit
- Typical input/output devices include keyboards, mice, displays, microphones, speakers, disk drives, CD-ROM drives, and flash drives.
- Computer readable media, such as the data storage device provide for data retention.
- computer readable media can include computer storage media and communication media.
- Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
- Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- client operating system is a program that manages the hardware and software resources of the client system.
- the client applications utilize the resources of the client 110 to directly perform tasks specified by the user.
- the network device enables the client 110 to send and receive data to/from the server 102 . Other configurations for the client 110 are possible.
- the central-access e-mail server 120 also known as a front-end server, provides an interface for the client devices 110 .
- the central-access email server 120 is a server configured to handle e-mail sent to and from users.
- the email server 120 is a Microsoft Exchange Server provided by Microsoft Corporation of Redmond, Wash. Other configurations are possible.
- the information sources 130 provide a back-end interface to the e-mail server 120 and contain one or more databases.
- One or more of the information sources 130 are contained within the system 100 . Examples of such databases include recipient mailbox stores, and address services such as an ACTIVE DIRECTORY® directory service from Microsoft Corporation. Other configurations are possible.
- E-mail messages are composed on a client device 110 .
- the client device 110 first establishes a session with the server 120 and communicates with the server. For example, the client may send the server information about its locale or language used. The client also receives information from the server, such as restrictions that may exist for the sender of the message. For example, the client may receive the sender's maximum message size.
- recipients are added to the To, CC, and BCC fields of the message.
- Recipients are added to the message by adding the recipient names individually or by including one or more distribution lists. Text, graphics, attachments, and other content are added to the body of the message.
- the adding of recipients is referred to as an e-mail compose event.
- the e-mail compose event generates communication with the server 120 .
- the server 120 is programmed to perform one or more checks based on the recipient or distribution list, as described further below. For example, the server 120 can check to see if the recipient has created an out of office notification, or can check to see how many users are defined for a particular distribution list.
- the central-access e-mail server 120 When the central-access e-mail server 120 receives an e-mail compose event, it accesses information sources 130 and validates the message content.
- Information obtained from information sources 130 regarding each recipient can include one of more of the following: (1) whether the recipient is internal or external to the organization, (2) whether the recipient is in or out of the office (e.g., whether or not the recipient has set an out of office indicator), (3) whether the recipient's mailbox is full, (4) whether the recipient has restricted access (see below), (5) whether the maximum number of recipients is exceeded, and (6) whether there is a custom mail tip for the recipient (i.e., a mail tip containing information specific to the recipient, such as “This mailbox is not monitored.” and “Please allow up to 48 hours for a response.”
- the e-mail address of the recipient is also checked to ensure that it is a valid SMTP address and to determine if it belongs to a recipient inside or outside the sender's organization. Furthermore, the e-mail address can be checked to determine if the address is within the scope of the sender's organization but does not belong to a recipient in the organization's directory. For example, this could occur if the sender misspelled the recipient's address or if the address belonged to a recipient who has departed the organization.
- configuration properties of individual mailboxes or of groups can specify restrictions as to access. For example, one can specify particular people or groups from which e-mail messages can be received.
- server 120 a set of attachment types that may or may not be sent in an e-mail message.
- the e-mail system can be configured so that executable code (having .exe extensions) or source code files may not be sent in an e-mail message.
- executable code having .exe extensions
- source code files may not be sent in an e-mail message.
- Information obtained from information sources 130 regarding a distribution list can include one or more of the following: (1) whether the distribution list is too large, (2) whether the distribution list has restricted access, (3) whether the distribution list is moderated (i.e. whether someone would receive the e-mail message and either approve or reject before forwarding to a larger group), and (4) whether there is a custom mail tip for the distribution list (i.e., a mail tip containing information specific to the distribution list).
- Information obtained from information sources 130 regarding the content of the message can include one or more of the following: (1) whether the message size is within administrator-defined parameters, (2) whether there any attachments included with the message that have restricted access, and (3) whether the message contains a reply-all response from a BCC recipient (i.e., whether a user who received the message as a result of being on the BCC line clicked Reply-All to the message).
- the central-access e-mail server 120 evaluates the information obtained from information sources 130 and determines whether there are any attributes of the e-mail message that should trigger a notification to the user. If the server 120 determines that the user should be notified, the server 120 sends a response to a client device 110 to alert the user of the status. The user can then take appropriate action.
- the user can delete the recipient's name from the message before sending the e-mail message.
- certain attribute evaluation tasks such as whether a recipient's mailbox is full or whether the recipient is out of the office, can typically only be done for recipients that are within the organization.
- the client when the user adds text to the body of the message, the client is programmed to check the text for compliance with corporate policy.
- the client retrieves a list of disallowed terms from the server upon session startup. If the client determines that there is a violation of corporate policy in the text, the client sends an e-mail compose event to the server.
- the e-mail compose event indicates to the server that a content policy violation has occurred in the text.
- a content policy violation occurs when certain words (keywords) are found in the message or in an attachment to the message that need to be excluded from the message based on administrator-defined policies.
- the keywords also provide an indication whether or not the exclusion only applies when the keywords are sent externally. Examples of such keywords include expletives, confidential code names for projects (for messages to external recipients) and personally identifiable information such as social security numbers.
- the client displays a dialog box.
- the dialog box states what the problem is, and requires the user to click OK before proceeding. For example, if the attribute is that the recipient's mail box is full, the e-mail server 120 communicates this to the client device 110 .
- the client device 110 in turn, notifies the user as described above.
- the client disables sending the e-mail message by disabling (e.g., graying out) the Send button.
- This response type might be used, for example, if the recipient is not authorized to see the contents of the message.
- the client displays a mail tip.
- the mail tip alerts the user to the problem with the message but does not require the user to take any action.
- This response type might be used, for example, if the recipient has set an out of office indicator.
- the responses can be conveyed by the client to the user in other manners.
- the mail tips are displayed in different positions within the user interface.
- an audible indication such as a beep is provided.
- the response is read aloud using text-to-speech technology. Other configurations are possible.
- FIG. 2 shows an illustration of an example mail tip 210 .
- the mail tip 210 appears between the Microsoft Office 2007 ribbon 220 and a header 225 including the To line 230 of the message.
- the ribbon 220 is a panel in Microsoft Office 2007 that contains command buttons and icons.
- the mail tip is seamlessly integrated into the message header.
- the location of the mail tip in the message header can be advantageous because the mail tip is in close proximity to the address field and can be readily noticed by the user.
- the mail tip 210 can also be displayed in a color, for example yellow, that allows it to stand out in the message header to further draw the user's attention. Audible and other visual alerts can also be used.
- the mail tip 210 indicates that the message can't be delivered because the recipient's mailbox is full.
- This mail tip 210 includes a remove recipient link 240 . Clicking on this link 240 deletes the recipient's name from the e-mail message.
- FIG. 3 shows an illustration of another example mail tip 310 .
- this mail tip 310 is located between a ribbon 305 and a header 315 .
- the recipient 320 is out of the office.
- the mail tip 310 also provides details that the recipient 320 included in an out of office message 330 .
- a details link 340 is provided to display the complete out of office message.
- a remove recipient link 350 is also provided to permit deletion of the recipient's name 320 from the e-mail message.
- the system 100 is programmed to provide a mail tip banner within a given amount of time so that the user can act accordingly. In one example, 90% of users receive a mail tip banner within 1, 3, 5, 7, or 10 seconds of an e-mail compose event. In another example, 99% of users receive a Mail tip banner within 5, 7, 10, or 15 seconds of an e-mail compose event. Other configurations are possible. For example, in other embodiments, network or other configurations may not allow the system to perform to these standards. In yet other embodiments, the system may perform more quickly.
- FIG. 4 shows four example types of client interfaces to an e-mail server, such as e-mail server 120 described above.
- a web-access client shown in block 410 , accesses an e-mail server remotely using an Internet connection.
- Outlook Web Access is a webmail service of Microsoft Exchange Server 2007.
- a client device such as a personal computer or a personal digital assistant can use a web browser to connect to Microsoft Exchange Server 2007 via Outlook Web Access. This brings up a user interface similar to the interface in Microsoft OUTLOOK® messaging and collaboration client. A user can compose an e-mail message using this interface.
- a second client shown in block 420 is Microsoft OUTLOOK® messaging and collaboration client.
- Microsoft OUTLOOK® messaging and collaboration client is an e-mail application that is part of the Microsoft Office suite.
- Microsoft OUTLOOK® messaging and collaboration client operates in conjunction with a Microsoft Exchange e-mail server such as Microsoft Exchange Server 2007.
- a user can compose, send and receive e-mails with Microsoft OUTLOOK® messaging and collaboration client.
- a third client shown in block 430 of FIG. 4 is a mobile access client such as Microsoft Mobile Access with ACTIVESYNC® technology or the Microsoft Windows Mobile Device Center for Microsoft Vista.
- a mobile access client like Microsoft Mobile Access with ACTIVESYNC® technology, a user can synchronize messages between a mobile device and the Microsoft Exchange Server 2007.
- the mobile device can be a cellular telephone or a personal digital assistant.
- a fourth client shown in block 440 of FIG. 4 is a voice-access client such as Microsoft Exchange Unified Messaging that is supported in Microsoft Exchange Server 2007.
- Microsoft Exchange Unified Messaging users have one inbox for e-mail and voicemail. Voicemails are delivered directly into the Microsoft OUTLOOK® messaging and collaboration client inbox.
- Microsoft Exchange Unified Messaging delivers access from Microsoft OUTLOOK® messaging and collaboration client, Outlook Web Access, a variety of mobile devices and ordinary telephones.
- the clients shown in FIG. 4 can generate e-mail compose events and the corresponding mail tips either directly or indirectly.
- e-mails can be composed using Microsoft OUTLOOK® and Microsoft Web Access and mail tips can be sent to these clients during the composition of the e-mail message as described above.
- voice mails deposited in a user's mail box using a voice-access client such as Microsoft Exchange Unified Messaging can be replied to and forwarded to generate an e-mail compose event.
- a web access module 510 provides an interface between a webmail client and the e-mail server 500 .
- the web access module 510 provides an interface between Outlook Web Access and Microsoft Exchange Server 2007.
- the web services module 520 Web services support machine to machine communication over a network, such as the Internet.
- One example of the web services module 520 is Exchange Web Services, part of Microsoft Exchange Server 2007.
- the mail tip module 530 which is an extension of the web services module.
- the mail tip module 530 contains mail tips appropriate for various e-mail compose events. Including the mail tips module 530 on the e-mail server provides for efficient management of mail tip messages.
- the mail tip module 530 is an extension to Exchange Web Services. Applications that use Exchange Web Services, such as mail tip module 530 , can access data store items. The data store items can be accessed locally on Microsoft Exchange Server 2007 or remotely via the Simple Access Object Protocol (SOAP).
- SOAP Simple Access Object Protocol
- the mail tip module 530 provides an engine for generating a variety of mail tips based on the validation of the e-mail message by the e-mail server.
- a third module shown in FIG. 5 is business logic module 540 .
- This module is part of the Microsoft Exchange Server 2007 core and provides an interface between front-end e-mail server modules, such as mail tip module 530 and back-end information sources.
- the business logic module 540 also contains drivers for the ACTIVE DIRECTORY® directory service database.
- FIG. 6 shows the interface between the e-mail clients and the central-access e-mail server.
- outlook web Access client 610 communicates with the web access interface 670 of the central access e-mail server 660 .
- the outlook client 620 , mobile access client 630 and voice access client 640 communicate with a mail tip module 685 .
- the web access interface 670 and mail tip module 685 receive e-mail compose events from the clients and in-turn send the clients responses containing a well-defined status.
- the client action is based on this status. For example, the client may respond with a speed bump (a dialog box) or by displaying a mail tip banner.
- FIG. 7 illustrates the information sources 700 that constitute the back-end databases of the e-mail server.
- the local cache 700 is contained within the e-mail server front end. It stores key items of recent server transactions, including recipients, distribution lists and key words.
- the local cache 700 also stores invalid SMTP addresses that were contained in the e-mail messages.
- the local cache 700 can include a list of domains (e.g., “company.com”) that do not accept e-mail. This information can be used to quickly inform someone addressing an e-mail to a recipient having an email address with a domain found in the local cache 700 that the address may be invalid.
- the local cache can include a list of distribution groups, their sizes and whether or not they include external recipients. This allows the server to advise the client how large their audience is and whether there are external people on the message.
- Other information sources 700 include the sender's mailbox 720 , recipient mailbox stores 730 (i.e. mailboxes of recipients), ACTIVE DIRECTORY® directory service 740 and one or more websites 750 . These information sources can be located on other machines. Information is typically obtained from these sources via Remote Procedure Calls (RPCs), via web services using the Simple Access Object Protocol (SOAP) or via http when information gathering is proxied (forwarded) to remote servers.
- RPCs Remote Procedure Calls
- SOAP Simple Access Object Protocol
- Active Directory 740 is a database that provides central authentication and authorization services for Windows based computers. It provides information about recipients of the e-mail message.
- FIG. 8 illustrates an example method of an email server to check the content of an e-mail message.
- an e-mail compose event is received at the e-mail server.
- the e-mail compose event occurs when a user adds a recipient or a distribution list to the e-mail message.
- the server evaluates the message. For example, the server determines whether the recipient's mailbox is full, whether the recipient or a distribution list has restricted access and whether the recipient is out of the office.
- the server checks the e-mail message against configured attributes of the e-mail system, such as whether the size of the message and the number of recipients listed on the message are within configured limits.
- the server obtains information about these items from a variety of information sources at operation 830 .
- information sources are the recipient's mailboxes, configuration parameters of the e-mail server and local cache of the e-mail server.
- the server at operation 840 validates the e-mail message and determines whether the user needs to be alerted to any changes that should be made to the message or to conditions where the message should not be delivered.
- a response is sent to the client device at operation 860 to provide status to the user.
- the response may include a mail tip or a dialog box.
- the server determines that the e-mail message should not be sent, the response may include a disabling mechanism, such as graying out and disabling the e-mail send button. If user attention is not required, the server does not send a status response to the client.
- Such checks can require querying of databases external to system 100 , such as a Domain Name System (DNS) system. It should be noted that these checks are “best effort” determinations and can never be 100% accurate.
- DNS Domain Name System
- a cache is kept of SMTP addresses for which communication has not been successful.
- This cache of SMTP addresses can be kept outside of the e-mail server, making use of other information sources within the organization.
- an organization may communicate with Microsoft HOTMAIL® web-based e-mail service.
- This external e-mail system may also keep track of SMTP addresses for which communication has been successful and for which communication has not been successful.
- the organization may combine caches.
- this external cache may be checked first as a way to speed up the response to the user. If the recipient's SMTP message is on the combined cache, the e-mail server can provide a faster response to the user.
- FIG. 9 illustrates a method of creating an e-mail using a client device.
- a user composes an e-mail message at a client device.
- the client device may receive a mail tip or receive a communication to invoke a dialog box which is displayed on the client device.
- the mail tip can contain information or a message alerting the user of an attribute of the e-mail message that the user may want to modify. If a dialog box was received at operation 930 , the user needs to click OK at operation 940 to acknowledge the information and to close the dialog box.
- the user may use the information in the mail tip or dialog box at operation 950 to modify the e-mail message before it is sent.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Economics (AREA)
- Marketing (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Operations Research (AREA)
- Computer Hardware Design (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Information Transfer Between Computers (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- This patent application is a continuation of co-pending U.S. patent application Ser. No. 11/927,592, filed Oct. 29, 2007 and entitled “Pre-Send Evaluation of E-Mail Communications,” the disclosure of which is incorporated herein, in its entirety, by reference.
- Due to the asynchronous nature of e-mail systems, it is possible for an e-mail message to not be successfully delivered to the intended recipient. The unsuccessful delivery of an e-mail message can occur for many reasons. For example, the e-mail message may be too large for the recipient's mailbox, or the recipient's mailbox may be full. In addition, embarrassing and costly mistakes can be made when composing e-mail messages. For example, a private e-mail may be inadvertently sent to a large audience, or confidential material may be inadvertently sent to external recipients. These problems occur because information about the e-mail system and about the recipients of an e-mail message are not available to the sender while the message is being composed. It is only after sending the message that the problem is discovered.
- The present disclosure relates to a systems and methods for validating the content of an e-mail message during the composition of the message and alerting a user of attributes associated with the message before the e-mail message is sent.
- In example embodiments, during the composition of the e-mail message, the server receives notification when certain compose events occur. This notification is presented to the user. The notification can take the form of a mail tip which alerts to user to attributes associated with the message.
- This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
- The accompanying drawings incorporated in and forming a part of the specification illustrate several aspects of the present disclosure, and together with the description serve to explain the principles of the disclosure. In the drawings:
-
FIG. 1 is an illustration of an example e-mail communication system. -
FIG. 2 is an illustration of an example banner for a mailbox full event. -
FIG. 3 is an illustration of an example banner for a recipient who is out-of-office. -
FIG. 4 is an illustration of example client interfaces. -
FIG. 5 is an illustration of example modules of an e-mail server. -
FIG. 6 is an illustration of example communication between example client interfaces and example modules of an e-mail server. -
FIG. 7 is an illustration of example information sources in an e-mail system. -
FIG. 8 is an illustration of an example flowchart for a server to validate the content of an e-mail message during the composition of the message. -
FIG. 9 is an illustration of an example flowchart for a client receiving validation of the content of an e-mail message during the composition of the message. - The present application is directed to systems and methods for validating the content of an e-mail message during the composition of the message, before the message is sent to its intended recipients.
-
FIG. 1 shows anexample system 100 for validating the content of an e-mail message. The system includes one ormore client devices 110, a central-access e-mail server 120, andinformation sources 130. - A
client device 110 may be a desktop device such as a personal computer or a mobile device such as a personal digital assistant. In example embodiments, theclient device 110 is a computer system, such as a desktop computer, laptop computer, personal data assistant, or cellular device. Theclient 110 can include input/output devices, a central processing unit (“CPU”), a data storage device, and a network device. Typical input/output devices include keyboards, mice, displays, microphones, speakers, disk drives, CD-ROM drives, and flash drives. Computer readable media, such as the data storage device, provide for data retention. By way of example, computer readable media can include computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Among the plurality of information stored on the data storage device is a client operating system (“OS”) and client applications. The client OS is a program that manages the hardware and software resources of the client system. The client applications utilize the resources of theclient 110 to directly perform tasks specified by the user. The network device enables theclient 110 to send and receive data to/from the server 102. Other configurations for theclient 110 are possible. - The central-
access e-mail server 120, also known as a front-end server, provides an interface for theclient devices 110. In example embodiments, the central-access email server 120 is a server configured to handle e-mail sent to and from users. In one embodiment, theemail server 120 is a Microsoft Exchange Server provided by Microsoft Corporation of Redmond, Wash. Other configurations are possible. - The
information sources 130 provide a back-end interface to thee-mail server 120 and contain one or more databases. One or more of theinformation sources 130 are contained within thesystem 100. Examples of such databases include recipient mailbox stores, and address services such as an ACTIVE DIRECTORY® directory service from Microsoft Corporation. Other configurations are possible. - E-mail messages are composed on a
client device 110. Theclient device 110 first establishes a session with theserver 120 and communicates with the server. For example, the client may send the server information about its locale or language used. The client also receives information from the server, such as restrictions that may exist for the sender of the message. For example, the client may receive the sender's maximum message size. - During the composition of the e-mail message, recipients are added to the To, CC, and BCC fields of the message. Recipients are added to the message by adding the recipient names individually or by including one or more distribution lists. Text, graphics, attachments, and other content are added to the body of the message.
- The adding of recipients, either individually or via a distribution list, is referred to as an e-mail compose event. The e-mail compose event generates communication with the
server 120. For example, when an individual recipient or a distribution list is added to the e-mail message, the name of the recipient or the distribution list is communicated to the server. Theserver 120 is programmed to perform one or more checks based on the recipient or distribution list, as described further below. For example, theserver 120 can check to see if the recipient has created an out of office notification, or can check to see how many users are defined for a particular distribution list. - When the central-
access e-mail server 120 receives an e-mail compose event, it accessesinformation sources 130 and validates the message content. Information obtained frominformation sources 130 regarding each recipient can include one of more of the following: (1) whether the recipient is internal or external to the organization, (2) whether the recipient is in or out of the office (e.g., whether or not the recipient has set an out of office indicator), (3) whether the recipient's mailbox is full, (4) whether the recipient has restricted access (see below), (5) whether the maximum number of recipients is exceeded, and (6) whether there is a custom mail tip for the recipient (i.e., a mail tip containing information specific to the recipient, such as “This mailbox is not monitored.” and “Please allow up to 48 hours for a response.” - The e-mail address of the recipient is also checked to ensure that it is a valid SMTP address and to determine if it belongs to a recipient inside or outside the sender's organization. Furthermore, the e-mail address can be checked to determine if the address is within the scope of the sender's organization but does not belong to a recipient in the organization's directory. For example, this could occur if the sender misspelled the recipient's address or if the address belonged to a recipient who has departed the organization.
- Regarding restricted access, configuration properties of individual mailboxes or of groups such as distribution lists can specify restrictions as to access. For example, one can specify particular people or groups from which e-mail messages can be received. In addition, one can define on server 120 a set of attachment types that may or may not be sent in an e-mail message. For example, the e-mail system can be configured so that executable code (having .exe extensions) or source code files may not be sent in an e-mail message. These properties can be predefined by the administrator of the e-mail system. Having this information available on a server permits it to be efficiently communicated to clients.
- Information obtained from
information sources 130 regarding a distribution list can include one or more of the following: (1) whether the distribution list is too large, (2) whether the distribution list has restricted access, (3) whether the distribution list is moderated (i.e. whether someone would receive the e-mail message and either approve or reject before forwarding to a larger group), and (4) whether there is a custom mail tip for the distribution list (i.e., a mail tip containing information specific to the distribution list). - Information obtained from
information sources 130 regarding the content of the message can include one or more of the following: (1) whether the message size is within administrator-defined parameters, (2) whether there any attachments included with the message that have restricted access, and (3) whether the message contains a reply-all response from a BCC recipient (i.e., whether a user who received the message as a result of being on the BCC line clicked Reply-All to the message). - The central-
access e-mail server 120 evaluates the information obtained frominformation sources 130 and determines whether there are any attributes of the e-mail message that should trigger a notification to the user. If theserver 120 determines that the user should be notified, theserver 120 sends a response to aclient device 110 to alert the user of the status. The user can then take appropriate action. - For example, if the response indicates that the recipient's mail box is full, the user can delete the recipient's name from the message before sending the e-mail message. It should be noted that certain attribute evaluation tasks, such as whether a recipient's mailbox is full or whether the recipient is out of the office, can typically only be done for recipients that are within the organization.
- As another example, when the user adds text to the body of the message, the client is programmed to check the text for compliance with corporate policy. The client retrieves a list of disallowed terms from the server upon session startup. If the client determines that there is a violation of corporate policy in the text, the client sends an e-mail compose event to the server. The e-mail compose event indicates to the server that a content policy violation has occurred in the text. A content policy violation occurs when certain words (keywords) are found in the message or in an attachment to the message that need to be excluded from the message based on administrator-defined policies. The keywords also provide an indication whether or not the exclusion only applies when the keywords are sent externally. Examples of such keywords include expletives, confidential code names for projects (for messages to external recipients) and personally identifiable information such as social security numbers.
- There are several types of responses that can be programmed by the client based on status received from the server. In one type of response, referred to as a speed bump, the client displays a dialog box. The dialog box states what the problem is, and requires the user to click OK before proceeding. For example, if the attribute is that the recipient's mail box is full, the
e-mail server 120 communicates this to theclient device 110. Theclient device 110, in turn, notifies the user as described above. - In another type of response, known as a roadblock, the client disables sending the e-mail message by disabling (e.g., graying out) the Send button. This response type might be used, for example, if the recipient is not authorized to see the contents of the message.
- In a third type of response, the client displays a mail tip. The mail tip alerts the user to the problem with the message but does not require the user to take any action. This response type might be used, for example, if the recipient has set an out of office indicator.
- In alternative embodiments, the responses can be conveyed by the client to the user in other manners. For example, in one alternative, the mail tips are displayed in different positions within the user interface. In other alternatives, an audible indication, such as a beep is provided. In yet another embodiment, the response is read aloud using text-to-speech technology. Other configurations are possible.
-
FIG. 2 shows an illustration of anexample mail tip 210. Themail tip 210 appears between the Microsoft Office 2007ribbon 220 and aheader 225 including the To line 230 of the message. Theribbon 220 is a panel in Microsoft Office 2007 that contains command buttons and icons. Thus, in the example shown, the mail tip is seamlessly integrated into the message header. The location of the mail tip in the message header can be advantageous because the mail tip is in close proximity to the address field and can be readily noticed by the user. Themail tip 210 can also be displayed in a color, for example yellow, that allows it to stand out in the message header to further draw the user's attention. Audible and other visual alerts can also be used. In this example, themail tip 210 indicates that the message can't be delivered because the recipient's mailbox is full. Thismail tip 210 includes aremove recipient link 240. Clicking on thislink 240 deletes the recipient's name from the e-mail message. -
FIG. 3 shows an illustration of anotherexample mail tip 310. Again, thismail tip 310 is located between aribbon 305 and aheader 315. In this example, therecipient 320 is out of the office. Themail tip 310 also provides details that therecipient 320 included in an out ofoffice message 330. In this example, a details link 340 is provided to display the complete out of office message. Aremove recipient link 350 is also provided to permit deletion of the recipient'sname 320 from the e-mail message. - In example embodiments, the
system 100 is programmed to provide a mail tip banner within a given amount of time so that the user can act accordingly. In one example, 90% of users receive a mail tip banner within 1, 3, 5, 7, or 10 seconds of an e-mail compose event. In another example, 99% of users receive a Mail tip banner within 5, 7, 10, or 15 seconds of an e-mail compose event. Other configurations are possible. For example, in other embodiments, network or other configurations may not allow the system to perform to these standards. In yet other embodiments, the system may perform more quickly. -
FIG. 4 shows four example types of client interfaces to an e-mail server, such ase-mail server 120 described above. A web-access client, shown inblock 410, accesses an e-mail server remotely using an Internet connection. For example, Outlook Web Access is a webmail service of Microsoft Exchange Server 2007. A client device, such as a personal computer or a personal digital assistant can use a web browser to connect to Microsoft Exchange Server 2007 via Outlook Web Access. This brings up a user interface similar to the interface in Microsoft OUTLOOK® messaging and collaboration client. A user can compose an e-mail message using this interface. - A second client shown in
block 420 is Microsoft OUTLOOK® messaging and collaboration client. Microsoft OUTLOOK® messaging and collaboration client is an e-mail application that is part of the Microsoft Office suite. Microsoft OUTLOOK® messaging and collaboration client operates in conjunction with a Microsoft Exchange e-mail server such as Microsoft Exchange Server 2007. A user can compose, send and receive e-mails with Microsoft OUTLOOK® messaging and collaboration client. - A third client shown in
block 430 ofFIG. 4 is a mobile access client such as Microsoft Mobile Access with ACTIVESYNC® technology or the Microsoft Windows Mobile Device Center for Microsoft Vista. Using a mobile access client like Microsoft Mobile Access with ACTIVESYNC® technology, a user can synchronize messages between a mobile device and the Microsoft Exchange Server 2007. The mobile device can be a cellular telephone or a personal digital assistant. - A fourth client shown in
block 440 ofFIG. 4 is a voice-access client such as Microsoft Exchange Unified Messaging that is supported in Microsoft Exchange Server 2007. With Microsoft Exchange Unified Messaging, users have one inbox for e-mail and voicemail. Voicemails are delivered directly into the Microsoft OUTLOOK® messaging and collaboration client inbox. In addition, Microsoft Exchange Unified Messaging delivers access from Microsoft OUTLOOK® messaging and collaboration client, Outlook Web Access, a variety of mobile devices and ordinary telephones. - The clients shown in
FIG. 4 can generate e-mail compose events and the corresponding mail tips either directly or indirectly. For example, e-mails can be composed using Microsoft OUTLOOK® and Microsoft Web Access and mail tips can be sent to these clients during the composition of the e-mail message as described above. In addition, the voice mails deposited in a user's mail box using a voice-access client such as Microsoft Exchange Unified Messaging can be replied to and forwarded to generate an e-mail compose event. - Referring now to
FIG. 5 , an example illustration of the modules in a central-access e-mail server 500 are shown. Aweb access module 510 provides an interface between a webmail client and thee-mail server 500. For example, theweb access module 510 provides an interface between Outlook Web Access and Microsoft Exchange Server 2007. - Also shown in
FIG. 5 is theweb services module 520. Web services support machine to machine communication over a network, such as the Internet. One example of theweb services module 520 is Exchange Web Services, part of Microsoft Exchange Server 2007. Also shown inFIG. 5 is themail tip module 530 which is an extension of the web services module. Themail tip module 530 contains mail tips appropriate for various e-mail compose events. Including themail tips module 530 on the e-mail server provides for efficient management of mail tip messages. - In one embodiment, the
mail tip module 530 is an extension to Exchange Web Services. Applications that use Exchange Web Services, such asmail tip module 530, can access data store items. The data store items can be accessed locally on Microsoft Exchange Server 2007 or remotely via the Simple Access Object Protocol (SOAP). Themail tip module 530 provides an engine for generating a variety of mail tips based on the validation of the e-mail message by the e-mail server. - A third module shown in
FIG. 5 isbusiness logic module 540. This module is part of the Microsoft Exchange Server 2007 core and provides an interface between front-end e-mail server modules, such asmail tip module 530 and back-end information sources. Thebusiness logic module 540 also contains drivers for the ACTIVE DIRECTORY® directory service database. -
FIG. 6 shows the interface between the e-mail clients and the central-access e-mail server. As shown inFIG. 6 , outlookweb Access client 610 communicates with theweb access interface 670 of the centralaccess e-mail server 660. Theoutlook client 620,mobile access client 630 andvoice access client 640 communicate with amail tip module 685. Theweb access interface 670 andmail tip module 685 receive e-mail compose events from the clients and in-turn send the clients responses containing a well-defined status. The client action is based on this status. For example, the client may respond with a speed bump (a dialog box) or by displaying a mail tip banner. -
FIG. 7 illustrates theinformation sources 700 that constitute the back-end databases of the e-mail server. Thelocal cache 700 is contained within the e-mail server front end. It stores key items of recent server transactions, including recipients, distribution lists and key words. Thelocal cache 700 also stores invalid SMTP addresses that were contained in the e-mail messages. For example, thelocal cache 700 can include a list of domains (e.g., “company.com”) that do not accept e-mail. This information can be used to quickly inform someone addressing an e-mail to a recipient having an email address with a domain found in thelocal cache 700 that the address may be invalid. In an alternative example, the local cache can include a list of distribution groups, their sizes and whether or not they include external recipients. This allows the server to advise the client how large their audience is and whether there are external people on the message. -
Other information sources 700 include the sender'smailbox 720, recipient mailbox stores 730 (i.e. mailboxes of recipients), ACTIVE DIRECTORY® directory service 740 and one ormore websites 750. These information sources can be located on other machines. Information is typically obtained from these sources via Remote Procedure Calls (RPCs), via web services using the Simple Access Object Protocol (SOAP) or via http when information gathering is proxied (forwarded) to remote servers.Active Directory 740 is a database that provides central authentication and authorization services for Windows based computers. It provides information about recipients of the e-mail message. -
FIG. 8 illustrates an example method of an email server to check the content of an e-mail message. Atoperation 810, an e-mail compose event is received at the e-mail server. The e-mail compose event occurs when a user adds a recipient or a distribution list to the e-mail message. Atoperation 820, the server evaluates the message. For example, the server determines whether the recipient's mailbox is full, whether the recipient or a distribution list has restricted access and whether the recipient is out of the office. In addition, the server checks the e-mail message against configured attributes of the e-mail system, such as whether the size of the message and the number of recipients listed on the message are within configured limits. - In order to evaluate the above items at
operation 820, the server obtains information about these items from a variety of information sources atoperation 830. Some examples of information sources are the recipient's mailboxes, configuration parameters of the e-mail server and local cache of the e-mail server. Based on the information obtained and content of the e-mail message, the server atoperation 840 validates the e-mail message and determines whether the user needs to be alerted to any changes that should be made to the message or to conditions where the message should not be delivered. - At
operation 850, if there are any aspects of the e-mail message that require user attention, a response is sent to the client device atoperation 860 to provide status to the user. The response may include a mail tip or a dialog box. In addition, if the server determines that the e-mail message should not be sent, the response may include a disabling mechanism, such as graying out and disabling the e-mail send button. If user attention is not required, the server does not send a status response to the client. - Regarding the recipient's SMTP address, a determination can be made on validity by examining the domain of the address (i.e., everything to the right of the “@” sign). For example, it can be determined if the domain is invalid, if it contains a common misspelling or the domain does not accept e-mail messages. Such checks can require querying of databases external to
system 100, such as a Domain Name System (DNS) system. It should be noted that these checks are “best effort” determinations and can never be 100% accurate. - In addition, in one embodiment a cache is kept of SMTP addresses for which communication has not been successful. This cache of SMTP addresses can be kept outside of the e-mail server, making use of other information sources within the organization. For example, an organization may communicate with Microsoft HOTMAIL® web-based e-mail service. This external e-mail system may also keep track of SMTP addresses for which communication has been successful and for which communication has not been successful. For efficiency purposes, the organization may combine caches. When evaluating the validity of an SMTP address, instead of accessing an information source associated with the e-mail server, this external cache may be checked first as a way to speed up the response to the user. If the recipient's SMTP message is on the combined cache, the e-mail server can provide a faster response to the user.
-
FIG. 9 illustrates a method of creating an e-mail using a client device. Atoperation 910, a user composes an e-mail message at a client device. As the message is composed, atoperation 920, the client device may receive a mail tip or receive a communication to invoke a dialog box which is displayed on the client device. The mail tip can contain information or a message alerting the user of an attribute of the e-mail message that the user may want to modify. If a dialog box was received atoperation 930, the user needs to click OK atoperation 940 to acknowledge the information and to close the dialog box. The user may use the information in the mail tip or dialog box atoperation 950 to modify the e-mail message before it is sent. - Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/971,109 US10305830B2 (en) | 2007-10-29 | 2013-08-20 | Pre-send evaluation of E-mail communications |
US16/410,989 US10637813B2 (en) | 2007-10-29 | 2019-05-13 | Pre-send evaluation of E-mail communications |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/927,592 US8539029B2 (en) | 2007-10-29 | 2007-10-29 | Pre-send evaluation of E-mail communications |
US13/971,109 US10305830B2 (en) | 2007-10-29 | 2013-08-20 | Pre-send evaluation of E-mail communications |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/927,592 Continuation US8539029B2 (en) | 2007-10-29 | 2007-10-29 | Pre-send evaluation of E-mail communications |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/410,989 Continuation US10637813B2 (en) | 2007-10-29 | 2019-05-13 | Pre-send evaluation of E-mail communications |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130339462A1 true US20130339462A1 (en) | 2013-12-19 |
US10305830B2 US10305830B2 (en) | 2019-05-28 |
Family
ID=40584303
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/927,592 Active 2030-04-27 US8539029B2 (en) | 2007-10-29 | 2007-10-29 | Pre-send evaluation of E-mail communications |
US13/971,109 Active 2028-02-09 US10305830B2 (en) | 2007-10-29 | 2013-08-20 | Pre-send evaluation of E-mail communications |
US16/410,989 Active US10637813B2 (en) | 2007-10-29 | 2019-05-13 | Pre-send evaluation of E-mail communications |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/927,592 Active 2030-04-27 US8539029B2 (en) | 2007-10-29 | 2007-10-29 | Pre-send evaluation of E-mail communications |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/410,989 Active US10637813B2 (en) | 2007-10-29 | 2019-05-13 | Pre-send evaluation of E-mail communications |
Country Status (6)
Country | Link |
---|---|
US (3) | US8539029B2 (en) |
EP (1) | EP2220610A4 (en) |
JP (1) | JP5406842B2 (en) |
KR (1) | KR101838748B1 (en) |
CN (1) | CN101842803A (en) |
WO (1) | WO2009058649A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9684798B2 (en) | 2015-05-01 | 2017-06-20 | International Business Machines Corporation | Audience-based sensitive information handling for shared collaborative documents |
US20180131647A1 (en) * | 2016-11-10 | 2018-05-10 | Airwatch Llc | Email composition assistance based on out-of-office recipients in distribution lists |
Families Citing this family (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8539029B2 (en) * | 2007-10-29 | 2013-09-17 | Microsoft Corporation | Pre-send evaluation of E-mail communications |
US9083667B2 (en) * | 2008-01-16 | 2015-07-14 | International Business Machines Corporation | System and method for follow-on message processing |
US8280963B2 (en) * | 2008-04-10 | 2012-10-02 | Microsoft Corporation | Caching and exposing pre-send data relating to the sender or recipient of an electronic mail message |
US8171089B2 (en) * | 2008-07-25 | 2012-05-01 | International Business Machines Corporation | Privileged and restricted email processing to multiple recipients based on sender defined visibility settings |
US7984105B2 (en) | 2009-06-15 | 2011-07-19 | Research In Motion Limited | Method, devices and system having out of office based presence |
US20100332975A1 (en) * | 2009-06-25 | 2010-12-30 | Google Inc. | Automatic message moderation for mailing lists |
US8996623B2 (en) * | 2009-10-13 | 2015-03-31 | International Business Machines Corporation | Cost management for messages |
US8166121B2 (en) * | 2009-12-31 | 2012-04-24 | International Business Machines Corporation | Situation based presence notification leveraging |
US20110219424A1 (en) * | 2010-03-05 | 2011-09-08 | Microsoft Corporation | Information protection using zones |
US9838349B2 (en) * | 2010-03-08 | 2017-12-05 | Microsoft Technology Licensing, Llc | Zone classification of electronic mail messages |
US9292835B2 (en) | 2011-06-30 | 2016-03-22 | International Business Machines Corporation | Determining communication recipient availability |
EP2562697A1 (en) * | 2011-08-26 | 2013-02-27 | Research In Motion Limited | Electronic communication device and method for processing messages |
US8965984B2 (en) * | 2011-08-26 | 2015-02-24 | Blackberry Limited | Electronic communication device and method for processing messages |
JP5783059B2 (en) * | 2012-01-19 | 2015-09-24 | 富士通株式会社 | E-mail information transmission program, e-mail information transmission method, and e-mail information transmission apparatus |
US9712467B2 (en) * | 2014-02-28 | 2017-07-18 | International Business Machines Corporation | Iterative method to successfully send large electronic messages |
US10250538B2 (en) | 2014-06-14 | 2019-04-02 | Trisha N. Prabhu | Detecting messages with offensive content |
US9686217B2 (en) * | 2014-06-14 | 2017-06-20 | Trisha N. Prabhu | Method to stop cyber-bullying before it occurs |
US11095585B2 (en) | 2014-06-14 | 2021-08-17 | Trisha N. Prabhu | Detecting messages with offensive content |
US20150372961A1 (en) * | 2014-06-19 | 2015-12-24 | International Business Machines Corporation | Notification generation system for messages |
WO2016163043A1 (en) * | 2015-04-10 | 2016-10-13 | 株式会社ソリトンシステムズ | Electronic mail transmission error determination device, electronic mail transmission system, and recording medium |
US11032229B2 (en) * | 2015-07-31 | 2021-06-08 | International Business Machines Corporation | System and method for visual classification of email participants |
US10243890B2 (en) * | 2016-01-12 | 2019-03-26 | Google Llc | Methods and apparatus for determining, based on features of an electronic communication and schedule data of a user, reply content for inclusion in a reply by the user to the electronic communication |
US10778621B2 (en) * | 2016-06-06 | 2020-09-15 | Microsoft Technology Licensing, Llc | Location integration into electronic mail system |
US11405345B2 (en) | 2016-11-01 | 2022-08-02 | Microsoft Technology Licensing, Llc | E-mail with smart reply and roaming drafts |
US10554598B2 (en) * | 2016-12-09 | 2020-02-04 | Microsoft Technology Licensing, Llc | Accessibility processing when making content available to others |
US10419448B2 (en) * | 2017-01-09 | 2019-09-17 | Microsoft Technology Licensing, Llc | Enhanced email service |
US10757053B2 (en) * | 2017-03-02 | 2020-08-25 | Microsoft Technology Licensing, Llc | High confidence digital content treatment |
US10601938B2 (en) * | 2017-04-12 | 2020-03-24 | Microsoft Technology Licensing, Llc | Organizationally programmable intranet push notifications |
JP6533823B2 (en) * | 2017-05-08 | 2019-06-19 | デジタルア−ツ株式会社 | INFORMATION PROCESSING APPARATUS, INFORMATION PROCESSING SYSTEM, PROGRAM, RECORDING MEDIUM, AND INFORMATION PROCESSING METHOD |
US11652776B2 (en) | 2017-09-25 | 2023-05-16 | Microsoft Technology Licensing, Llc | System of mobile notification delivery utilizing bloom filters |
JP6994344B2 (en) * | 2017-10-06 | 2022-01-14 | 東芝テック株式会社 | Information processing equipment, information processing methods and programs |
US20190182197A1 (en) * | 2017-10-10 | 2019-06-13 | Soliton Systems K.K. | Warning apparatus for preventing electronic mail wrong transmission, electronic mail transmission system, and program |
CN107846517A (en) * | 2017-11-13 | 2018-03-27 | 维沃移动通信有限公司 | Message method and mobile terminal |
CN108833258A (en) * | 2018-06-12 | 2018-11-16 | 广东睿江云计算股份有限公司 | A kind of mail service actively discovers abnormal method |
US10715473B2 (en) * | 2018-07-24 | 2020-07-14 | International Business Machines Corporation | Optimized message exchange |
US10785177B1 (en) * | 2019-07-22 | 2020-09-22 | Capital One Services, Llc | Systems and methods for screening electronic communications |
CN111404806A (en) * | 2020-03-16 | 2020-07-10 | 深信服科技股份有限公司 | Method, device and equipment for detecting harpoon mails and computer readable storage medium |
CN113468589A (en) * | 2020-03-30 | 2021-10-01 | 微软技术许可有限责任公司 | Detecting data collection validity |
CN113938313A (en) * | 2021-11-15 | 2022-01-14 | 展讯半导体(成都)有限公司 | Message sending method and related device |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8539029B2 (en) * | 2007-10-29 | 2013-09-17 | Microsoft Corporation | Pre-send evaluation of E-mail communications |
Family Cites Families (97)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH05241993A (en) | 1992-03-03 | 1993-09-21 | Nec Corp | Mailing system |
JPH09200256A (en) | 1996-01-23 | 1997-07-31 | Nec Corp | Electronic mail system |
US5923848A (en) | 1996-05-31 | 1999-07-13 | Microsoft Corporation | System and method for resolving names in an electronic messaging environment |
US6108688A (en) | 1996-06-12 | 2000-08-22 | Sun Microsystems, Inc. | System for reminding a sender of an email if recipient of the email does not respond by a selected time set by the sender |
US5943478A (en) | 1997-04-04 | 1999-08-24 | Flash Communications, Inc. | System for immediate popup messaging across the internet |
US6434601B1 (en) | 1999-03-31 | 2002-08-13 | Micron Technology, Inc. | Pre test electronic mail process |
US6539385B1 (en) | 1999-06-11 | 2003-03-25 | Abuzz Technologies, Inc. | Dual-use email system |
US6796494B1 (en) | 1999-06-18 | 2004-09-28 | Steven M. Gonzalo | Method and system for configuring a publicly accessible computer system |
US6671718B1 (en) * | 1999-06-28 | 2003-12-30 | Mark Meister | Email client application incorporating an active transmit authorization request |
US6430604B1 (en) | 1999-08-03 | 2002-08-06 | International Business Machines Corporation | Technique for enabling messaging systems to use alternative message delivery mechanisms |
JP2001109680A (en) | 1999-10-08 | 2001-04-20 | Hitachi Ltd | Electronic mail system, electronic mail client device and electronic mail server device |
AU2001231220A1 (en) | 2000-01-28 | 2001-08-07 | Global Technology Marketing International | Recipient selection and message delivery system and method |
US7634528B2 (en) | 2000-03-16 | 2009-12-15 | Microsoft Corporation | Harnessing information about the timing of a user's client-server interactions to enhance messaging and collaboration services |
US6684238B1 (en) | 2000-04-21 | 2004-01-27 | International Business Machines Corporation | Method, system, and program for warning an email message sender that the intended recipient's mailbox is unattended |
US7444381B2 (en) | 2000-05-04 | 2008-10-28 | At&T Intellectual Property I, L.P. | Data compression in electronic communications |
US6972874B2 (en) | 2000-07-06 | 2005-12-06 | Canon Kabushiki Kaisha | Image communicating apparatus |
US6839737B1 (en) | 2000-07-19 | 2005-01-04 | Neoplanet, Inc. | Messaging system for indicating status of a sender of electronic mail and method and computer program product therefor |
US7814162B2 (en) | 2000-08-22 | 2010-10-12 | International Business Machines Corporation | Self-protecting e-mail |
US6895426B1 (en) * | 2000-10-17 | 2005-05-17 | Microsoft Corporation | Addresses as objects for email messages |
GB0027280D0 (en) | 2000-11-08 | 2000-12-27 | Malcolm Peter | An information management system |
US7895271B1 (en) | 2000-12-29 | 2011-02-22 | At&T Intellectual Property I, L.P. | Method and apparatus for managing and compacting electronic mail messages |
US20060059544A1 (en) | 2004-09-14 | 2006-03-16 | Guthrie Paul D | Distributed secure repository |
US20060064739A1 (en) * | 2004-09-17 | 2006-03-23 | Guthrie Paul D | Relationship-managed communication channels |
KR100383167B1 (en) | 2001-05-10 | 2003-05-09 | (주)디쏘테크놀로지 | An e-mail address verifying & adjusting system and the e-mail verifying & adjusting method |
US6944357B2 (en) | 2001-05-24 | 2005-09-13 | Microsoft Corporation | System and process for automatically determining optimal image compression methods for reducing file size |
JP2003006091A (en) | 2001-06-20 | 2003-01-10 | Casio Comput Co Ltd | Electronic equipment, communication equipment and program |
US7305441B2 (en) | 2001-07-20 | 2007-12-04 | International Business Machines Corporation | Time-sensitive messages and events |
JP2003108480A (en) * | 2001-09-28 | 2003-04-11 | Fuji Color Service Co Ltd | Method and program for confirming electronic mail address |
US6501834B1 (en) | 2001-11-21 | 2002-12-31 | At&T Corp. | Message sender status monitor |
US20030120733A1 (en) * | 2001-12-21 | 2003-06-26 | Forman George H. | Email system that allows sender to check recipient's status before sending an email to the recipient |
CA2419435A1 (en) | 2002-02-13 | 2003-08-13 | Peter T. O'brien | Sender-initiated print-on receipt functionality in an electronic messaging environment |
US7937443B2 (en) | 2002-03-10 | 2011-05-03 | Talkway, Inc. | Email messaging program with built-in video and/or audio media recording and/or playback capabilities |
JP2003273934A (en) | 2002-03-18 | 2003-09-26 | Fujitsu Ltd | Electronic mail management method |
US20030200265A1 (en) | 2002-04-19 | 2003-10-23 | Henry Steven G. | Electronic mail address validation |
US7395329B1 (en) | 2002-05-13 | 2008-07-01 | At&T Delaware Intellectual Property., Inc. | Real-time notification of presence availability changes |
US7522910B2 (en) | 2002-05-31 | 2009-04-21 | Oracle International Corporation | Method and apparatus for controlling data provided to a mobile device |
US7569553B2 (en) | 2002-07-03 | 2009-08-04 | Coley Pharmaceutical Group, Inc. | Nucleic acid compositions for stimulating immune responses |
EP1538530A4 (en) | 2002-07-23 | 2007-11-07 | Eighting Kk | Informing system |
CA2414154A1 (en) | 2002-12-12 | 2004-06-12 | Mark W. Brooks | System and method for transmitting a file associated with an e-mail |
US7366760B2 (en) | 2003-01-03 | 2008-04-29 | Microsoft Corporation | System and method for improved client server communications of email messages |
US7546348B2 (en) * | 2003-05-05 | 2009-06-09 | Sonicwall, Inc. | Message handling with selective user participation |
US20050010644A1 (en) | 2003-07-07 | 2005-01-13 | Brown Scott T. | High performance electronic message delivery engine |
US7996470B2 (en) | 2003-10-14 | 2011-08-09 | At&T Intellectual Property I, L.P. | Processing rules for digital messages |
JP4457634B2 (en) | 2003-10-20 | 2010-04-28 | 富士通株式会社 | E-mail transmission / reception device, method, and program |
US20050108336A1 (en) | 2003-11-13 | 2005-05-19 | International Business Machines Corporation | Optional receipt of an email attachment |
US7457955B2 (en) | 2004-01-14 | 2008-11-25 | Brandmail Solutions, Inc. | Method and apparatus for trusted branded email |
US20050262449A1 (en) | 2004-05-03 | 2005-11-24 | Microsoft Corporation | Online service switching and customizations |
US7499976B2 (en) | 2004-05-28 | 2009-03-03 | International Business Machines Corporation | Warning and avoidance of sending email messages to unintended recipients |
US20060036712A1 (en) | 2004-07-28 | 2006-02-16 | Morris Robert P | System and method for providing and utilizing presence information |
US7593984B2 (en) | 2004-07-30 | 2009-09-22 | Swift Creek Systems, Llc | System and method for harmonizing changes in user activities, device capabilities and presence information |
RU2289211C2 (en) | 2004-08-23 | 2006-12-10 | Андрей Иванович Сорокин | Method and system for processing electronic mail |
JP5241993B2 (en) | 2004-09-02 | 2013-07-17 | オート化学工業株式会社 | Curable composition and sealant composition |
EP1790112A2 (en) * | 2004-09-07 | 2007-05-30 | Philippe J. M. Coueignoux | Controlling electronic messages |
NL1027274C2 (en) * | 2004-10-18 | 2006-04-19 | Ebuzon B V | Method and system for sending electronic mail via a network. |
US7212814B2 (en) | 2004-11-24 | 2007-05-01 | Research In Motion Limited | Methods and apparatus for efficiently managing the storage of e-mail message information for a mobile station |
EP1681651A1 (en) * | 2004-12-22 | 2006-07-19 | Sap Ag | Virtual calendar |
KR100614866B1 (en) | 2005-02-01 | 2006-08-22 | 엔에이치엔(주) | System and Method for Determining Possibility of Mail Receipt Before Sending Mail |
US7792860B2 (en) | 2005-03-25 | 2010-09-07 | Oracle International Corporation | System for change notification and persistent caching of dynamically computed membership of rules-based lists in LDAP |
US8171416B2 (en) * | 2005-03-29 | 2012-05-01 | International Business Machines Corporation | Confirmation system and method for instant messaging |
US8583740B2 (en) * | 2005-04-25 | 2013-11-12 | Google Inc. | Actionable quarantine summary |
US8069215B2 (en) | 2005-05-16 | 2011-11-29 | Cisco Technology, Inc. | Configurable downloading of content pointed to in electronic messages |
US7567553B2 (en) | 2005-06-10 | 2009-07-28 | Swift Creek Systems, Llc | Method, system, and data structure for providing a general request/response messaging protocol using a presence protocol |
US20070005708A1 (en) | 2005-06-21 | 2007-01-04 | Cornell Juliano | Authorizing control for electronic communications |
US20060294188A1 (en) | 2005-06-22 | 2006-12-28 | International Business Machines Corporation | Providing status information about email recipients |
CN100496054C (en) | 2005-07-01 | 2009-06-03 | 英华达(上海)电子有限公司 | Method for searching internetwork address on computer |
KR100800776B1 (en) | 2005-07-22 | 2008-02-01 | 삼성전자주식회사 | E-mail transmission method and apparatus |
US20070043866A1 (en) | 2005-08-18 | 2007-02-22 | International Business Machines Corporation | Predictive email actions and load prompts |
JP2007102334A (en) * | 2005-09-30 | 2007-04-19 | Ntt Data Corp | System, method and computer program for preventing information leakage by e-mail |
US20070088788A1 (en) | 2005-10-14 | 2007-04-19 | International Business Machines Corporation | Method and system for enhancing e-mail correspondence |
JP2007115192A (en) * | 2005-10-24 | 2007-05-10 | Chial & Associates:Kk | File management system, information processor, authentication system and file use right setting system |
US20070130323A1 (en) | 2005-12-02 | 2007-06-07 | Landsman Richard A | Implied presence detection in a communication system |
EP1793543B1 (en) | 2005-12-02 | 2011-03-23 | Microsoft Corporation | Messaging service |
JP4808030B2 (en) | 2006-01-12 | 2011-11-02 | ヤフー株式会社 | E-mail warning device, mail server, and e-mail warning method |
JP2007193717A (en) | 2006-01-23 | 2007-08-02 | Mixa Kk | Emailing method and emailing program |
US8296370B2 (en) | 2006-02-13 | 2012-10-23 | Research In Motion Limited | System and method of sharing auto-reply information |
WO2007134305A2 (en) | 2006-05-12 | 2007-11-22 | Convenous, Llc | Apparatus, system, method and computer program product for collaboration via one or more networks |
US20070294428A1 (en) * | 2006-06-19 | 2007-12-20 | Ido Guy | Method and System for Email Messaging |
US20080034043A1 (en) | 2006-08-03 | 2008-02-07 | International Business Machines Corporation | Electronic mail message replay constraints |
US20080086530A1 (en) | 2006-10-09 | 2008-04-10 | Gandhi Rajeev H | System and method for restricting replies to an original electronic mail message |
DE102006050236A1 (en) | 2006-10-18 | 2008-04-24 | Schefenacker Vision Systems Germany Gmbh | Headlight system for vehicles, preferably for motor vehicles |
US20080104177A1 (en) * | 2006-10-30 | 2008-05-01 | Keohane Susann M | Method to facilitate sender notification of out-of-office status of e-mail addressee |
US20080104175A1 (en) * | 2006-10-30 | 2008-05-01 | Keohane Susann M | Automatically transmitting e-mail to specified backup address for out-of-office recipient |
US8484296B2 (en) | 2006-11-17 | 2013-07-09 | At&T Intellectual Property I, L.P. | Systems and methods for displaying electronic mail messages |
US8081745B2 (en) | 2006-12-14 | 2011-12-20 | Microsoft Corporation | Dynamic information publication enabling direct access to a preferred communication channel connection in integrated communication server |
US20080147818A1 (en) * | 2006-12-14 | 2008-06-19 | Itzchak Sabo | Email enhancement |
US8775523B2 (en) * | 2006-12-27 | 2014-07-08 | International Business Machines Corporation | Method and system to intelligently route message requests |
US8280936B2 (en) | 2006-12-29 | 2012-10-02 | Intel Corporation | Packed restricted floating point representation and logic for conversion to single precision float |
US7720919B2 (en) | 2007-02-27 | 2010-05-18 | Cisco Technology, Inc. | Automatic restriction of reply emails |
KR20090003547A (en) | 2007-06-15 | 2009-01-12 | 삼성전자주식회사 | Image forming apparatus and electronic mail processing method thereof |
US20090007143A1 (en) | 2007-06-28 | 2009-01-01 | Microsoft Corporation | Server quota notification |
US20090100184A1 (en) * | 2007-10-16 | 2009-04-16 | International Business Machines Corporation | Protecting context sensitive information from being transmitted from an instant message client |
US8635288B2 (en) | 2007-12-18 | 2014-01-21 | Alcatel Lucent | Methods and systems for expiration handling in electronic message systems |
US8117648B2 (en) | 2008-02-08 | 2012-02-14 | Intersections, Inc. | Secure information storage and delivery system and method |
US20090216843A1 (en) | 2008-02-26 | 2009-08-27 | Willner Barry E | System and method for collaborative email review |
US8280963B2 (en) | 2008-04-10 | 2012-10-02 | Microsoft Corporation | Caching and exposing pre-send data relating to the sender or recipient of an electronic mail message |
US20090288035A1 (en) | 2008-05-15 | 2009-11-19 | Microsoft Corporation | Scrollable views in a client/server application |
US8280965B2 (en) | 2008-12-10 | 2012-10-02 | International Business Machines Corporation | Method and system for managing electronic mail |
-
2007
- 2007-10-29 US US11/927,592 patent/US8539029B2/en active Active
-
2008
- 2008-10-23 WO PCT/US2008/080900 patent/WO2009058649A2/en active Application Filing
- 2008-10-23 CN CN200880114595A patent/CN101842803A/en active Pending
- 2008-10-23 KR KR1020107008905A patent/KR101838748B1/en active IP Right Grant
- 2008-10-23 EP EP08845424A patent/EP2220610A4/en not_active Ceased
- 2008-10-23 JP JP2010531232A patent/JP5406842B2/en active Active
-
2013
- 2013-08-20 US US13/971,109 patent/US10305830B2/en active Active
-
2019
- 2019-05-13 US US16/410,989 patent/US10637813B2/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8539029B2 (en) * | 2007-10-29 | 2013-09-17 | Microsoft Corporation | Pre-send evaluation of E-mail communications |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9684798B2 (en) | 2015-05-01 | 2017-06-20 | International Business Machines Corporation | Audience-based sensitive information handling for shared collaborative documents |
US9684799B2 (en) | 2015-05-01 | 2017-06-20 | International Business Machines Corporation | Audience-based sensitive information handling for shared collaborative documents |
US9824237B2 (en) | 2015-05-01 | 2017-11-21 | International Business Machines Corporation | Audience-based sensitive information handling for shared collaborative documents |
US9830477B2 (en) | 2015-05-01 | 2017-11-28 | International Business Machines Corporation | Audience-based sensitive information handling for shared collaborative documents |
US20180131647A1 (en) * | 2016-11-10 | 2018-05-10 | Airwatch Llc | Email composition assistance based on out-of-office recipients in distribution lists |
US11128580B2 (en) * | 2016-11-10 | 2021-09-21 | Airwatch Llc | Email composition assistance based on out-of-office recipients in distribution lists |
US11539644B2 (en) * | 2016-11-10 | 2022-12-27 | Airwatch Llc | Email composition assistance based on out-of-office recipients in distribution lists |
Also Published As
Publication number | Publication date |
---|---|
EP2220610A4 (en) | 2013-01-02 |
KR101838748B1 (en) | 2018-04-26 |
CN101842803A (en) | 2010-09-22 |
WO2009058649A2 (en) | 2009-05-07 |
US20090113001A1 (en) | 2009-04-30 |
JP2011502308A (en) | 2011-01-20 |
US10305830B2 (en) | 2019-05-28 |
EP2220610A2 (en) | 2010-08-25 |
JP5406842B2 (en) | 2014-02-05 |
US8539029B2 (en) | 2013-09-17 |
US20190268292A1 (en) | 2019-08-29 |
KR20100084160A (en) | 2010-07-23 |
WO2009058649A3 (en) | 2009-07-02 |
US10637813B2 (en) | 2020-04-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10637813B2 (en) | Pre-send evaluation of E-mail communications | |
US20230344794A1 (en) | Email based task management system | |
EP1680728B1 (en) | Method and apparatus to block spam based on spam reports from a community of users | |
US7970834B2 (en) | Method and program product for tracking a file attachment in an e-mail | |
US10187332B2 (en) | Generation and retrieval of report information | |
US9165285B2 (en) | Shared attachments | |
US9015252B2 (en) | Method and system for forcing e-mail addresses into blind carbon copy (“Bcc”) to enforce privacy | |
US20040260710A1 (en) | Messaging system | |
US20070073816A1 (en) | Method and system for providing increased information and improved user controls for electronic mail return receipts | |
JP2004517414A (en) | E-mail management and organization system and method | |
US20080098071A1 (en) | Method and process to unsubscribe from on-going electronic message threads | |
US20090282112A1 (en) | Spam identification system | |
US7030730B1 (en) | System and method for formatting an electronic message | |
US20150081816A1 (en) | Electronic message management system | |
US8095604B2 (en) | Automatically modifying distributed communications | |
US20100070590A1 (en) | Method and apparatus for electronic communication | |
US20060116162A1 (en) | Methods for providing a subscriber service | |
TWI285040B (en) | Notification system for instant message and method thereof | |
US20070005710A1 (en) | Message communication channel | |
KR101223674B1 (en) | E-mail client daemon system for # mail and method of sending # mail using the system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034544/0541 Effective date: 20141014 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |