Email Encryption for Microsoft 365 & Google Workspace

Secure SMTP Connector for Healthcare Email

Using Google Workspace for healthcare email is not possible without using a third-party tool for compliance. Microsoft Office 365 can support encryption for HIPAA compliance, but it is difficult to configure and requires users manually enable encryption on a per email basis. LuxSci's Secure Connector is unlike other email encryption gateways in that it encrypts every email automatically to reduce the risk of breaches caused by human errors. LuxSci provides the flexibility to opt-in to more secure methods of encryption for highly sensitive messages.

Learn more about how to configure Secure Connector email encryption for Google and Microsoft.

SecureLine^TM Encryption Technology

LuxSci's SecureLine^TM encryption engine automatically encrypts every email sent from Google Workspace or Microsoft 365 accounts. It works like this—messages are securely transmitted to LuxSci via SMTP. Then SecureLine encrypts the emails according to your settings before securely delivering them. SecureLine is extremely flexible and encryption settings can be configured to meet a variety of security, usability, compliance, and deliverability needs.

Learn More About SecureLine

Secure Connector Features

In addition to encrypting every outbound email, Secure Connector has additional security and compliance features that include message delivery reporting; SPF, DKIM, and DMARC support; dedicated servers and clusters; and support for email archival.

Show Features

Pricing

General Features

All Plans Include
HIPAA-compliant: Business Associate Agreement
HIPAA-compliant: Send ePHI in your email messages
SecureLine^TM email encryption	*
Dedicated servers for isolation and security	available
Dedicated IP addressess for email delivery reputation management	available
Email Archival	available
Ticket, Chat, & Phone Support

*Available when dedicated servers or clusters are purchased.

Additional Features

(+) show all descriptions

Feature
Reporting: Messages Sent
Searchable, sortable, and downloadable reports of messages sent.
Reporting: Tracking and Deliverability
Searchable, sortable and downloadable reports with delivery details of every message to every recipient. You see what has been sent, what is still queued and what has been delivered successfully. If a message was not delivered successfully, you will know exactly why. Reports include: The cause of any delay Reason why a message bounced The recipient server's delivery response. Aggregate reports give you overall delivery statistics on a daily and monthly basis.
Reporting: Email Delivery Failure Reports
Tailor and receive automated email alerts (for delivery failures) when and how you choose. At a frequency of your choice For any email address or list of your choice Alert details include: When the message was sent Who sent it and from what address What the subject was The address of the recipient that failed Exactly why the delivery failed These email alerts are HTML for easy reading. They also include a CSV (Excel) file with all of the data for easy analysis. These reports make it easy for you to manage your mailing lists, discover addresses that are spelled wrong, and to remove old and non-working addresses.
Reporting: Email Open Tracking
Reporting: Email URL Click Tracking
Reporting: Email Bounce Tracking
Authentication by username and password
SMTP Services authenticated with a username and password are supported and recommended.
Authentication by IP
SMTP Services authenticated by the connecting IP address and/or the From address in the message are supported for compatibility with systems that do not support username/password authentication (e.g. Google and Microsoft).
FIPS-Recommended TLS Security
Use of your choice of insecure SMTP, SMTP over TLS, and SMTP over SSL. You may optionally choose to lock down your account to enforce the use of SSL or TLS.
Alternate SMTP Ports
Alternate ports for SMTP access, including use of port 80. This helps ensure the sending process even if firewalls or ISP blocking policies exist.
IP Address Masking - Hide Your IP
Hide the IP address of all computers or servers you use to send messages. Blocking your own address helps prevent messages from being blocked by the recipient.
Message Size Limit	200 MB
Messages can be up to 200 MB in encoded size. This includes all attachments.
1000 Recipient per Message Limit
Sent to just one IP address or as many as 1000 recipients per message.
Sending Limit: Users can send up to 300 messages/day
Individual users are restricted to 300 messages per day unless you sign up for a "High Volume" account, which allows you to send as many messages as you purchase.
Sending Limit: Send to as many recipients per month as you purchase	(upgrade)
Feedback Loops with Major ISPs
We collect spam reports via agreements with major ISPs. This helps us detect spamming and other issues quickly which helps keep our servers off of block lists. Users and administrators can peruse SPAM complains reports in our web interface. Users and administrators can also have digests of their received SPAM complaints emailed to them automatically. These contain detailed information in attached CSV files so users know about any issues as soon as possible, making opting complaining recipients out of mailing lists quick and easy.
SPF, DKIM, DMARC Support
Email Capturing
Direct copies of all sent messages sent to another email address of your choice.
Support for Email Archival
Add Email Archival services.
Recipient Restrictions and Suppression Lists
Use allow and deny lists to control to whom or to what domains messages can be sent. Send copies of all outbound email messages to an email address of your choice.
Taglines/Disclaimers
Automatically add taglines or disclaimers to all outbound email messages. These can appear in plain text or in HTML format
Email Content Monitoring
Scan all outbound email for specific content (keywords, phrases or regular expressions). Matched messages can be denied, sent to an auditor, or auto-encrypted using SecureLine^TM.
WebMail
WebMail access for sending email messages; includes an integrated calendar and address book.

