8 messages in net.sourceforge.lists.courier-maildropRE: [maildropl] maildrop+mysql quota
FromSent OnAttachments
Maxim KalinkevichMar 10, 2003 6:18 am 
Philon TervingMar 13, 2003 3:18 pm 
Jacob S. BarrettMar 14, 2003 8:19 am 
RolanMar 16, 2003 7:25 pm 
Jacob S. BarrettMar 18, 2003 8:04 am 
Rolan YangApr 25, 2003 9:50 am 
p dont thinkApr 25, 2003 11:44 am 
Rolan YangApr 25, 2003 1:54 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [maildropl] maildrop+mysql quotaActions...
From:p dont think (pdon@angrynerds.com)
Date:Apr 25, 2003 11:44:42 am
List:net.sourceforge.lists.courier-maildrop

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

-----Original Message----- From: cour@lists.sourceforge.net [mailto:courier- mail@lists.sourceforge.net] On Behalf Of Rolan Yang Sent: Friday, April 25, 2003 9:50 AM To: Jacob S. Barrett; cour@lists.sourceforge.net Subject: Re: [maildropl] maildrop+mysql quota

Are you using the standalone version of maildrop?

I'm pretty much gave up on attempting to use mysql based maildrop quotas. and resorted to some dirty shell scripting that runs "maildirmake -q"

How does maildrop know to re-create a maildirsize file if you delete it? There must be a flag somewhere that indicates the maildirsize had existed before.

Another thing that's been bugging me is that the maildrop man page lists a -w option which supposedly sends a soft quota warning message however this simply does not work (I am using delivery mode, btw). When using "deliverquota" it succeeds, but not with "maildrop -w 90"

~Rolan

Jacob S. Barrett wrote:

I deleted it and it came back after the first message was delivered. My guess is that maildrop creates them if they don't exist where the default ./Maildir delivery doesn't so you have to create it first.

-Jake

Rolan wrote:

Would it still work if you deleted the maildirsize file?

Jacob S. Barrett wrote:

I use maildrop 1.5.0 on freebsd 4.7 working with mysql - there to be stored base of users. I needed to make a quota for virtual users and I have faced with a problem. With the help maildirmake -q it is possible to specify the size of a quota which to be stored(kept) in a file maildirsize - and then all works. If to define quota in mysql database - that does not work.

Whether who faced with similar? It is possible specify size of quota only in mysql ?

Are you using the courier port in FreeBSD. I had to update it a bit to bet a newer maildrop that supported quota messages before I could use it. It is all working for me. I have mysql virtual users with quota in the database. You must initially set the quota with maildirmake -q but after each message delivery the maildirsize quota is updated from the database value.

_______________________________________________ Courier-maildrop mailing list Cour@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/courier-maildrop