An email trust service

[0013] An email trust service is described. In an embodiment, an email message is received at an email distribution service for distribution to client devices corresponding to recipients of the email message. Authentication techniques may be applied to email messages to verify that the email message was received from an authorized domain as specified in the sender address field of the email message. The authentication technology may include a domain key identified mail (DKIM) authentication technology or a SenderID (sender ID) authentication technology. Authenticating an email message using DKIM or SenderID can be used to determine whether the email message was received from a sender authorized to send email messages from authorized domains.

[0014] Additionally, it can be determined whether an extended validation certificate is associated with an authorized domain in order to determine whether the authorized domain can be trusted. An Extended Validation certificate is a standardized digital certificate issued to indicate that the entity or organization responsible for authorizing a domain can be trusted. A trust indicator can then be associated with the email message to provide an indication that the email message is trusted when displayed at the client device. In an embodiment, the trust indicator is a website icon associated with the authorized domain, and the website icon may be associated with and displayed with the email message at the client device to indicate that the email message is trusted.

[0015] Although the features and concepts of the described systems and methods for email trust services can be implemented in any number of different environments, systems, devices, and/or different configurations, embodiments of email trust services are described in the following example devices, Described in the context of systems and configurations.

[0016] figure 1 An example system 100 is shown in which various embodiments of an email trust service may be implemented. The example system 100 includes a client device 102 that may be configured as any type of client device 104 . Some of these various client devices include wired and/or wireless devices, and may also be referred to as user devices and/or portable devices. The example system 100 also includes an email distribution service 106 that receives email messages 108 for distribution to different client devices corresponding to each recipient of the email message. The email distribution service may transmit email messages to client devices 104 via communication network 110 .

[0017] Any of the services and devices may communicate via communication network 110, which may be implemented to include wired and/or wireless networks that facilitate email message distribution and data communications. A communication network may also be implemented using any type of network topology and/or communication protocol, and may be represented or otherwise implemented as a combination of two or more networks. Communication networks may also include mobile operator networks managed by mobile operators, such as communication service providers, cell phone providers, and/or Internet service providers. A mobile operator can facilitate mobile data and/or voice communications for any type of wireless device or mobile phone (eg, cellular, VoIP, Wi-Fi, etc.).

[0018] Email distribution service 106 may include server devices to receive email messages, for example, from different enterprise domains 112 and to transmit or otherwise distribute the received email messages to any number of different client devices. In this example system 100 , the email distribution service includes a storage medium 114 for storing or otherwise maintaining various data, such as email messages, extended validation certificates 116 , and trust indicators 118 . A storage medium may be implemented as any type of memory and/or suitable electronic data storage. Additionally, the email distribution service can be implemented as a subscription-based service from which any of the various client devices 104 can request email messages. For example, when a request for an email message is received from a client device, the email distribution service manages the distribution of the email message to different client devices, and the email distribution service transmits or provides the data segments of the email message to the client equipment.

[0019] In this example system 100, email distribution service 106 includes email trust service 120, which may be implemented as computer-executable instructions, such as a software application, and executed by one or more processors to Various embodiments described herein are implemented. Email distribution services may also utilize any number and combination of e.g. Figure 7 Implemented by the different components further described in the example device shown in . Additionally, the email trust service may be implemented as a separate service from the email distribution service (eg, on a separate server, through a third-party service, or on a client device).

[0020] In various embodiments, email trust service 120 is implemented to determine whether email message 108 can be trusted, eg, whether the email message originates from trusted enterprise domain 112 . An email trust service is then executed to associate a trust indicator with the email message to generate a trusted email message 122 .

[0021] To determine whether email message 108 is trusted, email trust service 120 is executed to apply authentication techniques to verify that the email message was received from an authorized domain as specified in the sender address field of the email message. For example, the email trust service verifies that email messages are received from reputable sources, such as reputable companies, financial institutions, or other legitimate businesses with known corporate domains 112 . The sender address field of an email message (also known as the "From" address) indicates the address from which the email message was received and can be divided into two parts: the username of the sender of the email message, and the source of the email message domain name. The sender address of the e-mail message may be "johnstarbank.com". The sender's username is "john" and the domain name is "starbank.com". In this example, an email trust service is implemented to verify that the email message was actually received from the domain name "starbank.com".

