This is a discussion on Re: [courier-users] within the Courier-Imap forums, part of the Mail Servers and Related category; This is a MIME GnuPG-signed message. If you see this text, it means that your E-mail or Usenet ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages. The Internet standard for MIME PGP messages, RFC 2015, was published in 1996. To open this message correctly you will need to install E-mail or Usenet software that supports modern Internet standards. --===============1172636160== Content-Type: multipart/signed; boundary="=_mimegpg-commodore.email-scan.com-26341-1204981663-0001"; micalg=pgp-sha1; protocol="application/pgp-signature" This is a MIME GnuPG-signed message. If you see this text, it means that your E-mail or Usenet software does not support MIME signed messages. The Internet standard for MIME PGP messages, RFC 2015, was published in 1996. To open this message correctly you will need to install E-mail or Usenet software that supports modern Internet standards. --=_mimegpg-commodore.email-scan.com-26341-1204981663-0001 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Bernd Wurst writes: > Hi. > > On Saturday 08 March 2008, Sam Varshavchik wrote: >> > Wouldn't it make sense to update the default configuration to be "SSL23" >> > so that it works with in-the-wild openssl clients? >> No, but I will update the comments. This is one of those things where some >> mild pain is beneficial in the long term, of forcing SSL2 onto the ash heap >> of history. > > Well, I did not get any connect with latest openssl CLI client when set to > SSL3. Only gnutls clients were able to connect. > Would you say that any production server can work with this setting? > > To make it clearer: courier-0.53.2 worked fine with setting SSL3 (that one > does not have a setting SSL23) but courier 0.58 did not. I don't know what > you've changed but that's the result of my tests yesterday. The "SSL23" setting in 0.58 is the same thing as the "SSL3" setting in 0.53. --=_mimegpg-commodore.email-scan.com-26341-1204981663-0001 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQBH0o+fx9p3GYHlUOIRAtTeAJ9VHFyZY+1TwSgbKb7nt6 6x6+TEFACeLG4M Yjw/VDkVhxQlF9Z2T5AuN8M= =dPK/ -----END PGP SIGNATURE----- --=_mimegpg-commodore.email-scan.com-26341-1204981663-0001-- --===============1172636160== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ --===============1172636160== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users --===============1172636160==-- |