Re: [vchkpw] 90% CPU in vchkpw
On Tuesday 29 October 2002 21:22, Brad Dameron wrote: > What does "softlimit" do? it limits the ammount of memory the process may use. in this case about 2MB ram. Luis, which options did you use when compiling vpopmail? > > > -Original Message- > > From: Luis Gustavo Facioni Barcellos [mailto:lbarcellos@;emater.tche.br] > > Sent: Tuesday, October 29, 2002 11:58 AM > > To: [EMAIL PROTECTED] > > Subject: [vchkpw] 90% CPU in vchkpw > > > > > > Hi, all > > > > I have a qmail 1.0.3, daemontools 0.76, qmail-scanner 1.12 with mcafee, > > vpopmail 5.2.1 and sqwebmail 3.3.4 in a brand new Slackware 8.1 box. > > > > Its all running fine, but sometimes the server stops authenticating. The > > top shows a vchkpw process consuming more then 90% CPU and I get a > > *server busy* on client. > > > > my qmail-pop3/run script: > > #!/bin/sh > > env - PATH="/usr/local/qmail/bin:/usr/local/bin" > > MAXCON=40 > > exec /usr/local/bin/softlimit -m 200 \ > > /usr/local/bin/tcpserver -v -H -R -c "$MAXCON" 0 pop3 \ > > /usr/local/qmail/bin/qmail-popup mydomain.here.com \ > > /usr/local/vpopmail/bin/vchkpw /usr/local/qmail/bin/qmail-pop3d > > Maildir 2>&1 > > > > Someone could tell where do I start to fix it? > > > > TIA > > -- > > Gustavo > > -- > > * "Duct tape is like the Force. It has a light side, a dark side, and it > > holds the universe together." > > -- -- Best Regards --- Justin Heesemannionium Technologies [EMAIL PROTECTED]www.ionium.org
Re: [vchkpw] Vpopmail Debian - Problem sending Mials
On 29.10.2002 21:27 Uhr, "David Phillips" <[EMAIL PROTECTED]> wrote: > tcp.smtp (compiled into tcp.smtpd.cdb) controls which IP's are allowed to > connect to tcpserver. It defaults to allow (which would be a single > ":allow" line). Setting RELAYCLIENT for an IP tells qmail-smtpd to allow it > to relay mail. Ok. Got that. > Normally, this file contains all IP's on your network, assuming you want > them to relay through qmail. The following is an example. RBLSMTPD is only > needed if you are using rblsmtpd. Leaving it blank tells rblsmtpd to not > perform lookups against that address (you don't want it looking up your own > addresses): > > 127.:allow,RELAYCLIENT="",RBLSMTPD="" > 192.168.:allow,RELAYCLIENT="",RBLSMTPD="" Well obviously I forgot the '127.:...' entry. Now it works fine locally. I will jut go an try online now. >> My run file is (I just changed the path of the vpopmail-home): > > If your domains directory is on /var, then make sure you have enough space > for all the mail. Yes I will do so. >> #!/bin/sh >> QMAILDUID=`id -u qmaild` >> NOFILESGID=`id -g qmaild` >> MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` > > As a tip, you can get rid of QMAILDUID and NOFILESGID by adding -U to the > tcpserver command line and using "envuidgid qmaild" as the first thing after > exec. What will this help me? >> exec softlimit -m 200 \ >> tcpserver -v -R -l 0 -x /var/lib/vpopmail/etc/tcp.smtp.cdb -c >> "$MAXSMTPD" \ >> -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp qmail-smtpd 2>&1 >> >> When I try to send a message I get the 5.7.1 error. >> I read all the documentation for Newbies on relaying from Chris. > > Does your tcp.smtp file set RELAYCLIENT for the IP that you are sending > from? Yes, I got '127.: ...' and '192.168.0.:... ' as an entry. Now on my online setup I got the following problem: In my office I am sitting behind a firewall. I got a t1 connection but I do _not_have_a fix IP. I am obviously sending mails only from the domains listed in rcpthosts but somehow I still get the 5.7.1 error! Argh. > vpopmail will create vpopmail/etc/open-smtp that it merges with tcp.smtp > when building tcp.smtp.cdb. It does this automatically for any IP that > successfully authenticates via POP3 (or anything using vchkpw, such as > Courier IMAP). tcp.smtp.cdb is automatically rebuilt when this happens. > > You need to make sure vpopmail/bin/clearopensmtp is being run from cron > every 30-60 minutes, otherwise these IP's will never expire. Do I have to check this or has this already been done automatically? Thanks for your kind help. Zeno
[vchkpw] Question about vpopmail and shared folders
I am using vpopmail with courier-imap as my mail solution and I love it so far. I've got a small question about shared folders. When creating a shared mail folder under a shared mailbox directory structure, you use the -s flag to specify permission to the folder. How can this work with virtual domains? I don't see a way of specifying specific permissions and only doing global read/write access to the folder. Taylor Dondich
[vchkpw] how to handle quota
helo all i already put that question but no answer till i receive. i want to know how i implement quota on folders in a single INBOX or Maildir. When quota exceed no mail will come. so plz guide to how implement quota on Maildir qmailadmin implement but it creates problems. thanks. wait for reply.
RE: [vchkpw] Courier-Imap and Sqwebmail
This would probably be a good question for courier-imap or sqwebmail. -Original Message- From: Fernando Costa de Almeida [mailto:falmeida@;easyit.com.br] Sent: Tuesday, October 29, 2002 12:06 PM To: [EMAIL PROTECTED] Subject: [vchkpw] Courier-Imap and Sqwebmail Hi, Ive installed Courier-Imap with vchkpw authentication (qmail + vpopmail + qmailadmin + Courier-IMAP), and all works well: I can connect to the server and etc... But there is a problem: If I delete the Drafts folder (used by Sqwebmail), Sqwebmail shows an errors when I try to send a message, because it needs this folder to store something. The question is: How can I avoid that users delete this folder in Courier-IMAP? Sorry if it was off-topic... Thanks in advance, ___ ALMEIDA, Fernando Costa de Computeasy Informática www.computeasy.com.br BSD USER BSD050945 ICQ 72293951
Re: [vchkpw] 90% CPU in vchkpw
Brad Dameron writes: > What does "softlimit" do? http://cr.yp.to/daemontools/softlimit.html -- David Phillips <[EMAIL PROTECTED]> http://david.acz.org/
Re: [vchkpw] Vpopmail Debian - Problem sending Mials
Zeno Davatz writes: > I followed the below HOWTO and think is great - it helped me a lot. I > managed to send and receive messages locally an online. Cool. > What I do not quite understand yet is how vpopmail and qmail handle > the outgoing messages via smtp: vpopmail does not affect outgoing mail. It controls whether or not certain IP's are allowed to relay mail when connecting to qmail-smtpd. >> * Change the run script for qmail-smtpd (/service/qmail-smtpd/run) >> to use vpopmail. The tcp.smtp.cdb file needs to point to the one in >> the vpopmail home directory (ex. /home/vpopmail/etc/tcp.smtp.cdb). >> This step makes POP-before-SMTP work. > Does this file contain the all the hosts for witch my Server will send > Email? tcp.smtp (compiled into tcp.smtpd.cdb) controls which IP's are allowed to connect to tcpserver. It defaults to allow (which would be a single ":allow" line). Setting RELAYCLIENT for an IP tells qmail-smtpd to allow it to relay mail. Normally, this file contains all IP's on your network, assuming you want them to relay through qmail. The following is an example. RBLSMTPD is only needed if you are using rblsmtpd. Leaving it blank tells rblsmtpd to not perform lookups against that address (you don't want it looking up your own addresses): 127.:allow,RELAYCLIENT="",RBLSMTPD="" 192.168.:allow,RELAYCLIENT="",RBLSMTPD="" > My run file is (I just changed the path of the vpopmail-home): If your domains directory is on /var, then make sure you have enough space for all the mail. > #!/bin/sh > QMAILDUID=`id -u qmaild` > NOFILESGID=`id -g qmaild` > MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` As a tip, you can get rid of QMAILDUID and NOFILESGID by adding -U to the tcpserver command line and using "envuidgid qmaild" as the first thing after exec. > exec softlimit -m 200 \ > tcpserver -v -R -l 0 -x /var/lib/vpopmail/etc/tcp.smtp.cdb -c > "$MAXSMTPD" \ > -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp qmail-smtpd 2>&1 > > When I try to send a message I get the 5.7.1 error. > I read all the documentation for Newbies on relaying from Chris. Does your tcp.smtp file set RELAYCLIENT for the IP that you are sending from? vpopmail will create vpopmail/etc/open-smtp that it merges with tcp.smtp when building tcp.smtp.cdb. It does this automatically for any IP that successfully authenticates via POP3 (or anything using vchkpw, such as Courier IMAP). tcp.smtp.cdb is automatically rebuilt when this happens. You need to make sure vpopmail/bin/clearopensmtp is being run from cron every 30-60 minutes, otherwise these IP's will never expire. -- David Phillips <[EMAIL PROTECTED]> http://david.acz.org/
RE: [vchkpw] 90% CPU in vchkpw
What does "softlimit" do? --- Brad Dameron Network Account Executive TSCNet Inc. www.tscnet.com Silverdale, WA. 1-888-8TSCNET > -Original Message- > From: Luis Gustavo Facioni Barcellos [mailto:lbarcellos@;emater.tche.br] > Sent: Tuesday, October 29, 2002 11:58 AM > To: [EMAIL PROTECTED] > Subject: [vchkpw] 90% CPU in vchkpw > > > Hi, all > > I have a qmail 1.0.3, daemontools 0.76, qmail-scanner 1.12 with mcafee, > vpopmail 5.2.1 and sqwebmail 3.3.4 in a brand new Slackware 8.1 box. > > Its all running fine, but sometimes the server stops authenticating. The > top shows a vchkpw process consuming more then 90% CPU and I get a > *server busy* on client. > > my qmail-pop3/run script: > #!/bin/sh > env - PATH="/usr/local/qmail/bin:/usr/local/bin" > MAXCON=40 > exec /usr/local/bin/softlimit -m 200 \ > /usr/local/bin/tcpserver -v -H -R -c "$MAXCON" 0 pop3 \ > /usr/local/qmail/bin/qmail-popup mydomain.here.com \ > /usr/local/vpopmail/bin/vchkpw /usr/local/qmail/bin/qmail-pop3d > Maildir 2>&1 > > Someone could tell where do I start to fix it? > > TIA > -- > Gustavo > -- > * "Duct tape is like the Force. It has a light side, a dark side, and it > holds the universe together." > -- > > >
[vchkpw] Courier-Imap and Sqwebmail
Hi, Ive installed Courier-Imap with vchkpw authentication (qmail + vpopmail + qmailadmin + Courier-IMAP), and all works well: I can connect to the server and etc... But there is a problem: If I delete the Drafts folder (used by Sqwebmail), Sqwebmail shows an errors when I try to send a message, because it needs this folder to store something. The question is: How can I avoid that users delete this folder in Courier-IMAP? Sorry if it was off-topic... Thanks in advance, ___ ALMEIDA, Fernando Costa de Computeasy Informática www.computeasy.com.br BSD USER BSD050945 ICQ 72293951
Re: [vchkpw] Vpopmail Debian - Problem sending Mials
Hi I followed the below HOWTO and think is great - it helped me a lot. I managed to send and receive messages locally an online. What I do not quite understand yet is how vpopmail and qmail handle the outgoing messages via smtp: On 24.10.2002 2:06 Uhr, "David Phillips" <[EMAIL PROTECTED]> wrote: ... \snip > * Install vpopmail from source. The Debian packages are pretty old and seem > to be buggy, at least the last time I tried. > > * Change the run script for qmail-smtpd (/service/qmail-smtpd/run) to use > vpopmail. The tcp.smtp.cdb file needs to point to the one in the vpopmail > home directory (ex. /home/vpopmail/etc/tcp.smtp.cdb). This step makes > POP-before-SMTP work. Does this file contain the all the hosts for witch my Server will send Email? My run file is (I just changed the path of the vpopmail-home): #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec softlimit -m 200 \ tcpserver -v -R -l 0 -x /var/lib/vpopmail/etc/tcp.smtp.cdb -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp qmail-smtpd 2>&1 When I try to send a message I get the 5.7.1 error. I read all the documentation for Newbies on relaying from Chris. Thanks for any help and hints. Zeno > * Install a qmail-pop3d service. The easiest way to do this is qmail-conf. > You could use qmail-conf to redo all the qmail services, but it is easier to > stick with the ones that qmail-run sets up: > > http://www.din.or.jp/~ushijima/qmail-conf.html > > * Allow incoming connections to pop3d. By default, it does not allow any > connections. There is an add-client script in > /var/qmail/service/qmail-pop3d that can be used. To simply allow > connections from everywhere, create an empty tcp file and run the Makefile. > You will need to run the Makefile after using add-client. > > * Change the qmail-pop3d run script to use vpopmail. It needs to use vchkpw > as the checkpassword program. Change this to your vchkpw program (ex. > /home/vpopmail/bin/vchkpw). The parameter to be changed is the second > parameter to qmail-popup. > > * Restart all of the services: > > svc -t /service/qmail-* > > * You can make things easier if you add /var/qmail/bin and the vpopmail bin > directory to root's PATH. > > -- > David Phillips <[EMAIL PROTECTED]> > http://david.acz.org/
Re: [vchkpw] Vdeldomain
On 29.10.2002 20:14 Uhr, "Clayton Weise" <[EMAIL PROTECTED]> wrote: > Check your qmail configs to see if it's in there: > > /var/qmail/control/virtualdomains > /var/qmail/control/rcpthosts > /var/qmail/users/assign > > And after you've changed those, you'll need to run a qmail-newu to rebuild > the assign cdb file. Thanks Clayton, for your kind help. You saved my night. Zeno > -Original Message- > From: Zeno Davatz [mailto:zdavatz@;ywesee.com] > Sent: Tuesday, October 29, 2002 10:49 AM > To: [EMAIL PROTECTED] > Subject: [vchkpw] Vdeldomain > > > I deinstalled vpopmail and installed it again from source. > > I do vdeldomain yweseelocal.com and get: > Error: Domain does not exist. > > I do vadddomain yweseelocal.com and get: > Error: Domain already exists. > > What can I do to remove the domain completely so that I can add it again. > > Thanks for any help and hints. > > Zeno > > > > > -- Mit freundlichen Grüssen / best regards Zeno Davatz Strategie & Akquisition +41 1 350 85 86 www.ywesee.com > intellectual capital connected > www.generika.cc
Re: [vchkpw] Re: qmailadmin-limits update
On Tue, 29 Oct 2002, Brian Kolaci wrote: > > > > > On Thu, 24 Oct 2002, John Johnson wrote: > > > > > I am not a programmer but from what I can see this > > > looks like a clean and very efective way to do the > > > qmailadmin-limits. If you try to bloat things down > > > for something that MIGHT be added or changed then > > > we really will not have things really planned, they > > > will be half planned and still open waiting for the > > > stuff people might want to add to the tables. I say > > > we go with this, lock it down and make it happen and > > > deal with tomarrow when tomarrow happens as far as the > > > tables. > > > > > > -John > > > > > > > Yeah. This sounds good. I just find out that I need qmailadmin-limits > > myself too, and it would be nice to store this data in mysql. > > > > Brian, do you already have some patches for this? > > > > I'm willing to test and maybe spent some time coding this if needed.. > > > > > > - Pasi Kärkkäinen > > > I've had the basic table layouts done since January > and have been running in production with a patched > vdelivermail and qmailadmin since then. Mine supports > the limits as given, and the quotas (not message counts) > in vdelivermail. It should take more or less an hour to > get this written - actually just change what I have > to include the additional fields, however you're only > the second person to reply to this. I was hoping to get > a consensus from people as to what else is needed or > required, or find out if its overkill and to strip some. > OK. Sounds good. Maybe you should just put those patches available.. people could test them and start giving feedback.. At least I would do so :) > Thanks, > > Brian > - Pasi Kärkkäinen ^ . . Linux /-\ Choice.of.the .Next.Generation.
[vchkpw] LDAP-patch
Hi, this is my second drop to make the LDAP-Code from vpopmail more robust. The second patch includes my first patch I send a 3 weeks ago. To review my work I'll give a link where all patches are available. Changes: - multiple domains stored in LDAP - operational - vsetuserquota stored in LDAP - operational - Bugfixes - Code cleanup For each Domain a seperate OU is setup, so that a user [EMAIL PROTECTED] is different from user [EMAIL PROTECTED] I have testet the following which worked: - vadddomain - vadduser - vdeluser - vdeldomain - vsetuserquota - compatible to qmailadmin - compatible to vdeliver My next TODO items: - code cleanup - more flexible error handling - add more items stored in LDAP You are welcome to test it on your system, for me it works !! You can download my patches on : http://www.tiski.de/linux/patches/vpopmail/patch-ldap-1.gz http://www.tiski.de/linux/patches/vpopmail/patch-ldap-2.gz Note this are not incremental patches !! Copy the patch-ldap-2.gz to your vpopmail dir, gunzip it and use: patch -p1 < patch-ldap-2 to aplly. The patches are against vpopmail-5.3.8, but they should apply cleanly against vpopmail-5.3.8. Enjoy Jens This mail sent through Novasoft WWW-Mail
Re: [vchkpw] Does qmailadmin support MySQL....
On Wed, 30 Oct 2002, Neo Wee Teck wrote: > Does qmailadmin support MySQL for vpopmail? > > Yes, if you have compiled vpopmail with mysql support. qmailadmin just talks to vpopmail, and vpopmail talks to whatever backend you have configured it to talk to. - Pasi Kärkkäinen ^ . . Linux /-\ Choice.of.the .Next.Generation.
RE: [vchkpw] Vdeldomain
Check your qmail configs to see if it's in there: /var/qmail/control/virtualdomains /var/qmail/control/rcpthosts /var/qmail/users/assign And after you've changed those, you'll need to run a qmail-newu to rebuild the assign cdb file. -Clayton -Original Message- From: Zeno Davatz [mailto:zdavatz@;ywesee.com] Sent: Tuesday, October 29, 2002 10:49 AM To: [EMAIL PROTECTED] Subject: [vchkpw] Vdeldomain I deinstalled vpopmail and installed it again from source. I do vdeldomain yweseelocal.com and get: Error: Domain does not exist. I do vadddomain yweseelocal.com and get: Error: Domain already exists. What can I do to remove the domain completely so that I can add it again. Thanks for any help and hints. Zeno
[vchkpw] 90% CPU in vchkpw
Hi, all I have a qmail 1.0.3, daemontools 0.76, qmail-scanner 1.12 with mcafee, vpopmail 5.2.1 and sqwebmail 3.3.4 in a brand new Slackware 8.1 box. Its all running fine, but sometimes the server stops authenticating. The top shows a vchkpw process consuming more then 90% CPU and I get a *server busy* on client. my qmail-pop3/run script: #!/bin/sh env - PATH="/usr/local/qmail/bin:/usr/local/bin" MAXCON=40 exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -H -R -c "$MAXCON" 0 pop3 \ /usr/local/qmail/bin/qmail-popup mydomain.here.com \ /usr/local/vpopmail/bin/vchkpw /usr/local/qmail/bin/qmail-pop3d Maildir 2>&1 Someone could tell where do I start to fix it? TIA -- Gustavo -- * "Duct tape is like the Force. It has a light side, a dark side, and it holds the universe together." --
[vchkpw] Error compiling
Hi, The first error was that make could not find "mysql.h" ( I copied "vmysql.h") After that I receive the following error when running "make" : vauth.c:35: parse error before 'mysql_update' Any Assistance would be appreciated. You have a good day now, Carl
[vchkpw] Vdeldomain
I deinstalled vpopmail and installed it again from source. I do vdeldomain yweseelocal.com and get: Error: Domain does not exist. I do vadddomain yweseelocal.com and get: Error: Domain already exists. What can I do to remove the domain completely so that I can add it again. Thanks for any help and hints. Zeno
[vchkpw] Does qmailadmin support MySQL....
Does qmailadmin support MySQL for vpopmail?
Re: [vchkpw] Re: qmailadmin-limits update
> > On Thu, 24 Oct 2002, John Johnson wrote: > > > I am not a programmer but from what I can see this > > looks like a clean and very efective way to do the > > qmailadmin-limits. If you try to bloat things down > > for something that MIGHT be added or changed then > > we really will not have things really planned, they > > will be half planned and still open waiting for the > > stuff people might want to add to the tables. I say > > we go with this, lock it down and make it happen and > > deal with tomarrow when tomarrow happens as far as the > > tables. > > > > -John > > > > Yeah. This sounds good. I just find out that I need qmailadmin-limits > myself too, and it would be nice to store this data in mysql. > > Brian, do you already have some patches for this? > > I'm willing to test and maybe spent some time coding this if needed.. > > > - Pasi Kärkkäinen I've had the basic table layouts done since January and have been running in production with a patched vdelivermail and qmailadmin since then. Mine supports the limits as given, and the quotas (not message counts) in vdelivermail. It should take more or less an hour to get this written - actually just change what I have to include the additional fields, however you're only the second person to reply to this. I was hoping to get a consensus from people as to what else is needed or required, or find out if its overkill and to strip some. Thanks, Brian > > > > Brian Kolaci writes: > > > > > > > > I've done some thinking about the many suggestions about handling > > > the limits and wanted to summarize some of the pros & cons. > > > > > > First was whether to use a generic approach that had a > > > table with domain, name, value which has a row for each > > > parameter, or to use a single row will all values per domain. > > > > > > The pros: > > > > > > - allows extensability - we can easily add new attributes with a new row > > > > > > The cons: > > > > > > - consumes more space - there's overhead of N-1 times the size of > > >the domainname, plus N times the size of the option name, plus > > >overhead for the value to be able to hold the largest possible value > > >even for smaller items. > > > - updates not atomic - there would have to be N update statements to > > >change a value. We would have to encapsulate the updates within a > > >transaction. > > > - performance - there would be more data going back and forth to/from > > >the sql server. We would also have to store all data as strings in > > >the database and do conversions. When we perform updates, there would > > >have to be N updates sent to the server, which is N round trips plus > > >the transaction overhead. > > > > > > At first when I saw the suggestion I thought it was a great idea, > > > however after thinking it over, I believe performance and reliability > > > would suffer just to save an "alter table" if/when the schema needs to > > > be extended. > > > > > > That being said, I'll continue down the path of a single row per domain, > > > however if others have arguments to the contrary, please speak up. > > > > > > The schema needs to be adjusted to accomodate all the requests I've seen. > > > Both the C structure and the database schema needs to change. > > > > > > I've read the Maildir++ quotas and understand that the concept of a > > > "Maildir quota" encapsulates both a maximum size and maximum message count. > > > It appears to be just a string that contains "#S,#C", which combines > > > the Size and the Count into one string, where the #C is optional. I > > > personally would want them separated as two values, since you can't do > > > much with the combined string but pass it around. To actually use it, > > > you need to split them up with a parser and convert them to numbers. > > > I think the API should keep them as numbers in the structure in C. Its > > > easy enough to combine them with a snprintf(), but more work to parse > > > them out to actually use/enforce them. How they're stored in the database > > > and/or file doesn't really matter (but should be discussed). I believe > > > they were combined due to the old hack to put the quota value into > > > the "shell" field of a password record. Being that we're in new > > > territory here, we don't even have the concept of message count in > > > .qmailadmin-limits files or the database, so adding a field/column > > > for the "default per-user message count" or "per-domain message count" > > > shouldn't be an issue, and would even keep the old fileformat backward > > > compatible. In fact, it appears the vqpasswd structure has already > > > been amended to add a "clear password", so why wasn't it just updated > > > to add fields for "storage quota" and "max message count" ? Wouldn't
Re: [vchkpw] Re: qmailadmin-limits update
On Thu, 24 Oct 2002, John Johnson wrote:
> I am not a programmer but from what I can see this
> looks like a clean and very efective way to do the
> qmailadmin-limits. If you try to bloat things down
> for something that MIGHT be added or changed then
> we really will not have things really planned, they
> will be half planned and still open waiting for the
> stuff people might want to add to the tables. I say
> we go with this, lock it down and make it happen and
> deal with tomarrow when tomarrow happens as far as the
> tables.
>
> -John
>
Yeah. This sounds good. I just find out that I need qmailadmin-limits
myself too, and it would be nice to store this data in mysql.
Brian, do you already have some patches for this?
I'm willing to test and maybe spent some time coding this if needed..
- Pasi Kärkkäinen
> Brian Kolaci writes:
>
> >
> > I've done some thinking about the many suggestions about handling
> > the limits and wanted to summarize some of the pros & cons.
> >
> > First was whether to use a generic approach that had a
> > table with domain, name, value which has a row for each
> > parameter, or to use a single row will all values per domain.
> >
> > The pros:
> >
> > - allows extensability - we can easily add new attributes with a new row
> >
> > The cons:
> >
> > - consumes more space - there's overhead of N-1 times the size of
> >the domainname, plus N times the size of the option name, plus
> >overhead for the value to be able to hold the largest possible value
> >even for smaller items.
> > - updates not atomic - there would have to be N update statements to
> >change a value. We would have to encapsulate the updates within a
> >transaction.
> > - performance - there would be more data going back and forth to/from
> >the sql server. We would also have to store all data as strings in
> >the database and do conversions. When we perform updates, there would
> >have to be N updates sent to the server, which is N round trips plus
> >the transaction overhead.
> >
> > At first when I saw the suggestion I thought it was a great idea,
> > however after thinking it over, I believe performance and reliability
> > would suffer just to save an "alter table" if/when the schema needs to
> > be extended.
> >
> > That being said, I'll continue down the path of a single row per domain,
> > however if others have arguments to the contrary, please speak up.
> >
> > The schema needs to be adjusted to accomodate all the requests I've seen.
> > Both the C structure and the database schema needs to change.
> >
> > I've read the Maildir++ quotas and understand that the concept of a
> > "Maildir quota" encapsulates both a maximum size and maximum message count.
> > It appears to be just a string that contains "#S,#C", which combines
> > the Size and the Count into one string, where the #C is optional. I
> > personally would want them separated as two values, since you can't do
> > much with the combined string but pass it around. To actually use it,
> > you need to split them up with a parser and convert them to numbers.
> > I think the API should keep them as numbers in the structure in C. Its
> > easy enough to combine them with a snprintf(), but more work to parse
> > them out to actually use/enforce them. How they're stored in the database
> > and/or file doesn't really matter (but should be discussed). I believe
> > they were combined due to the old hack to put the quota value into
> > the "shell" field of a password record. Being that we're in new
> > territory here, we don't even have the concept of message count in
> > .qmailadmin-limits files or the database, so adding a field/column
> > for the "default per-user message count" or "per-domain message count"
> > shouldn't be an issue, and would even keep the old fileformat backward
> > compatible. In fact, it appears the vqpasswd structure has already
> > been amended to add a "clear password", so why wasn't it just updated
> > to add fields for "storage quota" and "max message count" ? Wouldn't
> > that be cleaner? Sorry for going off topic... I'll stick to the subject
> > now.
> >
> > So my suggestion would be to store 4 "quota type" fields to handle
> > storage/message count for per-domain/per-user. Any comments?
> >
> > Here's what I would see as a new C structure:
> >
> > /*
> > * permissions for non-postmaster admins
> > */
> > #define VLIMIT_DISABLE_CREATE 0x01
> > #define VLIMIT_DISABLE_MODIFY 0x02
> > #define VLIMIT_DISABLE_DELETE 0x04
> >
> > struct vlimits {
> > int maxpopaccounts;
> > int maxaliases;
> > int maxforwards;
> > int maxautoresponders;
> > int maxmailinglists;
> > int diskquota;
> > int maxmsgcount;
> > int defaultquota;
> > int defaultmaxmsgcount;
> > /* the following are 0 (false) or 1 (true) */
> > short disable_pop;
> > short disable_im
Re: [vchkpw] Default-quota per domain and per user..
On Mon, 28 Oct 2002, Pasi Kärkkäinen wrote: > > Hello! > > I have read the README.quotas from vpopmail 5.2.1, but I still have some > questions.. > > 1. What is the correct way to setup per domain default-quota? How does it >work? Where is the quota-information stored? It needs patched qmail to >understand it? > > 2. How can I override the per-domain quota for some specific user in that >domain? Just use the vsetuserquota for that user, and it then uses the >user's own quota rather than the domain-wide quota? > > 3. Does courier-imapd understand the per-domain quota if user does not >have specific quota for him/her? How about qmail's pop3d? > > 4. Can domain admins (postmaster) edit the per user quota from qmailadmin? >needs some patch? > > I'm currently running vpopmail 5.0.1, so I need to upgrade at least to > 5.2.1.. should I upgrade to 5.3.x, are there any enhancements to quota > code compared to 5.2.1 ? > > How is this qmailadmin-limits related to quota? I've been reading the > discussion on the list during last couple of days but I'm not quite sure > what is qmailadmin-limits used for.. > Quoting myself.. I played with these things a little, and it seems to be like this: - With vqadmin (or by editing ~vpopmail/domains/domain/.qmailadmin-limits) you can specify maximun number of accounts and the default quota etc for each domain. Qmailadmin honours these limits and sets the quota like specified in .qmailadmin-limits, if you don't specify some other quota for that user. - In vpopmail vdelivermail is responsible for handling the Maildir++ quota when user gets new mail via SMTP. No need to patch Qmail. I suppose vdelivermail gets the per user quota information from vpopmail (from the backend you have compiled vpopmail with, mysql, ldap or so). - --enable-hardquota in vpopmail causes the mail to be bounced back if the user is over quota. Without this option the mail will NOT be bounced back when the user is over quota. so.. I think that's how it works? And in pop/imap servers you only need to update the maildirsize file when you remove mails from the server (because pop/imap servers can't add new files to the Maildir), correct? Courier supports this out-of-the-box, and there is separate patch for the qmail's pop3d too with vpopmail.. Then question about qmailadmin.. I remember reading from the archives that somebody had a patch for qmailadmin to modify per user quota.. is that available from someplace? And the qmailadmin-limits discussion on the list a while ago is about storing the contents of .qmailadmin-limits file in mysql? (Plus of course patching vqadmin and qmailadmin to use it from mysql too). Thanks! - Pasi Kärkkäinen ^ . . Linux /-\ Choice.of.the .Next.Generation.
[vchkpw] Limiting size of the emails sent based on quota
Hi all, I have to add the following feature in my email system: "Users of a determined domain can't sent email with size greater than 20% of their quota." Ive already have vpopmail, sqwebmail, qmailadmin, vqadmin working well with LDAP and quotas, but I dont know (yet) how to do the feature above. Any help willl be apreciated, ___ ALMEIDA, Fernando Costa de Computeasy Informática www.computeasy.com.br BSD USER BSD050945 ICQ 72293951
Re: [vchkpw] Qmail Vpopmail
- Original Message - From: "Joeffrey Betita" <[EMAIL PROTECTED]> To: "Vchkpw" <[EMAIL PROTECTED]> Sent: Tuesday, October 29, 2002 10:22 PM Subject: [vchkpw] Qmail Vpopmail > > i already change the checkpassword. below is my configuration. what should > i do next. > > > #!/bin/sh > MAXCON=100 > exec /usr/local/bin/softlimit -m 500 \ > /usr/local/bin/tcpserver -v -R -H -c "$MAXCON" \ > 0 110 /var/qmail/bin/qmail-popup example.com.ph /bin/vchkpw \ > /var/qmail/bin/qmail-pop3d Maildir 2>&1 Joeffrey, More than likely it should be this (note the change to the vchkpw path on the 2nd last line of the script) : #!/bin/sh MAXCON=100 exec /usr/local/bin/softlimit -m 500 \ /usr/local/bin/tcpserver -v -R -H -c "$MAXCON" \ 0 110 /var/qmail/bin/qmail-popup example.com.ph /home/vpopmail/bin/vchkpw \ /var/qmail/bin/qmail-pop3d Maildir 2>&1 Also, I reckon the softlimit is set a bit high I would recommend 200 for a "standard" vpopmail install, or 300 for installs using the MySQL backend. Michael.
[vchkpw] Qmail Vpopmail
i already change the checkpassword. below is my configuration. what should i do next. #!/bin/sh MAXCON=100 exec /usr/local/bin/softlimit -m 500 \ /usr/local/bin/tcpserver -v -R -H -c "$MAXCON" \ 0 110 /var/qmail/bin/qmail-popup example.com.ph /bin/vchkpw \ /var/qmail/bin/qmail-pop3d Maildir 2>&1 do i have to create a file /var/qmail/supervise/qmail-pop3d/vchkpw insert this script or configuration Here is a sample startup line for qmail-pop3d and vchkpw env - PATH="/var/qmail/bin:/usr/local/bin" \ tcpserver -H -R 0 pop-3 \ /var/qmail/bin/qmail-popup your.domain.com \ /home-dir-of-vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir & --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.408 / Virus Database: 230 - Release Date: 10/24/2002
