Re: [vchkpw] About to release new devel version 5.3.20
On Tuesday, March 25, 2003, at 04:25 PM, Robin Bowes wrote: I'm about to release a new 5.3.20 devel version. Does anyone have any patches they would like to submit? No, but would it be difficult to move mysql options from vmysql.h to configure options, e.g. ./configure \ --with-mysql-update-server=servername \ --with-mysql-update-user=username \ --with-mysql-update-password=password \ --with-mysql-read-server=servername \ --with-mysql-read-user=username \ --with-mysql-read-password=password The --with-mysql-read-* options could be optional, i.e. use the update server values if the read server is not present. I'd really like to see this. Cheers, R. I would like to see that as well. :) Matt
Re: [vchkpw] About to release new devel version 5.3.20
On Tuesday 25 March 2003 01:47, Brian Kolaci wrote: Hi Justin, There are currently ways to limit IMAP. One thing you should remember is that the vlimits API is for full domain limits, not individual users. There are permission bits in the GID field in the password entry for the user. These I believe work. Before actually implementing the API, I sent out a request for all the additional items people wanted to see over and above what I wanted. This way the database schema would only have to be written once, and filled in later. Some limit the qmailadmin app, others go directly into vdelivermail. Others will go into other areas. Overall, I think we have a functional system as is, with placeholders for future features. The wishlist is high, but only so many things can make each release. If you've got the cycles and can crank out some of it tonight, send in a patch. Hm, i tried to explain by mentioning disable_imap as an example. disable_pop, disable_smtp, disable_webmail ... things like that should be cared for in vchkpw. furthermore, vadduser doesn't care for maxpopaccounts, valias ignores maxaliases... I guess it's ok, the way it is now. And: I love it the way it is for a 5.3.20. But: not for 5.4.0. The next stable release shouldn't have placeholders for a very nice system and get some of the features added for every update release. Instead it should have a working system with fully implemented vlimits. But this is just my opinion, and since I've always used the vpopmail-dev versions, the whole 5.4.0 release isn't bothering me that much :) -- Mit internetten Grüßen / Best Regards --- Justin Heesemannionium Technologies [EMAIL PROTECTED]www.ionium.org
Re: [vchkpw] About to release new devel version 5.3.20
On Mon, Mar 24, 2003 at 01:53:58PM -0600, Ken Jones wrote: Does anyone have any patches they would like to submit? Hi Ken, I've a patch at http://romana.now.ie/#vadddomain-maildir which slighly modifies the -e flag to vadddomain. I wanted a way to specify a ``catchall'' in the same way as qmailadmin does: supply a pathname to write directly into the catchall user's Maildir. Using -e as it is currently -- specifying an email address -- means I don't get access to the original envelope recipient in the Delivered-To header line. Applying the patch does not change vaddomain's behaviour when one specifies an email address with -e. But if one specifies a value without an @ symbol it is taken as a user into whose Maildir catchall mail should be delivered (as qmailadmin does). With the patch, I can say: vadddomain -e postmaster maildir.org And get: fridge# cat maildir.org/.qmail-default | /usr/local/vpopmail/bin/vdelivermail '' /usr/local/vpopmail/domains/maildir.org/postmaster ATB, james
Re: [vchkpw] About to release new devel version 5.3.20
Ken, - Original Message - From: Ken Jones [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 24, 2003 7:53 PM Subject: [vchkpw] About to release new devel version 5.3.20 I'm about to release a new 5.3.20 devel version. Does anyone have any patches they would like to submit? No, but would it be difficult to move mysql options from vmysql.h to configure options, e.g. ./configure \ --with-mysql-update-server=servername \ --with-mysql-update-user=username \ --with-mysql-update-password=password \ --with-mysql-read-server=servername \ --with-mysql-read-user=username \ --with-mysql-read-password=password The --with-mysql-read-* options could be optional, i.e. use the update server values if the read server is not present. I'd really like to see this. Cheers, R. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.463 / Virus Database: 262 - Release Date: 17/03/2003
Re: [vchkpw] About to release new devel version 5.3.20
It will be a good idea to support procmail I still having problems when bouncing messages. I'm about to release a new 5.3.20 devel version. Does anyone have any patches they would like to submit? Some differences from the 5.3.19 release 1) copies the vlimits.h file into the vpopmail/include directory. The latest qmailadmin devel release needs the vlimits.h file. 2) New --enable-rebuild-tcpserver-file option to disable rebuilding of that file for sites that use the tcpserver/mysql patch. 3) configure did not display the ldap option at the end if --enable-ldap=y is used 4) new --enable-active-directory option. This is the initial active directory module code to let vpopmail use active directory as an authentication store. 5) new vauth_crypt() api function to encapsulate the normal crypt() function. Active directory servers requrie an active directory call to do authentication. It won't just hand back an encrypted password to use with crypt() 6) replace pw_comp() function with new vauth_crypt() function. Thta's about it. If no one submits patches by end of day Tuesday, I'll release 5.3.20 as is. The plan then is to let Bill Shupp finish up some things before we release a new 5.4.0 stable version in association with a new qmailadmin 1.2.0 release. Cheers Ken Jones
Re: [vchkpw] About to release new devel version 5.3.20
On Monday 24 March 2003 20:53, Ken Jones wrote: I'm about to release a new 5.3.20 devel version. Does anyone have any patches they would like to submit? Thta's about it. If no one submits patches by end of day Tuesday, I'll release 5.3.20 as is. The plan then is to let Bill Shupp finish up some things before we release a new 5.4.0 stable version in association with a new qmailadmin 1.2.0 release. Fine. I really think we should finish vlimits before 5.4.0. At least to an extent where it actually is doing something. -- Mit internetten Grüßen / Best Regards --- Justin Heesemannionium Technologies [EMAIL PROTECTED]www.ionium.org
Re: [vchkpw] About to release new devel version 5.3.20
On Monday 24 March 2003 20:53, Ken Jones wrote: I'm about to release a new 5.3.20 devel version. Does anyone have any patches they would like to submit? Thta's about it. If no one submits patches by end of day Tuesday, I'll release 5.3.20 as is. The plan then is to let Bill Shupp finish up some things before we release a new 5.4.0 stable version in association with a new qmailadmin 1.2.0 release. Fine. I really think we should finish vlimits before 5.4.0. At least to an extent where it actually is doing something. Its been working for me since mid last year. I've submitted the patches only this year, starting around January. It essentially wraps the .qmailadmin-limits file access to an API and also allows the information to be stored in MySQL. When I put together the API, I had asked for other wishlist items, which I put into the structures but haven't implemented such as permissions. The quotas, limits, defaults limits, etc. all work fine and have been for quite some time. So I have no idea what you mean that it should do something. The infrastructure is now there for people to implement the items they wished for. If I get spare cycles, I'll look at them, but the areas I use were done a year ago, except for domain quotas which was completed last month. Brian
Re: [vchkpw] About to release new devel version 5.3.20
On Monday 24 March 2003 22:05, you wrote: On Monday 24 March 2003 20:53, Ken Jones wrote: I'm about to release a new 5.3.20 devel version. Does anyone have any patches they would like to submit? Thta's about it. If no one submits patches by end of day Tuesday, I'll release 5.3.20 as is. The plan then is to let Bill Shupp finish up some things before we release a new 5.4.0 stable version in association with a new qmailadmin 1.2.0 release. Fine. I really think we should finish vlimits before 5.4.0. At least to an extent where it actually is doing something. Its been working for me since mid last year. I've submitted the patches only this year, starting around January. It essentially wraps the .qmailadmin-limits file access to an API and also allows the information to be stored in MySQL. When I put together the API, I had asked for other wishlist items, which I put into the structures but haven't implemented such as permissions. The quotas, limits, defaults limits, etc. all work fine and have been for quite some time. So I have no idea what you mean that it should do something. The infrastructure is now there for people to implement the items they wished for. If I get spare cycles, I'll look at them, but the areas I use were done a year ago, except for domain quotas which was completed last month. Brian ok, sorry brian :) it is just that i don't use qmailadmin and i don't want to. if i have some option in my vlimits which denies imap, then why does vchkpw allow me to login via imap ?? this is what i feel vlimit should do. for limiting some userfrontend i actually don't need any feature of vpopmail, as i can easily use my own mysql tables. furthermore there is no single ./vsetlimit utility. this isn't meant to attack you in any way, brian, and i didn't say _you_ should do all this. you did a great job adding the vlimits, which are able to do more, than they are doing at the moment. -- Mit internetten Grüßen / Best Regards --- Justin Heesemannionium Technologies [EMAIL PROTECTED]www.ionium.org
Re: [vchkpw] About to release new devel version 5.3.20
On Monday 24 March 2003 22:05, you wrote: On Monday 24 March 2003 20:53, Ken Jones wrote: I'm about to release a new 5.3.20 devel version. Does anyone have any patches they would like to submit? Thta's about it. If no one submits patches by end of day Tuesday, I'll release 5.3.20 as is. The plan then is to let Bill Shupp finish up some things before we release a new 5.4.0 stable version in association with a new qmailadmin 1.2.0 release. Fine. I really think we should finish vlimits before 5.4.0. At least to an extent where it actually is doing something. Its been working for me since mid last year. I've submitted the patches only this year, starting around January. It essentially wraps the .qmailadmin-limits file access to an API and also allows the information to be stored in MySQL. When I put together the API, I had asked for other wishlist items, which I put into the structures but haven't implemented such as permissions. The quotas, limits, defaults limits, etc. all work fine and have been for quite some time. So I have no idea what you mean that it should do something. The infrastructure is now there for people to implement the items they wished for. If I get spare cycles, I'll look at them, but the areas I use were done a year ago, except for domain quotas which was completed last month. Brian ok, sorry brian :) it is just that i don't use qmailadmin and i don't want to. if i have some option in my vlimits which denies imap, then why does vchkpw allow me to login via imap ?? this is what i feel vlimit should do. for limiting some userfrontend i actually don't need any feature of vpopmail, as i can easily use my own mysql tables. furthermore there is no single ./vsetlimit utility. this isn't meant to attack you in any way, brian, and i didn't say _you_ should do all this. you did a great job adding the vlimits, which are able to do more, than they are doing at the moment. Hi Justin, There are currently ways to limit IMAP. One thing you should remember is that the vlimits API is for full domain limits, not individual users. There are permission bits in the GID field in the password entry for the user. These I believe work. Before actually implementing the API, I sent out a request for all the additional items people wanted to see over and above what I wanted. This way the database schema would only have to be written once, and filled in later. Some limit the qmailadmin app, others go directly into vdelivermail. Others will go into other areas. Overall, I think we have a functional system as is, with placeholders for future features. The wishlist is high, but only so many things can make each release. If you've got the cycles and can crank out some of it tonight, send in a patch. Thanks, Brian
Re: [vchkpw] About to release new devel version 5.3.20
On Monday 24 March 2003 06:47 pm, Brian Kolaci wrote: On Monday 24 March 2003 22:05, you wrote: On Monday 24 March 2003 20:53, Ken Jones wrote: I'm about to release a new 5.3.20 devel version. Does anyone have any patches they would like to submit? Thta's about it. If no one submits patches by end of day Tuesday, I'll release 5.3.20 as is. The plan then is to let Bill Shupp finish up some things before we release a new 5.4.0 stable version in association with a new qmailadmin 1.2.0 release. Fine. I really think we should finish vlimits before 5.4.0. At least to an extent where it actually is doing something. Its been working for me since mid last year. I've submitted the patches only this year, starting around January. It essentially wraps the .qmailadmin-limits file access to an API and also allows the information to be stored in MySQL. When I put together the API, I had asked for other wishlist items, which I put into the structures but haven't implemented such as permissions. The quotas, limits, defaults limits, etc. all work fine and have been for quite some time. So I have no idea what you mean that it should do something. The infrastructure is now there for people to implement the items they wished for. If I get spare cycles, I'll look at them, but the areas I use were done a year ago, except for domain quotas which was completed last month. Brian ok, sorry brian :) it is just that i don't use qmailadmin and i don't want to. if i have some option in my vlimits which denies imap, then why does vchkpw allow me to login via imap ?? this is what i feel vlimit should do. for limiting some userfrontend i actually don't need any feature of vpopmail, as i can easily use my own mysql tables. furthermore there is no single ./vsetlimit utility. this isn't meant to attack you in any way, brian, and i didn't say _you_ should do all this. you did a great job adding the vlimits, which are able to do more, than they are doing at the moment. Hi Justin, There are currently ways to limit IMAP. One thing you should remember is that the vlimits API is for full domain limits, not individual users. There are permission bits in the GID field in the password entry for the user. These I believe work. Before actually implementing the API, I sent out a request for all the additional items people wanted to see over and above what I wanted. This way the database schema would only have to be written once, and filled in later. Some limit the qmailadmin app, others go directly into vdelivermail. Others will go into other areas. Overall, I think we have a functional system as is, with placeholders for future features. The wishlist is high, but only so many things can make each release. If you've got the cycles and can crank out some of it tonight, send in a patch. Thanks, Brian Check the authlib/preauthvchkpw.c in your courier-imap distribution. It should contain a check for NO_IMAP, which is part of the flags vpopmail supports per user. The vmoduser command line lets you turn on or off imap access if your preauthvchkpw.c file has that check. The standard courier-imap distribution has had that check in it for quite awhile. KenJones
Re: [vchkpw] About to release new devel version 5.3.20
Ken, have no any patches to add, only suggestions i wrote earlier: when sql-logging activated by configure, and database with logs get crashed -- i guess we shouldnt try to recreate tables... best, Vladimir Kabanov.
Re: [vchkpw] About to release new devel version 5.3.20
Brian Kolaski sent in a new patch today for qmailadmin that probably fixes the problem. Execllent! I spent couple of hours hunting for it :-) Myabe it could be good for future releases but I miss one feature: My users wnat to be informed on their mobiles about new mail, so I wrote wrapper script that could be put into .qmail taking a phone number as a parameter but qmailadmin lacks of chance for user to put his number into account details form. I thought it would be nice if during configure run admin could set smtn like --with-wrapper-scripts=/usr/bin/one|/usr/bin/two --with-wrapper-label=Featur e one|Feature two so that in moduser page there were additiona fields labelled corresponding. If filled, qmailadmin would put |/usr/bin/one parameter_from_field_one |/usr/bin/two parameter_from_field_two /home/vpopmail/domains/... This way users could also implement some customized filtering action on their mailboxes. Solt