[0022] A variety of different authentication techniques may be applied to email message 108 by email trust service 120 . In one embodiment, the email trust service applies Domain Keys Identified Mail (DKIM) authentication technology and/or SenderID authentication technology to email messages. Both DKIM and SenderID can be used to verify that an email message was received from an authorized domain as specified in the sender address field of the email message.

[0023] After verifying that email message 108 was received from an authorized domain, email trust service 120 may determine whether extended validation certificate 116 is associated with the authorized domain from which email was received. In one embodiment, the email trust service may extract the domain name from the sender address field of the email message and establish a secure connection with the domain, eg, by connecting to a website associated with the domain. For example, the email trust service may extract the domain "starbank.com" from the sender address "johnstarbank.com" and then establish a secure connection with the website "www.starbank.com", which may be the enterprise domain 112 .

[0024] When the secure connection is established, a certificate is received from the enterprise domain 112 as part of the secure connection. Email trust service 120 may then examine the certificate presented by the domain to determine if the certificate is an extended validation certificate. If the certificate is an Extended Validation certificate, the Email Trust Service determines that the email was received from a trusted domain that has been verified by the Extended Validation certificate authority.

[0025]Email trust service 120 is executed to then associate trust indicator 118 with email message 108 to generate trusted email message 122 . A trust indicator may be any type of image, graphic, text or sound indication that an email message is trusted. In an embodiment, trust indicator 118 is a website icon, such as website icon 124 associated with an enterprise domain 112 that has been verified as trusted. Email trust services can obtain favicons associated with authorized corporate domains. A favicon associated with a business domain typically includes a logo or picture associated with a particular domain, such as a business or organization logo.

[0026] In an embodiment, email trust service 120 is implemented to utilize storage medium 114 to cache extended validation certificate 116 and/or website icon 124 . When a subsequent email message is then received from the same enterprise domain 112, the email trust service can utilize the cached extended validation certificate to verify that the extended validation certificate is associated with the enterprise domain. Similarly, when determining that a subsequent email message is trusted, the email trust service may associate a cached favicon with the trusted email message.

[0027] The example client device 102 includes an email application 126 that can request, receive, and process email messages for a user at the client device. The client device may receive the trusted email message 128 from the email distribution service 106, for example, when a user at the client device launches an email application. Client device 102 may then display the trusted email message with a trust indicator or website icon that indicates to the recipient of the email message that the email message is trusted.

[0028] Email distribution service 106 may receive a request for email message 108 from client device 102, and then generate a displayable version of trusted email message 122, which is delivered to the client device as a trusted email message 122. Mail message 128 is displayed. A trusted email message may be displayed with an associated trust indicator, such as a website icon, to indicate to recipients of the email message that the email message is trusted. An example of displaying a trust indicator such as a favicon along with an email message at a client device is shown and referenced below. figure 2 and image 3 be described.

[0029] In one embodiment, email trust service 120 at email distribution service 106 may receive a request to add an authorized domain to email safe list 130 , eg, from client device 120 . For example, after the trusted email message 122 is transmitted to the client device, the recipient of the trusted email message may request that the domain name specified in the sender address field of the email message be added to the email safe list. Then, when determining whether a subsequently received email message is trusted, the email trust service can determine whether the domain name specified in the sender address field of the email message is maintained on the email safe list. For example, if an e-mail message is received from a domain listed in an e-mail safe list, the e-mail trust service can determine that the e-mail is a trusted. The email distribution service 106 may also maintain an email block list 132 of domain names that are not trusted by users or have been determined to be untrusted.

