Email encryption is easy to set up with Greenview Data's hosted encryption. Depending on how fast these steps are completed, encryption is ready within 2 days.
If you are already a Greenview Data customer, just submit a support ticket requesting the Encryption service. We will have a few quick questions about your infrastructure (how many users, IP address of your mail server, etc.) and your needs for filtering (HIPAA, Financial terms, SSNs, etc.).
If you are not a customer yet, it's just as easy! All you have to do isand we'll walk you through the process.
Create MX records for a subdomain called zixvpm.<Your Domain></kvd> when they are supplied to you by our support staff.
If you are an existing ZixGateway customer, these MX records will initially point to your existing ZixGateway, or whatever exists on the "zivpm.<Your Domain>" subdomain. By changing them, you're only introducing us as a relay before your existing ZixGateway. This means that you'll just have an additional "hop" in front of your existing ZixGateway, which will still do the decrypting of the messages until it gets de-activated in Step 3.
If you are not an existing ZixGateway customer, these MX records will never be queried, and will not impact your mail flow at all.
Answer a brief questionnaire including your mail server's IP address(es), and what filters you'd like enabled. For reference, here is the questionnaire:
If you have an existing ZixGateway, our support staff will walk you through decommissioning its keys and re-activating the service right before Step 4. If timed correctly this step will have minimal impact on your mail flow.
When prompted by our staff, you can set a smart host on your mail server to relay mail through our encryption gateways.
links to, , , , , and mail server configurations.
Optional encryption configurations some clients my find useful:
Create SPF records for your domain. Although the MX records above are in a subdomain called zivpm.<Your Domain>", the SPF/TXT records should be in your main domain's zone. Your TXT records will include all of our outbound servers, using three "include" statements.
For instance, include:
<example-tld>.spf-a.smtp25.com include:<example-tld>.spf-b.smtp25.com include:<example-tld>.spf-c.smtp25.com
Although this step is optional, it cannot be stressed enough how important it is. Since the email messages are not encrypted by our service until they reach our servers, messages will leave your infrastructure in clear text unless you secure your transmission to us. Self-signed certs will work fine, and most servers include functionality to generate them (Exchange 2007/2010 do by default).