Mailman 3 July 2002 - Mailman-Developers

Some issues with the CVS head
by Ross Boylan 30 Jul '02

30 Jul '02

I just got the latest Mailman sources from CVS, and noticed a couple of things. 1) Required Python Version Some of the modules (e.g., DNS.py) require Python 2.2 (e.g., reference to email modules). Yet the readme says Python 2.1.3 or greater is required. The wiki http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage says Python 2.0 will be required. This is of particular concern for me because I'm thinking of borrowing some parts for a Zope product, and Zope 2.5 uses Python 2.1 and reportedly will not work with 2.2. This is, of course, not a good reason for Mailman to stay on Python 2.1. I'm aware of the ZMailman project and sent a message to their list. However, what I'm doing probably goes in a different direction (I really just want the Bounce handling). 2) Code Inconsistencies Bouncer uses getBounceInfo. MemberAdaptor implements this (as well as OldMemberAdaptor), but MailingList doesn't inherit from it. So it looks as if everything is not quite hooked up yet. 3) A Stylistic Comment I also find it a little weird to see base classes making calls to methods that they don't define or inherit from, on the assumption that they will be mixed into something that does define them. It seems to me if this could be avoided, or at least if the classes could inherit from the classes with the relevant protocols, it would be cleaner. A lower tech approach would be to note the dependencies in class comments. But I think the inheritance might make the dependencies explicit while still preserving the ability to factor out chunks of functionality. 4) A Little Python Question Could anyone explain to me what this is doing? (e.g. from DNS.py) return filter(None, addrs) There are several uses of this filter(None,..) idiom in the code. The 2.0 code even says return filter(None, addrs) or None The docs for filter say the first argument should be a function, which None is not. When I try it, it seems to be a noop (i.e., filter(None, foo) == foo). And or'ing with None (false) also seems pointless.

2 1

Re: [Mailman-Developers] Cute TMDA use
by J C Lawrence 29 Jul '02

29 Jul '02

On Mon, 29 Jul 2002 16:48:30 -0700 Chuq Von Rospach <chuqui(a)plaidworks.com> wrote: > On 7/29/02 4:31 PM, "Barry A. Warsaw" <barry(a)python.org> wrote: >> I guess if the default moderation bit is set, then we wouldn't send >> out the confirmation message, and non-member postings would have to >> be approved just like they are today. > I would set things up so that they don't go into the moderation queue > until they're confirmed, and then moderated as normal. The moderator > stuff doesn't change, except that the moderator doesn't see them until > the user confirms them. That closes the hole of the moderator having > to deal with spam to the posting address. So basically, you put TMDA > in front of the moderator, not replace the moderator in that case. The > list is still moderated, just whitelisted THEN moderated. Precisely. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

Make clobber_date default and configurable
by Krischan Jodies 29 Jul '02

29 Jul '02

The default for clobber_date is "set time in archive to time of the date header of e-mail". I think the better default is to set the time to the resent time. At least this default should be configurable in mm_conf.py. Thanks, Krischan -- Service Network GmbH, mailto:kjodies@SerNet.DE, http://www.SerNet.DE phone: +49-551-370000-0, fax: +49-551-370000-9

2 1

[ mailman-Patches-564747 ] Makes "powered by" icons into links
by noreply＠sourceforge.net 29 Jul '02

29 Jul '02

Patches item #564747, was opened at 2002-06-05 03:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=564747&group_i… Category: Web UI Group: Mailman 2.0.x >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: W Isaac Carroll (zaak) Assigned to: Nobody/Anonymous (nobody) >Summary: Makes "powered by" icons into links Initial Comment: This makes the Mailman, Python, and GNU icons at the bottom of the web UI pages into links to their respective web sites. There are already links if mm_cfg.IMAGE_LOGOS is false. This patch simply makes the graphical version have the links as well. Patch against version 2.0.9 ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-29 18:29 Message: Logged In: YES user_id=12800 I'm rejecting this patch (actually without looking at the details -- sorry), because we've had too many complaints about these logos being hyperlinked. I'm actually disabling the links altogether. The problem is that the GNU, Python, and Mailman folks get way too many unrelated requests for unsubscription or other membership issues, just because frustrated people will click on anything to get their issue resolved. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=564747&group_i…

1 0

[ mailman-Bugs-588222 ] Downgrade detected on 2.0.13 "upgrade"?
by noreply＠sourceforge.net 29 Jul '02

