Abstract: A hash module of a mail sender creates a hash data context structure. The hash module processes the headers and the body of an e-mail message in the order required, for example by the DKIM specification, until the data to be hashed has been input. The hash module converts the context structure into printable characters and the encoded structure is transmitted over the Internet or other network to the next participating system. The token authority's hash module decodes the context back into binary form. After ensuring business logic is satisfied, it generates additional headers required for signature, which are then added to the developing hash. The hash module finalizes the hash function and creates the hash value. The authorization module creates the signature and returns it to the e-mail module, which attaches the signature to the message and transmits it to the destination mailbox provider, which verifies the token.

Abstract: A hash module of a mail sender creates a hash data context structure. The hash module processes the headers and the body of an e-mail message in the order required, for example by the DKIM specification, until the data to be hashed has been input. The hash module converts the context structure into printable characters and the encoded structure is transmitted over the Internet or other network to the next participating system. The token authority's hash module decodes the context back into binary form. After ensuring business logic is satisfied, it generates additional headers required for signature, which are then added to the developing hash. The hash module finalizes the hash function and creates the hash value. The authorization module creates the signature and returns it to the e-mail module, which attaches the signature to the message and transmits it to the destination mailbox provider, which verifies the token.

Abstract: Effective aspects of stamping outbound e-mail are combined with a registration system for e-mail senders. A mail sender participates by registering From: line information with a trusted third-party repository known as a stamp authority. When the sender sends an e-mail message, a hash of the From: line is compared against the From: line information for the sender stored in the repository. If the result is a match, the e-mail is allowed to be sent, subject to any other restrictions imposed by the stamping process. If there is not a match, then the e-mail is prevented from being stamped.

Abstract: Effective aspects of stamping outbound e-mail are combined with a registration system for e-mail senders. A mail sender participates by registering From: line information with a trusted third-party repository known as a stamp authority. When the sender sends an e-mail message, the From: line is compared against the From: line information for the sender stored in the repository. If the result is a match, the e-mail is allowed to be sent. If there is not a match, then the e-mail is prevented from being stamped.

Abstract: Certification of embedded content in e-mail is provided. A sender wishing to have code certified for inclusion in e-mail sends the code to a token authority. A code verification engine acting automatically or in conjunction with an analyst examines the code to determine whether it poses a risk of harm to e-mail recipients. If not, the token authority issues a certificate for the embedded content. The mail sender sends e-mail to recipients including the embedded content, and the certification is sent in conjunction with the content itself. A mailbox provider inspects the received e-mail to determine whether it includes embedded content and, if so, whether a certification is attached that the embedded content is not harmful. If not, or if the message includes uncertified content in addition to certified content, then the message is rejected, or delivered with a warning that certification is not present.