2 messages in net.sourceforge.lists.courier-maildropFw: [maildropl] MAIDROP + MYSQL AND Q...
FromSent OnAttachments
Terence DewaeleJan 2, 2002 12:04 pm 
Terence DewaeleJan 2, 2002 6:19 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:Fw: [maildropl] MAIDROP + MYSQL AND QUOTAActions...
From:Terence Dewaele (dewa@dream-up.com)
Date:Jan 2, 2002 6:19:40 pm
List:net.sourceforge.lists.courier-maildrop

----- Original Message ----- From: "Deim Agoston" <ag@idg.hu> To: "Terence Dewaele" <dewa@dream-up.com> Sent: Thursday, January 03, 2002 12:34 AM Subject: Re: [maildropl] MAIDROP + MYSQL AND QUOTA

I want use maildrop for deliver mail and apply the quota in mailbox. I use postfix with vitual user and courier-imap & courier-pop with virtual user too.

Me too. I use postfix's VDA at the time.

I don't know how to configure maildrop for use mysql userdb and in same time apply quota.

I have seen a line define quota. Look for the maildropmysql.config. You should copy it under /etc.

I have add (in master.cf) : maildrop unix - n n - - pipe flags=R user=vmail argv=/usr/bin/maildrop -d ${recipient}

And don't forget to add maildrop_recipient_limit=1 into main.cf or you will loose mail.

My questions are: - how stable the mysql support in maildrop (I will test at home but I want to be sure before use it on production systems) - how fast it is: I currently use postfix's VDA but may change to maildrop if it's faster (I will test it too but I'm curious about real life experience) - I've seen in the documentation the MAILBOX_MODE and if the mbox file is not there maildrop will create one. Any future plans to include similar thing for Maildir++/Maildir? It's not a true problem as an administration interface could create one but I'm courious. - With maildrop version 1.3.4 I had to upgrade and apply a patch written for maildrop-1.3.2 (it was actually rewrite of line numbers of previous patch writen by a brazilian guy not real upgrading). That was because if I would use postfix+maildrop with userdb and the virtual user doesn't exists in the db the message stand deferred because the return code. It was EX_TEMPFAIL (75) instead of EX_NOUSER (67) what postfix expects if the recipient doesn't exists. So, should I update the patch again? (I will test it but I can do it only 2 days later and I'm curious.) Bye, Ago