Sounds like you have some debugging messages turned on
somewhere, and that's what gets logged in the bounce, instead
of maildrop's output.
maildrop's actual error message is "maildrop: maildir over quota".
OK, I found that problem. First I upgraded to maildrop 2.0.2, thinking
maybe it had been compiled with debugging on. That wasn't it, so then I
saw and removed the "-V10" argument to maildrop in the postfix
master.cf. Now I am getting something else, only partially right.
The message is now:
<te...@example.com>: permission denied. Command output: WARN: quota
string '25600000' not parseable maildrop: maildir over quota.
So except for that "WARN" part, it is ok. Do I have to regenerate all
the 'maildirsize' files for the new version of maildrop? The test
maildir I am using has a 25MB quota, and is almost all the way full.
Here are the entire contents of its maildirsize file:
[wenadmin@mail]% 10:14 # cat maildirsize
25600000S
24650393 3
[wenadmin@mail]% 10:14 #
Is this no longer the correct format? If it is, and I don't have to
regenerate the maildirsize files, how can I fix the "WARN: quota string
'25600000' not parseable" message? I assume that the correct message I
should see would be like:
<te...@example.com>: permission denied. Command output: maildir over
quota.
Which would make a lot more sense to my users, and look a lot less like
a server error.
Thanks for your help so far...
SPAM-FREE 1.0(2476)