| 30+ Sure Ways to Earn Money |
| Audience: technical | ||
|
|
NMA ZSentry APICompatible: The API
offers a ZSentry engine with SSL/SMTP send and receive connectors. Works with Microsoft Exchange Server,
Outlook, Word, C# and .NET, as well as Java, PHP, and other automation tools. No download. No plugins.
No requirements on any existing plugins. No installation. Pricing: This service is priced attractively for bulk sale and is offered in addition to a Desktop, Web, and Mobile ZSentry subscription. There is no free personal offer for this service. For pricing and quantity discounts, Government, Non-Profit, and Education pricing please Contact us. Purpose: The ZSentry Application Programming Interface (API) allows your server or even office application to connect to ZSentry. The API works with all ZSentry editions. How it Works: Developers can connect a system to a ZSentry engine for encryption/decryption directly or through a message service or application, using SSL SMTP, automatically. ZSentry can also send the resulting secure emails using its own SMTP server, without requiring SSL, or use another resource as a mail relay with or without SSL. With the ZSentry API, developers are not limited to use HTTPS with ZSentry App™. You can also connect using ZSentry Zero™, which enables SMTPS (SMTP over TLS/SSL, also called implicit SSL) on TCP port 465. With port 465 there is no ZSentry data exchange without TLS, including the ZSentry Username and Password data. Contrary to the submission port 587 with STARTTLS where the connection changes from non-SSL into SSL, port 465 has TLS-at-connect required. We prefer port 465 because every connection is encrypted from the start, preventing the SSL bridge attack (a well-known problem also for web browsers). We tested servers with the dovecot/postfix Debian implementation and, without any errors, against many clients including Outlook, Windows Mail, Apple Mail, Entourage, and Thunderbird, on Windows XP, Vista, Linux, and Mac OS X. Some Outlook versions can only work with the port that we use (465). Exchange Server: Since 2000, Microsoft Exchange Server extensively uses standards-based SMTP, the same standard used by ZSentry. You can define SMTP connectors in Exchange, both sending and receiving, using SSL and port 465. Exchange SMTP connectors are compatible with the ZSentry API, which can work with Exchange, through Exchange, and directly with clients. You can choose which model to use, or use any. For example, depending on who you are sending to, you can select to use Exchange as a non-SSL mail relay, to send the message after it is encrypted by ZSentry. Or, you can select to send in SSL to Exchange, which then defines whether or not to encrypt using ZSentry, and how to send it, all based on some policy you defined in Exchange. Benefits: The ZSentry Zero Benefits and also:
Use Now:Contact Us >> for information on licensing and using the ZSentry API. | |
| Main Technical Notes | ||
Titles and product names are trademarks of NMA, Inc. as described in our Legal Statement. We protect Your Privacy.