All messages sent using the RMail service are transmitted as Registered Email™ messages and return a Registered Receipt™ email record to the sender to certify and prove email delivery, content and timestamp, without requiring any compliant action from the recipient. 

The Registered Receipt email has the capability to authenticate and accurately reproduce the original email and attachments, including any attached disclosures, which satisfies the E-Sign Act’s retention and accurate reproduction requirements. And the Registered Receipt email, because it can be provided to third parties and used to authenticate the content and attachments to the email, may be retained by creditors to enable access to parties entitled to access to the records for the period required by law, which satisfies the E-Sign Act’s access requirements.

When a Registered Receipt email is verified by sending it to the address verify@rpost.net, the sender receives a Receipt Authentication email. The RPost system verifies the receipt’s integrity, re-constructs the original delivery audit trail and transmission times and associates that delivery with the message content including attachments and sends this information by email in a Receipt Authentication message back to the party that submitted the receipt for verification. Without verifying the receipt, the message delivery, content and times may be subject to disputes similar to a traditional email.

The Registered Receipt email is a self-contained and self-authenticating record of an RMail message.  The receipt documents the entire email transaction and is durable, portable, and verifiable for proof sending, delivery, content and official time, sent and received.

The attached HTMLReceipt.htm file contains a digitally signed copy of the original email, attachments, audit trail, delivery information, digital fingerprints, and official times.  This information is cryptographically signed and embedded in the Registered Receipt email with no copy stored in the RPost Cloud.