29 Jul '02

Bugs item #588222, was opened at 2002-07-29 15:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=588222&group_i… Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Paul Marshall (paulmarshll) Assigned to: Nobody/Anonymous (nobody) >Summary: Downgrade detected on 2.0.13 "upgrade"? Initial Comment: I am running Red Hat 7.3, Python 1.5.2, and Mailman 2.1b2. When I try to install Mailman 2.0.13 the ./configure works, however on the make install it begins working then errors out: Downgrade detected, from version 0x20100b2 to version 0x2000df0 This is probably not safe. Exiting. Now that it has done this I am unable to start Mailman up. Another person working on the system may have upgraded to Python 2.2 however, according to Barry Warsaw, newer versions of python should work just fine. Thanks for the help. Paul Marshall ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-29 16:52 Message: Logged In: YES user_id=12800 Um, Mailman 2.1b2 is "newer" than Mailman 2.0.13 so this is indeed a downgrade. The patch has no relevance to Mailman 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=588222&group_i…

1 0

[ mailman-Bugs-588222 ] Downgrade detected on 2.0.13 "upgrade"?
by noreply＠sourceforge.net 29 Jul '02

29 Jul '02

Bugs item #588222, was opened at 2002-07-29 14:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=588222&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Paul Marshall (paulmarshll) Assigned to: Nobody/Anonymous (nobody) Summary: Downgrade detected on 2.0.13 "upgrade"? Initial Comment: I am running Red Hat 7.3, Python 1.5.2, and Mailman 2.1b2. When I try to install Mailman 2.0.13 the ./configure works, however on the make install it begins working then errors out: Downgrade detected, from version 0x20100b2 to version 0x2000df0 This is probably not safe. Exiting. Now that it has done this I am unable to start Mailman up. Another person working on the system may have upgraded to Python 2.2 however, according to Barry Warsaw, newer versions of python should work just fine. Thanks for the help. Paul Marshall ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=588222&group_i…

1 0

Re: [Mailman-Developers] Re: Cute TMDA use
by J C Lawrence 29 Jul '02

29 Jul '02

<<tmda-users added to distribution list as this is probably of more interest/topicality there>> On Mon, 29 Jul 2002 10:51:46 -0600 Jason R Mastaler <Jason> wrote: > J C Lawrence <claw(a)kanga.nu> writes: >> There are cases where I don't want this however, and its proving >> rather a bitch to make a non-shared whitelist hang off a shared >> configuration (in my case a shared procmail RC). > I haven't found this to be the case at all, but I'm also driving my > setup with dot-qmail files which makes this sort of thing trivial. I can't comment well in reaction to QMail as I don't and haven't used it. However I suspect that it doesn't solve the problem I'm referencing, as its not MTa based or specific. I have the MTA (currently Exim and Postfix) configured to deliver all Mailman-related messages sent to the system (-owner, -admin, -request, and list posts) to a singe procmail filter (obviously, shared among all lists and aliases). I'm using procmail as I'm also doing MIME filtering and other pre-processing of messages before handing them to TMDA or the MLM. To goal is arrive at a configuration where no maintenance or extra/unusual actions are required; of alias files, dot files, TMDA configs, TMDA filters, etc as lists are added and removed from the system, or for the normal running and operation of a list. On the TMDA side what I'd like to arrive at a configuration where: -- blacklists are shared -- each list has an auto-whitelist which is private to that list -- each list authenticates messages sent to it against the appropriate Mailman config.db. -- In validating a message for a given list no files or sources other than the shared blacklist, the private whitelist, and the list-specific roster are checked. Essentially this means a fully private TMDA filter setup for each list (modulo the blacklist, but I'm willing to compromise on that). Choice of TMDA incoming filter can be selected at runtime (argument to tmda-incoming) but I can't compute the contents of the incoming filter at runtime in any regard. Filter rules are single qualifier only. Filter files don't have internal variable replacement logic so that they can rewrite themselves depending on the Sender or similar (thus effectively providing multiple qualifier logic). The base result of these configuration constraints is that I have to write a custom incoming filter for each list, pointing at the appropriate private auto-whitelist, Mailman config etc, each filter identical to every other except for the internal list name references. I'd rather have a single self-adapting incoming filter. What I'd really like is to be able to conditionally nest TMDA filters ala: # Generic access controls from-file ~list/.tmda/lists/blacklist bounce from-file ~list/.tmda/lists/whitelist ok # Custom list specific filters (includes file if exists) #include-if "~list/.tmda/filters/${LISTNAME}" # Generic list-specific filters from-file ~list/.tmda/lists/whitelist.${LISTNAME}.auto ok from-mailman -attr=members ~list/lists/${LISTNAME} ok from-mailman -attr=digest_members ~list/lists/${LISTNAME} ok from ${LISTNAME}-admin(a)kanga.nu ok from ${LISTNAME}-owner(a)kanga.nu ok That way if I should want to add extra constraints, authentication sources, behaviours etc to a given list I can, just by dropping a file in the filters directory. Currently I'm hacking my way around this by having a wrapper shell script which assembles a PID-specific incoming filter in /tmp, calls tmda-filter against it, and then deletes it afterward in cleanup. Ugly, expensive, hackish, but works. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

