The technology* behind Dynamic Mail Content
Dynamic Mail Content mail messaging
The following takes place when sending, reading or editing a dynamic content mail message:
- When mail is composed, the mail client sends the message content and any attachments to a content server for storage and management
- The content server stores the content in a file and returns a pointer to the content
- The mail client stores the content pointer in the mail header (and, optionally, attachment content pointers in the respective MIME attachment headers), stores a canned message in the message body and sends the message through the mail system
- When the recipient receives the message, the mail client fetches the content pointer from the header and uses it to send a request to the content server to retrieve the message content
- The content server fetches the content and returns it to the mail client for display
- If the recipient opens an attachment, the attachment content is retrieved the same way as above
- In order to edit a mail message, the sender selects the message to be edited and makes the desired changes
- The mail client sends an update request, along with the content pointer contained in the original message and the edited content, to the content server
- The content server replaces the content of the original message with the edited content
- Attachment editing is done the same way as above
Authentication
All commands for sending, reading or editing dynamic content sent by the mail client to the content server include the user's e-mail address and password. Thus, spoofing a dynamic content message is only possible if the spoofer knows the password of the user he is trying to spoof.
Secure communications and storage
All data transferred between the mail client and the content server is encrypted, using the same technology to secure credit card transactions in transit. Thus, there is very little chance that your mail would be intercepted and read by unauthorized users when it's sent via dynamic content. The content may optionally be stored encrypted, to provide further protection.
* Protected under US Patent #5,815,663
