Data Leung wrote:
Dear List ,
i found somethings interesting , every time when I send e-mail from
A...@test.com to B...@test.com , afterwards when I type ps ax .
I willing found the following " pipe " willing appear for a while ( 5 ~ 10
sec ) .
flags=Rhu user=vmail argv=/usr/bin/maildrop -w 95 -d ${recipient}
My question is , that's normal or not ?
OR because of -d ${recipient} not a valid value so it just wait for time out
and doesn't deliver the warn message ?
Where I could found the error log IF maildrop got miss-config ? since I have
a log create under /var/log/maildrop. Inside the log it sounds like only
show up " Success " logging .
And i don't know how to specified the " Log " level under /etc/maildroprc "
.
run maildrop manually
maildrop -V 6 -d somerecipient -w 95 < message.eml
(run it once as root and once as vmail).
do that with a recipient that is almost over-quota.
make sure the full path where you place your warning message is
accessible. This includes checking all parent directories. make sure no
selinx/apparmor/.... is preventing maildrop from doing its job. (not
probable, but check anyway).
6 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] quotawarnmsg not sent...