FAQ: What to Know About Secure High Volume Sending

Is it difficult to configure?

In just a few short steps you can configure Secure Connector for your organization. LuxSci's highly rated support team is also available to assist with set up.

How many messages can my users send?

Secure Connector customers can send up to 300 email messages/day (this can be upgraded if needed); customers can send each message to up to 1000 recipients. Secure Connector customers cannot send bulk email of any kind. For email marketing and large-scale sending needs, we offer a separate High Volume Secure Sending service. We can add this service onto your account.

Can I send HIPAA-compliant email to anyone?

Yes. LuxSci SecureLine^TM enables you to send compliant email to anyone with an email address. Your recipients do not need to use LuxSci themselves.

Can recipients of my secure email messages reply to me?

Yes. Recipients of your secure email messages can reply to you. See: Are Replies to My HIPAA-Compliant Secure Emails Also Secure?

Can we opt-in or opt-out of encryption for some messages?

To reduce the risk of sending unencrypted messages, LuxSci automatically encrypts every email for HIPAA customers. If some messages do not include ePHI, you can choose to opt-out of using encryption for them. LuxSci does not support opt-in encryption (where you manually specify which messages need encryption) for HIPAA-compliant accounts, because it's too risky for HIPAA compliance. We do support opt-in encryption if you do not need HIPAA compliance.

When and where is the email encrypted?

When you send an email message, it is transmitted securely to LuxSci's servers using TLS. Once the message arrives, LuxSci encrypts the message for each of your recipients and then delivers the encrypted message to the recipient's email servers. Based on your account preferences, who the recipients are, where their email host is, and settings in your account, the encryption used can take the form of: SMTP TLS, Secure Message Pick Up (Escrow), PGP, or S/MIME. The type of encryption used is determined at send time.

eBook: HIPAA-compliant Email Basics

Safeguarding your healthcare practice and protecting patient privacy

Book 1 in the LuxSci Internet Security Series.

Created by Erik Kangas, PhD

Get the HIPAA eBook

HIPAA-compliant Email Encryption for Microsoft Office 365, Google, Exchange

Secure Connector
For Your Existing Email

Secure SMTP Connector for Healthcare Email

SecureLine^TM Encryption Technology

Secure Connector Features

General Features

Additional Features

FAQ: What to Know About Secure High Volume Sending

eBook: HIPAA-compliant Email Basics

Safeguarding your healthcare practice and protecting patient privacy

Learn Why G2 Crowd Users Love LuxSci

HIPAA-compliant Email Encryption for Microsoft Office 365, Google, Exchange

Secure ConnectorFor Your Existing Email

Secure SMTP Connector for Healthcare Email

SecureLineTM Encryption Technology

Secure Connector Features

General Features

Additional Features

FAQ: What to Know About Secure High Volume Sending

eBook: HIPAA-compliant Email Basics

Safeguarding your healthcare practice and protecting patient privacy

Learn Why G2 Crowd Users Love LuxSci

Secure Connector
For Your Existing Email

SecureLine^TM Encryption Technology