This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ncc-services-wg@ripe.net/
[ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es
- Previous message (by thread): [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es
- Next message (by thread): [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
tp
ripe at dial.pipex.com
Wed Dec 20 14:16:52 CET 2006
Have you documented any more about the technicalities, such as which version.release(s) you support, level negotiation, what ciphersuites .... Tom Petch ----- Original Message ----- From: "Brian Riddle" <brian at ripe.net> To: <ncc-services-wg at ripe.net>; <db-wg at ripe.net> Sent: Wednesday, December 20, 2006 10:39 AM Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es > [Apologies for duplicate e-mails] > > Dear Colleagues, > > After our successful implementation testing of Transport Layer Security > (TLS) over the last few months, we will be implementing TLS on our > external mail exchanges (MXs). > > We will upgrade our mail server software on 8 January 2007, followed by > implementation of TLS on 10 January 2007. > > If you experience problems with mail delivery to the RIPE NCC after the > implementation, please send a e-mail to ops at ripe.net. To do this, > however, you might have to disable TLS on your MX server or send the > email from a MX server that does not have TLS enabled. > > > Regards, > > Brian Riddle > IT Manager > RIPE NCC >
- Previous message (by thread): [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es
- Next message (by thread): [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]