From wplug at badgertronics.com Sat Feb 1 08:47:26 2003 From: wplug at badgertronics.com (Mark Dalrymple) Date: 1 Feb 2003 13:47:26 -0000 Subject: [wplug-web] status update In-Reply-To: (jo2y@midnightlinux.com) References: Message-ID: <20030201134726.12576.qmail@59.acronhosting.net> > I know the sudden change of server venues derailed several of us, but > could we inventory where we are and report back to the list? > Someday I'll create that gant chart to figure out what is waiting on what. all the requisite software installed and running. I've got it kind of up and running on http://www.wplug.org:8082/ - this is the dev site. I figured we'd scram the db once or twice. The boxes on the left are mason-style components, and I have a news module installed and a sample static content page. At home I've got the data model built for the GUM manager. I want to finish that next week. I'm waiting for Evan and Zach to finish their HTML style / recomendation stuff. I guess if we don't see that in the next week, we can always fall back to the orange-and-grey design from a version or two ago. Wheeee, ++md From bethlynn at cs.cmu.edu Thu Feb 6 16:49:24 2003 From: bethlynn at cs.cmu.edu (Beth Lynn Lauris) Date: Thu, 6 Feb 2003 16:49:24 -0500 (EST) Subject: [wplug-web] please update website Message-ID: Hi, Could someome please update the website to include James O'Kane's iptables talk this saturday? thanks, Beth Lynn From zman at wplug.org Thu Feb 6 19:46:48 2003 From: zman at wplug.org (Zach Paine) Date: Thu, 6 Feb 2003 19:46:48 -0500 Subject: [wplug-web] please update website In-Reply-To: Message-ID: Done. On Thursday, February 6, 2003, at 04:49 PM, Beth Lynn Lauris wrote: > Hi, > > Could someome please update the website to include > James O'Kane's iptables talk this saturday? > > thanks, > > Beth Lynn > > _______________________________________________ > wplug-web mailing list > wplug-web at wplug.org > http://www.wplug.org/mailman/listinfo/wplug-web From wplug at badgertronics.com Sun Feb 9 20:20:16 2003 From: wplug at badgertronics.com (Mark Dalrymple) Date: 10 Feb 2003 01:20:16 -0000 Subject: [wplug-web] GUM stuff for new website Message-ID: <20030210012016.30064.qmail@59.acronhosting.net> Hey Gang, I've added a GUM meeting package thingie to the dev site: http://wplug.org:8082/ Pulls things out of the db, etc. If you haven't created a login yet, go ahead and make one and AIM/IRC me and I'll give you privs to the back-end. This is just the dev site, so don't spend too much time making stuff real, since the data will not make it to the live site. I have some more stuff to add to it, but I figured I'd let folks play around with it now. Wheee, ++md From jo2y at midnightlinux.com Wed Feb 19 19:59:47 2003 From: jo2y at midnightlinux.com (James O'Kane) Date: Wed, 19 Feb 2003 19:59:47 -0500 (EST) Subject: [wplug-web] schema for mailing lists Message-ID: Assumptions: People will have many addresses, but only one primary The column and table names I have below are vague table mailing_lists { id other_mailing_list_foo_that_I_need_to_lookup } table mailing_list_map { user_id mailing_list_id other_user_specific_options } Then we can do a query to get the list of subscribers. select users.email_address from users,mailing_lists, mailing_list_map where users.id = mailing_list_map.user_id AND mailing_list_map.mailing_list_id = mailing_lists.id AND mailing_lists.id = ; That seems complicated to me, and I'm not sure my join is correct. Is this the right direction? If my assumption about one primary per person is wrong, we can add multiple items to the _map table and add a column called email, and beef up the select query. -james From eksortso at linuxmail.org Thu Feb 20 12:25:06 2003 From: eksortso at linuxmail.org (David Ostroske) Date: Thu, 20 Feb 2003 12:25:06 -0500 Subject: [wplug-web] schema for mailing lists Message-ID: <20030220172506.29185.qmail@linuxmail.org> From: "James O'Kane" Date: Wed, 19 Feb 2003 19:59:47 -0500 (EST) > Assumptions: > People will have many addresses, but only one primary > The column and table names I have below are vague We'll just concern ourselves with the keys and the appropriate data fields for now. > table mailing_lists { > id > other_mailing_list_foo_that_I_need_to_lookup > } > > table mailing_list_map { > user_id > mailing_list_id > other_user_specific_options > } > > Then we can do a query to get the list of subscribers. > select users.email_address from users,mailing_lists, mailing_list_map > where users.id = mailing_list_map.user_id AND > mailing_list_map.mailing_list_id = mailing_lists.id AND mailing_lists.id = > ; > > That seems complicated to me, and I'm not sure my join is correct. > Is this the right direction? Your join is correct, James. Actually, the join to mailing_lists might be redundant, since the mailing_list_map would have the desired mailing list's ID in it already. But the additional join asserts that the desired list really exists. It would be better to have another table, containing users' email addresses and some sort of flag designating a primary account. That would make the query more complex: SELECT user_addresses.email_address FROM user_addresses, users, mailing_lists, mailing_list_map WHERE mailing_lists.id = AND mailing_lists.id = mailing_list_map.mailing_list_id AND mailing_list_map.user_id = users.id AND users.id = user_addresses.user_id AND user_addresses.primary = -1 --include this line if you just want primary addresses ; (I hope I got this SQL dialect right. There might be JOIN clauses and boolean fields, but I don't know right now.) But, if you want to associate a single email address with a given user in a given mailing list, then putting the email address in the _map table would make sense. SELECT mailing_list_map.email_address FROM mailing_lists, mailing_list_map WHERE mailing_lists.id = AND mailing_lists.id = mailing_list_map.mailing_list_id ; You can always join this to the users table again, if you only want certain users. > If my assumption about one primary per person is wrong, we can add > multiple items to the _map table and add a column called email, and beef > up the select query. > > -james If you want multiple email addresses, but do not want them connected to particular mailing lists, then my first query would work. The second query would work better for mailing to just those addresses associated with a mailing list, but the concept of a "primary" email address would still need to be addressed. --- David Ostroske eksortso at linuxmail.org -- ______________________________________________ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze From jo2y at midnightlinux.com Thu Feb 20 17:59:04 2003 From: jo2y at midnightlinux.com (James O'Kane) Date: Thu, 20 Feb 2003 17:59:04 -0500 (EST) Subject: [wplug-web] schema for mailing lists In-Reply-To: <20030220172506.29185.qmail@linuxmail.org> Message-ID: It's not exactly a 'primary' email address, but rather one that the user wants to get email. In some cases, for whatever reason, people might want to get email sent to more than one address. They also might want to have different options for each address, one might get digest while the other gets regular format mail. So I think we need to put an email address field on the _map table. (We could put just extra email addresses in a seperate table with a unique id, but that doesn't seem nessesary, unless we plan to use them for anything else?) I still need to double check the Mailman API to see what types of queries it normally does. But for example, given a list name, it would want all of the addresses of who it should send mail to. Another is given an email address, is it allowed to send mail to the list in question. -james From jo2y at midnightlinux.com Thu Feb 20 18:46:44 2003 From: jo2y at midnightlinux.com (James O'Kane) Date: Thu, 20 Feb 2003 18:46:44 -0500 (EST) Subject: [wplug-web] schema for mailing lists In-Reply-To: Message-ID: Don't feel you need to read all of these, but these are the functions I need to impliment. Some are optional, but it limits the mailman web and email interfaces. I'm assuming self is an object reference or some other data, that one can extract the real list name from. -james This is from the readme: Members have three pieces of identifying information: a unique identifying opaque key (KEY), a lower-cased email address (LCE), and a case-preserved email (CPE) address. Adaptors must ensure that both member keys and lces can uniquely identify a member, and that they can (usually) convert freely between keys and lces. Most methods must accept either a key or an lce, unless specifically documented otherwise. def getMembers(self): def getRegularMemberKeys(self): def getDigestMemberKeys(self): def isMember(self, member): def getMemberKey(self, member): def getMemberCPAddress(self, member): def getMemberCPAddresses(self, members): def authenticateMember(self, member, response): def getMemberPassword(self, member): def getMemberLanguage(self, member): def getMemberOption(self, member, flag): def getMemberName(self, member): def getMemberTopics(self, member): def getDeliveryStatus(self, member): def getDeliveryStatusChangeTime(self, member): def getDeliveryStatusMembers(self, def getBouncingMembers(self): def getBounceInfo(self, member): def addNewMember(self, member, **kws): def removeMember(self, memberkey): def changeMemberAddress(self, memberkey, newaddress, nodelete=0): def setMemberPassword(self, member, password): def setMemberLanguage(self, member, language): def setMemberOption(self, member, flag, value): def setMemberName(self, member, realname): def setMemberTopics(self, member, topics): def setDeliveryStatus(self, member, status): def setBounceInfo(self, member, info): From eksortso at linuxmail.org Fri Feb 21 14:51:31 2003 From: eksortso at linuxmail.org (David Ostroske) Date: Fri, 21 Feb 2003 14:51:31 -0500 Subject: [wplug-web] schema for mailing lists Message-ID: <20030221195131.1689.qmail@linuxmail.org> From: "James O'Kane" Date: Thu, 20 Feb 2003 17:59:04 -0500 (EST) > It's not exactly a 'primary' email address, but rather one that the user > wants to get email. In some cases, for whatever reason, people might want > to get email sent to more than one address. They also might want to have > different options for each address, one might get digest while the other > gets regular format mail. So I think we need to put an email address field > on the _map table. (We could put just extra email addresses in a seperate > table with a unique id, but that doesn't seem nessesary, unless we plan > to use them for anything else?) The way that you describe it, the _map table would act more like a "subscriptions" table than as a simple map. It would hold fields for the different mailing options for a given subscription. And if someone wanted delivery to more than one address, then they would simply subscribe twice. > I still need to double check the Mailman API to see what types of queries > it normally does. But for example, given a list name, it would want all of > the addresses of who it should send mail to. Another is given an email > address, is it allowed to send mail to the list in question. Pardon my ignorance in this matter; I'm just trying to help. But, if you have complex queries for retrieving email addresses, etc., could you define views in the database that would return just the data that Mailman would expect? Or are you strictly limited to using only tables? > -james --- David Ostroske eksortso at linuxmail.org -- ______________________________________________ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze From jo2y at midnightlinux.com Fri Feb 21 16:02:32 2003 From: jo2y at midnightlinux.com (James O'Kane) Date: Fri, 21 Feb 2003 16:02:32 -0500 (EST) Subject: [wplug-web] schema for mailing lists In-Reply-To: <20030221195131.1689.qmail@linuxmail.org> Message-ID: On Fri, 21 Feb 2003, David Ostroske wrote: > Pardon my ignorance in this matter; I'm just trying to help. But, if you > have complex queries for retrieving email addresses, etc., could you > define views in the database that would return just the data that > Mailman would expect? Or are you strictly limited to using only tables? This would be up to PostgreSQL and markd2, our database guru. I've given him final say to any database structure changes. I've not dealt with views much. Are they cheaper than an equivelent join? -james From wplug at badgertronics.com Fri Feb 21 16:17:50 2003 From: wplug at badgertronics.com (Mark Dalrymple) Date: 21 Feb 2003 21:17:50 -0000 Subject: [wplug-web] schema for mailing lists In-Reply-To: (jo2y@midnightlinux.com) References: Message-ID: <20030221211750.11843.qmail@59.acronhosting.net> > I've not dealt with views much. Are they cheaper than an equivelent join? They're usually equivalent to pasting in the view definition into the query. Deep levels of views can sometimes make the optimizer miss some options. In terms of person understanding , views can be helpful for hiding complex queries involving joins across lots of tables. Wheee, ++Mark Dalrymple, markd at badgertronics.com. http://badgertronics.com "Q: I need a random number generator. A: Count errors in Herbert Schildt's C books. No one has detected any consistent pattern." -- Peter Seebach, from The *other* C FAQ From wplug at badgertronics.com Mon Feb 24 18:46:09 2003 From: wplug at badgertronics.com (Mark Dalrymple) Date: 24 Feb 2003 23:46:09 -0000 Subject: [wplug-web] proxy fun Message-ID: <20030224234609.5833.qmail@59.acronhosting.net> Hey Gang, I've been playing with my reverse proxy thing for the wplug.org front-end, and am seeing something that's confusing me. I've got my proxy (AOLserver based) listening on port 8083. If it sees an url with /mailman or /pipermail at the start, it'll talk to the apache server currently running wplug.org. The weird thing is that apache isn't resolving the url correctly (or something). I get Not Found The requested URL /mailman/listinfo/wplug was not found on this server. Apache/1.3.27 Server at www.wplug.org Port 8080 But if I go directly to wplug.org:8080 or just wplug.org with that url it works great. If I go through my proxy, nothing happens. I don't see any activity happen in the access_log or the error_log in /var/www/www.wplug.org/logs. I do see activity in those logs if I put in a bad url like http://www.wplug.org/hot/monkeybot/sex What's also interesting is that the proxying to the aolserver/acs instance running on port 8081 works great. So things I'm wondering are: * Are there any other apache logs with diagnostic information * Is apache looking for any specific headers that I might not be providing - and if so, is there a way to get it to trace exactly which HTTP headers it's getting. to compare what it gets from a browser vs what it's getting from me. Thanks, ++md From jo2y at midnightlinux.com Mon Feb 24 19:04:29 2003 From: jo2y at midnightlinux.com (James O'Kane) Date: Mon, 24 Feb 2003 19:04:29 -0500 (EST) Subject: [wplug-web] proxy fun In-Reply-To: <20030224234609.5833.qmail@59.acronhosting.net> Message-ID: I see some activity in /var/log/httpd/error_log which makes me think that you aren't sending the host: header to apache. I tried to do this via telnet. Normally, one can type: GET /mailman/listinfo HTTP/1.0 host: www.wplug.org That's a blank line before apache starts to send output. When I try, I can only type the GET line before things start processing. -james From wplug at badgertronics.com Tue Feb 25 09:09:27 2003 From: wplug at badgertronics.com (Mark Dalrymple) Date: 25 Feb 2003 14:09:27 -0000 Subject: [wplug-web] proxy fun In-Reply-To: (jo2y@midnightlinux.com) References: Message-ID: <20030225140927.29476.qmail@59.acronhosting.net> > I see some activity in /var/log/httpd/error_log which makes me think that > you aren't sending the host: header to apache. woop! thanks for the clue. The Host: header I was sending along was malformed. ++md