Re: [courier-users] Any alternatives to virtual user accounts for

Daniel Kasak wrote:
> Gordon Messmer wrote:
>> Daniel Kasak wrote:
>>
>>> I've discovered that the way I set the folders up will not work with
>>> a newer courier-imap server,
>>
>> Why not?
>>
> That's the million-dollar question.
> ...

It's an interesting problem, and I might look at that when I'm back from
St. Louis, unless you're committed to migrating off of Courier, in which
case there's no real reason.

>>> and now I'm in the precarious situation that I can't re-compile my
>>> existing version ( don't know why ), against MySQL ... which I have
>>> to do because I've upgraded MySQL and the client libraries have been
>>> renamed. The situtation is becoming more desperate.
>>
>> I was under the impression that the wire protocol had not changed.
>> You should be able to leave your old client libraries in place after
>> the upgrade. You'll just have two versions of the runtime library
>> installed.
>
> No. MySQL keep bumping the version number of their client libraries.

Yes, they do. That does not always mean that old clients can't connect
to new servers. In this case, it should not.

> From 4.0.x to 4.1.x they changed the authentication mechanism.

That's true. They have a page documenting things that you can do to
upgrade the server without breaking old clients:
http://dev.mysql.com/doc/refman/5.0/en/old-client.html

This suggests that you should be able to continue using applications
linked against the old client libraries.

> I don't
> know what they changed from 4.1.x to 5.0.x. But anyway, the client
> libraries are not where stuff expects them ( because of the version
> number bump )

The libraries are not where applications expect them because you removed
them as part of the upgrade (I assume). I'm suggesting that if you had
not removed them, your applications would have continued to work. It is
perfectly acceptable to have two different versions of the client
libraries installed simultaniously.

>, so there are 2 solutions:
>
> a) recompile, or:
> b) sym-link the old library name to point at the new one

There's a third option:
c) put the old library back where it was, without changing the new
client library.

> Option a) is impossible - the old version of courier-imap that we need
> to support our unsupported shared folder setup no longer compiles for me.

That's probably not difficult to fix, if you want to pursue it.

> Option b) is dodgy as hell.

Yes, it is. I wouldn't suggest it.


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users