tags 225048 +unreproducible thanks On Thursday 25 March 2004 12.28, Pascal Hakim wrote: [dovecot] > Doesn't this bug only happen in mbox files? You could simply drop mbox > support, it appears to be working fine with maildir (which is how I > suspect how must people are using it (I certainly am (woah! 3 levels of > nested brackets))). I'd be most annoyed if my mailserver suddenly decided not to work anymore after an upgrade. So, better drop dovecot from testing *now*. People who have dovecot will not really notice, and perhaps this will be motivation for someone (upstream?) to fix that bug. Or drop dovecot from testing, and add a new package dovecot-nombox which then doesn't have that bug. A debconf notice 'dovecot now doesn't support mbox folders anymore' does *not* suffice, imho, as a quick apt-get upgrade suddenly escalates to a convert-the-mailserver (and users' .procmailrc, too, and maybe the POP server doesn't even support maildir, and ...) As a dovecot user, I can say that I never, ever had any data loss with dovecot (yes, I'm using mbox). I have a few folders which frequently get one or a few new mail and then are emptied again, and all the messages that should be there, were there. So I'd say downgrade at least until somehone can reproduce this with a different installation than the submitter's. Note also that the submitter runs a self-made woody backport, so it could just be bad dovecot / libc / compiler / whatever interaction. cheers -- vbi -- Every bug you find is the last one.
Attachment:
pgp10bfcV9pXp.pgp
Description: signature