2 1

RELEASED Mailman 2.0.13
by barry＠zope.com 29 Jul '02

29 Jul '02

I've released Mailman 2.0.13 which fixes some incompatibilties with Python 1.5.2 that crept into Mailman 2.0.12. This also fixes a minor configure incompatibility on Solaris platforms (and possibly others). If you're using Python 1.5.2 with Mailman 2.0.12 you should definitely upgrade. The upgrade is safe if you're using newer Python versions too. See the NEWS file excerpt below. As usual, I've made both full source tarballs and patches available. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to download all the patches and the source tarball. If you decide to install the patches, please do read the release notes first: http://sourceforge.net/project/shownotes.php?release_id=97760 See also: http://www.gnu.org/software/mailman http://www.list.org http://mailman.sf.net Cheers, -Barry -------------------- snip snip -------------------- 2.0.13 (29-Jul-2002) - Fixed some Python 1.5.2 compatibility problems that crept into Mailman 2.0.12. - Fixed some configure script incompatibilities on certain platforms.

1 0

TypeError: list objects are unhashable
by Romek Krisztián 29 Jul '02

29 Jul '02

Hello! I use Python 2.2 and Mailman 2.0.12. I was using my copy of Mailman when I've experienced the following error: Jul 29 18:49:01 2002 qrunner(3629): Traceback (most recent call last): Jul 29 18:49:01 2002 qrunner(3629): File "/var/mailman/Mailman/Archiver/Archiver.py", line 221, in ArchiveMail Jul 29 18:49:01 2002 qrunner(3629): h.processUnixMailbox(f, HyperArch.Article) Jul 29 18:49:01 2002 qrunner(3629): File "/var/mailman/Mailman/Archiver/pipermail.py", line 528, in processUnixMailbox Jul 29 18:49:01 2002 qrunner(3629): self.add_article(a) Jul 29 18:49:01 2002 qrunner(3629): File "/var/mailman/Mailman/Archiver/HyperArch.py", line 917, in add_article Jul 29 18:49:01 2002 qrunner(3629): self._charsets[cs] = self._charsets.get(cs, 0) + 1 Jul 29 18:49:01 2002 qrunner(3629): TypeError: list objects are unhashable Jul 29 18:49:01 2002 (3629) CORRUPT ARCHIVE FOR LIST: listname This was when I sent my message to the list. After that I searched on Google about this problem. Somebody told to delete the pipermail.pck file in the archives directory. Okey, deleted. Next: my message was sent to everybody subscribed to the list, but I didn't find it in the archive list but one html file with numbers in the filename. Can you tell me something about what i am doing wrong and how can i fix this error? Krisztian Romek

1 0

[ mailman-Patches-585643 ] Mailman 2.0.13 candidate patch
by noreply＠sourceforge.net 29 Jul '02

29 Jul '02

Patches item #585643, was opened at 2002-07-23 18:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=585643&group_i… Category: None Group: Mailman 2.0.x >Status: Closed >Resolution: Accepted Priority: 8 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Mailman 2.0.13 candidate patch Initial Comment: Mailman 2.0.12 had compatibility problems with Python 1.5.2. This patch fixes these AFAICT, and a few other small bugs that have cropped up. Note that this is a candidate patch. The actual MM2.0.13 patch may be different. However I would really appreciate folks using Mailman 2.0.12 (especially if you're using Python 1.5.2) to give this patch a try and see if it fixes your problems. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-29 12:17 Message: Logged In: YES user_id=12800 I'm releasing MM2.0.13 today. It will be slightly different than this patch. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-07-25 12:00 Message: Logged In: NO This fixed the problems I'd been having on my Solaris 8 box running Mailman 2.0.12 and Python 1.52. Thanks much. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=585643&group_i…

