Vincent Fox wrote:
> Bob Dye wrote:
BD> But it does seem odd that it supports STARTTLS on 143 but not 993.
VF> This is not odd, this is working as specified.
Indeed.
VF> TLS is enabling encryption on a connection that
VF> has started without it.
Maybe people would be less confused if "TLS" wer
Bob Dye wrote:
>
> But it does seem odd that it supports STARTTLS on 143 but not 993.
This is not odd, this is working as specified.
TLS is enabling encryption on a connection that
has started without it.
There's a cogent argument that 993 should be depecrated
as the vestige of "stunnel days" tha
On 01/25/2010 07:12 PM, Andrew Morgan wrote:
> On Mon, 25 Jan 2010, Bob Dye wrote:
>
>> OK. Thanks.
>>
>> But it does seem odd that it supports STARTTLS on 143 but not 993.
>
> The IMAP command "STARTTLS" is only offered by the server when the
> connection is currently unencrypted, such as when you
On Mon, 25 Jan 2010, Bob Dye wrote:
> OK. Thanks.
>
> But it does seem odd that it supports STARTTLS on 143 but not 993.
The IMAP command "STARTTLS" is only offered by the server when the
connection is currently unencrypted, such as when you first connect to
port 143. Port 993 is an SSL port,
Andrew Morgan wrote:
On Mon, 25 Jan 2010, Bob Dye wrote:
Andrew Morgan wrote:
On Sat, 23 Jan 2010, Bob Dye wrote:
I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
TLS works fine if I connect to the imap port (143). If I try to
connect instead via the imaps port (993), t
On Mon, 25 Jan 2010, Bob Dye wrote:
> Andrew Morgan wrote:
>> On Sat, 23 Jan 2010, Bob Dye wrote:
>>
>>> I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
>>>
>>> TLS works fine if I connect to the imap port (143). If I try to connect
>>> instead via the imaps port (993), the
Examples:
[1] openssl s_client -connect mail.columbia.edu:993
[2] openssl s_client -connect mail.columbia.edu:143 -starttls imap
[3] openssl s_client -connect mail.columbia.edu:993 -starttls imap
[1] and [2] should work ; [3] fails.
The U Wash IMAP server gives the same results.
These alterna
On 01/25/2010 02:26 PM, Bob Dye wrote:
Patrick Boutilier wrote:
On 01/25/2010 11:51 AM, Bob Dye wrote:
Patrick Boutilier wrote:
On 01/24/2010 10:39 AM, Bob Dye wrote:
Joseph Brennan wrote:
--On Saturday, January 23, 2010 4:54 PM -0800 Bob Dye
wrote:
I'm running Cyrus-imapd 2.3.7 on a
Patrick Boutilier wrote:
On 01/25/2010 11:51 AM, Bob Dye wrote:
Patrick Boutilier wrote:
On 01/24/2010 10:39 AM, Bob Dye wrote:
Joseph Brennan wrote:
--On Saturday, January 23, 2010 4:54 PM -0800 Bob Dye
wrote:
I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
TLS
Andrew Morgan wrote:
On Sat, 23 Jan 2010, Bob Dye wrote:
I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
TLS works fine if I connect to the imap port (143). If I try to
connect instead via the imaps port (993), the attempt times out and I
get the following in the log:
On 01/25/2010 01:28 PM, Andrew Morgan wrote:
On Sat, 23 Jan 2010, Bob Dye wrote:
I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
TLS works fine if I connect to the imap port (143). If I try to connect
instead via the imaps port (993), the attempt times out and I get the
fo
On 01/25/2010 11:51 AM, Bob Dye wrote:
Patrick Boutilier wrote:
On 01/24/2010 10:39 AM, Bob Dye wrote:
Joseph Brennan wrote:
--On Saturday, January 23, 2010 4:54 PM -0800 Bob Dye
wrote:
I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
TLS works fine if I connect t
On Sat, 23 Jan 2010, Bob Dye wrote:
> I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
>
> TLS works fine if I connect to the imap port (143). If I try to connect
> instead via the imaps port (993), the attempt times out and I get the
> following in the log:
>
> imaps[27170]:
Patrick Boutilier wrote:
On 01/24/2010 10:39 AM, Bob Dye wrote:
Joseph Brennan wrote:
--On Saturday, January 23, 2010 4:54 PM -0800 Bob Dye
wrote:
I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
TLS works fine if I connect to the imap port (143). If I t
On 01/24/2010 10:39 AM, Bob Dye wrote:
> Joseph Brennan wrote:
>> --On Saturday, January 23, 2010 4:54 PM -0800 Bob Dye
>> wrote:
>>
>>
>>> I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
>>>
>>> TLS works fine if I connect to the imap port (143). If I try to connect
>>> inst
Joseph Brennan wrote:
--On Saturday, January 23, 2010 4:54 PM -0800 Bob Dye
wrote:
I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
TLS works fine if I connect to the imap port (143). If I try to connect
instead via the imaps port (993), the attempt times out and I get
--On Saturday, January 23, 2010 4:54 PM -0800 Bob Dye
wrote:
> I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
>
> TLS works fine if I connect to the imap port (143). If I try to connect
> instead via the imaps port (993), the attempt times out and I get the
> following in
I'm running Cyrus-imapd 2.3.7 on a Redhat Enterprise Linux 5 system.
TLS works fine if I connect to the imap port (143). If I try to connect
instead via the imaps port (993), the attempt times out and I get the
following in the log:
imaps[27170]: imaps TLS negotiation failed: [xx.xx.xx.xx]
im
18 matches
Mail list logo