Hi..

I think I found the cause for a problem, that some people (including myself) happen to experience when running vpopmail's vdelivermail from maildrop filter files, with either 'delete' or 'bounce-no-mailbox' as parameter.

The reason why maildrop so often exits with

maildrop: error writing to mailbox. maildrop: Unable to deliver to mailbox.

is because vdelivermail exits, before it read the pipe completly. vdelivermail simply checks whether the receipient is valid, and if not, exits at once, causing a SIGPIPE in maildrop. Apperently adding exception {} to the to "$VPOP" instruction doesnt help.

This result can be reproduced quite easily, even for those without vpopmail: create a maildropfilter  'test': to "|exit 100"

and feed it some text: # maildrop test < test maildrop: error writing to mailbox. maildrop: Unable to deliver to mailbox. # echo $? 75

now alter the test maildirfilter: to "|sleep 1; exit 100" # maildrop test < test # echo $? 100

So, what is the solution? Shouldn't maildrop catch sigpipes and act accordingly?