[0030] Any of the different client devices 104 can be configured as a client device 102 and can be utilized as referenced Figure 7 The example device shown in is further described in any number and combination of different components. In this example system 100, client device 104 may be implemented as any one or combination of television client device 134, computer device 136, gaming system 138, electrical device, electronic device, and/or may be implemented to receive Any other type of device for the content of audio, video and/or image data in any form (such as e-mail messages). Various client devices may also include wireless devices implemented to receive and/or transmit wireless data, such as any of a mobile phone 140 (e.g., cellular, VoIP, WiFi, etc.), a portable computer device 142, a media player device 144 One or a combination, and/or any other wireless device that can receive media content (such as email messages) in any form of audio, video, and/or image data. The client system may include a corresponding client device and display device 146 that together render the email message for display. The display device may be implemented as any type of television, high definition television (HDTV), LCD or similar display system.

[0031] figure 2 An example 200 of a trusted email message 202 displayed at a client device is shown in accordance with various embodiments described herein. The trusted e-mail message is as referenced figure 1 An example of a trusted email message 128 received at a client device 102 is depicted. The trusted email message includes a trust indicator 204 that provides an indication that the email message is trusted. The trust indicator can be displayed as any type of text, image, animation, color, sound, or other indication to the email recipient that the email is trusted.

[0032] In this example, the trust indicator 204 is a website icon for the domain "starbank.com". The display of the favicon indicates to the e-mail recipient that e-mail messages from the domain "starbank.com" are trusted, and that the e-mail recipient can feel comfortable replying to the e-mail message and/or, for example, by choosing to include in the e-mail A hyperlink 206 within the message interacts with the email message. In one embodiment, trust indicator 204 is also a user-selectable control that a user can select to initiate an interaction, such as displaying a website associated with an enterprise domain.

[0033] image 3 An example 300 of a list view 302 of email messages displayed at a client device is shown in accordance with various embodiments described herein. In this example, a trust indicator is displayed adjacent to each email message in the list view to indicate trusted email messages received from authorized domains. For example, an email message from "johnstarbank.com" is displayed in the list view and a Star Bank website icon 304 is displayed adjacent to the email message to indicate that the email message is trusted.

[0034] The list view 302 of email messages also includes an email message from "paulworldgym.com" that includes a trust indicator displayed as a check mark next to the email message. In this example, the domain "worldgym.com" may not have an associated favicon, and a generic trust indicator is provided by the email trust service and displayed to indicate that the domain "worldgym.com" is trusted. It should be noted that other types of general trust indicators may be used in place of the check marks depicted in this example.

[0035] The list view 302 of email messages also includes an email message from "cindystatecollege.com" that includes a non-trust indicator displayed as a circle adjacent to the email message with a line through the circle. In this example, the domain "statecollege.com" was determined by the email trust service to not be a trusted domain, and the non-trust indicator indicates that the domain should not be trusted by the recipient of the email message. It should be noted that other types of non-trust indicators may be used in place of the non-trust indicators depicted in this example.

[0036] The list view 302 of email messages also includes an email message from "shaneworldbiz.com" that includes a trust indicator 306 displayed as a question mark next to the email message. In this case, the question mark trust indicator indicates that the email trust service has not determined whether the domain "worldbiz.com" is trusted. For example, the domain might be an authorized domain, but not have an associated Extended Validation certificate. Accordingly, a question mark trust indicator is displayed to indicate that the email message may or may not be trusted. In one embodiment, trust indicator 306 is also a user-selectable control that a user may select to initiate an interaction, such as displaying user interface 308 .

[0037] The user interface enables the email recipient to request that the domain name specified in the sender address field of the email message be added to the email safe list of domains trusted by the user, or to the email block list of domains not trusted by the user. In this example, an email recipient may request that "worldbiz.com" be added to an email safe list or be added to an email block list. For example, if an email recipient regularly does business with "worldbiz.com," the email recipient could request that the domain be added to the email safelist. Alternatively, if the email recipient frequently receives spam from "worldbiz.com," the email recipient may request that the domain be added to the email block list. As described above, the request is communicated to the email trust service at the email distribution service, and the email trust service adds the domain name to the email safe list or to the email block list in accordance with the request.

[0038] Figure 4 shows the included as referenced figure 1 An example system 400 of a client device 102 is depicted. Example system 400 allows for a ubiquitous environment for a seamless user experience when running applications on any type of computer, television, and/or mobile device. When transitioning from one device to the next while utilizing applications, engaging in video games, watching videos, listening to music, etc., services and applications operate substantially similarly in all environments for a common user experience.

