Common Questions
What programs does RPost support?
RPost has a “Send Registered” button software for Microsoft Outlook (2000, 2002, XP, 2003, 2007, 2010), Lotus Notes (5, 6, 7, 8), Novell GroupWise (5, 6), Outlook Express and Windows Mail and BlackBerry. RPost also has service available for webmail (Hotmail, Yahoo, Gmail), Zimbra, Salesforce.com, and Macs and from the server as well using no software at all. Read More
The email receipt functionality exists in Microsoft Outlook. What can Registered Email® offer me that Outlook message tracking and read receipts cannot?
Microsoft Exchange can utilize the read receipt and delivery receipt features for message tracking for internal messages. Microsoft Outlook can also request a read receipt for external Internet messages. The Microsoft read receipt feature however requires interaction and compliance on the part of the recipient as well as a compatible mail client. Such a read receipt is also a plain text file that offers no protection of integrity. This is very different from the service RPost offers. RPost creates a Delivery Receipt that will prove the official time sent and delivered, the content (including any attachments) delivered and the delivery status. RPost uses industry standard cryptographic technologies in a unique way to ensure that validity and integrity of the receipt. Read More
We have a PKI implementation in our environment. Does this eliminate the need for Registered Email service?
No. A PKI implementation does not eliminate the need for Registered Email®. In an environment where a PKI system is correctly implemented, digital certificates can be used to provide message integrity, confidentiality, authenticity and non-repudiation. The recipient of a message can use the PKI system to prove the integrity and authenticity of a message assuming the chain of CA trust is valid and unbroken. However, the sender cannot use PKI to prove that a message was delivered to an external recipient. In fact the PKI system does nothing for the sender to verify and prove message delivery. The RPost system can work in conjunction with the PKI system to add value to the messaging process with proof of delivery. Further, RPost Digital Seal technology can extend authentication to the second, third+ recipient as email is forwarded (recipients can verify authorship and original content). With PKI systems, often the act of forwarding an email breaks the capability for a future recipient to verify the email origin and authenticity.
How does Registered Email® service integrate with PKI implementations?
1. Outlook Digital Certificate Integration options.
The RPost Add-In for Microsoft Outlook has the option to integrate with users' digital certificates. However, this option is only compatible with certain PKI implementations. The Registered Email® software can utilize commercial X.509 certificates that are stored in the Outlook Local Address Book for recipients. The user can configure one certificate from the local user certificate store to be defined as the email user certificate. If this option is used in Outlook, a user can send "Registered" messages that are encrypted and signed using the RPost Add-In.
2. RPost Mail Server Filter and PKI Integration.
If an RPost Mail Server Filter is installed then mail clients can send "Registered" messages using the subject-line tagging method. If this method is used, then messages can be encrypted using any PKI implementation.
How can I trust the security of the RPost system?
Security is of paramount importance to RPost at every level. To this end all business infrastructure, procedures and policies are designed to meet strict security standards. RPost classifies all customer email as both sensitive and critical and takes appropriate measures to ensure the security and availability of this information. Also note that RPost information systems do not store customer messages. Third party accreditation of RPost infrastructure and operations was undertaken by the United States Postal Service in the form of a Security Certification & Accreditation process. This was broad in scope covering everything from network security to financial stability and viability. Various USPS contractors were used in the process including TRW and PriceWaterhouseCoopers. The conclusion of the process was that RPost's infrastructure and operations ensure scalability, security, availability, performance and resilience.
For further information on RPost security request the whitepaper: "RPost Security Certification" from
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
Can you prove that the message was opened?
The RPost system uses a variety of methods to establish the delivery status of Registered Email®. The ability to prove whether the message was opened depends on the technical configuration of the recipient environment. RPost can prove a message was opened in some but not all cases.
Can the recipient mail server prevent you from proving delivery?
The minimum standard for proof of email delivery is delivery to the mail server. If a message is delivered, the RPost system will gather evidence to prove this in 100% of cases.
Is any action required on the part of the recipient to prove delivery?
No action is required on the part of the recipient to prove delivery. If the recipient acknowledges delivery through the use of existing read receipt technology (eg. Microsoft Outlook read receipt) then this information with be utilized to further enhance the delivery status information.
When I opened your email, a pop up appeared asking me to confirm receipt. I marked "no". Did you still obtain a receipt for the delivery?
Yes. Confirmation of receipt by the end user is not required to prove delivery. However, if the end user does confirm receipt in this way the information will be used.
