Re: [vchkpw] Postgres in 5.3.16 - I see it, how do I enable it?
1.) CVS I strongly agree. The development snapshots are nice and all but for those of us who are trying to hack on it CVS would be a real boon. Especially with the new website design that thends to hide what I'd call the CVS snapshot versions. 2.) Actually reading their own mailing lists. I do believe they do this currently, although I imagine that it is not a top priority for them as they, as pretty much all of us, are out to make money. If it is becoming inter7's policy to give these lists a (much?) lower priority, then it should be labelled as such -- a user-supported mailing list hosted by inter7, rather than what it comes across as now -- a user/devel mailing list in which the developers and mainters are active participants. I don't like to make a nuisance of myself by CC:ing people directly when I know that they're subscribed to the list -- if they're not responding, it's because they're either too busy or disinterested at the time. Either way though, it'd be nice to have some kind of indication of the level of maintainer interest/activity in the lists. Regards, Andrew
Re: [vchkpw] Postgres in 5.3.16 - I see it, how do I enable it?
On Thursday 20 February 2003 09:59, Andrew Kohlsmith wrote: 1.) CVS I strongly agree. The development snapshots are nice and all but for those of us who are trying to hack on it CVS would be a real boon. Especially with the new website design that thends to hide what I'd call the CVS snapshot versions. 2.) Actually reading their own mailing lists. I do believe they do this currently, although I imagine that it is not a top priority for them as they, as pretty much all of us, are out to make money. If it is becoming inter7's policy to give these lists a (much?) lower priority, then it should be labelled as such -- a user-supported mailing list hosted by inter7, rather than what it comes across as now -- a user/devel mailing list in which the developers and mainters are active participants. I thought of another one: 3.) Separation between the developer's mailing list and the user's mailing list. I think that would go a long way toward helping vpopmail developers communicate more effectively. I don't like to make a nuisance of myself by CC:ing people directly when I know that they're subscribed to the list -- if they're not responding, it's because they're either too busy or disinterested at the time. Either way though, it'd be nice to have some kind of indication of the level of maintainer interest/activity in the lists. Regards, Andrew -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net We are actively looking for companies that do a lot of long distance faxing and want to cut their long distance bill by up to 50%. Contact [EMAIL PROTECTED] for more info.
Re: [vchkpw] Postgres in 5.3.16 - I see it, how do I enable it?
Hi, everyone. Just wanted to clear a few things up :) As far as CVS is concerned, Inter7's development team is not the largest. I tried to make the case for CVS some time ago, but it isnt looking as if it will fly. If you're interested in new development on vpopmail, take a look on www.shupp.org. I know Bill is working on patches here and there. Im aware of a postgres module, but Im not sure how up to date it is. Quite a few of our vpopmail modules came about due to client demands and funding. So, put simply, if we dont have funding, and we dont need it, someone else might need to put it together. I know that just about all of the techs, and developers over here follow the mailing list. Myself, I dont read every single thread, and I dont always have time to help everyone out on the smaller issues, but we do make a shared attempt to support the mailing lists we host. Having a development list is a good idea. Although, this mailing list *WAS* meant to not only be a support forum, but also a place to send patches. If you do submit a patch, please do not be offended if you receive no reply, or receive a late one. We do go over all patches we see on the list. However, we cannot accept all of them, as they stand, into future releases, and we dont always have the time to respond about the status of every patch. Posting the patch to the mailing list allows others who would like to use the patches to install them without waiting for us. Jesse Guardiani wrote: On Thursday 20 February 2003 09:59, Andrew Kohlsmith wrote: 1.) CVS I strongly agree. The development snapshots are nice and all but for those of us who are trying to hack on it CVS would be a real boon. Especially with the new website design that thends to hide what I'd call the CVS snapshot versions. 2.) Actually reading their own mailing lists. I do believe they do this currently, although I imagine that it is not a top priority for them as they, as pretty much all of us, are out to make money. If it is becoming inter7's policy to give these lists a (much?) lower priority, then it should be labelled as such -- a user-supported mailing list hosted by inter7, rather than what it comes across as now -- a user/devel mailing list in which the developers and mainters are active participants. I thought of another one: 3.) Separation between the developer's mailing list and the user's mailing list. I think that would go a long way toward helping vpopmail developers communicate more effectively. I don't like to make a nuisance of myself by CC:ing people directly when I know that they're subscribed to the list -- if they're not responding, it's because they're either too busy or disinterested at the time. Either way though, it'd be nice to have some kind of indication of the level of maintainer interest/activity in the lists. Regards, Andrew -- mailto:[EMAIL PROTECTED] Matt Brookings - Chief Technical Officer Inter7 Internet Technologies, Inc. www.inter7.com - 847-492-0470 Prices at http://www.inter7.com/prices
Re: [vchkpw] Postgres in 5.3.16 - I see it, how do I enable it?
On Wednesday, February 19, 2003, at 08:33 PM, Andrew Kohlsmith wrote: Anyone? There must be some developmental work going on with it or it wouldn't have been in the tarball. I am willing to help work on it but I need some help getting over this initial hurdle (cleanly). Nice, responsive list. :-/ Attached is a patch to 5.3.16 which will get vpgsql to actually work (seems to work right for auth and relay, have NOT extensively tested it yet) -- I have not included the configure script changes since they were really nasty and I'm sure there is a better way. ATM the database, user and password are all hardcoded, and I did not change the existing ability to create the database if it doesn't already exist. That seems like a really nasty thing to allow -- basically you are granting the vpopmail database user full access to the vpopmail table where it would seem more prudent to only allow inserts, updates and deletes. (not create/drop). Anyway. Another nasty is that the database notification daemon will spit its info out to the network (i.e. anyone accessing vchkpw) -- I will include a fix for that soon as well as some general cleanups and any other bus I find. I hope to do some more extensive testing, including clear passwords and open relay in the next few days. Adding domains/users and authenticating definately is working though, and the tables seem to be updating correctly for relay and lastauth. Andrew, Are you sure this diff is against 5.3.16? It does not apply to my copy, or the one on Inter7's devel page (which should be the same). Thanks, Bill Shupp
Re: [vchkpw] Postgres in 5.3.16 - I see it, how do I enable it?
Are you sure this diff is against 5.3.16? It does not apply to my copy, or the one on Inter7's devel page (which should be the same). bah... I looked at the diff and saw ^Ms at the end of all the lines so I stripped them out. Attached is a fixed version that *does* apply. Regards, Andrew vpopmail-5.3.16-postgreschanges.diff.gz Description: GNU Zip compressed data
Re: [vchkpw] Postgres in 5.3.16 - I see it, how do I enable it?
On Thursday, February 20, 2003, at 11:15 AM, Andrew Kohlsmith wrote: Are you sure this diff is against 5.3.16? It does not apply to my copy, or the one on Inter7's devel page (which should be the same). bah... I looked at the diff and saw ^Ms at the end of all the lines so I stripped them out. Attached is a fixed version that *does* apply. Regards, Andrew Looks great. I've added it to 5.3.17, which I'll post later today. Thanks! Bill Shupp
Re: [vchkpw] Postgres in 5.3.16 - I see it, how do I enable it?
Anyone? There must be some developmental work going on with it or it wouldn't have been in the tarball. I am willing to help work on it but I need some help getting over this initial hurdle (cleanly). Nice, responsive list. :-/ Attached is a patch to 5.3.16 which will get vpgsql to actually work (seems to work right for auth and relay, have NOT extensively tested it yet) -- I have not included the configure script changes since they were really nasty and I'm sure there is a better way. ATM the database, user and password are all hardcoded, and I did not change the existing ability to create the database if it doesn't already exist. That seems like a really nasty thing to allow -- basically you are granting the vpopmail database user full access to the vpopmail table where it would seem more prudent to only allow inserts, updates and deletes. (not create/drop). Anyway. Another nasty is that the database notification daemon will spit its info out to the network (i.e. anyone accessing vchkpw) -- I will include a fix for that soon as well as some general cleanups and any other bus I find. I hope to do some more extensive testing, including clear passwords and open relay in the next few days. Adding domains/users and authenticating definately is working though, and the tables seem to be updating correctly for relay and lastauth. Regards, Andrew vpopmail-5.3.16-postgreschanges.diff.gz Description: GNU Zip compressed data
Re: [vchkpw] Postgres in 5.3.16 - I see it, how do I enable it?
That's good. Haven't played with postgres lately. MySQL seemed easy and quick enough. I've added a patch that checks the return code from vopen_smtp_relay(). It used to be void. I changed the interpretation such that it needs to return non-zero if the given IP address wasn't already in the table, and zero on error or the IP was in the table and just the timestamp was updated. I don't know the syntax for postgres. Would you be able to make that modification? I also don't have an oracle Pro C compiler. I typically use OCI. So I don't know how to update the voracle.pc file. If you or anyone knows how to update that, please send an update. Also, you don't have to grant DROP privs, just give it CREATE and it has the auto-create feature built in. You only need to grant DROP if you disable the MANY_DOMAINS option, which you probably don't want to do anyway. Not sure which database notification daemon you're speaking of. Thanks, Brian Anyone? There must be some developmental work going on with it or it wouldn't have been in the tarball. I am willing to help work on it but I need some help getting over this initial hurdle (cleanly). Nice, responsive list. :-/ Attached is a patch to 5.3.16 which will get vpgsql to actually work (seems to work right for auth and relay, have NOT extensively tested it yet) -- I have not included the configure script changes since they were really nasty and I'm sure there is a better way. ATM the database, user and password are all hardcoded, and I did not change the existing ability to create the database if it doesn't already exist. That seems like a really nasty thing to allow -- basically you are granting the vpopmail database user full access to the vpopmail table where it would seem more prudent to only allow inserts, updates and deletes. (not create/drop). Anyway. Another nasty is that the database notification daemon will spit its info out to the network (i.e. anyone accessing vchkpw) -- I will include a fix for that soon as well as some general cleanups and any other bus I find. I hope to do some more extensive testing, including clear passwords and open relay in the next few days. Adding domains/users and authenticating definately is working though, and the tables seem to be updating correctly for relay and lastauth. Regards, Andrew
Re: [vchkpw] Postgres in 5.3.16 - I see it, how do I enable it?
Ok I see that vpgsql is there... how the hell do I turn it on? The configure script has no clue about it, and I don't see a reference in Makefile.in at all Anyone? There must be some developmental work going on with it or it wouldn't have been in the tarball. I am willing to help work on it but I need some help getting over this initial hurdle (cleanly). Regards, Andrew