[0039] In the example system 400, multiple devices may be interconnected by a central computing device, which may be local to the multiple devices or may be located remotely from the multiple devices. In one embodiment, the central computing device may be a cloud of one or more server computers connected to the plurality of devices through a network (Internet) or other data communication link. In an embodiment, the interconnection architecture enables functionality across multiple devices to provide a common and seamless experience to users of the multiple devices. Each of these devices may have different physical requirements and capabilities, and the central computing device uses a platform that allows for an experience that is tailored to a particular device, yet is common to all devices. In one embodiment, a class of target devices is created, and the user experience is tailored to this generic device class. A class of devices may be defined by their physical characteristics, type of use, or other common characteristics.

[0040] In different implementations, client device 102 may be implemented in a variety of different configurations, such as for computer 402, mobile device 404, and television 406 uses. Each of these configurations includes devices that may have generally different configurations and capabilities, and client devices may be configured in one or more of the different device classes. For example, a client device may be implemented as any type of personal computer, desktop computer, multi-screen computer, laptop computer, tablet, netbook, or the like.

[0041] Client device 102 may also be implemented as any type of mobile device, such as a mobile phone, portable music player, portable gaming device, tablet computer, multi-screen computer, and the like. The client device may also be implemented as any type of television device with or connected to a generally larger screen in a casual viewing environment. These devices include TVs, set-top boxes, game consoles, and more. The techniques described herein can be supported by these different configurations of client devices and are not limited to the particular instance of the email trust service described herein.

[0042]Cloud 408 includes and/or represents platform 410 for email service 412 . The platform abstracts the underlying functionality of hardware, such as server devices, and/or the software resources of the cloud. Email services may include applications and/or data that may be utilized when computer processing is performed on a server remote from the client device. For example, an e-mail service may include, for example, the reference figure 1 Email distribution service 106 and/or email trust service 120 are depicted. Email service 412 may be provided as a service over the Internet and/or over a user network such as a cellular or WiFi network.

[0043] Platform 410 can abstract the resources and functionality to connect client device 102 with other computing devices. The platform can also be used to abstract resource scaling to provide a level of scale commensurate with the requirements encountered for services performed via the platform. Thus, implementation of the functionality of email application 126 may be distributed throughout system 400 in one interconnected device embodiment. For example, email application 126 may be implemented partially on the client device and via a platform that abstracts the functionality of the cloud.

[0044] Example methods 500 and 600 according to one or more embodiments of the email trust service refer to the corresponding Figure 5 and Image 6 to describe. In general, any of the functions, methods, procedures, components and modules described herein can be implemented using software, firmware, hardware (eg, fixed logic circuitry), manual processing, or any combination thereof. A software implementation represents program code that performs specified tasks when executed by a computer processor. The example methods may be described in the general context of computer-executable instructions, which may include software, applications, routines, programs, objects, components, data structures, procedures, modules, functions, and the like. Program code can be stored in one or more computer readable memory devices local to the computer processor and/or remote from the computer processor. The methods can also be practiced by multiple computer devices in a distributed computing environment. Furthermore, the features described herein are platform independent and can be implemented on a wide variety of computing platforms with a wide variety of processors.

[0045] Figure 5 An example method 500 for an email trust service is shown and described with reference to an email distribution service. The order in which the method blocks are described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement a method or an alternate method.

[0046] At block 502, an email message is received for distribution to client devices corresponding to recipients of the email message. For example, email distribution service 106 ( figure 1 ) receives email messages 108 for distribution to different client devices 104 corresponding to the respective recipients of those email messages.

[0047] At block 504, authentication techniques are applied to the email message to verify that the email message was received from an authorized domain. For example, email trust service 120 applies authentication techniques to email message 108 to verify that the email message was received from an authorized domain as specified in the sender address field of the email message. The authentication technology may include Domain Keys Identified Mail (DKIM) authentication technology and/or SenderID authentication technology. The email trust service may prevent delivery of the email message to the client device if the authentication technique indicates that the email message was not received from an authorized domain. Alternatively, the email trust service may associate a non-trust indicator with the email message, which is then displayed at the client device along with the email message to indicate to the email recipient that the email message is not trusted.

