You have solved a problem that's been irking me for months.
The problem was that I only put the # of bytes in the quota field and
did not
specify it in the "20000000S" maildrop format. After updating the field,
the softquota
warning message also began to work! What a beautiful thing.
Even with the corrupt data in the "quota" field, maildrop was able to
fallback and
correctly do its accounting when I manually created the maildirsize file
with maildirmake.
However, I guess the "warning" part of code does a comparison
with the quota data from the mysql table, and not the maildirsize file.
Thanks much,
~Rolan
p dont think wrote:
Using the most recent version of maildrop, I have no such problems and
need no custom scripts, etc. Make sure you compiled with
--enable-maildirquota and --enable-maildropmysql and that your
maildropmysql.config file is specified by something like
--with-mysqlconfig=/etc/maildrop/maildropmysql.conf and that you have
configured a quota column in that file.
I found that if maildrop does not understand the contents of that column
in mysql, it will ignore the quota functionality, so make sure the
column is of the correct format.... such as "5000000S" or
"5000000S,300C" (obviously, it's a varchar, not an int column).
If your maildirsize file is being recreated, that says to me that it is
working file... sorry to chime in so late on this thread, but isn't that
what you want?
Also, the -w flag will work fine as long as there is a maildirsize file
and everything is set up correctly.... make sure the warning message
text is where maildrop expects - for me, that was
/usr/local/etc/quotawarnmsg
Cheers,
paul
8 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] maildrop+mysql quota
