Maildrop: unable to open mailbox

yesterday I did a big misstake - i added the unstable sources to the sources.lst (to update my mumble server) and my apt-auto updater did a complete update of my server tonight. Its a debian lenny machine. With the old setup everything worked fine

The Problem is now that maildrop cant deliver new emails to the maildir:

To your original problem. Debian has two maildrop packages, one with mysql support and a second one without maildrop support. It seems as if you replaced the maildrop on your system with the one without mysql support, this results in the problem that myaildrop can not lookup the maildir anymore in mysql and so the delivery fails. You should reinstall the original maildrop package that is used in the perfect server guide.

Can you tell me the commands you used to fix this. I have the same problem.
I did do a apt-get remove maildrop and then did a apt-get install maildrop and still no go. I did disable the sources that I had enabled before so not sure what else to do??

I think you either forgot the apt-get update to get the old packages into the cache or you have a diffrent problem.

Try

maildrop -v

Click to expand...

- if you have another version then 0.60.0-2 you have still the wrong one. Remove it - apt-get update && apt-get install courier-maildrop and verify again.
If you got it you can hold the package (i would use aptitude instead of apt) so it keeps the current version until you say so. Its

I did do the apt-get update after I posted and tried again to no avail. I did you what you suggested and still no go. The difference is that when I did it I only did apt-get install maildrop, you suggested courier-maildrop.

Code:

root@wci:~# maildrop -v
maildrop 2.0.4 Copyright 1998-2005 Double Precision, Inc.
GDBM/DB extensions enabled.
Maildir quota extension enabled.
This program is distributed under the terms of the GNU General Public
License. See COPYING for additional information.
root@wci:~#

Glad my fix is working for everyone, I just wish the new version was working too. :-/ I have no idea when the package owner will fix it, that's up to them.

Also, you don't need to remove courier-maildrop first if you had put it on for testing as part of this debacle; the 'install maildrop=2.0.4-3' will remove it for you since it conflicts.

My hope is when the new version is fixed, someone will be nice enough to post it up here so we can 'aptitude unhold maildrop' and let it update again. My fear is some security flaw will become known in this version and we won't be able to correct it due to this upgrade bug.

Mhh... its in the unstable sources (im on debian) so its "okay" that it might not work properly.

My question was related to ispconfig and its support of the new courier authlib. As far as i understand it maildrop uses the courier authlib - in the previous version they directly used a mysql auth from maildrop.

With correct setting files (provided by ispconfig) working with this new auth lib the current maildrop should work, right ?

My question was related to ispconfig and its support of the new courier authlib. As far as i understand it maildrop uses the courier authlib - in the previous version they directly used a mysql auth from maildrop.

Click to expand...

No, thats not the case as maildrop auth is not configured separately. Maildrop uses the normal auth mechanism of courier and this is set at compile time by the maildrop package maintainer. ISPConfig configures only courier-authdaemon which is used as authentication source for all courier based applications incl. maildrop.

Which Ubuntu version do you use that causes this problem? I installed just a fresh Ubuntu 9.10 server with all updates applied and ISPConfig 3.0.1.6 and the mail delivery works, no maildrop errors. Maybe there is a bug in the maildrop package that occurs only when its is updated and not when its newly installed.

[update] This is the version of the maildrop package installed on my test system: