Skip to main content

Receipt Authentication email

Updated

All messages sent using the RMail service are transmitted as Registered Email™ messages and return a Registered Receipt™ email record to the sender.

The Registered Receipt email has the capability to authenticate by being sent to verify@r1.rpost.net and accurately reproduce the original email and attachments, including any attached disclosures, which satisfies the E-Sign Act’s retention and accurate reproduction requirements. 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. Registered Receipts can be authenticated for as long as you have a copy of that Receipt.

When a Registered Receipt email is authenticated, the sender and the party that submitted the original receipt receive a Receipt Authentication email. Without verifying the receipt, the message delivery, content and times may be subject to disputes similar to a traditional email.

This article covers the following topics:

 

Understanding each section of the of the Receipt Authentication email

The following segment breaks down the Receipt Authentication email into its basic components with an explanation of each section in greater detail. Click on any of the following links to jump to that section:

Message Header

1111.png

Details:
- Subject: Receipt: <Original email subject>
- From: Authentication
- From email address: support@r1.rpost.net
- To: Address sending for verification and the sender's address

 

Receipt Authentication Attachments

22222.png

Details:
- Original Email: The first attachment is the original email and attachments sent to the recipient.
- Server Logs: All other attachments are various transmission logs including any SMTP Logs, SMTP history, HTTP, MUA and DSN records.

Original email

333.png

Server logs

444.png

 

Delivery Status Section

55555555.png

Details:
- Address: This column lists all the addresses the RMail message was sent to, including the Bcc recipients.
- Status: RMail uses algorithms to translate the SMTP and additional transmission data for a clear indication of the status of the message. The delivery status is unique for each recipient with one of four statuses available:
- Delivered and Opened: This status means the email was opened between the time the email was delivered to the recipient and the time the Registered Receipt email was issued. If an email is opened after the receipt is issued and within 30-days the email was sent, the sender may receive an Open Receipt. This is the highest level of delivery.
- Delivered to Mailbox: This status means the email was received by the recipient’s mail system and placed in the partition of the mail server where the recipient collects email. This is the second highest level of delivery.
- Delivered/Relayed to Mail Server: This status means the message was delivered, and accepted, by the recipient’s authorized agent for collecting Internet email. This is the baseline for delivery of an email.
- Delivery Failure: This is the only non-delivery status. The email was unable to be delivered to the recipient. Possible reasons for this status include but not limited to the following:
The recipient mailbox is full
The email was sent to a bad address
The email was too large for the recipient’s set maximum size
The recipient’s email system is down at the time of receiving
- Details: This column lists the highlights from the recorded server information to give the sender additional information as to what status is shown in the Status column. When the status is Delivered and Opened, the open detection methods will be one or both of the following:
- MUA: The recipient’s Mail User Agent (Outlook or other) was used to detect the email was opened.
- HTTP: The RMail web call-out (US Patents 9,432,313; 8,161,104, among others) was used to detect the email was opened
- Delivered (UTC): This is the time the email was accepted as delivered by the recipient’s mail system in the UTC time zone.
- Delivered (local): This is the time the email was accepted as delivered by the recipient’s mail system in the time zone of the sender’s mail system.
Note: The offset is in +/- the hour offset from UTC and takes into account daylight savings time if observed. If the UTC and Local times are identical, it may be the sending server is not set to offset for the local time. If this is the case, the offset can be changed for the sender (or customer account) to reflect the true local time
- Opened (local): This is the time the email was detected as being opened in the sender’s local time zone.
Note: Not all emails will be detected as opened, even if the recipient opens the email.

 

Message Envelope

6666.png

Details:
- From: This is the sender’s email address
- Subject: This is the sender’s email subject
- To: Recipients in the sender’s “To” field
- Cc: Recipients in the sender’s “Cc” field
- Bcc: Recipients in the sender’s “Bcc” field
- Network ID: This is the sender’s network server identification address
- Received by the RMail System: This is the time the email was received by the RPost Cloud and the same time as the Received by RMail time located in the Acknowledgement email.
Note: This time is typically seconds earlier than the Delivered (UTC) time located in the Delivery Status section of the receipt.
- Client Code: If a sender assigns a Client/Reference code to the email at the time of sending, the code will be located in this row.

 

Message Statistics

7777777.png

Details:
- Tracking Number: This is a unique number assigned and used to identify this specific transaction. There are no two Message IDs that are the same.
- Message Size: This is the cumulative size of the email body and all attachments in bytes.
- Features Used: The RMail features used for a specific message and are displayed with icons. A full list of features used may be viewed here: https://www.rmail.com/support/featuresused/.
Note: Icons will also be displayed in the Details column of the Delivery Status section of the receipt for all RMail messages sent except when sent as Track & Prove - Marked as a Registered Email message.
- File Size: This displays the size of each attachment.
- File Name: This displays a list of all attachments with file type extensions

 

Delivery Audit Trail

8888.png

Details:
The Delivery Audit trail is a recording of the Internet transaction metadata for each recipient. Listed in this section is the SMTP dialogue as well as other transmission data which is a statement of fact as to as to the transmission of the message to each recipient. This information is recorded in its original form and translated by RMail into the information seen in the Delivery Status section of the receipt.

 

How to authenticate an Open Receipt

In case of an escalated dispute or question involving an Open Receipt, this receipt may be further authenticated anytime by forwarding it to the verification address verify@r1.rpost.net along with its attached HTMLReceipt.htm file. The resulting Open Receipt authentication email will then be sent to both the submitter of the receipt and the original sender of the RMail message to show proof and authenticity. No copies of these are stored in the RPost Cloud.

The Open Receipt Authentication email is similar in appearance to the Open Receipt email except for the attachments.

000000.png

The Open Receipt Authentication contains the following attachment.

- The information inside the Open Receipt email in XML format.

Note: The data presented in the Receipt Authentication is stored inside the Open Receipt email itself, not inside the RPost Cloud.

 

Video: Receipt Authentication Email

The following short videos explains how you can both prove and verify than an email was sent and delivered using RMail, as well as authenticate the content of the received email.

This video uses RMail app for Outlook Desktop

This video uses RMail app for Gmail