From thomas at xs4all.net Wed Mar 5 02:30:23 2003 From: thomas at xs4all.net (Thomas Wouters) Date: Tue Mar 4 20:30:34 2003 Subject: [Mailman-Developers] API Mailman In-Reply-To: <04b601c2d83f$a8de37b0$7801a8c0@mmugar> References: <04b601c2d83f$a8de37b0$7801a8c0@mmugar> Message-ID: <20030305013023.GA23319@xs4all.nl> On Wed, Feb 19, 2003 at 02:52:23PM -0300, Manuel SiMaR Rodriguez wrote: > I need know if exist a function to retrive a admin password like.... > oldpw = mlist.getMemberPassword(address) Unless this changed since Mailman 2.0 (but it doesn't look that way) you cannot do this. The list-admin and site-admin passwords are stored using a one-way encryption technique similar to what most UNIX systems use to store system passwords. This is so an information leak doesn't leak out the list/site-passwords. The member passwords are much less important, and they are stored in a reversable format so they can be mailed out in the monthly reminder (on 'Mailman Day', as some people I know started calling it :) You can compare an admin password (by encrypting the entered password and comparing it with the encrypted version) and you can overwrite it, but you can't get an unencrypted version of it. -- Thomas Wouters Hi! I'm a .signature virus! copy me into your .signature file to help me spread! From thomas at xs4all.net Wed Mar 5 02:35:30 2003 From: thomas at xs4all.net (Thomas Wouters) Date: Tue Mar 4 20:38:41 2003 Subject: [Mailman-Developers] public archives and email adresses In-Reply-To: <200302271530.52927.K.Hansen@biostat.ku.dk> References: <200302271530.52927.K.Hansen@biostat.ku.dk> Message-ID: <20030305013530.GB23319@xs4all.nl> On Thu, Feb 27, 2003 at 03:30:52PM +0100, Kasper Daniel Hansen wrote: > If I have public archives and a member of the list has a signature in their > email reader, this signature is included in the archive. But - at least in my > list - it is quite common for signatures to include the posters email adress > which therefore are being made accesible on a public webpage. > Is it possible to strip messages of the signature before they are being > archived? If so - how? No, you can't really do that. The problem is that you can't see where signatures start. Sure, sane people use the correct signature marker ('-- ', as I have below) so you can detect the start of signatures, but that's not all. Some mailers put quoted text below the signature, so if they used a proper signature marker you would end up removing the entire quoted mail. And what to think of people who accidentily put -- somewhere in their email ? The rest of the email would vanish :) And then there's the problem of people inserting email addresses in other locations in the email -- almost as frequent as adding them to your signature. All in all, it's a better idea to post-process the archives to try and detect and mangle email addresses (but half-heartedly; Barry knows how hard it is to detect all possible email addresses :) But I don't think Mailman currently has any of that. The latter part could be added, for sure, but it would require going over each email before or during archiving. Also note that I've not followed Mailman development in a while, so I may be horribly wrong, sorry. :) -- Thomas Wouters Hi! I'm a .signature virus! copy me into your .signature file to help me spread! From thomas at xs4all.net Wed Mar 5 03:00:31 2003 From: thomas at xs4all.net (Thomas Wouters) Date: Tue Mar 4 21:00:35 2003 Subject: [Mailman-Developers] Alternative MemberAdaptors In-Reply-To: <15956.64136.366613.284548@gargle.gargle.HOWL> References: <15956.64136.366613.284548@gargle.gargle.HOWL> Message-ID: <20030305020031.GC23319@xs4all.nl> On Thu, Feb 20, 2003 at 10:55:52AM -0500, barry@python.org wrote: [ MemberAdaptors ] > I've found a few things during this experience that point to things we > ought to improve. I don't have a lot of time right now, but I wanted > to put this out there to start the discussion. I'll quickly mention a > few things. I haven't looked at MemberAdaptors in any level of detail yet, but I do intend to write one or two member adaptors for our internal company lists. One is a straight (My)SQL one that takes data from a simple set of tables, one of which is specifically for Mailman (and thus easy to change.) The other would be a much more complex adaptor that hooks right into our company database ('NSA', PostgreSQL with an OO interface library written in Perl[*]) using XML-RPC. I already use XML-RPC from Python to test and twiddle with so much more ease than from Perl or PHP, so I'm sure that's not going to be an issue. The main reason for using the XML-RPC interface is, however, to be able to access all the email aliasses the list subscribers have. The company-internal lists are strictly controlled, and every day or so someone will post a message from their new funky alias, which will be held. I thought Mailman 2.1 was going to have a mechanism to avoid that (a listing of 'these emailaddresses are also me' in the options page) but that may have been a dream. In any case, I can add that :) I'm also not sure whether I really want a full MemberAdaptor for the XML-RPC case, or a mix of another backend and XML-RPC. Anyway, neither implementation would be transactional (and the MySQL server is 3.x.) > - I wanted to hook into the BDB transaction (txn) machinery, and I > found a convenient hook. I overloaded MailList.Lock() to include a > txn begin, MailList.Save() to do a txn commit, and MailList.Unlock() > to do a txn abort. This seems to work well as long as aborting > after committing is harmless (it is in BDB). I'd like to get > feedback from the SQL folks (or other MemberAdaptor developers) on > whether we need more explicit transaction support or whether the > basically necessary hooks are already there. Well, I can't really tell without (re-)grokking the code more, but in any case an abort after a commit should not pose a problem; it's just a matter of remembering state. Many SQL implementations won't even care if you do 'BEGIN WORK; ; COMMIT; ROLLBACK;' -- they'll give a notice, but not abort anything. When not doing anything transactional, it gets easier, of course. Maintain all state in the Adaptor, and only commit something to a backend on the Save() :) > - We really need to optimize the MemberAdaptor API and the > implementations that use them. Especially methods that return > lists, e.g. getMembers() and friends. Right now, everything has to > return a list, but I could do much better by returning iterators, > because I can load my iterator up with a BDB cursor. This has the > advantage of not requiring the entire member database to be loaded > into memory just to iterate over it. Unfortunately, too much of the > rest of the code assumes these methods return lists, and while I > started to go down the iterator path, I backed out of it because of > the complexity. This is highly backend dependent... In the XML-RPC case, you really don't want an XML-RPC call to go out for every list member (especially not if the xmlrpc library doesn't support/use keepalive.) On the other hand, getting the entire list into the adaptor and then returning an iterator to that list to Mailman might be suboptimal if Mailman ever has to decide between playing convenient (a list) and playing nice (an iterator). > There are other optimizations that would require a bit more > thought. E.g. the admin's Membership List page seems to require > that the entire member database be iterated over to chunkify and > bucketize. Fixing this probably requires both changes to the u/i > and changes to the interface. It also makes life more difficult for > OldStyleMemberships, although BDBMemberAdaptor can probably be > fairly easily elaborated. And in SQL, the optimal way to do this is probably to count the number of entries, and then split it into chunks, get whichever chunk is desired, and the first and last entry of the other chunks. The count can be done entirely in the SQL server, and is generally pretty damned fast. This will definately pay off for very large lists, but it's not really trivial to expose all that logic to the adaptor in a future-proof way. Maybe-we-should-do-a-Mailman-Sprint-at-PyCon-Barry-ly y'rs :) [*] 'NSA' is also the reason I'm not as active as I once was... I hate Perl, much more so now than before I actually used it full-time. But, I get to go to PyCon, so I haven't lost my soul completely yet :) -- Thomas Wouters Hi! I'm a .signature virus! copy me into your .signature file to help me spread! From mal at lemburg.com Wed Mar 5 14:10:58 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed Mar 5 08:18:08 2003 Subject: [Mailman-Developers] Alternative MemberAdaptors In-Reply-To: <20030305020031.GC23319@xs4all.nl> References: <15956.64136.366613.284548@gargle.gargle.HOWL> <20030305020031.GC23319@xs4all.nl> Message-ID: <3E65F762.2090300@lemburg.com> Thomas Wouters wrote: > On Thu, Feb 20, 2003 at 10:55:52AM -0500, barry@python.org wrote: > > [ MemberAdaptors ] FYI, I'm working on a MemberAdaptor for mxODBC and DCOracle2 (which won't be open sourced though). >>I've found a few things during this experience that point to things we >>ought to improve. I don't have a lot of time right now, but I wanted >>to put this out there to start the discussion. I'll quickly mention a >>few things. >> >>- I wanted to hook into the BDB transaction (txn) machinery, and I >> found a convenient hook. I overloaded MailList.Lock() to include a >> txn begin, MailList.Save() to do a txn commit, and MailList.Unlock() >> to do a txn abort. This seems to work well as long as aborting >> after committing is harmless (it is in BDB). I'd like to get >> feedback from the SQL folks (or other MemberAdaptor developers) on >> whether we need more explicit transaction support or whether the >> basically necessary hooks are already there. This worked for me as well. I did have to use a central database controller, though, in order to maintain transaction state independently of the MemberAdaptor. >>- We really need to optimize the MemberAdaptor API and the >> implementations that use them. Especially methods that return >> lists, e.g. getMembers() and friends. Right now, everything has to >> return a list, but I could do much better by returning iterators, >> because I can load my iterator up with a BDB cursor. This has the >> advantage of not requiring the entire member database to be loaded >> into memory just to iterate over it. Unfortunately, too much of the >> rest of the code assumes these methods return lists, and while I >> started to go down the iterator path, I backed out of it because of >> the complexity. I found that I had to recode the admin.py CGI stuff. Most of the code seems to be built with the idea of having very fast access to all aspects of the member data. With databases and other external storages this is not the case. It is often better to get all the member data for a chunk of members at once, then calling out to the storage for each and every bit of information. >> There are other optimizations that would require a bit more >> thought. E.g. the admin's Membership List page seems to require >> that the entire member database be iterated over to chunkify and >> bucketize. Fixing this probably requires both changes to the u/i >> and changes to the interface. It also makes life more difficult for >> OldStyleMemberships, although BDBMemberAdaptor can probably be >> fairly easily elaborated. -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, Mar 05 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ Python UK 2003, Oxford: 27 days left EuroPython 2003, Charleroi, Belgium: 111 days left From sb.list at sb.org Sat Mar 8 16:26:35 2003 From: sb.list at sb.org (Stonewall Ballard) Date: Sat Mar 8 16:26:39 2003 Subject: [Mailman-Developers] Can't create list from web Message-ID: I'm running 2.1+ (just updated it), and have discovered that I can't create lists from the web anymore. I get this: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 176, in process_request mlist.Create(listname, owner, pw, langs) File "/usr/local/mailman/Mailman/MailList.py", line 444, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 362, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 91, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/actnetmembers.mbox' The list itself is not created (not listed by bin/list_lists). A directory of that name is created in the lists directory, but it's empty and it has its permissions set incorrectly (the group "s" bit is not set). I deleted the empty directory and used bin/newlist to create it. This time it worked, but the permissions were still wrong. check_perms complained: directory permissions must be 02775: /usr/local/mailman/archives/private/actnetmembers (fixing) directory permissions must be 02775: /usr/local/mailman/archives/private/actnetmembers.mbox (fixing) directory permissions must be 02775: /usr/local/mailman/lists/actnetmembers (fixing) I have not created a list since I updated to 2.1, and since I updated my server to OS X Jaguar (10.2.4) Server. Any ideas? - Stoney From terri at zone12.com Wed Mar 12 15:50:41 2003 From: terri at zone12.com (Terri Oda) Date: Wed Mar 12 15:47:39 2003 Subject: [Mailman-Developers] Mailman 2.1 Topics for Dummies Message-ID: <20030312205041.GA3510@ostraya.zone12.com> I'm writing the mailman list subscriber documentation and I'm trying to find a good way to explain how topics work. Most if it isn't too hard to do, but, unfortunately, I'd have to explain regular expressions to people for them to be able to look at any topic and figure out how to post to it. That seems a little excessive, so I've simplified and just give examples to show some things which they're likely to encounter. But I wonder... Wouldn't it be easier if Mailman could just *tell* people what needs to appear in their subject line or keywords line when they click on the details of any given topic? If your topic regexp is something like \[Networking\] then it's not going to be inherantly obvious to everyone that that means you put [Networking] in your Subject line, and if people make the logical error of using \[Networking\] in their subject line, it won't work. I'm not sure the best way to avoid this... maybe something which gives a minimally matching expression so if someone checks the details for the networking topic, they see: Name: Networking course Pattern (as regexp): \[Networking\] Description: Networking course for complete beginners wishing to establish a simple home newtork To post under this topic , put "[Networking]" (witout the quotes) into the Subject: or the Keywords: line in your message. (These lines can also appear in the first X lines of the body of your message.) I know, I can put this into the description, but we can't assume everyone will do this, and right now the member interface doesn't even mention how this matching is done -- for all the subscriber knows, the pattern could match on the entire message! The suggested tag for posting could be generated from the regular expression or inputted by the admin. Also, does it say anywhere that this is done case-insensitively? I didn't see it when I was glancing around, but it's possible that I missed it. If it doesn't say so, can we make it say so somewhere? It should say so at least in the admin pages, but I can't think of any good reason not to mention it on the member options page too. Terri From Daniel.Buchmann at bibsys.no Wed Mar 12 22:53:43 2003 From: Daniel.Buchmann at bibsys.no (Daniel Buchmann) Date: Wed Mar 12 16:55:57 2003 Subject: [Mailman-Developers] Serious bug shunting messages Message-ID: <1047506024.3464.7.camel@fornax.bibsys.no> Sorry, didn't have the time to look if there already was a bug report on SF for this one... I'm getting this traceback and a lot of files in qfiles/shunt/, seems to be something with digests and i18n? List language is Norwegian. Mar 12 22:47:24 2003 (10688) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 82, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 264, in process part.set_payload(_("""\ File "/home/mailman/Mailman/i18n.py", line 78, in _ return _translation.gettext(s) % dict UnicodeError: ASCII decoding error: ordinal not in range(128) This is giving me a major headache... I'm having 60+ messages stuck in the shunt queue, and people complaining about lists not working, messages not getting through, etc... anyone else seen this? I'm using latest Release_2_1-maint CVS branch... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030312/a3cb6777/attachment.bin From barry at python.org Wed Mar 12 17:03:45 2003 From: barry at python.org (Barry A. Warsaw) Date: Wed Mar 12 17:04:14 2003 Subject: [Mailman-Developers] Serious bug shunting messages References: <1047506024.3464.7.camel@fornax.bibsys.no> Message-ID: <15983.44737.74664.227008@gargle.gargle.HOWL> >>>>> "DB" == Daniel Buchmann writes: DB> This is giving me a major headache... I'm having 60+ messages DB> stuck in the shunt queue, and people complaining about lists DB> not working, messages not getting through, etc... anyone else DB> seen this? Ha! I'll bet you have messages with rfc2231 encoded non-ascii filename or description parameters. But that's just a wild guess. :) Peer's been haranguing me about similar problems for weeks. I /think/ I might have a solution but I want to test it a little bit more before I commit it to the head. I need to backport a bunch of head changes to the maint branch. We'll see if I have time for all that tonight. synchronicit-ly y'rs, -Barry From Daniel.Buchmann at bibsys.no Thu Mar 13 09:06:13 2003 From: Daniel.Buchmann at bibsys.no (Daniel Buchmann) Date: Thu Mar 13 03:11:22 2003 Subject: [Mailman-Developers] Serious bug shunting messages In-Reply-To: <15983.44737.74664.227008@gargle.gargle.HOWL> References: <1047506024.3464.7.camel@fornax.bibsys.no> <15983.44737.74664.227008@gargle.gargle.HOWL> Message-ID: <1047542775.2706.22.camel@fornax.bibsys.no> On Wed, 2003-03-12 at 23:03, Barry A. Warsaw wrote: > > Peer's been haranguing me about similar problems for weeks. I > /think/ I might have a solution but I want to test it a little bit > more before I commit it to the head. I need to backport a bunch of > head changes to the maint branch. We'll see if I have time for all > that tonight. Thanks a lot Barry! The recently committed change to i18n.py solved the problem! :D My qfiles/shunt/ dir is now empty. I also had a problem with the daily cron/senddigests, but it went away after patching i18n.py. ;) Btw: where is the message pipeline in Mailman? What I want to do is change the order of the tests that cause messages to be held etc. (See my post http://mail.python.org/pipermail/mailman-developers/2003-February/014847.html) Thanks, hope to see you around on #mailman again sometime soon. ;) .dan -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030313/2218c66b/attachment.bin From Dan.Mick at sun.com Thu Mar 13 04:54:13 2003 From: Dan.Mick at sun.com (Dan Mick) Date: Thu Mar 13 07:58:51 2003 Subject: [Mailman-Developers] Serious bug shunting messages In-Reply-To: <1047542775.2706.22.camel@fornax.bibsys.no> References: <1047506024.3464.7.camel@fornax.bibsys.no> <15983.44737.74664.227008@gargle.gargle.HOWL> <1047542775.2706.22.camel@fornax.bibsys.no> Message-ID: <3E707F75.9070201@sun.com> Daniel Buchmann wrote: > Btw: where is the message pipeline in Mailman? See Defaults.py From fil at rezo.net Thu Mar 13 14:35:20 2003 From: fil at rezo.net (Fil) Date: Thu Mar 13 08:35:22 2003 Subject: [Mailman-Developers] a unicode thanks + spamassassin question In-Reply-To: <3E707F75.9070201@sun.com> References: <1047506024.3464.7.camel@fornax.bibsys.no> <15983.44737.74664.227008@gargle.gargle.HOWL> <1047542775.2706.22.camel@fornax.bibsys.no> <3E707F75.9070201@sun.com> Message-ID: <20030313133520.GI26445@rezo.net> Hi Barry, just a note to mention that last night's corrections have solved the "daily reminder unicode traceback" that I had been getting for a week. Thanks. BTW, does anyone have a current pointer how how to integrate spamassassin into the Mailman pipe? (A Google search brings a lot of old stuff.) -- Fil From barry at python.org Thu Mar 13 08:41:37 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Mar 13 08:42:15 2003 Subject: [Mailman-Developers] Serious bug shunting messages References: <1047506024.3464.7.camel@fornax.bibsys.no> <15983.44737.74664.227008@gargle.gargle.HOWL> <1047542775.2706.22.camel@fornax.bibsys.no> Message-ID: <15984.35473.326287.180726@gargle.gargle.HOWL> >>>>> "DB" == Daniel Buchmann writes: DB> Thanks a lot Barry! The recently committed change to i18n.py DB> solved the problem! :D My qfiles/shunt/ dir is now empty. I DB> also had a problem with the daily cron/senddigests, but it DB> went away after patching i18n.py. ;) Excellent! DB> Btw: where is the message pipeline in Mailman? What I want to DB> do is change the order of the tests that cause messages to be DB> held etc. (See my post DB> http://mail.python.org/pipermail/mailman-developers/2003-February/014847.html) This part's definitely kludgy, and I have ideas for how to fix it. But for now, there are two places to look. First is GLOBAL_PIPELINE in Defaults.py.in. There you'll see that it calls out to the Moderate module and then to the Hold module. There's been a bit of thrash on the order of these. ;) Then, inside Hold.py, you'll see that process() hard codes the order in which conditions are tried. Changing this requires hacking the code. My idea (for 2.2 or 3.0 -- I'm still conflicted) is that /all/ the hold tests would be applied to a message and there'd be some way for admins to either see all the conditions that apply or select the priority in which they cause a message to be held or rejected. Not much more detail than that, but it's definitely something on my radar. Suggestions are welcome! DB> Thanks, hope to see you around on #mailman again sometime DB> soon. ;) I'm trying to hang out there occasionally these days! -Barry From fil at rezo.net Thu Mar 13 15:34:33 2003 From: fil at rezo.net (Fil) Date: Thu Mar 13 09:34:37 2003 Subject: [Mailman-Developers] a unicode thanks + spamassassin question In-Reply-To: <20030313133520.GI26445@rezo.net> References: <1047506024.3464.7.camel@fornax.bibsys.no> <15983.44737.74664.227008@gargle.gargle.HOWL> <1047542775.2706.22.camel@fornax.bibsys.no> <3E707F75.9070201@sun.com> <20030313133520.GI26445@rezo.net> Message-ID: <20030313143433.GA2829@rezo.net> > just a note to mention that last night's corrections have solved the "daily > reminder unicode traceback" that I had been getting for a week. Thanks. Oops! bin/list_members doesn't work anymore Traceback (most recent call last): File "/home/mailman/bin/list_members", line 240, in ? main() File "/home/mailman/bin/list_members", line 218, in main print >> fp, formataddr((safe(name), addr)) File "/home/mailman/bin/list_members", line 103, in safe return unicode(addr, ENC, 'replace').encode(ENC, 'replace') TypeError: coercing to Unicode: need string or buffer, int found -- Fil From barry at python.org Thu Mar 13 10:54:45 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Mar 13 10:55:17 2003 Subject: [Mailman-Developers] a unicode thanks + spamassassin question References: <1047506024.3464.7.camel@fornax.bibsys.no> <15983.44737.74664.227008@gargle.gargle.HOWL> <1047542775.2706.22.camel@fornax.bibsys.no> <3E707F75.9070201@sun.com> <20030313133520.GI26445@rezo.net> <20030313143433.GA2829@rezo.net> Message-ID: <15984.43461.267067.381157@gargle.gargle.HOWL> Fixed. From bryanf at samurai.com Fri Mar 14 06:19:40 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Fri Mar 14 06:19:44 2003 Subject: [Mailman-Developers] list.org DNS fubar? Message-ID: Someone might want to look at this. admin.root:/> host www.list.org Host not found. admin.root:/> host list.org list.org mail is handled (pri=100) by colossus.bilow.com list.org mail is handled (pri=10) by mail.zork.org I tried direct queries to all the listed name servers, none are returning A records for list.org. Thanks, Bryan From jam at jamux.com Fri Mar 14 07:36:35 2003 From: jam at jamux.com (John A. Martin) Date: Fri Mar 14 07:36:40 2003 Subject: [Mailman-Developers] list.org DNS fubar? In-Reply-To: (Bryan Fullerton's message of "Fri, 14 Mar 2003 06:19:40 -0500") References: Message-ID: <87n0jyyvjg.fsf@athene.jamux.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "BryanW" == Bryan Fullerton >>>>> "[Mailman-Developers] list.org DNS fubar?" >>>>> Fri, 14 Mar 2003 06:19:40 -0500 BryanW> I tried direct queries to all the listed name servers, BryanW> none are returning A records for list.org. Usefull might be which gave "interesting" results for list.org at approxomately Fri Mar 14 07:30 EST 2003 (UTC - -0500). jam -----BEGIN PGP SIGNATURE----- iD8DBQE+cczFUEvv1b/iXy8RAqjyAKCCRfx1KWLVJpJ2QCMj46ET9PNHFQCgkksk 9NQtZ/dg37q26snE0qfzwI8= =akeQ -----END PGP SIGNATURE----- From mal at lemburg.com Fri Mar 14 13:54:24 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Fri Mar 14 07:54:59 2003 Subject: [Mailman-Developers] list.org DNS fubar? In-Reply-To: References: Message-ID: <3E71D100.9010001@lemburg.com> Bryan Fullerton wrote: > Someone might want to look at this. > > admin.root:/> host www.list.org > Host not found. > admin.root:/> host list.org > list.org mail is handled (pri=100) by colossus.bilow.com > list.org mail is handled (pri=10) by mail.zork.org > > I tried direct queries to all the listed name servers, none are > returning A records for list.org. ;; QUESTION SECTION: ;list.org. IN ANY ;; ANSWER SECTION: list.org. 7083 IN SOA ns.BILOW.COM. mike.BILOW.COM. 2003031202 3600 1800 604800 7200 list.org. 81963 IN NS NS4.BILOW.COM. list.org. 81963 IN NS NS1.ZORK.org. list.org. 81963 IN NS NS3.BILOW.COM. ;; AUTHORITY SECTION: list.org. 81963 IN NS NS3.BILOW.COM. list.org. 81963 IN NS NS4.BILOW.COM. list.org. 81963 IN NS NS1.ZORK.org. ;; ADDITIONAL SECTION: NS1.ZORK.org. 172683 IN A 12.109.142.4 NS3.BILOW.COM. 172683 IN A 198.136.189.254 NS4.BILOW.COM. 172683 IN A 207.51.72.226 Looks like the last update to ns.bilow.com screwed up the entries... or someone is hacking DNS here. -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, Mar 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ Python UK 2003, Oxford: 18 days left EuroPython 2003, Charleroi, Belgium: 102 days left From thomas at xs4all.net Fri Mar 14 14:47:08 2003 From: thomas at xs4all.net (Thomas Wouters) Date: Fri Mar 14 08:47:12 2003 Subject: [Mailman-Developers] list.org DNS fubar? In-Reply-To: References: Message-ID: <20030314134708.GL2112@xs4all.nl> On Fri, Mar 14, 2003 at 06:19:40AM -0500, Bryan Fullerton wrote: > Someone might want to look at this. > admin.root:/> host www.list.org > Host not found. > admin.root:/> host list.org > list.org mail is handled (pri=100) by colossus.bilow.com > list.org mail is handled (pri=10) by mail.zork.org The machine is down; Barry contacted the admins last night: 22:09 ok, list.org crashed and will be back up soon. i bet the dns update was to point it at new nameservers 22:10 for now mailman.sf.net is good enough Note that the time is CET, so that's ehm, late afternoon american time. -- Thomas Wouters Hi! I'm a .signature virus! copy me into your .signature file to help me spread! From barry at python.org Fri Mar 14 09:03:35 2003 From: barry at python.org (Barry A. Warsaw) Date: Fri Mar 14 09:04:06 2003 Subject: [Mailman-Developers] Re: list.org DNS fubar? References: Message-ID: <15985.57655.673124.338642@gargle.gargle.HOWL> >>>>> "BF" == Bryan Fullerton writes: BF> Someone might want to look at this. Known issue. I've been in contact with the domain owner (a friend and Mailman inventor John Viega) and they're working on it. Until then, mailman.sf.net should be a fine mirror. -Barry From dag at sonsorol.org Sat Mar 15 21:40:51 2003 From: dag at sonsorol.org (Chris Dagdigian) Date: Sat Mar 15 21:40:32 2003 Subject: [Mailman-Developers] odd problem: since MM 2.1 upgrade all links to public list archives are broken Message-ID: <3E73E433.2090007@sonsorol.org> Hi mailman developers, First off; thanks for a wonderful package. We've been using Mailman for years to keep thousands of open source bioinformatics developers and users in touch with each other. Now I've got a problem that seems really odd. I'm a little bit afraid that it may have been caused by some old cruft left over in our mailman dir which has been subjected to many mailman upgrade installs over the years. The SMTP/mailman box is a Dec Alpha workstation running Redhat Linux 6.x with python 2.3. The problem: Since upgrading to Mailman 2.1 (problem persists with MM 2.1.1) all of our mailman list pages that point to the public list archives are broken. The URL is presented as "/pipermail/" instead of "/pipermail//" This prevents our web vistors from getting to our list archives as they are presented with a "you are not allowed to access /pipermail/" error each time. We have not changed our templates at all. In fact I blew away the templates directory right before upgrading to 2.1.1. I've verified in the template HTML that the "MM-List-Name" etc. data seems to be in the right place. Here are a couple of example pages with broken links to the public list archives: http://bioperl.org/mailman/listinfo/bioperl-l http://open-bio.org/mailman/listinfo/moby-l The list name is obviously getting substituted into other parts of the page. It's just not getting appended to the end of "/pipermail/" in the URL for the public list archive. Private archives work fine. I've taken one list and converted the archives from public->private and the resulting "listinfo" page then produces a perfect link to the private archive. Any hints? Has anyone seen this before? Regards, Chris -- Chris Dagdigian, BioTeam Inc. - Independent Bio-IT & Informatics consulting Office: 617-666-6454, Mobile: 617-877-5498, Fax: 425-699-0193 PGP KeyID: 83D4310E Yahoo IM: craffi Web: http://bioteam.net From marilyn at deliberate.com Mon Mar 17 12:30:56 2003 From: marilyn at deliberate.com (Marilyn Davis) Date: Mon Mar 17 15:31:09 2003 Subject: [Mailman-Developers] Virtual domains Message-ID: Someone who runs mailman lists on a virtual domain through cpanel has asked that I help him get eVote running on his lists. His host is trying to help too. But cpanel is proprietary and seems to set up the lists automatically by appending the aliases to the valiases file for the virtual domain. If the list is: test@my.net, the alias posts to test_my.net. But mailman seems to know, in some circumstances, like in list_lists, that the real name of the list is "test". Can anyone please give me a clue about how this is handled? Does anyone know anything about cpanel? Any clues at all will be greatly appreciated. I'm just banging my head against it and getting no where. Thanks. Marilyn Davis From chuqui at plaidworks.com Mon Mar 17 15:40:26 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Mon Mar 17 18:40:32 2003 Subject: [Mailman-Developers] plus addresses fail in find_members Message-ID: Looks like mailman doesn't handle plussed addresses right: plaidworks.com 156# echo "chuqui+test@plaidworks.com" | add_members -r - testlist Subscribed: chuqui+test@plaidworks.com plaidworks.com 157# find_member chuqui chuqui+test@plaidworks.com found in: testlist plaidworks.com 158# find_member chuqui+test seems like there's no way to find a plussed address from the command line without doing a dump, locating it, then doing a find_member on some subset. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ From rmg at terc.edu Tue Mar 18 01:05:52 2003 From: rmg at terc.edu (Robby Griffin) Date: Tue Mar 18 01:09:40 2003 Subject: [Mailman-Developers] plus addresses fail in find_members In-Reply-To: Message-ID: On Monday, Mar 17, 2003, at 18:40 US/Eastern, Chuq Von Rospach wrote: > plaidworks.com 158# find_member chuqui+test > > seems like there's no way to find a plussed address from the command > line without doing a dump, locating it, then doing a find_member on > some subset. That's a python regex which would match chuquitest, chuquiitest, chuquiiitest, etc. Try backslashing or bracketing the plus. From Remco.vandenBerg at dse.nl Tue Mar 4 11:04:37 2003 From: Remco.vandenBerg at dse.nl (Remco van den Berg) Date: Tue Mar 18 09:10:49 2003 Subject: [Mailman-Developers] How to use real virtual hosting? Message-ID: <20030304100437.GB9110@kemphaan.dekelen.veldhoven.nl> Dear developpers, I'm working as a volunteer for an non-profit ISP-like organisation named Digitale Stad Eindhoven (Digital City Eindhoven) in de Netherlands. (DSE http://www.dse.nl/) We provide web service to all kind of organisations in and around Eindhoven. Many sports clubs for example do have their website on our DSE server. The sports clubs do have their own virtual domain on our server. For exaple: volleyballclub.dse.nl and soccerclub.dse.nl Every club also have their own account name. Let's asume we are dealing with the unix accounts "volley" and "soccer" in this example. So far the intro... now my problem/questions... I'm looking at installing mailman on our server with the purpose to give the mailing list service to our clubs. But, as far as I understand mailman for now, mailman isn't really programmed in such a way that it can deal with virtual hosts. Only the web interface is aware of virtual hosting. Am I right? When installing a mailing list for a soccerclub we cannot run the same list on a different virtual domain for the volleyball club. True? We want for example these (different!) lists: team1@volleybalclub.dse.nl and team1@soccerclub.dse.nl The aliases needed for these mailing lists are stored in the same alias file and so they cannot exist together. OK, I think everybody understands our problem now. Main questions are: Is there a work-around to use mailmain in this environment? Can we store lists-data and archives in the home directories of the accounts linked to the virtual domains? We don't want to compile and install mailman for every club, so is it possible to only compile and install the mail wrapper program for every account? And then install a private mm_cfg.py file for every account which then points to the private data and archives directories? Or, can we include an extra command-line-parameter to a global mail wrapper program which holds the account name? Such that this parameter will tell the other scripts (post admin bounces etc.) to look in the home directory of the account. Can we work around the fact that all mailing list aliases are also stored in the non-virtual alias file? So that the aliases in the virtual alias file directly point to the private mail wrapper of the clubs? etc. etc. Any help is appreciated. Thanks for some answers, Regards, Remco van den Berg (sysadmin DSE) -- ---------------------------------------------------------------------------- Remco van den Berg Admin DSE http://www.dse.nl/rvdberg/ GSX750F http://www.dse.nl/ ---------------------------------------------------------------------------- From Niklas.Nikitin at kau.se Wed Mar 12 11:04:46 2003 From: Niklas.Nikitin at kau.se (Niklas Nikitin) Date: Tue Mar 18 09:10:50 2003 Subject: [Mailman-Developers] Strip out attachments in the archive Message-ID: <0c2701c2e87e$cfd74470$6dde0ac1@cs.kau.se> Hi, I am running Mailman 2.1.1 on our server. Today I disallow archiving, but I want to allow archiving for all lists. "My" users have the habit to attach huge documents to the e-Mail's, so I do not want to archive the attachments. I still want the attachments to be sent to all members on the list. In the archive I want to strip out the attachment and keep the rest of the document (and if possible to add a line like: "An attachment have been removed"). Can this be done, and if so how? TIA Niklas From a.carter at cordis.lu Wed Mar 12 12:44:46 2003 From: a.carter at cordis.lu (CARTER Anthony) Date: Tue Mar 18 09:10:51 2003 Subject: [Mailman-Developers] English (USA) Message-ID: <1047469486.87700.19.camel@intra241.intrasoft.lu> Hi, I would like to know if there is any way that we can remove the "USA" bit from the language options? For example, instead of "English (USA)" have just "English" Thanks, Anthony Carter From maechler at stat.math.ethz.ch Thu Mar 13 10:34:02 2003 From: maechler at stat.math.ethz.ch (Martin Maechler) Date: Tue Mar 18 09:10:53 2003 Subject: [Mailman-Developers] Bad "Uncaught bounce" [forwarded] Message-ID: <15984.20618.378369.354318@gargle.gargle.HOWL> Dear Mailman developers, first, thanks a LOT for the great software! Since I didn't find it easy to submit a bug report (for mailman 2.1) --- it was easy to **browse** bug reports, but not to submit via sourceforge --- I allow myself to forward this to you. Note this is one of many "Uncaught bounce notification"s I'm getting --- which clearly should have been caught. An even clearer one, yesterday was "User unknown" : ----- The following addresses had permanent fatal errors ----- ----- Transcript of session follows ----- ... while talking to akasolvr.vub.ac.be.: >>> RCPT To: <<< 553 ... User mathie.roelants unknown at vub.ac.be 550 ... User unknown ----- Message header follows ----- Thanks a lot for hints, Martin Maechler http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <>< -------------- next part -------------- An embedded message was scrubbed... From: mailman-bounces@stat.math.ethz.ch Subject: Uncaught bounce notification Date: Wed, 12 Mar 2003 17:00:27 +0100 Size: 7610 Url: http://mail.python.org/pipermail/mailman-developers/attachments/20030313/587f7930/attachment-0001.eml From nneul at umr.edu Thu Mar 13 10:29:14 2003 From: nneul at umr.edu (Nathan Neulinger) Date: Tue Mar 18 09:10:55 2003 Subject: [Mailman-Developers] patch to add a DEFAULT_UCFIRST_REAL_NAME option Message-ID: <20030313162912.GA4387@umr.edu> This patch adds a DEFAULT_UCFIRST_REAL_NAME option, defaulting to 1, which allows site admin to request that new lists all be created with the list name being all lowercase by default, instead of the mixed case name. -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: nneul@umr.edu University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 -------------- next part -------------- Index: Mailman/Defaults.py.in =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Defaults.py.in,v retrieving revision 2.115 diff -u -r2.115 Defaults.py.in --- Mailman/Defaults.py.in 13 Mar 2003 05:46:56 -0000 2.115 +++ Mailman/Defaults.py.in 13 Mar 2003 16:27:41 -0000 @@ -767,6 +767,10 @@ DEFAULT_MAX_NUM_RECIPIENTS = 10 DEFAULT_MAX_MESSAGE_SIZE = 40 # KB +# Should lists be created by default as 'Listname' or as 'listname'. Set to +# 0 to create list name in all lowercase. +DEFAULT_UCFIRST_REAL_NAME = 1 + # These format strings will be expanded w.r.t. the dictionary for the # mailing list instance. DEFAULT_SUBJECT_PREFIX = "[%(real_name)s] " Index: Mailman/MailList.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/MailList.py,v retrieving revision 2.104 diff -u -r2.104 MailList.py --- Mailman/MailList.py 24 Feb 2003 15:37:57 -0000 2.104 +++ Mailman/MailList.py 13 Mar 2003 16:27:41 -0000 @@ -307,7 +308,10 @@ mm_cfg.DEFAULT_BOUNCE_MATCHING_HEADERS self.anonymous_list = mm_cfg.DEFAULT_ANONYMOUS_LIST internalname = self.internal_name() - self.real_name = internalname[0].upper() + internalname[1:] + if mm_cfg.DEFAULT_UCFIRST_REAL_NAME: + self.real_name = internalname[0].upper() + internalname[1:] + else: + self.real_name = internalname self.description = '' self.info = '' self.welcome_msg = '' From nneul at umr.edu Thu Mar 13 10:36:11 2003 From: nneul at umr.edu (Nathan Neulinger) Date: Tue Mar 18 09:10:56 2003 Subject: [Mailman-Developers] Updated patch that allows posting authorization for members of other lists Message-ID: <20030313163609.GA4419@umr.edu> This patch allows you to specify +listname in the accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers, and discard_these_nonmembers boxes in the list configuration, and will dynamically include the members of those lists. This is very useful when you have lists that forward to other lists. For example: mygroup-leaders mygroup-helpers mygroup-workers with mygroup-all forwarding to each of the above. You could put +mygroup-helpers +mygroup-workers +mygroup-leaders in the accept box for each of those lists, and it will allow any of the members of any of the lists to post to the mygroup-all list. Or similar affect for other configurations. -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: nneul@umr.edu University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 -------------- next part -------------- Index: Mailman/MailList.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/MailList.py,v retrieving revision 2.104 diff -u -r2.104 MailList.py --- Mailman/MailList.py 24 Feb 2003 15:37:57 -0000 2.104 +++ Mailman/MailList.py 13 Mar 2003 16:27:41 -0000 @@ -30,6 +30,7 @@ import socket import urllib import cPickle +import string from cStringIO import StringIO from UserDict import UserDict @@ -1347,3 +1351,64 @@ if mm_cfg.DEFAULT_SERVER_LANGUAGE not in langs: langs.append(mm_cfg.DEFAULT_SERVER_LANGUAGE) return langs + + + +# +# Added at University of Wollongong by Peter Gray (pdg@uow.edu.au) +# +# The idea here is that addresses of the form +listname@domain +# are actually other mailman lists. The domain must match the +# domain of the current list. + + def expand_sublists(self, old_recipients): + """returns an expanded list of the members. (all lowercase)""" + + new_recipients = self.internal_expand_sublists(old_recipients, 0) + return new_recipients + + def internal_expand_sublists(self, old_recipients, recursion_depth): + + dirty = 0 + + recursion_depth = recursion_depth + 1 + + if recursion_depth > 50: + # Screw you guys, I'm going home. + raise Error.MMListError, self.internal_name() + + new_recipients = [] + + for full_address in old_recipients: + if full_address[0] != '+': + new_recipients.append(full_address) + continue + + s = string.split(full_address, '@') + local = s[0][1:] + domain = None + if len(s) >= 2: + domain = s[1] + if domain != self.host_name: + new_recipients.append(full_address) + continue + + try: + sublist = MailList(local, lock=0) + except: +# Do we mail to the address or raise an exception? +# For the moment, just treat the address as a real one + new_recipients.append(full_address) + continue + + dirty = 1 + new_member_list = sublist.getMemberCPAddresses(sublist.getRegularMemberKeys() + sublist.getDigestMemberKeys()) + + for new_member in new_member_list: + new_recipients.append(new_member) + + if not dirty: return new_recipients + return self.internal_expand_sublists(new_recipients, recursion_depth) + +# End local additions + Index: Mailman/Handlers/Moderate.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/Moderate.py,v retrieving revision 2.13 diff -u -r2.13 Moderate.py --- Mailman/Handlers/Moderate.py 31 Dec 2002 03:28:41 -0000 2.13 +++ Mailman/Handlers/Moderate.py 13 Mar 2003 16:27:41 -0000 @@ -87,15 +87,15 @@ else: sender = msg.get_sender() # From here on out, we're dealing with non-members. - if matches_p(sender, mlist.accept_these_nonmembers): + if matches_p(sender, mlist.expand_sublists(mlist.accept_these_nonmembers)): return - if matches_p(sender, mlist.hold_these_nonmembers): + if matches_p(sender, mlist.expand_sublists(mlist.hold_these_nonmembers)): Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost) # No return - if matches_p(sender, mlist.reject_these_nonmembers): + if matches_p(sender, mlist.expand_sublists(mlist.reject_these_nonmembers)): do_reject(mlist) # No return - if matches_p(sender, mlist.discard_these_nonmembers): + if matches_p(sender, mlist.expand_sublists(mlist.discard_these_nonmembers)): do_discard(mlist, msg) # No return # Okay, so the sender wasn't specified explicitly by any of the non-member From syed at mimos.my Fri Mar 14 19:06:24 2003 From: syed at mimos.my (mr_zali) Date: Tue Mar 18 09:10:58 2003 Subject: [Mailman-Developers] delete list that have space Message-ID: <3E71B7B0.8000305@mimos.my> Hi, I create a list named free software. But how i want to delete the list. Using 'rmlist' command still no effect. I'm using Mailman-2.0.12. From paul at quintessenz.org Fri Mar 14 21:35:40 2003 From: paul at quintessenz.org (Paul Boehm) Date: Tue Mar 18 09:11:00 2003 Subject: [Mailman-Developers] unsubscribe.py Message-ID: <20030314203540.GA29712@danube.quintessenz.org> Hi, Our NGO has lots of administrative overhead, because users manage to subscribe to our mailinglists, but find the unsubscribe procedure a lot harder (log in with password, go to options, unsubscribe) than bugging us. Because of this, we've added a drop-in unsubscribe CGI to our mailman install, which allows unsubscribe to work in a manner similiar to subscribing. Security-wise this should have no adverse implications, as challenge base unsubscription already is available via email, in stock mailman. To allow for i18n support, we'd really like to have our additional cgi accepted into the main tree. paul PS: Please CC me in replies, as i'm currently not subscribed to this list. From paul at quintessenz.org Fri Mar 14 21:40:46 2003 From: paul at quintessenz.org (Paul Boehm) Date: Tue Mar 18 09:11:02 2003 Subject: [Mailman-Developers] unsubscribe.py Message-ID: <20030314204046.GB29712@danube.quintessenz.org> forgot the attachment -------------- next part -------------- # Copyright (C) 1998-2003 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. """Process subscription or roster requests from listinfo form.""" import sys import os import cgi import signal from Mailman import mm_cfg from Mailman import Utils from Mailman import MailList from Mailman import Errors from Mailman import i18n from Mailman import Message from Mailman.UserDesc import UserDesc from Mailman.htmlformat import * from Mailman.Logging.Syslog import syslog SLASH = '/' ERRORSEP = '\n\n

' # Set up i18n _ = i18n._ i18n.set_language(mm_cfg.DEFAULT_SERVER_LANGUAGE) def main(): doc = Document() doc.set_language(mm_cfg.DEFAULT_SERVER_LANGUAGE) parts = Utils.GetPathPieces() if not parts: doc.AddItem(Header(2, _("Error"))) doc.AddItem(Bold(_('Invalid options to CGI scxipt'))) print doc.Format() return listname = parts[0].lower() try: mlist = MailList.MailList(listname, lock=0) except Errors.MMListError, e: # Avoid cross-site scripting attacks safelistname = Utils.websafe(listname) doc.AddItem(Header(2, _("Error"))) doc.AddItem(Bold(_('No such list %(safelistname)s'))) print doc.Format() syslog('error', 'No such list "%s": %s\n', listname, e) return # See if the form data has a preferred language set, in which case, use it # for the results. If not, use the list's preferred language. cgidata = cgi.FieldStorage() language = cgidata.getvalue('language') if not Utils.IsLanguage(language): language = mlist.preferred_language i18n.set_language(language) doc.set_language(language) # We need a signal handler to catch the SIGTERM that can come from Apache # when the user hits the browser's STOP button. See the comment in # admin.py for details. # # BAW: Strictly speaking, the list should not need to be locked just to # read the request database. However the request database asserts that # the list is locked in order to load it and it's not worth complicating # that logic. def sigterm_handler(signum, frame, mlist=mlist): # Make sure the list gets unlocked... mlist.Unlock() # ...and ensure we exit, otherwise race conditions could cause us to # enter MailList.Save() while we're in the unlocked state, and that # could be bad! sys.exit(0) mlist.Lock() try: # Install the emergency shutdown signal handler signal.signal(signal.SIGTERM, sigterm_handler) process_form(mlist, doc, cgidata, language) mlist.Save() finally: mlist.Unlock() def process_form(mlist, doc, cgidata, lang): listowner = mlist.GetOwnerEmail() realname = mlist.real_name results = [] # The email address being subscribed, required email = cgidata.getvalue('email', '') if mlist.isMember(email): mlist.ConfirmUnsubscription(email) results = _("""Your unsubscribe request has been received. \ To confirm that you really want to be unsubscribed, you will soon \ get a confirmation email, which contains further instructions.""") else: results = _("""You're not subscribed with that email address.""") # Show the results print_results(mlist, results, doc, lang) def print_results(mlist, results, doc, lang): # The bulk of the document will come from the options.html template, which # includes its own html armor (head tags, etc.). Suppress the head that # Document() derived pages get automatically. doc.suppress_head = 1 replacements = mlist.GetStandardReplacements(lang) replacements[''] = results output = mlist.ParseTags('unsubscribe.html', replacements, lang) doc.AddItem(output) print doc.Format() From marki at host.sk Mon Mar 17 12:40:32 2003 From: marki at host.sk (Marek Podmaka) Date: Tue Mar 18 09:11:04 2003 Subject: [Mailman-Developers] list statistics Message-ID: Hi! I have written a program to generate statistics on email messages (which are in MBOX format) called MailListStat (MLS). It computes a lot of stats (TOP authors, subjects, mailers, some graphs, ...) Output is in text format (to be posted to list) or HTML format. Now it supports cache files for faster operations (uses PHP wrapper to allow user to choose language and some others options and stats are displayed from cache files really fast). New version (not yet released) can add new messages to cache file, so it's possible to automatically update cache file from .forward/.procmailrc... I would like to ask how this can be used with mailman. The best option in my opinion would be possibility to run MLS after new message is received for the list. Other options include using cron to daily generate the cache file or subscribing special user to the list who will run MLS from .forward/alias. But I think the first option is best. I have seen some requests for similar functionality in mailman, so I think it would be fine to integrate these two... Homepage of MLS: http://freshmeat.net/projects/mls HAVE A NICE DAY :-) -- bYE, Marki From demic at pabalan.net Mon Mar 17 22:12:29 2003 From: demic at pabalan.net (demic@pabalan.net) Date: Tue Mar 18 09:11:06 2003 Subject: [Mailman-Developers] help in modifying the archives by author Message-ID: <1047910349.3e75d7cdf2954@mail.pabalan.net> Hi! I would like to make some changes in my lists' archives. I want my archives to be viewed in folders where all mails coming from a sender should be placed to its own folder named after him so that if I click on my archives' site and view it by author,(e.g mysite.com/pipermail/mylist/2003-March/author.html),folders will show up sender A sender B sender C I am running mailman with version 2.0.13 Any help? Thanks in advance!!! ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ From marty at penguinarts.com Mon Mar 17 17:02:40 2003 From: marty at penguinarts.com (Marty Galyean) Date: Tue Mar 18 09:11:08 2003 Subject: [Mailman-Developers] plus addresses fail in find_members In-Reply-To: References: Message-ID: <1047945761.1446.6.camel@localhost.localdomain> Try putting a \\ before the +. Like this: chuqui\\+@plaidworks.com Looks like the plus may be getting interpreted as a regex op without the double escape. Marty On Mon, 2003-03-17 at 16:40, Chuq Von Rospach wrote: > > Looks like mailman doesn't handle plussed addresses right: > > plaidworks.com 156# echo "chuqui+test@plaidworks.com" | add_members -r > - testlist > Subscribed: chuqui+test@plaidworks.com > > > plaidworks.com 157# find_member chuqui > chuqui+test@plaidworks.com found in: > testlist > > plaidworks.com 158# find_member chuqui+test > > seems like there's no way to find a plussed address from the command > line without doing a dump, locating it, then doing a find_member on > some subset. > > > > > > > > > -- > Chuq Von Rospach, Architech > chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From detlef.neubauer at charite.de Tue Mar 18 13:31:11 2003 From: detlef.neubauer at charite.de (Detlef Neubauer) Date: Tue Mar 18 09:11:10 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] delete list that have space In-Reply-To: mr_zali's message of "Fri, 14 Mar 2003 19:06:24 +0800" References: <3E71B7B0.8000305@mimos.my> Message-ID: mr_zali writes: > I create a list named free software. :-) > But how i want to delete the list. Using 'rmlist' command still > no effect. I'm using Mailman-2.0.12. Try rmlist "free software" or rmlist free\ software Mit freundlichen Gruessen Detlef Neubauer -- .oO GnuPG Key auf http://www.keyserver.net/ Oo. From simar at rodriguezmanuel.com.ar Tue Mar 18 11:19:23 2003 From: simar at rodriguezmanuel.com.ar (Manuel "SiMaR" Rodriguez) Date: Tue Mar 18 09:17:55 2003 Subject: [Mailman-Developers] unsubscribe References: Message-ID: <011401c2ed59$6499aba0$94b5e818@yinqe8xkai0czlw> ----- Original Message ----- From: "Marek Podmaka" To: Sent: Monday, March 17, 2003 8:40 AM Subject: [Mailman-Developers] list statistics > Hi! > > I have written a program to generate statistics on email messages (which > are in MBOX format) called MailListStat (MLS). It computes a lot of stats > (TOP authors, subjects, mailers, some graphs, ...) Output is in text > format (to be posted to list) or HTML format. Now it supports cache files > for faster operations (uses PHP wrapper to allow user to choose language > and some others options and stats are displayed from cache files really > fast). > > New version (not yet released) can add new messages to cache file, so it's > possible to automatically update cache file from .forward/.procmailrc... > > I would like to ask how this can be used with mailman. The best option in > my opinion would be possibility to run MLS after new message is received > for the list. Other options include using cron to daily generate the cache > file or subscribing special user to the list who will run MLS from > .forward/alias. But I think the first option is best. I have seen some > requests for similar functionality in mailman, so I think it would be fine > to integrate these two... > > Homepage of MLS: http://freshmeat.net/projects/mls > > HAVE A NICE DAY :-) > > -- > bYE, Marki > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers > From thomas at xs4all.net Tue Mar 18 17:00:34 2003 From: thomas at xs4all.net (Thomas Wouters) Date: Tue Mar 18 11:00:47 2003 Subject: [Mailman-Developers] installation path In-Reply-To: <3E5ED814.1A27698A@mimos.my> References: <3E5ED814.1A27698A@mimos.my> Message-ID: <20030318160034.GZ2112@xs4all.nl> Apologies for the late reply, it seems the message was stuck in the approval queue. On Fri, Feb 28, 2003 at 11:31:33AM +0800, syed wrote: > >From the documentation, the default installation path is /home/mailman. > It is practical we install mailman in /home/mailman or we should install > it at other location? (e.g /var/www/html) Or do you have special > installation path to install mailman. I'm asking this silly question > because i'm quiet confuse when other software(actually i'm trying to setup > savannah) always asking me where is mailman cgi-bin path? The default installation path was /home/mailman in Mailman 2.0 and earlier, but is /usr/local/mailman for Mailman 2.1 and later. However, you can easily change that (using the --prefix argument to configure) and you can split off parts of the installation by using, e.g., the --exec-prefix and --with-var-prefix arguments to configure. The default paths, including the cgi-bin path, and how you can change them, are all explained in the installation manual. The cgi-bin path is {prefix}/cgi-bin by default (so, if you have Mailman 2.1 and the default $prefix, it would be /usr/local/mailman/cgi-bin.) -- Thomas Wouters Hi! I'm a .signature virus! copy me into your .signature file to help me spread! From thomas at xs4all.net Tue Mar 18 17:03:11 2003 From: thomas at xs4all.net (Thomas Wouters) Date: Tue Mar 18 11:03:28 2003 Subject: [Mailman-Developers] English (USA) In-Reply-To: <1047469486.87700.19.camel@intra241.intrasoft.lu> References: <1047469486.87700.19.camel@intra241.intrasoft.lu> Message-ID: <20030318160311.GA2112@xs4all.nl> Aplogies for the late reply, it seem the message was stuck in the approval queue. On Wed, Mar 12, 2003 at 12:44:46PM +0100, CARTER Anthony wrote: > I would like to know if there is any way that we can remove the "USA" > bit from the language options? For example, instead of "English (USA)" > have just "English" Well, you can certainly do that for your own Mailman installation; just search for 'USA' and remove the string where you see it :) Whether we want that by default in the distributed Mailman is something else. I'd personally be against it, because there is a real difference between, for instance, English for the British and English for the Americans. Calling it English (USA) at least makes it clear which version it is, even if there isn't (yet) a British variant. Or is there ? -- Thomas Wouters Hi! I'm a .signature virus! copy me into your .signature file to help me spread! From terri at zone12.com Tue Mar 18 19:45:34 2003 From: terri at zone12.com (Terri Oda) Date: Tue Mar 18 19:41:18 2003 Subject: [Mailman-Developers] How to use real virtual hosting? In-Reply-To: <20030304100437.GB9110@kemphaan.dekelen.veldhoven.nl> References: <20030304100437.GB9110@kemphaan.dekelen.veldhoven.nl> Message-ID: <20030319004534.GF964@ostraya.zone12.com> > We want for example these (different!) lists: > > team1@volleybalclub.dse.nl and team1@soccerclub.dse.nl > > The aliases needed for these mailing lists are stored in the same > alias file and so they cannot exist together. On one of my servers, we solve this problem by having, say, list@host1 and list@host2 actually be called "host1" and "host2" in Mailman, but we have mail aliases that make list@host1 and list@host2 work, and the appropriate setting to let Mailman know that list@host1 and list@host2 are appropriate posting addresses for lists host1 and host2 respectively. In our case, it's only the actual posting addresses where we want the same name, but it wouldn't be too hard to extend this to hide more than just the one address. You could probably do something similar by naming your mailing lists team1_volleyball and team1_soccer and then setting up the appropriate mailing aliases so that team1@volleyballclub.dse.nl and team1@soccerclub.dse.nl work as expected (similarly for team1-request@volleyballclub.dse.nl, etc.) If you don't like having the longer urls that'll result, you could also make http://volleybalclub.dse.nl/mailman/listinfo/team1 equivalent to http://volleybalclub.dse.nl/mailman/listinfo/team1_volleyball using mod_rewrite in Apache, or something similar for the webserver of your choice. It's a bit of a hack, though, since, of course, the list itself will still advertise addresses like team1_volleyball-request@volleyballclub.dse.nl, but it probably beats multiple installations of Mailman and it's fairly seamless to your users unless you forget to make some aliases. Terri From nneul at umr.edu Tue Mar 18 18:47:28 2003 From: nneul at umr.edu (Nathan Neulinger) Date: Tue Mar 18 19:47:36 2003 Subject: [Mailman-Developers] How to use real virtual hosting? In-Reply-To: <20030319004534.GF964@ostraya.zone12.com> References: <20030304100437.GB9110@kemphaan.dekelen.veldhoven.nl> <20030319004534.GF964@ostraya.zone12.com> Message-ID: <1048034848.13153.23.camel@cessna.rollanet.org> Actually, as long as you reasonably automate things, multiple installations of mailman is not a big deal. What sucks rocks is having to run multiple mailman controller processes simultaneously, when a simple iterative queue processor would cover the needs of most sites. There was a post on this list a while back on an unsupported way to do that. I'd very much like to see this be a supported mechanism, via something as simple as: mailmanctl -s oneshot Then, for sites that need that functionality of a non-ugly-hack virtual hosting, they have a easy way to do this in a supported fashion - just call mailmanctl -s oneshot for each installation of mailman in sequence every X minutes, perhaps even running a few in parallel for extra performance, but not running ALL of them at the same time. -- Nathan On Tue, 2003-03-18 at 18:45, Terri Oda wrote: > > We want for example these (different!) lists: > > > > team1@volleybalclub.dse.nl and team1@soccerclub.dse.nl > > > > The aliases needed for these mailing lists are stored in the same > > alias file and so they cannot exist together. > > On one of my servers, we solve this problem by having, say, list@host1 and > list@host2 actually be called "host1" and "host2" in Mailman, but we have > mail aliases that make list@host1 and list@host2 work, and the appropriate > setting to let Mailman know that list@host1 and list@host2 are appropriate > posting addresses for lists host1 and host2 respectively. > > In our case, it's only the actual posting addresses where we want the same > name, but it wouldn't be too hard to extend this to hide more than just the > one address. > > You could probably do something similar by naming your mailing lists > team1_volleyball and team1_soccer and then setting up the appropriate > mailing aliases so that team1@volleyballclub.dse.nl and > team1@soccerclub.dse.nl work as expected (similarly for > team1-request@volleyballclub.dse.nl, etc.) If you don't like having the > longer urls that'll result, you could also make > http://volleybalclub.dse.nl/mailman/listinfo/team1 equivalent to > http://volleybalclub.dse.nl/mailman/listinfo/team1_volleyball using > mod_rewrite in Apache, or something similar for the webserver of your > choice. > > It's a bit of a hack, though, since, of course, the list itself will still > advertise addresses like team1_volleyball-request@volleyballclub.dse.nl, but > it probably beats multiple installations of Mailman and it's fairly seamless > to your users unless you forget to make some aliases. > > Terri > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers -- ------------------------------------------------------------ Nathan Neulinger EMail: nneul@umr.edu University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 From dag at sonsorol.org Wed Mar 19 10:23:09 2003 From: dag at sonsorol.org (Chris Dagdigian) Date: Wed Mar 19 10:22:43 2003 Subject: [Mailman-Developers] Re: odd problem: since MM 2.1 upgrade all links to public listarchives are broken In-Reply-To: <3E73E433.2090007@sonsorol.org> References: <3E73E433.2090007@sonsorol.org> Message-ID: <3E788B5D.6050605@sonsorol.org> Replying to my own message since the problem has been fixed and I'd like to get the solution into the archives in case any long-time mailman users get bitten by the same bug. We _were_ bitten by cruft hanging around from previous mailman installations :) The culprit was a "mm_cfg.py" file that had not been touched or overwritten by a mailman upgrade install since early 2000. That file contained "old" mailman config settings including this line: PUBLIC_ARCHIVE_URL = '/pipermail' This was what was screwing up the URLs to our archives in the listinfo HTML. It seems that (not sure for how long now) much of this stuff is supposed to be in Mailman/Defaults.py Our solution was to blow away mm_cfg.py and replace it with the generic mm_cfg.py.disg from the mailman 2.1.1 installer. We then edited Mailman/Defaults.py to update our default server name and all is well. -Chris Chris Dagdigian wrote: > > Hi mailman developers, > > First off; thanks for a wonderful package. We've been using Mailman for > years to keep thousands of open source bioinformatics developers and > users in touch with each other. > > Now I've got a problem that seems really odd. I'm a little bit afraid > that it may have been caused by some old cruft left over in our mailman > dir which has been subjected to many mailman upgrade installs over the > years. > > The SMTP/mailman box is a Dec Alpha workstation running Redhat Linux 6.x > with python 2.3. > > > The problem: > > Since upgrading to Mailman 2.1 (problem persists with MM 2.1.1) all of > our mailman list pages that point to the public list archives are broken. > > The URL is presented as "/pipermail/" instead of > "/pipermail//" > > This prevents our web vistors from getting to our list archives as they > are presented with a "you are not allowed to access /pipermail/" error > each time. > > We have not changed our templates at all. In fact I blew away the > templates directory right before upgrading to 2.1.1. I've verified in > the template HTML that the "MM-List-Name" etc. data seems to be in the > right place. > > Here are a couple of example pages with broken links to the public list > archives: > > http://bioperl.org/mailman/listinfo/bioperl-l > http://open-bio.org/mailman/listinfo/moby-l > > The list name is obviously getting substituted into other parts of the > page. It's just not getting appended to the end of "/pipermail/" in the > URL for the public list archive. > > > Private archives work fine. I've taken one list and converted the > archives from public->private and the resulting "listinfo" page then > produces a perfect link to the private archive. > > > Any hints? Has anyone seen this before? > > > Regards, > Chris > > -- Chris Dagdigian, BioTeam Inc. - Independent Bio-IT & Informatics consulting Office: 617-666-6454, Mobile: 617-877-5498, Fax: 425-699-0193 PGP KeyID: 83D4310E Yahoo IM: craffi Web: http://bioteam.net From thomas at xs4all.net Wed Mar 19 17:33:00 2003 From: thomas at xs4all.net (Thomas Wouters) Date: Wed Mar 19 11:44:55 2003 Subject: [Mailman-Developers] Re: odd problem: since MM 2.1 upgrade all links to public listarchives are broken In-Reply-To: <3E788B5D.6050605@sonsorol.org> References: <3E73E433.2090007@sonsorol.org> <3E788B5D.6050605@sonsorol.org> Message-ID: <20030319163300.GE2112@xs4all.nl> On Wed, Mar 19, 2003 at 10:23:09AM -0500, Chris Dagdigian wrote: > Our solution was to blow away mm_cfg.py and replace it with the generic > mm_cfg.py.disg from the mailman 2.1.1 installer. We then edited > Mailman/Defaults.py to update our default server name and all is well. No! You should not edit Defaults.py -- because it will get blown away. You need to edit mm_cfg.py (just add the variables you want to override) because it doesn't get blown away. You should check your mm_cfg.py after major version updates, to make sure the variables you override there still make sense, but this shouldn't be necessary for point releases, and should rarely make a difference for major releases (yours was an unlucky case, it seems. Also, old Mailman wasn't as easily upgradeable as Mailman 2.x :-) -- Thomas Wouters Hi! I'm a .signature virus! copy me into your .signature file to help me spread! From ricardo at rixhq.nu Wed Mar 19 22:55:02 2003 From: ricardo at rixhq.nu (Ricardo Kustner) Date: Wed Mar 19 16:55:06 2003 Subject: [Mailman-Developers] bin/remove_members & userack Message-ID: <3E78E736.6070605@rixhq.nu> Hi, I just noticed that bin/remove_members turns on "userack" by default... even though it's supposed to use the list config setting whether or not it should send a message to the unsubscribers (line 111 in remove_members says "userack = 1"). is this a bug or has this been done intentionally? I just happened to me a second time that I did a mass unsubscription with remove_members (because I had to reload the entire list of addresses on an announce list) and everybody received a message that they were removed again... which caused a lot of confusion :( Regards, Ricardo. From fil at rezo.net Thu Mar 20 12:07:16 2003 From: fil at rezo.net (Fil) Date: Thu Mar 20 06:09:15 2003 Subject: [Mailman-Developers] trailing garbage?? Message-ID: <20030320110716.GF13773@rezo.net> Hi, I've received this for the first time (almost uptodate CVS + email2.5b1 installed) Subject: Cron /usr/local/bin/python -S /usr/local/mailman/cron/senddigests Warning: Trailing garbage Warning: Trailing garbage -- Fil From coen at coachcoen.com Thu Mar 20 16:04:47 2003 From: coen at coachcoen.com (Coen de Groot) Date: Thu Mar 20 11:09:45 2003 Subject: [Mailman-Developers] Paid membership system - feedback? - warning: long Message-ID: Hi there, I will be changing a Mailman discussion list into a paid discussion list. As far as I can tell there isn't anything readily available for this So, unless anyone tells me otherwise, I will have to develop something myself I will be quite happy to make the end result available to anyone else who might find it useful Whilst I have a lot of programming experience, this will be my first Python project, so wish me luck :-) Oh, and I've got about a week or so to get a beta version, so not too much pressure Initially I will be importing the payments from a file which I maintain using different software. At a later stage everything will have to be integrated and automated In case anyone is interested, I have included some documentation of my plans below. Feel free to give me your feedback, especially with ideas on what will be impossible or what can be done better differently. I assume this is the right place for this email (size and subject). If not please let me know, just be gentle :-) See below for my documentation Coen Introduction This is the functional specification for the first phase of the Mailman membership system During phase 1 part of the process will still be done manually and/or by other systems. During a later phase all parts will be integrated and automated The following functions will be part of the system: a.. Maintaining a table of free and paid membership periods for each list member b.. Email renewal reminders c.. Blocking access past the membership period The following change(s) will be required to the existing Mailman system, to facilitate the new functionality: a.. When someone unsubscribes, the details will be stored in a new list of 'previously subscribed' members b.. When someone resubscribes, any periods will be copied from the 'previously subscribed' list c.. When someone resubscribes who is on the 'previously subscribed' list, and there isn't any valid period, they will be treated the same as if they are 'expired' (see below) Area 1 - Membership periods There are three types of membership period: 1.. Trial period 2.. Paid period 3.. Free period Membership periods can be set up as follows: 1.. Batch trial period set up 2.. Batch paid period set up 3.. Batch free period set up 4.. Automatic trial period set up, as a result of subscribing Batch trial period set up A process will read a structured file which lists recent sign ups. For each list member this contains the following information: 1.. Email address 2.. Date of sign up This file will be created by hand, from the sign-up log. Only entries after 7/2/03 will be used. Members who are known to have been a member before 7/2/03 will also be excluded Step 1 - File import The file will be read and each entry will be recorded against the list of members. A period tuple will be added with the period type ('trial'), period start and period end. The period end will be two months minus 1 day after the period start In the case of duplicate entries (against the same email address), the second entry will be ignored and an error message will be generated If the member doesn't exist, then s/he has probably unsubscribed since, so generate an error message and ignore Step 2 - Default setting All other members, those who don't yet have a trial membership period will be given a trial period which ends 6th April 2003. A period tuple will be added with the type period ('trial'), period start (empty) and period end (6/4/03) Log A log will be created which lists all period which were created, showing the email address, start date, end date, period type Batch paid period set up A process will read a structured file which lists payments. For each entry this contains the following information: 1.. List email address 2.. Period in months (typically 12, but might be 13 for anyone who ended up paying a little extra) This file will be created by hand For each member which is listed, a period tuple will be added with the period type ('paid'), start date (the day after the end of the trial period), end date (the specified number of months after the start date, minus 1 day) Log A log will be created which lists all period which were created, showing the email address, start date, end date, period type Batch free period set up A process will read a structured file which lists free periods. For each entry this contains the following information: 1.. List email address 2.. Period in months, or 0 for unlimited 3.. Type of free period ('benefit' or 'gift') Log A log will be created which lists all period which were created, showing the email address, start date, end date, period type Automatic trial set up, after subscribing When someone subscribes who hasn't subscribed before (i.e. there isn't already an entry for this email address), the system automatically gives them a 2 month trial period. This will be done as part of the normal subscribe function, for subscriptions via the website and via email Area 2 - Email renewal reminders Note: the standard welcome message will be changed to explain the trial period The following emails may be sent out by the system: 1.. 1 month after start of trial membership, if not yet paid, encouragement to pay, plus info on how to get the most from the list. Don't send if more than 3 days overdue. The wording of the email will allow for slightly late sending 2.. 2 weeks before end of trial membership, if not yet paid, reminder of end of trial period. Don't send if more than 2 days overdue. The wording of the email will allow for slightly late sending 3.. 3 days before end of trial membership, if not yet paid, final warning. Don't send if more than 1 day overdue. The wording of the email will allow for slightly late sending A daily process will be run which checks for messages that need to be sent Sent messages are recorded by adding a tuple to the list member, recording date and type of message). This is to prevent messages being sent twice Area 3 - Blocking access A daily process will check for any members whose membership has just expired. As far as the system is concerned, any member who does not have a membership period which covers today is 'expired' Any member which has become 'expired' today will be sent an email with notification of removal and information about any free options. And an 'expired' flag will be set No messages will be sent to 'expired' members: 1. The member will stop receiving direct list emails 2. The member will stop receiving digest emails 3. The member will stop receiving monthly password reminders 4. The member will stop receiving admin messages No email requests will be processed from 'expired' members 5. The member will not be able to send messages to the list, from the main email address and from any additional posting addresses 6. The member will not be able to change options by email 7. The member will not be able to subscribe again by email 'Expired' members will not be able to make any changes via the website interface: 8. The member will not be able to access the management screen 9. The member will not be able to subscribe again (at least not with any known email address) via the website No more direct list emails When building the distribution list for direct emails, 'expired' members will be excluded No more digest list emails When building the distribution list for digest emails, 'expired' members will be excluded No more monthly password reminder emails 'Expired' members won't be send monthly password reminder emails No more admin emails The list has a facility for 'direct' emails, which go directly to normal members and to digest members. When building the distribution list for 'direct' emails, 'expired' members will be excluded No more sending emails to the list When an email gets sent to the list from an 'expired' member, the list will discard the message and return a friendly reply to the member, explaining how his/her membership has expired, at what date, and what they can do about this No access to management screen When an 'expired' member goes to the management screen, they will see a very simple screen which explains the expired status and what they can do about it Can't change options via email When an 'expired' member tries to change options via email, they will receive a friendly reply which explains that their membership is expired, at what date, and what they can do about this Can't resubscribe via the website When an 'expired' member tries to resubscribe via the website they will see a screen which explains the expired status and what they can do about it Can't resubscribe via email When an 'expired' member tries to resubscribe via email they will receive a friendly reply which explains that their membership is expired, at what date, and what they can do about this From lj at mandala-designs.com Thu Mar 20 18:04:28 2003 From: lj at mandala-designs.com (ljacobs ) Date: Thu Mar 20 18:04:32 2003 Subject: [Mailman-Developers] Is there a solution to this error log output? Message-ID: <200303201804.AA24969382@mandala-designs.com> Python 2.2.2, RedHat 7.1, Mailman 2.1. Since upgrading to Postfix 2.0.6 (although that may be unrelated to this problem) I have been unable to post to my Mailman 2.1 moderated lists. (I never had this problem before.) The "vette" file responds properly with the "held" message and then the "approved" flag gets added as I approve the posting. However the "post" file never gets updated and the message gets shunted. The error log has this: Mar 20 17:32:37 2003 (18803) Uncaught runner exception: [Errno 4] Interrupted system call Mar 20 17:32:37 2003 (18803) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 139, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 335, in bulkdeliver refused = conn.sendmail(envsender, recips, msgtext) File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 61, in sendmail results = self.__conn.sendmail(envsender, recips, msgtext) File "/usr/local/lib/python2.2/smtplib.py", line 675, in sendmail (code,resp)=self.rcpt(each, rcpt_options) File "/usr/local/lib/python2.2/smtplib.py", line 459, in rcpt return self.getreply() File "/usr/local/lib/python2.2/smtplib.py", line 332, in getreply line = self.file.readline() Mar 20 17:32:37 2003 (18803) SHUNTING: 1048199310.616835+b29ca3709ff2c999169ceb1c0e1462215c6b2723 Is this a known bug or where should I look? Thanks. ________________________________________________________________ Sent via the WebMessaging system at mandala-designs.com From colin at mackinlay.demon.co.uk Thu Mar 20 23:34:45 2003 From: colin at mackinlay.demon.co.uk (Colin Mackinlay) Date: Thu Mar 20 18:36:54 2003 Subject: [Mailman-Developers] list_members output Message-ID: Hi, Just used the FAQ script to harvest members for umbrella lists - worked perfectly. One minor improvement would be useful: if the list_members command also outputs the name as well as email address in a format that sync_members could cope with then the membership listing of the umbrella list would be much easier to read. i.e. couldn't it output: Name Label ...etc as this format is acceptable on the mass subscription page. -- Colin Mackinlay From barry at python.org Fri Mar 21 23:55:43 2003 From: barry at python.org (Barry Warsaw) Date: Fri Mar 21 23:55:47 2003 Subject: [Mailman-Developers] Is there a solution to this error log output? In-Reply-To: <200303201804.AA24969382@mandala-designs.com> References: <200303201804.AA24969382@mandala-designs.com> Message-ID: <1048308943.18881.10.camel@geddy> On Thu, 2003-03-20 at 18:04, ljacobs wrote: > Python 2.2.2, RedHat 7.1, Mailman 2.1. > > Since upgrading to Postfix 2.0.6 (although that may be unrelated to this problem) I have been unable to post to my Mailman 2.1 moderated lists. (I never had this problem before.) The "vette" file responds properly with the "held" message and then the "approved" flag gets added as I approve the posting. However the "post" file never gets updated and the message gets shunted. The error log has this: It's probably not related to Postfix 2.0.6 per se, but it probably is related to the upgrade (something got misconfigured). > Mar 20 17:32:37 2003 (18803) Uncaught runner exception: [Errno 4] Interrupted system call Mailman is having trouble talking to your local Postfix process via port 25 socket. Look in your Postfix logs to see if there are any clues there. -Barry From barry at python.org Sat Mar 22 09:38:14 2003 From: barry at python.org (Barry Warsaw) Date: Sat Mar 22 09:38:45 2003 Subject: [Mailman-Developers] Re: [Mailman-checkins] mailman/Mailman ListAdmin.py,2.42,2.43 In-Reply-To: <20030321083014.GD17342@xs4all.nl> References: <1048219349.5204.5.camel@geddy> <20030321083014.GD17342@xs4all.nl> Message-ID: <1048343894.2346.6.camel@anthem> Redirecting here from mailman-checkins... On Fri, 2003-03-21 at 03:30, Thomas Wouters wrote: > On Thu, Mar 20, 2003 at 11:02:29PM -0500, Barry Warsaw wrote: > > On Wed, 2003-03-19 at 19:31, twouters@users.sourceforge.net wrote: > > > > Fix another of Peer's annoying bugs: somehow his next_request_id ended up > > > lower than the highest entry in the list config.db, so the assertion was > > > being triggered. We can just deal with the problem instead. > > > Very strange! Does this (and Peer's other problems) make us question > > the integrity of the LockFile algorithm? > > Yes, I'm going to setup a LockFile stresstest when I get a moment (which > will probably not be in the next three weeks, unfortunately.) Note that at the bottom of LockFile.py there's an attempt at a stress test. It would be good to code review this to make sure it's testing what we think it should test and what it ought to test . It's also never been really run in an NFS environment. I don't know if Peer's using NFS, but if so that would be the first place I'd suspect. -Barry From barry at python.org Sat Mar 22 10:50:40 2003 From: barry at python.org (Barry Warsaw) Date: Sat Mar 22 10:50:44 2003 Subject: [Mailman-Developers] bin/remove_members & userack In-Reply-To: <3E78E736.6070605@rixhq.nu> References: <3E78E736.6070605@rixhq.nu> Message-ID: <1048348240.18777.49.camel@geddy> On Wed, 2003-03-19 at 16:55, Ricardo Kustner wrote: > I just noticed that bin/remove_members turns on "userack" by default... > even though it's supposed to use the list config setting Fixed in cvs. -Barry From maechler at stat.math.ethz.ch Mon Mar 24 11:09:58 2003 From: maechler at stat.math.ethz.ch (Martin Maechler) Date: Mon Mar 24 05:10:08 2003 Subject: [Mailman-Developers] MM 2.1.1: another uncaught bounce that should have been caught Message-ID: <15998.55670.616747.307636@gargle.gargle.HOWL> Dear developers, thank you very much for an already fantastic product! I hope the following is helpful for improving this part of mailman... Martin Maechler http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <>< -------------- next part -------------- An embedded message was scrubbed... From: mailman-bounces@stat.math.ethz.ch Subject: Uncaught bounce notification Date: Fri, 21 Mar 2003 21:35:22 +0100 Size: 1870 Url: http://mail.python.org/pipermail/mailman-developers/attachments/20030324/40850740/attachment.eml From maechler at stat.math.ethz.ch Tue Mar 25 17:56:48 2003 From: maechler at stat.math.ethz.ch (Martin Maechler) Date: Tue Mar 25 11:57:04 2003 Subject: [Mailman-Developers] Another "uncaught bounce" that should have been Message-ID: <16000.35408.318069.823574@gargle.gargle.HOWL> {Mailman 2.1.1} I hope this continues to help improving the already good mailman software! Martin -------------- next part -------------- An embedded message was scrubbed... From: mailman-bounces@stat.math.ethz.ch Subject: Uncaught bounce notification Date: Tue, 25 Mar 2003 12:13:26 +0100 Size: 72016 Url: http://mail.python.org/pipermail/mailman-developers/attachments/20030325/3fd79788/attachment-0001.eml From lj at mandala-designs.com Fri Mar 28 08:51:21 2003 From: lj at mandala-designs.com (ljacobs ) Date: Fri Mar 28 08:51:30 2003 Subject: [Mailman-Developers] Problems mailing to the list Message-ID: <200303280851.AA42730214@mandala-designs.com> Folks -- Somehow this bogus address got entered into one of my lists. It was not obvious that this individual had entered this address or that it was being stored incorrectly, but while trying to understand why I was having problems with this list, I discovered this address, with quotes & all: "pgyallay"@keap@fone.net I have since deleted this address. Now in the error file, when I was attempting to mail to this moderator-only list, I would get the following: Mar 27 16:36:56 2003 (27183) Uncaught runner exception: Mar 27 16:36:56 2003 (27183) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 129, in _dispose status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 152, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 212, in process raise Errors.SomeRecipientsFailed(tempfailures, permfailures) SomeRecipientsFailed Mar 27 16:36:56 2003 (27183) SHUNTING: 1041577349.329875+47c1c7b9cd44c3e755ed5dc3549ab225ed1a848f I do not understand the python error message, but does it seem like this error might be related to the attempt to mail the bogus address? And is it possible that having this address wedged in my list would prevent other members to receive emails from ths list? That does appear to be the symptom, i.e., a very small number of subscribers received my last few mailings, and in fact when investigating the config.db with dumpb.db, it looked like most of the subscribers addressed had been flagged as bounced! I then tried to remove all members from the list, but the remove_members command failed to remove all the members even though they all received a remove message! I had forgotten to change the "do not email the members when removed/unsubscribed"! I understand there is a version of Mailman that prevents future subscriptions with bogus addresses, but does anyone think my problem with not being able to send messages to the entire list (8,600 members) is related to that bad address? Thanks for any help and suggestions. ________________________________________________________________ Sent via the WebMessaging system at mandala-designs.com From jan.kellermann at werk21.de Fri Mar 21 16:09:18 2003 From: jan.kellermann at werk21.de (Jan Kellermann) Date: Sat Mar 29 12:15:27 2003 Subject: [Mailman-Developers] New cvs-version: unshunt gives traceback directly to console. Message-ID: <008501c2efbb$d8d92ef0$0501a8c0@marx> Hi! after updating the cvs & installing i started unshunt. After Unshunt has ended following tracebacks came. it was the first time that I get tracebacks directly to console! it is a new error. I didnt see it before. i hoped that one day the cvs will emtpy my shunt-dir and not produce new errors :( greeting kelly. File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' From john at hdnet.org Sat Mar 22 23:41:01 2003 From: john at hdnet.org (John Kromodimedjo) Date: Sat Mar 29 12:15:29 2003 Subject: [Mailman-Developers] Hi all, Message-ID: <003a01c2f09a$354e9f10$858992cb@PATTHAI> Hi all, I am very new to Mailman. Can one of you direct me to the complete documentation of Mailman?? Thanks. John From Donal.Hunt at dcu.ie Tue Mar 25 19:14:23 2003 From: Donal.Hunt at dcu.ie (Donal Hunt) Date: Sat Mar 29 12:15:31 2003 Subject: [Mailman-Developers] Another "uncaught bounce" that should have been (Martin Maechler) References: Message-ID: <3E80AA8F.85847451@dcu.ie> The attachment doesn't seem to be available: http://mail.python.org/pipermail/mailman-developers/attachments/20030325/3fd79788/attachment.eml Is there a reason for that? Regards Donal DCU mailman-developers-request@python.org wrote: > > Send Mailman-Developers mailing list submissions to > mailman-developers@python.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/mailman-developers > or, via email, send a message with subject or body 'help' to > mailman-developers-request@python.org > > You can reach the person managing the list at > mailman-developers-owner@python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mailman-Developers digest..." > > ------------------------------------------------------------------------ > Today's Topics: > > 1. Another "uncaught bounce" that should have been (Martin Maechler) > > ------------------------------------------------------------------------ > > Subject: [Mailman-Developers] > Another "uncaught bounce" that should have been > Date: Tue, 25 Mar 2003 17:56:48 +0100 > From: Martin Maechler > To: mailman-developers > > {Mailman 2.1.1} > > I hope this continues to help improving the already good mailman > software! > Martin > > -------------- next part -------------- > An embedded message was scrubbed... > From: mailman-bounces@stat.math.ethz.ch > Subject: Uncaught bounce notification > Date: Tue, 25 Mar 2003 12:13:26 +0100 > Size: 72016 > Url: http://mail.python.org/pipermail/mailman-developers/attachments/20030325/3fd79788/attachment.eml > > ------------------------------------------------------------------------ > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From yfeng at whittier.edu Tue Mar 25 16:06:53 2003 From: yfeng at whittier.edu (Feng Jeffrey) Date: Sat Mar 29 12:15:32 2003 Subject: [Mailman-Developers] How to change web appearances on Listinfo, ListAdmin Message-ID: Hi, I've installed Mailman on our server and it works beautifully, but one thing people at our site want is to make the appearance of the index page "listinfo" look similar to the web pages on our site. Is there a way to do that? I found out I can change the appearances of the mail lists by changing the template files. Thanks in advance. Jeffrey ********************************************************************** Jeffrey Y. Feng Computing Services Whittier College Email: yfeng@whittier.edu ********************************************************************** From paul.mansfield at worldpay.com Fri Mar 28 15:54:08 2003 From: paul.mansfield at worldpay.com (Paul Mansfield) Date: Sat Mar 29 12:15:34 2003 Subject: [Mailman-Developers] mailman admin documentation site down? Message-ID: http://staff.imsa.edu/~ckolar/mailman/ is a link on http://www.list.org/docs.html the site appears down, and recent postings to this list don't appear to have said it already. does anyone have a mirror for this? thanks Paul From ckolar at imsa.edu Sat Mar 29 13:42:09 2003 From: ckolar at imsa.edu (Christopher Kolar) Date: Sat Mar 29 14:38:36 2003 Subject: [Mailman-Developers] mailman admin documentation site down? In-Reply-To: References: Message-ID: <3E85F711.6000309@imsa.edu> Paul Mansfield wrote: >http://staff.imsa.edu/~ckolar/mailman/ > >is a link on http://www.list.org/docs.html > >the site appears down, and recent postings to this list don't appear to have >said it already. > >does anyone have a mirror for this? > >thanks >Paul > > Our network was brought down Friday and again for a short time this morning (Saturday). Should be back to normal now. --chris From sb.list at sb.org Sat Mar 29 14:49:33 2003 From: sb.list at sb.org (Stonewall Ballard) Date: Sat Mar 29 14:53:36 2003 Subject: [Mailman-Developers] Confirm address change always returns error Message-ID: In 2.1.1+ (confirmed with a fresh CVS build today), when a user replies to a confirmation message sent by Mailman in response to an email address change (on the web page), Mailman changes the address, but replies with an error (below). This confuses users. The subscribe log has entries for the new address as "pending", then as "new", with no errors or apparent problems. It seems odd to me that this hasn't been reported as a bug, since it appears to have been around for several months, at least. Or is there something broken in my Mailman installation? I'm on OS X Server 10.2.4. BTW, note the typo "you are not current a member". TIA for any help. - Stoney > The results of your email command are provided below. Attached is your > original message. > > - Results: > You are not current a member. Have you already unsubscribed or changed > your email address? > > - Unprocessed: > On 3/29/03 2:32 PM, "savannounce-request@lists.sudburysavoyards.org" > wrote: >> Mailing list subscription confirmation notice for mailing list >> SavAnnounce >> >> We have received a request for subscription of your email address, >> "abc@stonetics.com", to the savannounce@lists.sudburysavoyards.org >> mailing list. To confirm that you want to be added to this mailing >> list, simply reply to this message, keeping the Subject: header >> intact. Or visit this web page: >> >> >> http://lists.sudburysavoyards.org/mailman/confirm/savannounce/df640af0ac9e917>> f >> 5df1b2a2b1caea98bfa55e1d >> >> >> Or include the following line -- and only the following line -- in a >> message to savannounce-request@lists.sudburysavoyards.org: >> >> confirm df640af0ac9e917f5df1b2a2b1caea98bfa55e1d >> >> Note that simply sending a `reply' to this message should work from >> most mail readers, since that usually leaves the Subject: line in the >> right form (additional "Re:" text in the Subject: is okay). > > - Ignored: >> >> If you do not wish to be subscribed from this list, please simply >> disregard this message. If you think you are being maliciously >> subscribed to the list, or have any other questions, send them to >> savannounce-owner@lists.sudburysavoyards.org. -- Stonewall Ballard stoney@sb.org http://stoney.sb.org/ From mrbill at mrbill.net Sat Mar 29 15:55:15 2003 From: mrbill at mrbill.net (Bill Bradford) Date: Sat Mar 29 16:55:19 2003 Subject: [Mailman-Developers] still having admin cookie problem Message-ID: <20030329215515.GN13285@mrbill.net> I'm running MM 2.1.1, and am *still* seeing the admin cookie problem - when I go to accept/discard posts that were held for moderation, select the option for each one, then hit submit - it then takes me *back* to the password entry screen, I have to enter the admin password *again*, and then do it all over and hit submit a second time before it will take effect. This has been tested and happens even with new installations of browsers that have *no* cookies stored. Suggestions? Bill -- bill bradford mrbill@mrbill.net austin, texas