maildrop common issues

“temporary failure. Command output: maildrop: error writing to mailbox. /usr/bin/maildrop: Unable to deliver to mailbox.” = Disk quota exceeded ( quotatools style kernel quota )

“temporary failure. Command output: /usr/bin/maildrop: Unable to create a dot-lock.” = Incorrect directory permissions/ Directory Maildir not created .

maildrop

Note to self on maildrop

– mailbox_command = /usr/bin/maildrop -d “$USER” -f “$SENDER” “$EXTENSION”
– mbox_command_maps = file
– mailbox_transport master.cf maildrop2 ( differs litely from maildrop )
– .forward

All these result on temporary fails… Since that happen’s had to activate
* maximal_queue_lifetime = 5m

– mailbox_transport results on
orig_to=<xyz@domain.pt>, relay=maildrop2, delay=0.04, delays=0.02/0/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: maildrop: authlib: groupid=100)

– mailbox_command results on
status=deferred (temporary failure. Command output: Unable to execute /dev/null Unable to execute /dev/null maildrop: maildir over quota. )

– mbox_command_maps results on
no error when overquota, message just get’s delivered

– .forward results on
relay=local, delay=0.03, delays=0.01/0/0/0.01, dsn=4.3.0, status=deferred (temporary failure. Command output: Unable to execute /dev/null Unable to execute /dev/null maildrop: maildir over quota. )

– local_transport by maildrop2 results in
status=deferred (temporary failure. Command output: maildrop: authlib: groupid=100)

Since I’m not using Virtual Users my option is but system users in passwd…
– mailbox_command

Added : 23 July 2008 , 22:05

Problems
– Unable to create a dot-lock.
. Wrong directory permissions ? dir permissions are ok
. wrong command? Command is correct.
. requires a valid shell ? Yes, need to have a valid shell so maildrop can create the Maildir with maildirmake in  maildroprc or execute other commands.
. .forward does everything ok

postfix

default_destination_rate_delay

default_destination_recipient_limit

postfix has the features !