Classifications

• • 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
• • 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/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
• • 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/48—Message addressing, e.g. address format or anonymous messages, aliases
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/12—Applying verification of the received information
  • H04L63/126—Applying verification of the received information the source of the received data
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Definitions

• FIG. 4 is a block diagram of a system including a computing device.
• multi-tenant hosting provider 120 may send an "EHLO" command to stand-alone organization 1 10 via SMTP.
• Stand-alone organization 1 10 may reply with a list of supported SMTP extensions, such as "DSN,” “STARTTLS,” and/or "SIZE". Consistent with embodiments of the invention, stand-alone organization 1 10 may indicate in the reply that it supports an attribution data element extension, such as by including an extension name of "XOORG" in the list of supported extensions.
• FIG. 2 is a flow chart setting forth the general stages involved in a method 200 consistent with embodiments of the invention for providing message source validation and attribution.
• Method 200 may be implemented using a computing device 400 as described in more detail below with respect to FIG. 4. Ways to implement the stages of method 200 will be described in greater detail below.
• Method 200 may begin at starting block 205 and proceed to stage 210 where computing device 400 may receive a message from a source organization.
• multi-tenant hosting provider 120 may receive a message from hosting tenant 125(A) for a recipient at stand-alone system 1 10
• the multi-tenant system may validate hosting tenants (e.g., hosting tenants 125(A)-B) and/or filtering tenants 135(A)-(B)), such as by requiring verifiable changes be made to domain ownership records by organizations seeking to host their e-mail communications associated with a given domain at multi-tenant host provider 120 and/or utilize services provided by multi-tenant e-mail filtering provider 130.
• hosting tenants e.g., hosting tenants 125(A)-B
• filtering tenants 135(A)-(B) such as by requiring verifiable changes be made to domain ownership records by organizations seeking to host their e-mail communications associated with a given domain at multi-tenant host provider 120 and/or utilize services provided by multi-tenant e-mail filtering provider 130.
• the multi-tenant system may also be operative to identify a sender of messages received by the multi-tenant system for delivery to one of its tenants.
• the multi-tenant system may have sufficient data (e.g. a fully qualified domain name (FQDN) in a message source organization's certificate) to identify stand-alone system 110 and may reliably attribute incoming messages to the first party based on a securely authenticated communication channel.
• FQDN fully qualified domain name
• computing device 400 may, for example, use an SMTP protocol extension.
• An XOORG command may be implemented within the SMTP framework and/or an XOORG parameter may be included in the existing "MAIL FROM:" command within the SMTP standard framework.
• the separate XOORG command may be used to transmit attribution data associated with multiple messages transmitted from a given source organization (e.g., a particular tenant from a multi-tenant system) during a single SMTP session while the XOORG parameter of the "MAIL FROM:” command may be varied for each message.
• the protocol extension may allow the receiving system to decide whether a message may be trusted before all the recipients and actual message data is received.
• the attribution data may be added to the message itself and transmitted in a header such as "X-Originator Organization".
• the value of the header may comprise the identity of the organization on whose behalf the message is being sent, and may comprise a fully -qualified domain name.
• the SMTP extension and the header are not mutually-exclusive and both may be provided.
• the data supplied in the protocol parameter may take precedence over the header value. If a discrepancy is detected by the receiving MTA, it may re-stamp the header to match the protocol parameter value.
• a system consistent with an embodiment of the invention may include a computing device, such as computing device 400.
• computing device 400 may include at least one processing unit 402 and a system memory 404.
• system memory 404 may comprise, but is not limited to, volatile (e.g. random access memory (RAM)), nonvolatile (e.g. read-only memory (ROM)), flash memory, or any combination.
• System memory 404 may include operating system 405, one or more programming modules 406, and may include a message transport agent (MTA) 407.
• Operating system 405, for example, may be suitable for controlling computing device 400' s operation.
• Embodiments of the invention may be practiced in conjunction with a graphics library, other operating systems, or any other application program and is not limited to any particular application or system. This basic configuration is illustrated in FIG. 4 by those components within a dashed line 408.
• Computing device 400 may have additional features or functionality.
• computing device 400 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape.
• additional storage is illustrated in FIG. 4 by a removable storage 409 and a non-removable storage 410.
• Computing device 400 may also contain a communication connection 416 that may allow device 400 to communicate with other computing devices 418, such as over a network in a distributed computing environment, for example, an intranet or the Internet.
• Communication connection 416 is one example of communication media.
• embodiments of the present invention may take the form of a computer program product on a computer-usable or computer- readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system.
• a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
• the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Computer Hardware Design (AREA)
• Computing Systems (AREA)
• General Engineering & Computer Science (AREA)
• Information Transfer Between Computers (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Priority Applications (10)

Applications Claiming Priority (2)

Publications (2)

Family

ID=44973578

Family Applications (1)

Country Status (10)

Cited By (1)

Families Citing this family (15)

Citations (3)

Family Cites Families (40)

• 2010
  • 2010-05-21 US US12/785,348 patent/US8707420B2/en active Active
• 2011
  • 2011-05-02 KR KR1020127030390A patent/KR101784756B1/ko not_active Expired - Fee Related
  • 2011-05-02 CN CN201180025046.3A patent/CN102918810B/zh active Active
  • 2011-05-02 CA CA2798124A patent/CA2798124C/en not_active Expired - Fee Related
  • 2011-05-02 KR KR1020177027593A patent/KR101903923B1/ko active Active
  • 2011-05-02 JP JP2013512630A patent/JP6092098B2/ja active Active
  • 2011-05-02 AU AU2011256698A patent/AU2011256698B2/en not_active Ceased
  • 2011-05-02 RU RU2012149431/08A patent/RU2569806C2/ru not_active IP Right Cessation
  • 2011-05-02 WO PCT/US2011/034800 patent/WO2011146232A2/en not_active Ceased
  • 2011-05-02 BR BR112012029427-0A patent/BR112012029427B1/pt active IP Right Grant
  • 2011-05-02 EP EP11783939.9A patent/EP2572328B1/en active Active
• 2014
  • 2014-04-22 US US14/258,140 patent/US9253126B2/en active Active

Patent Citations (3)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events