>
> Current James has several user features not in last release (hashed
> passwords, forwarding, alises).
>
> It should be possible and fairly easy to write a conversion tool,
> though. Contributions welcome!
This is probably needed.
>> Other than that everything is cool but these are serious features. In a
>> production enviornment they are neccessary. If they can already be done
>> please tell me how (and maybe add some documentation :-) It isn't
>> really a problem right now because I have small userlist and small
>> listserv's but think if I had 400+ users. Also the only way I think you
>> can shutdown the servers is killall java which isn't appropriate for
>> large systems.
>
>
> I disagree.
> What you say is true for minor releases,e.g. 1.2.1 to 1.*
> But I don;t think its true for either:
> a) CVS or nightly releases - which are in development, or
> b) Major release, e.g. 1.2.1 to 2.*, where backwards compatability might
> be broken - but should be detailed in release notes.
I agree nightly releases that are in development are in development and
should be taken exactly as that, however Major release changes, even if
backwards compatibility is broken should still offer a way to migrate
users. When people start to depend on Mail servers, and you release a
new Major release, I think people should be able to expect to at least
move their current users from one server to another pretty painlessly.
But this is a small feature that can be handled in some conversion or
administrative tool, so its not anything to stress about.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
