RMail provides multiple methods to transmit emails for processing, including popular options like Microsoft Outlook. Two key integration methods allow customers to easily integrate RMail into their applications. The first method uses the RMail domain extension via SMTP x-headers to create simple, one-way integrations for sending RMail messages from an application. The second method involves using the RMail REST APIs, which is the recommended approach for building feature rich full-fledged two-way integrations.
If you are looking to integrate with RMail and would like to explore the options in depth, contact your RPost representative who will involve our dedicated Integrations team to assess your requirements and advise.
On this article, we’ll review the RMail domain extension method.
Note: Only eligible customers and partners can use the RMail domain extension method. If you are not sure if you are eligible, please contact our Support team, or your Customer Success or Sales representative.
Sending Registered Email™ messages using SMTP
Emails can be routed to the RMail Cloud platform by adding a specific domain extension to the recipient's email addresses and including the subject line indicators or X-headers that correspond to the RMail features you would like to apply.
To route your email message to the RMail Cloud platform, follow these steps:
1. Compose the email.
2. Add the custom domain extension (suffix) shared by your RPost representative to all recipient’s email addresses (for example, amy@gmail.com.[suffix])
3. Add the subject line indicator or x-headers required to enable the RMail features you need for the message.
4. Send the email.
The message is routed to the RMail cloud platform for processing. The selected features are applied, and the email is then sent to the recipients.
Subject line indicators and X-headers
By adding subject line indicators and/or X-headers to your message, you can enable the desired RMail services and features to initiate the function within the platform.
Subject Line Indicators
RMail uses subject line tagging to indicate which feature should be applied to the message. Add the indicator at the beginning of the subject line, before the rest of your subject text.
The format is: [Indicator] [Subject]
Considerations:
1. The indicator must be added at the beginning of the subject line.
2. Indicators are not case sensitive.
3. A space may or may not be added after the indicator and before the subject text.
4. The subject line indicators may be combined to send a message using multiple RMail® features at a time. Simply append the required indicators one next to the other, like this:
[Indicator] [Indicator] [Subject]
The following is a list of the subject line indicators available.
Service/Feature |
Subject Indicator |
Sample Subject |
Track & Prove |
|
|
Marked Registered Email (default) |
None |
Important Email |
Unmarked Registered Email |
(C), ©, or (c) |
(C) Important Email |
Encryption |
|
|
Automatic: System password generated, always sent by email |
RPSX() |
RPSX() Important Email |
Custom: Password sent according to RPortal settings |
RPSX(password) |
RPSX(pass1234) Important Email |
Custom: Always send password by email |
RPSY(password) |
RPSY(pass1234) Important Email |
Custom: Never send password by email |
RPSZ(password) |
RPSZ(pass1234) Important Email |
E-Sign |
|
|
Hand Sign |
(RPX) |
(RPX) Important Email |
Sequential Hand Sign |
(RPXS) |
(RPXS) Important Email |
Email Sign |
(RPY) |
(RPY) Important Email |
Sequential Email Sign |
(RPYS) |
(RPYS) Important Email |
Additional Features |
|
|
Client Code |
(Clientcode) |
(RJohn12345) Important Email |
Register Reply or Send Unmarked and Register Reply |
(R+) or (C+) |
(R+) or (C+) Important Email |
Convert to PDF |
(2PDF) |
(2PDF) Important Email |
Convert to password protected PDF |
2PDF(password) |
2PDF(pass1234) Important Email |
Clean hidden metadata |
(RPMD) |
(RPMD) Important Email |
Zip compress file attachments |
(ZIP) |
(ZIP) Important Email |
Re-route Registered Receipt |
(Receipt:email address) |
(Receipt: user@domain.com) Important Email |
Note that the domain extension appended to the recipient’s email address and subject line indicator are removed during processing in the RMail Cloud platform, before the recipients receive the email message.
Examples:
a. “I want to send a Marked Registered email™ message to john@domain.com”.
1. Set the recipient address to: john@domain.com.[suffix]
2. Set the subject of the email like this: [Subject]
In this example, the message will be sent Registered and Marked.
b. “I want to send an RMail Registered email ™ message encrypted, with a custom password generated by me to john@domain.com”.
1. Set the recipient address to: john@domain.com.[suffix]
2. Set the subject of the email like this: RPSX(abc-123) [Subject]
In this example, the message will be sent message level encrypted with the decryption password “abc-123”.
c. “I want to send a Marked Registered email ™ message with a Client Code to john@domain.com”.
1. Set the recipient address to: john@domain.com.[suffix]
2. Set the subject of the email like this: (Client#1234) [Subject]
In this example, the message will be sent Registered and Marked, and it will be associated with the Client Code "Client#1234."
d. “I want to send an e-signature request to john@domain.com. I want the message to be encrypted at the message level, with a random password sent via email to the recipient”.
1. Set the recipient address to: john@domain.com.[suffix]
2. Set the subject of the email like this: RPSX()(RPX) [Subject]
In this example, the message will be sent encrypted at the message level, and a random password will be sent to the recipient in a separate email. The recipient will need to use the password to open the e-signature request message and sign.
X-Headers
RMail features can also be enabled using X-Header indicators in the message. The following is a list of the available X-Headers for each of the RMail features.
Note: The X-Headers will be applied to the message only if the related setting in RPortal at Company Level is set to "Set by User" and at User Level to "Set by App".
Track & Prove
Service |
X-Header |
Type |
Value |
Marked or Unmarked Registered Email™ message |
X-RPost-Type |
Integer |
|
Email address to which the Registered Receipt email will be sent |
X-RPost-Receipt |
String |
<email address> |
Email address to which a copy of the Registered Receipt email will be sent |
X-RPost-ReceiptCopy |
String |
<email address> |
Determines if the sender will receive the "RMail Acknowledgement - Proof of Sending" email or not |
X-RPost-NoAck |
Integer |
|
Determines if the sender will receive the Registered Receipt email or not |
X-RPost-NoReceipt |
Integer |
|
Allows to change the date format on the Registered Receipt email and on the Acknowledgment email |
X-RPost-DateFormat |
Integer |
|
It allows adding an ID to the email message that identifies the message on the originating platform |
X-Rpost-CustomerTrackingId |
String |
<Internal customer ID> |
Defines the language in which the email will be sent |
X-RPost-Language |
String |
Options include:
|
Enables Registered Reply for the email message. Replies to the email will be Registered Email™ messages, irrespective of the value assigned |
X-RPost-ReplyRegistered |
Integer |
0 |
Client/reference code that will be assigned to the Registered Email™ message sent. This code will be visible on the Registered Receipt email. |
X-RPost-ClientCode
|
String |
<Client code> |
Value to identify if the client code should be added to the RMail contract if an attachment for E-Sign was sent on the email. |
X-RPost-ShowClientCode |
Integer |
|
String that contains comma separated domains. If the recipients list of the email contains a recipient with any of those listed domains, the email is not sent to that recipient |
X-RPost-InternalDomainFilter |
String |
<Domains separated by comma> |
Example:
The X-Header for sending a Marked Registered Email™ message:
X-RPost-Type: 1
Encrypt
Service |
X-Header |
Type |
Value |
Message Level Encryption |
X-RPost-SecuRmail |
Integer |
1 |
TLS Encryption |
X-RPost-TLS |
Integer |
1 |
Generates a secure password for the email transaction automatically |
X-RPost-SecuRmail-AutoPassword |
Integer |
1 |
Allows sender to define a specific password for the email message |
X-RPost-SecuRmail-Password |
String |
<password> |
Allows recipient to retrieve the password for the email sent with Message Level encryption |
X-RPost-RetrievePassword |
Integer |
|
The auto-generated or- pre-defined password is automatically sent to the recipients in a separate email |
X-RPost-SendPassword |
Integer |
1 |
Allows the recipient to permanently set their own decryption password for future encrypted Registered Email™ messages. |
X-RPost-SetPassword |
Integer |
|
Example:
The X-Headers for sending an email that is encrypted at the message level, along with a randomly generated password for decryption sent to the recipients:
X-RPost-SecuRMail: 1
X-RPost-SecuRmail-AutoPassword: 1
X-RPost-SendPassword: 1
RMail E-Sign
Service |
X-Header |
Type |
Value |
Enables RMail E-Sign for the email message |
X-RPost-Esign |
Integer |
|
Enables RMail E-Sign with Smart Tags feature for the email message |
X-RPost-Annotation |
Integer |
0 |
Enables sequential signing for the RMail E-Sign email message |
X-RPost-Esign-Sequential |
Integer |
|
Determines the way in which the recipient will be allowed to sign the attached document/s |
X-RPost-HandSignMethod |
Integer |
|
Example
The X-Header for E-Sign E-Paper:
X-RPost-Esign: 1
RMail File Share
Service |
X-Header |
Type |
Value |
File Share feature will be enabled for the message when the total size of all attachments in the message exceeds the specified number of megabytes in this header |
X-RPost-FileSizeForLargeMail |
String |
<n° of megabytes> |
Should be added to an email sent using Domain Extension Integration method if you wish to send that email using File Share. Should contain the "Key" provided by the LargeFileTransfer API |
X-RPost-LargeMail |
String |
<key> |
Allows to define if a download notice should be sent via email to the sender every time an attachment sent with File Share is downloaded by a recipient |
X-RPost-LargeMailDownloadNotice |
Integer |
|
Manage attachments
Service |
X-Header |
Type |
Value |
Allows to clean the metadata from the attached PDF files (if any) |
X-RPost-CleanMetaDataPdf |
Integer |
|
Convert all attached MS Office files to PDF |
X-RPost-Convert-Pdf |
Integer |
1 |
Convert attached .DOC files to PDF |
X-RPost-Convert-Pdf-Doc |
Integer |
|
Convert attached .PPT files to PDF |
X-RPost-Convert-Pdf-Ppt |
Integer |
|
Convert attached .XLS files to PDF |
X-RPost-Convert-Pdf-Xls |
Integer |
|
Sets a custom password for generated PDF files. This is enabled only if any of the previous options are added |
X-RPost-Convert-Pdf-Password |
String |
<password> |
Allows for compressing the attachments to .ZIP format |
X-RPost-Convert-Zip |
Integer |
|
RMail SideNote
Service |
X-Header |
Type |
Value |
Defines the text the SideNote will have. Will work only if CC or BCC recipients are included and if the x-header for which recipients the SideNote should be sent is added |
X-RPost-Sidenote-Text |
String |
<SideNote message> |
Defines if the SideNote is sent to the BCC recipients or not |
X-RPost-Sidenote-Bcc |
Integer |
|
Defines if the SideNote is sent to the CC recipients or not |
X-RPost-Sidenote-Cc |
Integer |
|
Defines if the SideNote is sent to the TO recipients or not |
X-Rpost-Sidenote-To |
Integer |
|
RMail Disappearing Ink
Service |
X-Header |
Type |
Value |
Enable Disappearing Ink for the email message |
X-RPost-DisappearingInk |
Integer |
|
Sets the content of the Disappearing Ink |
X-RPost-DisappearingInk-ContentText |
String |
<Message> |
Sets the text of the link for the Disappearing Ink displayed in the recipient's email |
X-RPost-DisappearingInk-LinkText |
String |
<Text> |
Defines if the Disappearing Ink will be sent to the TO of the email |
X-RPost-DisappearingInk-To |
Integer |
|
Defines if the Disappearing Ink will be sent to the CC of the email |
X-RPost-DisappearingInk-Cc |
Integer |
|
Defines if the Disappearing Ink will be sent to the BCC of the email |
X-RPost-DisappearingInk-Bcc |
Integer |
|
Defines if the Disappearing Ink message should be password encrypted |
X-RPost-DisappearingInk-Encrypt |
Integer |
|
Defines the number of times the Disappearing Ink message can be viewed |
X-RPost-DisappearingInk-ViewNum |
Integer |
<Number of views allowed> |
Defines the length of time (in minutes) per view of the Disappearing Ink message |
X-RPost-DisappearingInk-ViewDuration |
Integer |
<X Minutes> |
RMail Redact+
Service |
X-Header |
Type |
Value |
Determines how the redacted -removed- text will be displayed to the recipient/s |
X-RPost-Redact |
Integer |
|
Contains the text to be redacted from the email body. The text sent on this header needs to be present exactly as it is on the email body between caret symbols (^). If the text is not present on the email body between caret symbols, the feature will not get triggered |
X-RPost-RedactText |
String |
<Text to be redacted from email body> |
Enables Double Blind CC feature for the email message |
X-RPost-RedactBcc |
Integer |
|
Note: Additional subject line indicators and X-Headers are available upon request and analysis from the RPost team.