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.
The SMTP method, which involves adding a domain extension and custom X-headers, is one of the common integration options due to its ease of implementation and flexibility in activating RMail® features.
Below are some common designs for SMTP integrations.
End users who want to send all emails via RMail® with specific features, such as email encryption, can integrate RMail® by replacing the current “Send” function. In this scenario, when a user presses the “Send” button in the platform’s user interface, the email is sent via RMail® with the selected feature (e.g., encryption). This option is ideal for organizations that want to ensure all emails are sent using a consistent set of predefined RMail® features.
Companies can integrate RMail® services as checkboxes or toggle switches within the email sending or composing interface, allowing users to select one or more features on-demand without additional pop-ups. Frequently used features can be pre-selected by default. This design is ideal for industry-specific software integrations where certain RMail® features need to be consistently applied across all users.
Companies looking to provide multiple RMail® services to end users can integrate a feature dialog window that appears just before a message is sent, presenting a range of RMail® options. This allows users to easily select one or more features per transaction, with commonly used features pre-selected by default. The integration touchpoint is a “Send Registered” button next to the existing “Send” button. When clicked, the dialog box appears, enabling users to choose the RMail® features to apply. This approach offers maximum control and flexibility for users.
Organizations that require all emails to be routed through RMail® from a workflow address can leverage the automated workflow method for seamless integration. This approach, typically deployed via SMTP (API available), involves appending the RMail® domain extension suffix to the recipient’s address, ensuring emails are processed through RMail® without altering the existing sending process. For example, sending to amy@gmail.com would route through RMail® by addressing it as amy@gmail.com.[suffix]. This method is particularly useful for automating routine communications such as invoices, policies, notices, and terms and conditions updates.
For more information on the RMail® domain extension method, visit our Help Center