[0048] At block 506, it is determined whether an extended validation certificate is associated with an authorized domain. For example, email trust service 120 determines whether extended validation certificate 116 is associated with an authorized domain. In an embodiment, the email trust service determines whether an extended validation certificate is associated with an authorized domain by extracting the domain name from the sender address field of the email message and then checking the certificate provided by the website associated with the domain name. If the email trust service determines that the certificate is not an extended validation certificate, the email trust service may prevent delivery of the email message to the client device. Alternatively, the email trust service may associate a non-trust indicator with the email message, which is then displayed at the client device along with the email message to indicate to the email recipient that the email message not trusted.

[0049] At block 508, a trust indicator is associated with the email message to generate a trusted email message. For example, email trust service 120 associates trust indicator 118 with email message 108 to generate trusted email message 122, eg, upon determining that an extended validation certificate is associated with an authorized domain. In an embodiment, the trust indicator is a website icon associated with the domain name specified in the sender address field of the trusted email message. For example, the email trust service requests a favicon from a website associated with the authoritative domain and is configured to distribute a favicon, and then receives the favicon from the website. Additionally, the email trust service may cache extended validation certificates and website icons for use in authenticating attached email messages.

[0050] At block 510, the trusted email message is transmitted to the client device for displaying the trusted email message with a trust indicator. For example, the email distribution service 106 transmits the trusted email message to the client device 102 corresponding to the recipient of the email message to display the trusted email message along with the trust indicator. The email distribution service generates a displayable version of the trusted email message for display at the client device, and a trust indicator is displayed adjacent to the trusted email message to indicate to the email recipient that the email message is trusted. The email distribution service also generates a list view of the email message for display at the client device, wherein the list view is displayed with trust indicators as website icons proximate to the trusted domains the email message was received from. email message.

[0051] At block 512, a request to add an authorized domain to an email safe list or to an email block list is received, and at block 514, based on the request, an authorized domain is added to an email safe list or to an email block list . For example, email trust service 120 at email distribution service 106 receives from client device 102 a request to add the authorized domain specified in the sender address field of the email message to email safe list 130 or to email block list 132. user request. The email trust service then adds the domain to an email safe list or to an email block list.

[0052] Image 6 An example method 600 of an email trust service is shown and described with reference to a client device. The order in which the method blocks are described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement a method or an alternate method.

[0053] At block 602, a request to download an email message for display is transmitted to an email distribution service. For example, client device 102 ( figure 1 ) transmits to the email distribution service 106 a request for an email message that has been sent to the user of the client device. At block 604, a trusted email message is received from an email distribution service. For example, client device 102 receives trusted email message 128 from email distribution service 106 , such as when a user at the client device launches email application 126 that requests, receives, and processes email messages.

[0054] At block 606, the trusted email message is displayed along with a trust indicator associated with the trusted email message. For example, client device 102 displays trusted email message 128 along with a trust indicator associated with the trusted email message (eg, on display device 146 or on an integrated display). In an embodiment, the trust indicator is displayed as a website icon associated with the domain name specified in the sender address field of the trusted email message. For example, trust indicator 204 ( figure 2 ) is displayed next to the trusted email message 202 to indicate that the email message is trusted. Similarly, trust indicator 304 ( image 3 ) is displayed in the list view 302 of email messages as a web icon next to the email message to indicate that the email message is trusted.

[0055] At block 608, a selection of a trust indicator is received, and at block 610, a user interface is displayed from which a user may request that the domain name be added to an email safe list or to an email block list. For example, client device 102 receives user selection of trust indicator 306 to initiate display of user interface 308 that enables the user to request that a domain be added to email safe list 130 or to email block list 132 . At block 612, a user request is communicated to the email distribution service to update the email safe list or email block list based on the request. For example, client device 102 transmits a request from the user to email distribution service 106, where email trust service 120 updates email safe list 130 or email block list 132 based on the request.