1 0

Re: [Mailman-Developers] Integrating TMDA (was Re: Cute TMDA use)
by J C Lawrence 29 Jul '02

29 Jul '02

On Sun, 28 Jul 2002 20:49:45 -0600 Jason R Mastaler <Jason> wrote: > On another note, the logical approach IMO is to build this > functionality into Mailman, rather than having to attach TMDA to your > Mailman installation. TMDA includes much more than is relevant for > protecting a mailing list. Given that the TMDA python product carries almost all the needed payload, I wonder if a TMDA-plugin rooted in the TMDA product doesn't make more sense. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

Re: [Mailman-Developers] Re: Cute TMDA use
by J C Lawrence 29 Jul '02

29 Jul '02

On Sun, 28 Jul 2002 20:25:33 -0600 Jason R Mastaler <Jason> wrote: > J C Lawrence <claw(a)kanga.nu> writes: >> No more problems with posters from non-subscribed addresses. They >> have a subscription to _GET_ mail and to define an allowed posting >> address. They can (trivially) define additional allowed posting >> addresses by just posting from them and confirming the post to get on >> the whitelist. > Yup. One thing I also do is share an auto-whitelist among all the > lists on my server. So, if claw(a)kanga.nu confirms his post to > tmda-users, he'll instantly be able to post to tmda-workers as well. > This makes things even more transparent for the end-user, particularly > at sites hosting many lists. True. There are cases where I don't want this however, and its proving rather a bitch to make a non-shared whitelist hang off a shared configuration (in my case a shared procmail RC). -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

Re: [Mailman-Developers] Re: Cute TMDA use
by J C Lawrence 29 Jul '02

29 Jul '02

On Fri, 26 Jul 2002 20:55:31 -0700 J C Lawrence <J> wrote: > Idle thought: While I don't have time to do this right now, is there any interest here in making a developing and testing list configuration under TMDA which re-writes all poster addresses to dated addresses at the list server, and then forwards mail to those addresses back to the original address? There are messy bits in the details of getting that to work, but it could be interesting, not only for harvesting control but for lists where poster anonymity AND the ability to privately email posters are both desired. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

2 1

[ mailman-Bugs-585833 ] Forward posts held for approval
by noreply＠sourceforge.net 27 Jul '02

27 Jul '02

Bugs item #585833, was opened at 2002-07-24 06:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i… Category: mail delivery Group: 2.1 beta >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Ousmane Wilane (wilane) Assigned to: Nobody/Anonymous (nobody) Summary: Forward posts held for approval Initial Comment: FWIW I'm using the current cvs. When I forward a mail which was held for approval to my email address (oversized mail in this case) I get the provided traceback in my logs and the mail in shunt q: ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-27 12:23 Message: Logged In: YES user_id=12800 Cool ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-27 10:29 Message: Logged In: YES user_id=47556 My shunt dir is clean. Thanks a lot. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-26 09:52 Message: Logged In: YES user_id=12800 It was a bogus pickle, probably created during the transition of the email package. The fix is simple: x = msg.get_payload() msg.set_payload([x]) I've attached a fixed message pickle below, substitute that for your .pck and see if that works for you. ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-26 08:15 Message: Logged In: YES user_id=47556 The .pck and .db are attached. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 23:33 Message: Logged In: YES user_id=12800 I'm re-opening this bug report. Can you upload the .pck and .db files for the message that won't unshunt? ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 13:26 Message: Logged In: YES user_id=47556 I swear I did restart it :):) More seriously I stop postfix, apache, mailman before upgrading as outlined in the UPGRADING file ... :) I also did verify that ListAdmin.py 2.39 was checked out This time I'll paste the traceback here (it's thrown in logs/error when I try to unshunt the messages): Jul 24 17:17:25 2002 (30049) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 134, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 307, in bulkdeliver msgtext = msg.as_string() File "/usr/local/mailman/pythonlib/email/Message.py", line 99, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/local/mailman/pythonlib/email/Generator.py", line 81, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 109, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 141, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 283, in _handle_message g.flatten(msg.get_payload(0), unixfrom=0) File "/usr/local/mailman/pythonlib/email/Message.py", line 167, in get_payload raise TypeError, i TypeError: 0 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 11:46 Message: Logged In: YES user_id=12800 Be sure you "mailmanctl restart" :) ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 11:26 Message: Logged In: YES user_id=47556 Oops! After cvs -q up -P -d, The bug stood there with the same traceback. Maybe I'm doing something wrong but don't know what ... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 10:04 Message: Logged In: YES user_id=12800 Fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i…

