1) I was dissapointed to see that, while a fix that was provided, ready-made, a bug that seemend important to me was still in UNRESOLVED status. Unfortunately, I took it for granted that a ready-made fix would not remain UNRESOLVED for long and upgraded to James 2.2.0 on my production server, only to find that the RemoteDelivery gateway configuraiton does not allow for defining a username and password for authentication. My questions related to this are: a) Why has the fix not been incorporated? b) When will it be?
2) I'm finidng the long wait for IMAP support highly questionable. Though I'm glad to see that there is discussion of classloader-separated mailet packages, it's dissapointing that this is also not present in the current release. The two articles about James that I published for IBM were released in June of 2003, close to two years ago. I can't conceive of any reason why both the classloader deployment and IMAP support have been so long in comming. I'm not really asking why. What I'd really like to hear is a commitment to get the job done and a timeline to covers these two critical features, still not in place despite a clear understanding that they are important to the user community. It's a tough sell when there's no IMAP support and 'they're working on it' isn't really cutting it anymore. Comments?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
