courier-authlib problems.

[pete wright]

On 10/8/07, Tankko <tankko at gmail.com> wrote:
> I upgraded one of my servers to courier-authlib-base-0.60.0 from .59
> and I am now getting the following errors in my mail log:
>
> Oct  8 18:21:47 myserver.net authdaemond: Shared object
> "libauthvchkpw.so" not found, required by "authdaemond"
> Oct  8 18:21:47 myserver.net authdaemond: Installing libauthpam
> Oct  8 18:21:47 myserver.net authdaemond: Installation complete: authpam
> Oct  8 18:21:47 myserver.net authdaemond: Installing libauthldap
> Oct  8 18:21:47 myserver.net authdaemond: Shared object
> "libauthldap.so" not found, required by "authdaemond"
> Oct  8 18:21:47 myserver.net authdaemond: Installing libauthmysql
> Oct  8 18:21:47 myserver.net authdaemond: Shared object
> "libauthmysql.so" not found, required by "authdaemond"
> Oct  8 18:21:47 myserver.net authdaemond: Installing libauthpgsql
> Oct  8 18:21:47 myserver.net authdaemond: Shared object
> "libauthpgsql.so" not found, required by "authdaemond"
>
> and
>
> Oct  8 18:11:33 myserver.net  imapd-ssl: couriertls: connect:
> error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
> Oct  8 18:12:07 myserver.net  imapd-ssl: couriertls: connect:
> error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
>
> Thunderbird (OSX) has doesn't seem to care, but the iphone is now
> unable to get email.  I am using SSL to get mail via imap.
>
> I have a 2nd server that has not been upgraded to .60 yet, and it
> works fine.  But...the upgraded server has:
>
> courier-authlib-base-0.60.0         =   up-to-date with port
>
> and the non-upgraded server has:
>
> courier-authlib-0.59.3              <   needs updating (port has 0.60.0)
> courier-authlib-base-0.59.3         <   needs updating (port has 0.60.0)
> courier-authlib-vchkpw-0.59.3       <   needs updating (port has 0.60.0)
>
> I am assuming the upgraded server had these three ports as well before
> the upgrade, but I can not be 100% sure.  I always kept these 2 severs
> running the same versions of everything, so I assume they were.
>
> Anyone know how to fix this?
>

yea ran into a similar issue yesterday myself.  i had to make this
modification in /usr/local/etc/courier-imap/imapd-ssl:

TLS_PROTOCOL=SSL23

believe old default value was:
TLS_PROTOCOL=SSL3

HTH
-pete


-- 
~~o0OO0o~~
Pete Wright
www.nycbug.org
NYC's *BSD User Group