1 0

[ mailman-Bugs-585833 ] Forward posts held for approval
by noreply＠sourceforge.net 27 Jul '02

27 Jul '02

Bugs item #585833, was opened at 2002-07-24 10:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: Fixed Priority: 5 Submitted By: Ousmane Wilane (wilane) Assigned to: Nobody/Anonymous (nobody) Summary: Forward posts held for approval Initial Comment: FWIW I'm using the current cvs. When I forward a mail which was held for approval to my email address (oversized mail in this case) I get the provided traceback in my logs and the mail in shunt q: ---------------------------------------------------------------------- >Comment By: Ousmane Wilane (wilane) Date: 2002-07-27 14:29 Message: Logged In: YES user_id=47556 My shunt dir is clean. Thanks a lot. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-26 13:52 Message: Logged In: YES user_id=12800 It was a bogus pickle, probably created during the transition of the email package. The fix is simple: x = msg.get_payload() msg.set_payload([x]) I've attached a fixed message pickle below, substitute that for your .pck and see if that works for you. ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-26 12:15 Message: Logged In: YES user_id=47556 The .pck and .db are attached. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-26 03:33 Message: Logged In: YES user_id=12800 I'm re-opening this bug report. Can you upload the .pck and .db files for the message that won't unshunt? ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 17:26 Message: Logged In: YES user_id=47556 I swear I did restart it :):) More seriously I stop postfix, apache, mailman before upgrading as outlined in the UPGRADING file ... :) I also did verify that ListAdmin.py 2.39 was checked out This time I'll paste the traceback here (it's thrown in logs/error when I try to unshunt the messages): Jul 24 17:17:25 2002 (30049) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 134, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 307, in bulkdeliver msgtext = msg.as_string() File "/usr/local/mailman/pythonlib/email/Message.py", line 99, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/local/mailman/pythonlib/email/Generator.py", line 81, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 109, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 141, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 283, in _handle_message g.flatten(msg.get_payload(0), unixfrom=0) File "/usr/local/mailman/pythonlib/email/Message.py", line 167, in get_payload raise TypeError, i TypeError: 0 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 15:46 Message: Logged In: YES user_id=12800 Be sure you "mailmanctl restart" :) ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 15:26 Message: Logged In: YES user_id=47556 Oops! After cvs -q up -P -d, The bug stood there with the same traceback. Maybe I'm doing something wrong but don't know what ... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 14:04 Message: Logged In: YES user_id=12800 Fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i…

1 0

Re: [Mailman-Developers] Re: Cute TMDA use
by J C Lawrence 27 Jul '02

27 Jul '02

On Fri, 26 Jul 2002 20:06:33 -0700 Chuq Von Rospach <chuqui(a)plaidworks.com> wrote: > On 7/26/02 7:10 PM, "J C Lawrence" <claw(a)kanga.nu> wrote: >>> You know, I was kinda noodling in that direction, but I hadn't >>> figured THIS out. Whoof. >> Quite nice isn't it. It effectively abstracts the concepts of >> getting mail from being able to send mail. > Yes, it also change the paradigm of the subscription to meet the > multi-protocol reality we have today. Precisely. I figured you'd grab that bit and disappear over the horizon. > First, most of us are running lists with increasingly complex > distribution systems. JC has built some nice (and complex) ways to > allow reading and posting off the web. Thanks. Its a bit messy on the server side, but trivial from the user/web side. You get a "Reply" link and then a form with a TEXTAREA containing a properly quoted and attributed message you can type into. It even does The Right Thing with In-Reply-To: and References: headers. > I've been increasingly uncomfortable with the "gaza strip" aspect of > running lists. This seems to me a great way to open those gates a bit > -- safely. And build in some understanding that not everyone who's > "subscribed" is in the subscriber lists. You have the archives, and > the gateways, and the extended populations that are effectively > disenfranchised from posting today. This builds a system that > re-enfranchises them with minimal hassle and minimal risk of opening > the door to the bad guys. Aye, its a big step forward for our side in the cold war. > I think it's a great hack to get back to what we WANT lists to act > like, not what we've been slowly forced to turn them into. I've moved my previous mimefilter stuff under procmail, and have thrown TMDA into the loop with it as well (damned trivial actually, tho a bit messy on file-permissions). After a week or so of testing and play I'll post the recipe here and in the FAQ. Idle thought: Some lists have currency requirements. They discuss current events and really only want messages which are, well, current. A possible TMDA address: 1) Configure your MTA to run all outbound mail deliveries thru a filter which calls `tmda-inject` prior to delivery. For details of how I did this under Exim see: http://mla.libertine.org/tmda-users/200207/msg00308.html http://mla.libertine.org/tmda-users/200207/msg00309.html Doing similar under Postfix should be easy but I've not looked into it. 2) Write an outbound filter for TMDA which rewrites all list posts with a Reply-To: to a dated version of the list address. 3) Write a TMDA inbound filter to bounce/discard all list mail sent to a stale dated address. Result: All replies to the list which are "too old" are bounced/dropped. Currency! -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