[0056] Figure 7 shows that can be implemented as referring to the previous Figure 1-6 The various components of device 700 are examples of any device or service implemented by the device described. In an embodiment, the device may be implemented as a fixed or mobile device in any form of consumer, computer, server, portable, user, communication, telephone, navigation, television, appliance, game, media playback, and/or electronic device any one or combination. The device may also be associated with a user (ie, a person) and/or an entity that operates the device, such that a device describes a logical device including a user, software, firmware, hardware, and/or a combination of devices.

[0057] The device 700 includes a communication device 702 that allows for wired and/or wireless communication of device data 704, such as received data, data that is being received, data scheduled to be broadcast, data packets of data, and the like. Device data or other device content may include configuration settings for the device, media content stored to the device, and/or information associated with a user of the device. Media content stored on a device may include any type of audio, video and/or image data. The device includes one or more data inputs 706 via which any type of data, media content and/or input may be received, such as user selectable input, messages, communications, music, television content, recorded video content and any other type of audio, video and/or image data received from any content and/or data source.

[0058] Device 700 also includes a communication interface 708, such as any one or more of a serial, parallel, network, or wireless interface. A communication interface provides a connection and/or a communication link between a device and a communications network through which other electronic, computing, and communication devices communicate data with the device.

[0059] Device 700 includes one or more processors 710 (eg, any microprocessor, controller, etc.) that process various computer-executable instructions in order to control the operation of the device. Alternatively or in addition, the apparatus may be implemented using any one or combination of software, hardware, firmware, or fixed logic circuitry implemented in conjunction with the processing and control circuitry identified generally at 712 . Although not shown, the device may include a system bus or data transmission system coupling the different components within the device. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus.

[0060]Device 700 also includes one or more memory devices (eg, computer-readable storage media) 714 that allow data storage, such as random access memory (RAM), non-volatile memory (eg, read-only memory (ROM), flash memory, etc. ) and disk storage devices. The disk storage device may be implemented as any type of magnetic or optical storage device, such as a hard drive, recordable and/or rewritable disk, and the like. Devices may also include mass storage media devices.

[0061] Computer readable media can be any one or more available media that can be accessed by a computing device. By way of example, and not limitation, computer readable media may comprise storage media and communication media. Storage media includes volatile and nonvolatile media, removable and non-removable media, used in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data accomplish. storage media including, but not limited to, RAM, ROM, EEPROM, flash memory or other storage technology, CD-ROM, digital versatile disk (DVD) or other optical storage device, magnetic cartridge, tape, magnetic disk storage device or other magnetic storage device, or Any other medium that can be used to store information and that can be accessed by a computer.

[0062] 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. Communication media also 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 into the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[0063] Memory device 714 provides a data storage mechanism for storing device data 704 , other types of information and/or data, and various device applications 716 . For example, an operating system 718 may be maintained as a software application using a memory device and executed on a processor. Device applications may also include device managers, such as any form of control application, software application, signal processing and control modules, code native to a specific device, a hardware abstraction layer for a specific device, and the like.

[0064] In this example, device applications 716 include email application 720, such as when device 700 is implemented as a client device. Alternatively or in addition, the device application includes an email trust service 722, such as when the device is implemented as an email distribution service. Email applications and email trust services are shown as software modules and/or computer applications. Alternatively or in addition, the email application and/or email trust service may be implemented as hardware, software, firmware, fixed logic, or any combination thereof.

[0065] Device 700 also includes audio and/or video processing system 724 that generates audio data for audio system 726 and/or generates display data for display system 728 . An audio system and/or display system may include any device that processes, displays and/or otherwise reproduces audio, video, display and/or image data. Display data and audio signals may be transmitted to an audio device and/or display via an RF (Radio Frequency) link, S-Video link, Composite Video link, Component Video link, DVI (Digital Visual Interface), analog audio connection, or other similar communication link equipment. In an implementation, the audio system and/or the display system are external components of the device. Alternatively, the audio system and/or display system are integral components of the example device.

[0066] Although embodiments of the email trust service have been described in language specific to features and/or methods, the subject matter of the appended claims is not necessarily limited to the specific features or methods described. Rather, these specific features and methods are disclosed as example implementations of an email trust service.