Electronic Message System with Federation of Trusted Senders

An electronic challenge message having a data structure generated by an authorized server, the electronic challenge message comprising:

• an envelope portion identifying a sender and a recipient;
• a content portion containing data to be delivered to the recipient;
• and
• a federated token embedded in a field in one of the envelope portion or content portion identifying the authorized server, the federated token configured to be authenticated and validated by a second authorized server and used to deliver the challenge message to the recipient's inbox without the second authorized server generating a second challenge message.

An authorized server configured to process challenge messages, the authorized server comprising:

• a processor configured to execute computer-executable instructions;
• an authorization module comprising computer-executable instructions that are executable by the authorized server to:
• receive a first challenge message from a second server, the first challenge message comprising:
• an envelope portion identifying a first user associated with the first server as a recipient of the first challenge message and a second user associated with the second server as a sender of the first challenge message;
• a content portion containing data to be delivered to the first user;
• and
• a first federated token embedded in a field in one of the envelope portion or content portion, the first federated token identifying the second server;
• and
• determine at least one of whether the first federated token is authentic and whether the first federated token is valid;
• a tokenization module comprising computer-executable instructions that are executable by the authorized server to generate a second challenge message identifying a third user associated with the second server as a recipient of the second challenge message and a fourth user associated with the first server as a sender of the second challenge message, the second challenge message comprising:
• a second federated token configured to be authenticated and validated by the second server and used to deliver the second challenge message to an inbox of the third user without the second server generating a third challenge message in response to receiving the second challenge message.

The authorized server of claim 30, wherein the computer-executable instructions that are executable to exchange one or more partner keys with the second server include computer-executable instructions that are executable by the authorized server to perform at least one of:

• passing the second challenge message through a certificate authorizing server;
• sending the one or more partner keys to the second server with the second challenge message;
• or
• sending a message subsequent to the second challenge message to the second server, the subsequent message containing the one or more partner keys.

An authorized server configured to process challenge messages, the authorized server comprising:

• a processor configured to execute computer-executable instructions;
• computer-executable instructions that are executable by the authorized server to transmit an original message generated by a first user associated with the authorized server to a second server, the original message indicating a second user associated with the second server to receive the original message;
• an authorization module comprising computer-executable instructions that are executable by the authorized server to:
• receive a first challenge message from the second server, wherein the first challenge message was generated in response to the first user being unknown to the second user, the first challenge message comprising:
• an envelope portion identifying the first user as a recipient of the first challenge message and the second user as a sender of the first challenge message;
• a content portion containing data to be delivered to the first user;
• and
• a first federated token embedded in a field in one of the envelope portion or content portion, the first federated token identifying the second server;
• determine at least one of whether the first federated token is authentic and whether the first federated token is valid;
• and
• deliver the first challenge message to an inbox of the first sender when the first challenge message is at least one of authentic and valid;
• and
• a tokenization module comprising computer-executable instructions that are executable by the authorized server to generate a second challenge message identifying a third user associated with the second server as a recipient of the second challenge message and a fourth user associated with the first server as a sender of the second challenge message, the second challenge message comprising:
• a second federated token configured to be authenticated and validated by the second server and used to deliver the second challenge message to an inbox of the third user without the second server generating a third challenge message in response to receiving the second challenge message.