Re: Cute TMDA use
by J C Lawrence 27 Jul '02

27 Jul '02

Bounced as below. On Fri, 26 Jul 2002 14:36:12 -0700 Chuq Von Rospach <chuqui(a)plaidworks.com> wrote: > Have you sent this to barry? Not yet. Mind if I just bounce the whole message I'm replying to there (and possibly this reply)? > This is GREAT! Thought you might like it. > You know, I was kinda noodling in that direction, but I hadn't figured > THIS out. Whoof. Quite nice isn't it. It effectively abstracts the concepts of getting mail from being able to send mail. You subscribe to be able to get mail from the list (which also inserts same address on the whitelist). The whitelist (which you grow by confirmations) is then the list of addresses which are allowed to post (or reach the moderation interface. Quite distinct. Very 1980s. The TMDA lists are run this way, so I can't claim its original to me. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

2 1

Daily digests and other issues
by Will Galloway 26 Jul '02

26 Jul '02

Hi: I didn't see anything like this in MM-Users, so I hope it's OK to post here. I admin a ~1000 member outdoor activities list hosted at pair.com ("pairlist"), so I don't get to see the gory stuff, just the web interface. The size threshold trigger for daily digests stopped working last year, and I understand unoffically that it was a server loading issue that caused this. The server in question handles several hundred lists. Since our list has quite a bit of time sensitive info, and variable traffic levels, this feature is very important. Is there any change in the handling of this feature in 2.1.x that would reduce the CPU requirements? Or anything that pair can try to clean up their implementation to fix it? Other stuff: Duplicate and frivolous subscriptions are annoying, and a "discard" option for sub. requests would be much appreciated. Awareness of a pre-existing sub. request from the same address should be implemented. Rejection just confuses legitimate (albeit impatient) subscribers, and encourages people who are messing around to keep trying. In the same vein, the ability to modify/eliminate the default rejection message for posts would avoid antagonizing people who need coaching now and then. If true moderation and customization of all the various messages is forthcoming, then that's ideal. Thanks, Will Galloway

1 0

[ mailman-Bugs-585833 ] Forward posts held for approval
by noreply＠sourceforge.net 26 Jul '02

26 Jul '02

Bugs item #585833, was opened at 2002-07-24 06:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: Fixed Priority: 5 Submitted By: Ousmane Wilane (wilane) Assigned to: Nobody/Anonymous (nobody) Summary: Forward posts held for approval Initial Comment: FWIW I'm using the current cvs. When I forward a mail which was held for approval to my email address (oversized mail in this case) I get the provided traceback in my logs and the mail in shunt q: ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-26 09:52 Message: Logged In: YES user_id=12800 It was a bogus pickle, probably created during the transition of the email package. The fix is simple: x = msg.get_payload() msg.set_payload([x]) I've attached a fixed message pickle below, substitute that for your .pck and see if that works for you. ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-26 08:15 Message: Logged In: YES user_id=47556 The .pck and .db are attached. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 23:33 Message: Logged In: YES user_id=12800 I'm re-opening this bug report. Can you upload the .pck and .db files for the message that won't unshunt? ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 13:26 Message: Logged In: YES user_id=47556 I swear I did restart it :):) More seriously I stop postfix, apache, mailman before upgrading as outlined in the UPGRADING file ... :) I also did verify that ListAdmin.py 2.39 was checked out This time I'll paste the traceback here (it's thrown in logs/error when I try to unshunt the messages): Jul 24 17:17:25 2002 (30049) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 134, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 307, in bulkdeliver msgtext = msg.as_string() File "/usr/local/mailman/pythonlib/email/Message.py", line 99, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/local/mailman/pythonlib/email/Generator.py", line 81, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 109, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 141, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 283, in _handle_message g.flatten(msg.get_payload(0), unixfrom=0) File "/usr/local/mailman/pythonlib/email/Message.py", line 167, in get_payload raise TypeError, i TypeError: 0 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 11:46 Message: Logged In: YES user_id=12800 Be sure you "mailmanctl restart" :) ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 11:26 Message: Logged In: YES user_id=47556 Oops! After cvs -q up -P -d, The bug stood there with the same traceback. Maybe I'm doing something wrong but don't know what ... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 10:04 Message: Logged In: YES user_id=12800 Fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i…

