Aaron Stone wrote:
I just updated the 2.0 Status on the Wiki, and here's what's up: Not yet in CVS, needs to be done before release * Bug 97: all messages have RECENT flag in IMAP.
This will not be fixed in 2.0 afaik. Doing this with even a small semblance of correctness will require some possibly fairly intrusive changes in imapcommands.c
* Bug 91: Infinite loops in both imapd and pop3d.
I think the looping in the pop3 code was fixed already by you yourself. The imap loop is indeed a nasty and urgent matter. But reports have been slim lately regarding this issue and we really need a reliable test scenario to validate any attempts at fixing this. Unless of course someone discovers some glaring bug that explains this issue.
* Bug 118: dbmail-users -c username -W does not prompt for password on FreeBSD.
Could this be related to bug 141? getopt on freebsd is behaving different from the linux implementation.
Known problems and bugs to be addressed in a future release * Bug 125: Inefficiencies in ACL listing. * Bug 133: Inefficiencies in Mailbox listing.
Only clean and well tested fixes. No more butt-ugly hacks just for performance sake.
* Bug 129: Config file parser should be more robust (backport from 2.1?) * Bug 142: Merge preforking with the 2.0 codebase.
Disagree. No new features in 2.0 !!! 2.0 is a production release. Only bugfixes.
There are a bunch more bugs in the bugtracker, but nothing that's a full showstopper except for Bug 141, in which ajordan notes that dbmail-users is segfaulting for him. Since "it works for everyone else" I don't think we need to hold up 2.0.2 until we figure that one out.
Someone should evaluate the fix I send yesterday. Basic idea: my_strdup(optarg). -- ________________________________________________________________ Paul Stevens [EMAIL PROTECTED] NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands_______________________________________www.nfg.nl