Aaron Stone wrote:
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...

So fix it in 2.1. We're not even clear yet on how to fix this. We should allow ourselves a couple of iterations to get it right. I don't want to mess with the imap code in 2.0 anymore than absolutely necessary, and I'm pretty sure Ilja feels the same.

   * Bug 91: Infinite loops in both imapd and pop3d.

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*

I've done backtraces on the loop several times myself. perform_imap_search recursing endlessly everytime I got my hands on a looping dbmail-imapd.

I think Sean had a reliable method of triggering this one. Perhaps dbmail-imapd on freebsd still suffers from the loops. I dunno.

   * 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.

Great.

   * 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

True, but the looping bug has made me a bit more cautious. Preforking is very stable and has been tested on 2.0 more extensively than any other patch we've ever had our hands on. You outlined the issues involved in merging this one into 2.0 nicely, and they are minor. But as I said before I can live without preforking in 2.0.


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.

Yep. I read your mail on that one.

--
  ________________________________________________________________
  Paul Stevens                                  mailto:[EMAIL PROTECTED]
  NET FACILITIES GROUP                     PGP: finger [EMAIL PROTECTED]
  The Netherlands________________________________http://www.nfg.nl

Reply via email to