5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Possible ssl error?
FromSent OnAttachments
Mogens ValentinNov 10, 2002 7:03 pm 
Sam VarshavchikNov 10, 2002 8:14 pm 
Mogens ValentinNov 11, 2002 1:24 am 
Mogens ValentinNov 11, 2002 1:33 am 
Mogens ValentinNov 12, 2002 11:00 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Possible ssl error?Actions...
From:Mogens Valentin (mo@danbbs.dk)
Date:Nov 12, 2002 11:00:43 am
List:net.sourceforge.lists.courier-users

Mogens Valentin wrote:

After upgrading from RH 6.2 / 2.2.20 and courier-imap-1.4.6 to HR 7.2 / 2.4.19 and courier-imap-1.6, clients can no longer connect.

I've tried reinstalling the 'old' courier-imap.1.46, no change. The /etc/pamd./imap module is in place. I can log on locally to the system, and through ssh, so group/gshadow/passwd/shadow/PAM should work.

From /var/log/maillog :

Nov 11 03:01:45 mail imapd-ssl: Connection, ip=[::ffff:194.239.mm.nnn] Nov 11 03:01:45 mail imapd-ssl: couriertls: accept: error:1408F071:SSL routines:SSL3_GET_RECORD:bad mac decode Nov 11 03:01:45 mail imapd-ssl: couriertls: accept: error:1408E098:SSL routines:SSL3_GET_MESSAGE:excessive message size Nov 11 03:04:24 mail imapd-ssl: starttls: accept: error:1408F071:SSL routines:SSL3_GET_RECORD:bad mac decode

Two problems:

1. Using openssl-0.96b-something on RH7.2 didn't work using sslv3, which I had used before. Sslv2 solved the problem, except for an occational login problemm which may be contributed to something else.

2. Using Courier-imap-1.6 and AUTHSERVICE993=imaps didn't work as it used to with version 1.46 . AUTHSERVICE143=imap did the rest.

IT Networking, Security, Server Setup http://www.mrdev.com mrd@danbbs.dk Phone +45 32 525 878 Cell 51 227 668