All email transmission and transaction data to and from RMail are done by SMTP email with routing rules available. This historically has been the most popular method of integrating as the integration can be accomplished simply by adding an email domain extension and a custom header. Below are some common SMTP integration touchpoints. Click here for a customer success story. (Developer Note: link to First American Title success story)
End users that would like to send all emails via RMail with one feature, email encryption for example, may integrate one of the RMail features into the current platform by replacing the current “Send” function with RMail. In this scenario, when a user presses the “Send” button on the current platform’s user interface, the email is sent encrypted to the end user via RMail. For this type of integration, follow the steps in the appropriate feature section, i.e, Track & Prove, Email Encryption, E-Sign or File Share. This option is ideal for companies that would like to have all emails sent using a certain RMail feature.
Companies that would like to offer some of the RMail services using pre-defined settings may opt to add the RMail features as check boxes or toggle switches within the sending or composing user interface. This offers users a simple, on-demand option to add more to their email without the extra step of a feature pop-up. The end user may select one or multiple options per transaction with frequently used features pre-selected by default. This option is ideal for industry specific software integrations where a few of the RMail features are available to end users where the RMail features and settings are predetermined for consistency.
Feature Dialog Pop-up
Companies that would like to offer more than one RMail service to end users may opt for a feature dialog window to pop-up with several RMail options available. The end user may select one or multiple options per transaction with frequently used features pre-selected by default. In this scenario, the integration touchpoint would be a “Send Registered” button next to the current “Send” button. When this new button is pressed, a feature dialog box appears to select the type of RMail message to send. This option is ideal for companies that would like to offer several RMail features to end users, to give them maximum control. Example below.
Companies that would like to send all emails through RMail from a workflow address may select the automated workflow method. This option is typically deployed by SMTP (API available) by simply appending the suffix “.rpost.biz” to the end of the recipient address to route the message to the recipient via RMail with no other changes to current email sending. For example, sending an email to firstname.lastname@example.org would be sent through RMail by addressing it email@example.com. This is ideal for automation of invoices, policies, notices, updated terms and conditions, and more.
Sample RMail Track & Prove SMTP Development Instructions
The RMail Track & Prove service provides the sender with a Registered Receipt email containing the level of delivery, open tracking, time of sending and delivery, and is verifiable to produce the recreated transmission logs and original content. The Track & Prove service may be sent marked with a Registered Email banner or unmarked, with no banners or markings.
Sample User Interface
Feature control: Radio buttons
Sending Method: Add the suffix .rpost.biz to the end of each recipient address in the To, Cc and/or Bcc field. For example, emails addressed to firstname.lastname@example.org are sent to email@example.com.