<SPAN id=result_box class=medium_text><SPAN style="BACKGROUND-COLOR: #fff" title="eso es completamente cierto y se puede aplicar sin problemas a pop3, imap4" kc="That is completely true and can be applied easily to POP3, IMAP4
" jc="eso es completamente cierto y se puede aplicar sin problemas a pop3, imap4" closure_uid_dguknt="27"><FONT style="BACKGROUND-COLOR: #ebeff9" size=5>That is completely true and can be implemented easily to POP3 and IMAP4 the issue appears when the client try to use smtp ssl/tls and invoke the STARTTLS command. then the STunnel <SPAN id=result_box class=short_text><SPAN style="BACKGROUND-COLOR: #ebeff9" title="no se puede usar" kc="can not be used" jc="no se puede usar" closure_uid_dguknt="36">can not be used </SPAN></SPAN>but only the mercury ssl/tls native mode with all the the actual constraints.</FONT></SPAN><SPAN style="BACKGROUND-COLOR: #ebeff9" title="el problema ocurre al usar ssl/tls en smtp y el cliente invoca el comando starttls." kc="the problem occurs when using ssl / tls and client smtp invoke the STARTTLS command." jc="el problema ocurre al usar ssl/tls en smtp y el cliente invoca el comando starttls." closure_uid_dguknt="28"><SPAN id=result_box class=short_text><SPAN style="BACKGROUND-COLOR: #ebeff9" title="con las actuales limitaciones" kc="the existing constraints" jc="con las actuales limitaciones" closure_uid_dguknt="34"></SPAN></SPAN></SPAN></SPAN>

<P><SPAN id=result_box class=long_text><SPAN style="BACKGROUND-COLOR: #fff" title="dentro de mi organizacion existe una presion cada vez mayor para que todas las comunicaciones (pop/imap/smtp) sean encriptadas, pero me encuentro con el problema de que los certificados de Mercury son propietarios y no admite los generados desde otros sistemas como openssl o" kc="within my organization there is increasing pressure for all communications (pop / imap / smtp) are encrypted, but I find the issue of certificates of Mercury are proprietary and not support those generated from other systems such as openssl or " jc="dentro de mi organizacion existe una presion cada vez mayor para que todas las comunicaciones (pop/imap/smtp) sean encriptadas, pero me encuentro con el problema de que los certificados de Mercury son propietarios y no admite los generados desde otros sistemas como openssl o" closure_uid_8co6t9="28">within my organization we have an increasing and heavy pressure to process all communications (pop / imap / smtp) in an encrypted way, but the certificates of Mercury/32 are proprietary and not support those generated from other ways such as openssl or </SPAN><SPAN title=verisign kc="verisign
" jc="verisign" closure_uid_8co6t9="29">verisign, it is an issue for us since we need to use a specific certificates.</SPAN></SPAN></P> <P><SPAN class=long_text><SPAN title=verisign kc="verisign
" jc="verisign" closure_uid_8co6t9="29"> </SPAN><SPAN style="BACKGROUND-COLOR: #fff" title="¿alguien sabe si está previsto alguna nueva release de mercury que soporte este tipo de certificados?" kc="Does anyone know if you planned any new release of mercury that supports this kind of certificates?" jc="¿alguien sabe si está previsto alguna nueva release de mercury que soporte este tipo de certificados?" closure_uid_8co6t9="30">Does anyone know if is planned (soon) any new release of mercury that supports this kind of certificates?</SPAN></SPAN></P>

> within my organization we have an increasing and heavy pressure to process all communications (pop / imap / smtp) in an encrypted way, > but the certificates of Mercury/32 are proprietary and not support those generated from other ways such as openssl or verisign, it is an > issue for us since we need to use a specific certificates. > > Does anyone know if is planned (soon) any new release of mercury that supports this kind of certificates? Not sure but you can use OpenSSL via STunnel to make Mercury/32 work via any compliant certificate.  From the client point of view they will be using OpenSSL and from Mercury's it will be using the normal ports.