1 0

[ mailman-Bugs-585833 ] Forward posts held for approval
by noreply＠sourceforge.net 26 Jul '02

26 Jul '02

Bugs item #585833, was opened at 2002-07-24 10:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: Fixed Priority: 5 Submitted By: Ousmane Wilane (wilane) Assigned to: Nobody/Anonymous (nobody) Summary: Forward posts held for approval Initial Comment: FWIW I'm using the current cvs. When I forward a mail which was held for approval to my email address (oversized mail in this case) I get the provided traceback in my logs and the mail in shunt q: ---------------------------------------------------------------------- >Comment By: Ousmane Wilane (wilane) Date: 2002-07-26 12:15 Message: Logged In: YES user_id=47556 The .pck and .db are attached. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-26 03:33 Message: Logged In: YES user_id=12800 I'm re-opening this bug report. Can you upload the .pck and .db files for the message that won't unshunt? ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 17:26 Message: Logged In: YES user_id=47556 I swear I did restart it :):) More seriously I stop postfix, apache, mailman before upgrading as outlined in the UPGRADING file ... :) I also did verify that ListAdmin.py 2.39 was checked out This time I'll paste the traceback here (it's thrown in logs/error when I try to unshunt the messages): Jul 24 17:17:25 2002 (30049) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 134, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 307, in bulkdeliver msgtext = msg.as_string() File "/usr/local/mailman/pythonlib/email/Message.py", line 99, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/local/mailman/pythonlib/email/Generator.py", line 81, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 109, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 141, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 283, in _handle_message g.flatten(msg.get_payload(0), unixfrom=0) File "/usr/local/mailman/pythonlib/email/Message.py", line 167, in get_payload raise TypeError, i TypeError: 0 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 15:46 Message: Logged In: YES user_id=12800 Be sure you "mailmanctl restart" :) ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 15:26 Message: Logged In: YES user_id=47556 Oops! After cvs -q up -P -d, The bug stood there with the same traceback. Maybe I'm doing something wrong but don't know what ... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 14:04 Message: Logged In: YES user_id=12800 Fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i…

1 0

[ mailman-Bugs-572822 ] real_name attribute not changed
by noreply＠sourceforge.net 26 Jul '02

26 Jul '02

Bugs item #572822, was opened at 2002-06-23 14:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=572822&group_i… Category: configuring/installing Group: 2.0.x >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Christine Charity (ccharity) Assigned to: Nobody/Anonymous (nobody) Summary: real_name attribute not changed Initial Comment: When trying to change the name of a mailing list from MAILINGLISTNAME to mailinglistname (lowercase) the following error is returned: real_name attribute not changed! It must differ from the list's name by case only. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 23:51 Message: Logged In: YES user_id=12800 Works okay for me in MM 2.0.12 and 2.1cvs. Are you sure you didn't accidently add a space to the end of the new name? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=572822&group_i…

1 0

[ mailman-Bugs-574240 ] web ui confirm button placement
by noreply＠sourceforge.net 26 Jul '02

26 Jul '02

Bugs item #574240, was opened at 2002-06-26 15:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=574240&group_i… Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: web ui confirm button placement Initial Comment: Hi. Running 2.1b2 I just did a test subscription via email. When I clicked on the link to confirm the confirmation page came up properly. I am a bit bugged by the UI though. The Confirm button was way off to the left -- right under all of the user informaiton on the screen was the "dismiss and discard" button (or whatever it was labeled). After checking the info on the screen I very nearly hit the button because I could not see the real confirm burron and the discard button, being placed right under the info, seemed to instinctively be a good place for a confirm button. I would change the UI to at least get both of them in the center. Cheers, --chris ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 23:49 Message: Logged In: YES user_id=12800 Done. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=574240&group_i…

