HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (
-   Installation/Configuration (
-   -   Maildrop: unable to open mailbox (

KaiserGimmel 24th January 2010 20:10

[Solved]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:


Jan 24 17:54:33 torchwood postfix/pipe[17056]: 37ACA19CE099: to=<>, relay=maildrop, delay=0.06, delay
s=0.03/0.01/0/0.03, dsn=4.3.0, status=deferred (temporary failure. Command output: /usr/bin/maildrop: Unable to open mailbox. )
I didnt alter the permission and they are still correct. vmail is the owner of the /var/vmail folder.

I tried to deliver a recent mail to the maildir:


maildrop -V9 -d < /var/vmail/xxx/xxx/.Archives.2010/cur/1262701017.M786815P10300V0000000000000801I00000000 01BE213A_1.torchwood\,S\=19707\:2\,S

.mailfilter(5): LOGNAME=""
.mailfilter(6): EXTENSION=""
.mailfilter(7): RECIPIENT=""
.mailfilter(8): USER=""
.mailfilter(9): HOST=""
maildrop: Delivering to /var/vmail///.
maildrop: Unable to open mailbox.
I think the Recipient User and Host are not passed in correctly - dont know how to fix this.
My mercurial tells me that the is not altered - but for a overview:


alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
body_checks = regexp:/etc/postfix/body_checks
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
content_filter = amavis:[]:10024
header_checks = regexp:/etc/postfix/header_checks
html_directory = /usr/share/doc/postfix/html
inet_interfaces = all
mailbox_size_limit = 0
message_size_limit = 0
mime_header_checks = regexp:/etc/postfix/mime_header_checks
mydestination =, localhost, localhost.localdomain
myhostname =
mynetworks = [::1]/128
myorigin = /etc/mailname
nested_header_checks = regexp:/etc/postfix/nested_header_checks
proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps
readme_directory = /usr/share/doc/postfix
receive_override_options = no_address_mappings
recipient_delimiter = +
relay_domains = mysql:/etc/postfix/
relayhost =
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
smtpd_client_restrictions = check_client_access mysql:/etc/postfix/
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, check_recipient_access mysql:/etc/postfix/, reject_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_sasl_authenticated_header = yes
smtpd_sender_restrictions = check_sender_access mysql:/etc/postfix/
smtpd_tls_cert_file = /etc/postfix/smtpd.cert
smtpd_tls_key_file = /etc/postfix/smtpd.key
smtpd_tls_security_level = may
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtpd_use_tls = yes
transport_maps = proxy:mysql:/etc/postfix/
virtual_alias_domains =
virtual_alias_maps = proxy:mysql:/etc/postfix/, mysql:/etc/postfix/
virtual_gid_maps = static:5000
virtual_mailbox_base = /var/vmail
virtual_mailbox_domains = proxy:mysql:/etc/postfix/
virtual_mailbox_maps = proxy:mysql:/etc/postfix/
virtual_transport = maildrop
virtual_uid_maps = static:5000
The mysql settings work - same again nothing altered.

Anyone here can give me a clue how to fix this mess?
Would really appreciate it!

till 25th January 2010 09:38

You can not test maildrop like that, so its ok that your test failed.

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.

KaiserGimmel 25th January 2010 11:12

[Solved]Maildrop: unable to open mailbox
Hey till,

thanks for your fast answer - I did a downgrade of maildrop, and it fixed my problem!

For the history:

from the aptitude logs: courier-maildrop 0.60.0-2 -> 0.63.0-2 - so i removed the unstable sources and reinstalled courier-maildrop with that version.

After i entered "postfix flush" I even got all my emails :)

You made my day!

pebkac 2nd February 2010 00:23

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??


KaiserGimmel 2nd February 2010 00:46

Hello Steve,

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


maildrop -v
- 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

aptitude hold courier-maildrop

pebkac 2nd February 2010 00:54

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.


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.

This is after I ran


apt-get update && apt-get install courier-maildrop

pebkac 2nd February 2010 00:59

and just so you can see the error in the mail log.


Feb  1 14:50:48 wci postfix/qmgr[3164]: 1AB0EAC1CF: removed
Feb  1 14:50:48 wci maildrop[4548]: Unable to open mailbox.
Feb  1 14:50:48 wci postfix/pipe[4547]: 72A5AAC1D8: to=<>, relay=maildrop, delay=0.13, delays=0.04/0.02/0/0.07, dsn=4.3.0, status=deferred (temporary failure. Command output: /usr/bin/maildrop: Unable to open mailbox. )

pebkac 2nd February 2010 01:35

I tried it all again. It is installing the correct version, but when I do maildrop -v it says somethign else?????


root@wci:~# apt-get install courier-maildrop
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 0 to remove and 15 not upgraded.
Need to get 0B/951kB of archives.
After this operation, 2597kB of additional disk space will be used.
Selecting previously deselected package courier-maildrop.
(Reading database ... 45905 files and directories currently installed.)
Unpacking courier-maildrop (from .../courier-maildrop_0.60.0-2ubuntu1_i386.deb) ...
Processing triggers for man-db ...
Setting up courier-maildrop (0.60.0-2ubuntu1) ...

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.

rforsythe 2nd February 2010 04:27

This appears related to a maildrop package update pushed out in the last day or two. I was able to downgrade it using this command:

aptitude install maildrop=2.0.4-3

Then do this:

postfix flush

And now my queues are flushing fine. I am also using the following command to prevent this from re-updating, which I will 'unhold' at some point in the future when I see the issue has been resolved...

aptitude hold maildrop

Good luck folks, I had a lot of mail getting queued but seems OK now.

troggie_0092 2nd February 2010 06:22

What was wrong with maildrop that the update caused it to not connect to the mailbox?

Will it be fixed in time to come?

Thank you once again

All times are GMT +2. The time now is 10:23.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.