Paul J Stevens <[EMAIL PROTECTED]> said: > > 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
Seriously? This is a really annoying problem, I'd love to see it fixed... >> * 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. There are smart people having this problem, but without some way to even ballpark the bug, we're just treading water. Mr. Jordan was able to get a backtrace on bug 141 and I fixed it an hour later... *gdb hint hint bt* >> * 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. Nope, 141 was a null pointer (my fault). I have confirmed the getopt behavior that I suspected from the FreeBSD manpage on an OpenBSD box I have, but it does seem to work on that machine. So someone on specifically on FreeBSD will have to look into 118. >> 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. Agreed, I'm working in slow and steady wins the race mode on these. >> * 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. 129 was Ilja's suggestion, 142 was yours :-P >> 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). Turns out it was a easy (see above) and I fixed it yesterday. Aaron