1 0

Mm documentation server change
by Christopher Kolar 26 Jul '02

26 Jul '02

IMSA will be making some significant server changes this weekend, changes that will impact the location of the Mailman documents that we host. The new URL will be: http://staff.imsa.edu/~ckolar/mailman The pages will no longer be hosted on www.imsa.edu. There will be NO URL FORWARDING when the change is made this Saturday morning, so please change links as necessary. I will try to sort through the logs and pull out the URLs of people linking in to try to contact them personally, but if you maintain a page with a link and are reading this note please take appropriate action. Sorry about the short notice on this, I just found out myself. --chris /////\\\\\/////\\\\\ Christopher G. Kolar Coordinator of Information Technology Integration Illinois Mathematics and Science Academy ckolar(a)imsa.edu -- www.imsa.edu/~ckolar -- PGP Public Key ID: 0xC6492C72 Information literacy news, tools, and programs: <mailto:infoliteracy-subscribe@iti.cnsnet.imsa.edu>infoliteracy-subscribe(a)iti.cnsnet.imsa.<mailto:infoliteracy-subscribe@iti.cnsnet.imsa.edu>edu

2 1

Re: [Mailman-Developers] Modifying mailman to filter archived messages
by Laurence Berland 26 Jul '02

26 Jul '02

On Wednesday 24 July 2002 12:39 pm, Barry A. Warsaw wrote: > >>>>> "LB" == Laurence Berland <laurence(a)digitalpulp.com> writes: > LB> Just to clarify, body=msg.get_payload() sets body to the msg > LB> payload, and msg.set_payload(body) sets the msg payload to > LB> body, right? > > Basically, yes, as long as (in the set_payload() situation) you've got > a text/plain message. Whether to use set_payload() or attach() > depends on whether the container is multipart or not. Ouch-I guess I missed this little detail. I'm trying to get an idea of how best to do this. Does this work? (easier in pcode than english): if not msg.is_multipart and msg_type=="text/plain": bod=msg.get_payload() <do transform on bod> msg.set_payload(bod) elif msg.get_type() == 'multipart/mixed': for part in msg.walk() if part_type == "text/plain": bod=part.get_payload() <do transform on bod> part.set_payload(bod) I've sort of cobbled this together on the fly here, so if it's totally off please forgive my ignorance, stupidity, lack of sleep, etc... Laurence

2 1

[ mailman-Bugs-585833 ] Forward posts held for approval
by noreply＠sourceforge.net 26 Jul '02

26 Jul '02

Bugs item #585833, was opened at 2002-07-24 06:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i… Category: mail delivery Group: 2.1 beta >Status: Open Resolution: Fixed Priority: 5 Submitted By: Ousmane Wilane (wilane) Assigned to: Nobody/Anonymous (nobody) Summary: Forward posts held for approval Initial Comment: FWIW I'm using the current cvs. When I forward a mail which was held for approval to my email address (oversized mail in this case) I get the provided traceback in my logs and the mail in shunt q: ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 23:33 Message: Logged In: YES user_id=12800 I'm re-opening this bug report. Can you upload the .pck and .db files for the message that won't unshunt? ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 13:26 Message: Logged In: YES user_id=47556 I swear I did restart it :):) More seriously I stop postfix, apache, mailman before upgrading as outlined in the UPGRADING file ... :) I also did verify that ListAdmin.py 2.39 was checked out This time I'll paste the traceback here (it's thrown in logs/error when I try to unshunt the messages): Jul 24 17:17:25 2002 (30049) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 134, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 307, in bulkdeliver msgtext = msg.as_string() File "/usr/local/mailman/pythonlib/email/Message.py", line 99, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/local/mailman/pythonlib/email/Generator.py", line 81, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 109, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 141, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 283, in _handle_message g.flatten(msg.get_payload(0), unixfrom=0) File "/usr/local/mailman/pythonlib/email/Message.py", line 167, in get_payload raise TypeError, i TypeError: 0 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 11:46 Message: Logged In: YES user_id=12800 Be sure you "mailmanctl restart" :) ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 11:26 Message: Logged In: YES user_id=47556 Oops! After cvs -q up -P -d, The bug stood there with the same traceback. Maybe I'm doing something wrong but don't know what ... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 10:04 Message: Logged In: YES user_id=12800 Fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i…

1 0

Mailman-Developers July 2002