This feature request is being formally submitted on behalf of our client who is currently utilizing the RingCX Email Channel for customer communications.

The client has raised concerns regarding the ability to encrypt emails containing sensitive information. While RingCX supports SSL/TLS encryption for IMAP/SMTP connections (encryption in transit), there is currently no built-in support for end-to-end email encryption methods such as S/MIME or PGP.

At present:

SSL/TLS can be enabled by default for IMAP/SMTP connections.

Additional security configurations depend on the customer’s email server.

End-to-end encryption (S/MIME, PGP) is not supported within RingCX.

Message-level encryption is considered outside the scope of RingCX and is expected to be managed by the customer’s email provider or third-party security tools.

The client operates in an environment where sensitive and potentially regulated information may be transmitted via email. While TLS provides transport-level encryption, it does not provide message-level encryption from sender to recipient.

Requested Enhancement:

The client is requesting consideration for native support of end-to-end email encryption within the RingCX email channel, including:

S/MIME support for outbound and inbound email

PGP encryption support

Administrative controls to enforce encryption policies

Encryption status visibility and logging

Optional enforcement rules for compliance-driven environments

Business Justification:

Supports compliance requirements (e.g., HIPAA, GDPR, PCI-DSS, and other regulatory frameworks)

Reduces reliance on external encryption gateways or third-party solutions

Strengthens RingCX’s security posture in enterprise and regulated markets

Addresses customer security concerns that may impact broader adoption of the Email Channel

The lack of native encryption capability is currently viewed as a functional limitation by the client. We kindly request Product Team evaluation and roadmap consideration for this enhancement.