From noreply at sourceforge.net Sat May 1 06:57:58 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat May 1 06:58:02 2004 Subject: [ mailman-Patches-502668 ] new mlist option send_reminder_frequency Message-ID: Patches item #502668, was opened at 2002-01-12 13:11 Message generated for change (Comment added) made by doko You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=502668&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Matthias Klose (doko) Assigned to: Nobody/Anonymous (nobody) Summary: new mlist option send_reminder_frequency Initial Comment: For announcement mailing lists, which get only one or two mails each year, a monthly password reminder is too much. The list administrator can toggle the send_reminder once each year, but that's error prone. The attached patch adds a list specific option send_reminder_frequency with the values monthly (default), yearly and quaterly. the mailpasswds script is changed to ask for this option. I didn't yet figure out, how to update existing lists ... ---------------------------------------------------------------------- >Comment By: Matthias Klose (doko) Date: 2004-05-01 10:57 Message: Logged In: YES user_id=60903 updated patch for mailman-2.1.4 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-19 01:09 Message: Logged In: YES user_id=12800 Postponing until after MM2.1 ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2002-08-09 21:57 Message: Logged In: YES user_id=60903 Updated patch for the alternative (not introducing a new option, but extending the send_reminders option (updated to current CVS). ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2002-05-28 06:11 Message: Logged In: YES user_id=60903 Here is the updated alternative patch not introducing a new option, but extending the send_reminders option (updated to current CVS). ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2002-01-16 20:08 Message: Logged In: YES user_id=60903 Here is an alternative patch not introducing a new option, but extending the send_reminders option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=502668&group_id=103 From noreply at sourceforge.net Sun May 2 15:20:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun May 2 15:20:56 2004 Subject: [ mailman-Patches-946554 ] configure does not check for gettext/msgmerge Message-ID: Patches item #946554, was opened at 2004-05-02 21:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=946554&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: O.S. (olaf) Assigned to: Nobody/Anonymous (nobody) Summary: configure does not check for gettext/msgmerge Initial Comment: configure does not check for gettext/msgmerge, but when building with make it beaks. Mailman version 2.1.4 system: Debian stable/testing 3.0r2/3.1 python version: 2.3.3 architecture: intel-i386 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=946554&group_id=103 From noreply at sourceforge.net Tue May 4 18:39:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 4 18:39:21 2004 Subject: [ mailman-Bugs-948064 ] email address will slashes Message-ID: Bugs item #948064, was opened at 2004-05-04 12:39 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=948064&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael (ciberous) Assigned to: Nobody/Anonymous (nobody) Summary: email address will slashes Initial Comment: The mailing list login/(un)subscribe form does not accept email addresses with slashes in the name. In particular, the user has a LotusNotes email address which contains slashes. For example, an email address such as foo_bar/myschool/mydoe@notes.k12.hi.us will not be accepted by the form. It responds that the email address is illegal. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=948064&group_id=103 From noreply at sourceforge.net Tue May 4 21:57:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 4 21:57:19 2004 Subject: [ mailman-Bugs-948152 ] Out of date link on Docs webpage Message-ID: Bugs item #948152, was opened at 2004-05-05 01:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=948152&group_id=103 Category: documentation Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: quetza (user99) Assigned to: Nobody/Anonymous (nobody) Summary: Out of date link on Docs webpage Initial Comment: On http://www.list.org/docs.html there is a link to "HOWTO on using Exim and Mailman" (http://www.exim.org/howto/mailman.html) This refers to an old version of Exim (and mailman). The link should be: http://www.exim.org/howto/mailman21.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=948152&group_id=103 From noreply at sourceforge.net Tue May 4 22:03:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 4 22:03:39 2004 Subject: [ mailman-Patches-795012 ] show_qfiles script to dump qfiles/*/*.pck Message-ID: Patches item #795012, was opened at 2003-08-25 19:55 Message generated for change (Comment added) made by gward You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=795012&group_id=103 Category: command line scripts Group: Mailman 2.1 >Status: Closed Resolution: Accepted Priority: 5 Submitted By: Greg Ward (gward) Assigned to: Nobody/Anonymous (nobody) Summary: show_qfiles script to dump qfiles/*/*.pck Initial Comment: The attached script takes a list of filenames from the qfiles tree on the command line, and dumps each one. Handy when queued messages are pickles rather than plain text, and it presents the same UI in both cases. ---------------------------------------------------------------------- >Comment By: Greg Ward (gward) Date: 2004-05-04 22:03 Message: Logged In: YES user_id=14422 Barry, I think you forgot to close this one. Let's see if SF will let me do it. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-25 21:40 Message: Logged In: YES user_id=12800 Nice! Now, do you want to copyright assign to the FSF so I can add it to the distro? :) ---------------------------------------------------------------------- Comment By: Greg Ward (gward) Date: 2003-08-25 19:57 Message: Logged In: YES user_id=14422 oops, this time I'll actually check the stupid "upload" checkbox... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=795012&group_id=103 From noreply at sourceforge.net Thu May 6 08:16:30 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 6 08:16:33 2004 Subject: [ mailman-Bugs-949117 ] 2.1.5rc2 upgrade dies on corrupt qfiles Message-ID: Bugs item #949117, was opened at 2004-05-06 05:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=949117&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Brion Vibber (vibber) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.5rc2 upgrade dies on corrupt qfiles Initial Comment: Upgrading from 2.1.2 to 2.1.5rc2; a couple of the .pck files in qfiles/shunt were zero-length for reasons unknown. This caused the upgrade (make install) to fail with this message: updating old qfiles Traceback (most recent call last): File "bin/update", line 780, in ? errors = main() File "bin/update", line 709, in main update_qfiles() File "bin/update", line 441, in update_qfiles msg, data = dequeue(filebase) File "bin/update", line 497, in dequeue msg = cPickle.load(msgfp) EOFError make: *** [update] Error 1 Removing the zero-length files cleared that up. I did have one other problem; while investigating the first bit I dumped some info to a text file in qfiles, and the next make install failed with this error: updating old qfiles Traceback (most recent call last): File "bin/update", line 780, in ? errors = main() File "bin/update", line 709, in main update_qfiles() File "bin/update", line 434, in update_qfiles for filename in os.listdir(dirpath): OSError: [Errno 20] Not a directory: '/home/mailman/qfiles/blork' make: *** [update] Error 1 At least that had the filename in it. ;) Removed the file, and it installed/upgraded cleanly. So far so good... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=949117&group_id=103 From noreply at sourceforge.net Thu May 6 11:00:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 6 11:00:51 2004 Subject: [ mailman-Bugs-949244 ] Moderator Allowed to Post Message-ID: Bugs item #949244, was opened at 2004-05-06 15:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=949244&group_id=103 Category: configuring/installing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ducttape (ducttapeut) Assigned to: Nobody/Anonymous (nobody) Summary: Moderator Allowed to Post Initial Comment: Currently, the moderator cannot post to a moderated list that he/she is moderator of. He/she must first subscribe to the list. This would seem that common sense would allow the moderator of his/her own list to post. Alternatives without having to join the list, per above: 1) Moderator just simply approves his/her own post(s). 2) Be added to the allow list in filters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=949244&group_id=103 From noreply at sourceforge.net Thu May 6 11:01:38 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 6 11:01:41 2004 Subject: [ mailman-Bugs-949244 ] Moderator Not Allowed to Post Message-ID: Bugs item #949244, was opened at 2004-05-06 15:00 Message generated for change (Settings changed) made by ducttapeut You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=949244&group_id=103 Category: configuring/installing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ducttape (ducttapeut) Assigned to: Nobody/Anonymous (nobody) >Summary: Moderator Not Allowed to Post Initial Comment: Currently, the moderator cannot post to a moderated list that he/she is moderator of. He/she must first subscribe to the list. This would seem that common sense would allow the moderator of his/her own list to post. Alternatives without having to join the list, per above: 1) Moderator just simply approves his/her own post(s). 2) Be added to the allow list in filters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=949244&group_id=103 From noreply at sourceforge.net Fri May 7 14:54:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri May 7 14:54:16 2004 Subject: [ mailman-Patches-950067 ] remove 552 exception for SMTP perm/temp Message-ID: Patches item #950067, was opened at 2004-05-07 18:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=950067&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: remove 552 exception for SMTP perm/temp Initial Comment: Sendmail 8.12 uses 552 for "Message size exceeds fixed maximum message size", and that seems reasonably consistent with RFC 2821. Since it is not appropriate to retry on this error, 552 should be permanent. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=950067&group_id=103 From noreply at sourceforge.net Sat May 8 10:35:50 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat May 8 10:35:56 2004 Subject: [ mailman-Patches-886124 ] default action for the admin interface Message-ID: Patches item #886124, was opened at 2004-01-28 04:56 Message generated for change (Comment added) made by phelim_gervase You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=886124&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: default action for the admin interface Initial Comment: this patch changes the admindb interface such that each subscribe/held message has an extra action that can be taken: default. You then choose at the bottom what the default action will be (defer, reject, discard etc) ---------------------------------------------------------------------- Comment By: Pug Bainter (phelim_gervase) Date: 2004-05-08 09:35 Message: Logged In: YES user_id=484284 While a great idea for a patch, it doesn't work if you try to view the posts from users. Traceback (most recent call last): File "/opt/depot/mailman-2.1.4/scripts/driver", line 87, in run_main main() File "/opt/depot/mailman-2.1.4/Mailman/Cgi/admindb.py", line 163, in main process_form(mlist, doc, cgidata) File "/opt/depot/mailman-2.1.4/Mailman/Cgi/admindb.py", line 685, in process_form defaultaction = int(cgidata.getvalue('defaultaction')) TypeError: int() argument must be a string or a number ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=886124&group_id=103 From noreply at sourceforge.net Sat May 8 11:23:33 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat May 8 11:23:38 2004 Subject: [ mailman-Patches-886124 ] default action for the admin interface Message-ID: Patches item #886124, was opened at 2004-01-28 18:56 Message generated for change (Comment added) made by pabs3 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=886124&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: default action for the admin interface Initial Comment: this patch changes the admindb interface such that each subscribe/held message has an extra action that can be taken: default. You then choose at the bottom what the default action will be (defer, reject, discard etc) ---------------------------------------------------------------------- >Comment By: Pabs (pabs3) Date: 2004-05-08 23:23 Message: Logged In: YES user_id=35028 In the latest version of the patch on lists.indymedia.org the line where the error occurs has been replaced by the following. # Get what action to take by default defaultaction = mm_cfg.DEFER try: defaultaction = cgidata.getvalue('defaultaction') if defaultaction != None: defaultaction = int(defaultaction) except ValueError, TypeError: defaultaction = mm_cfg.DEFER # If the user has not specified a default, be safe and choose defer if defaultaction not in (mm_cfg.DEFER, mm_cfg.APPROVE, mm_cfg.REJECT, mm_cfg.DISCARD): defaultaction = mm_cfg.DEFER ---------------------------------------------------------------------- Comment By: Pug Bainter (phelim_gervase) Date: 2004-05-08 22:35 Message: Logged In: YES user_id=484284 While a great idea for a patch, it doesn't work if you try to view the posts from users. Traceback (most recent call last): File "/opt/depot/mailman-2.1.4/scripts/driver", line 87, in run_main main() File "/opt/depot/mailman-2.1.4/Mailman/Cgi/admindb.py", line 163, in main process_form(mlist, doc, cgidata) File "/opt/depot/mailman-2.1.4/Mailman/Cgi/admindb.py", line 685, in process_form defaultaction = int(cgidata.getvalue('defaultaction')) TypeError: int() argument must be a string or a number ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=886124&group_id=103 From noreply at sourceforge.net Mon May 10 06:36:49 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 10 06:36:53 2004 Subject: [ mailman-Patches-951167 ] patch for #923122 reply_goes_to_list allow poster+list ... Message-ID: Patches item #951167, was opened at 2004-05-10 10:36 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=951167&group_id=103 Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: URA Hiroshi (ura) Assigned to: Nobody/Anonymous (nobody) Summary: patch for #923122 reply_goes_to_list allow poster+list ... Initial Comment: This is patch for #923122 reply_goes_to_list allow poster+list option. http://sourceforge.net/tracker/index.php?func=detail&aid=923122&group_id=103&atid=350103 The patch introduces a new variable `add_poster_to_reply_to' per list. If `add_poster_to_reply_to' is `Yes' and poster isn't member of list, address to poster is added to Reply-To header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=951167&group_id=103 From noreply at sourceforge.net Mon May 10 06:44:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 10 06:44:48 2004 Subject: [ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option Message-ID: Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by ura You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl@freefriends.org ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-05-10 10:44 Message: Logged In: YES user_id=1007264 I uploaded the patch by different method. see following URL: http://sourceforge.net/tracker/index.php?func=detail&aid=951167&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 From noreply at sourceforge.net Mon May 10 14:15:06 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 10 14:15:28 2004 Subject: [ mailman-Bugs-815297 ] Breaking signatures in message/rfc822 attachement! Message-ID: Bugs item #815297, was opened at 2003-09-30 19:42 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: Breaking signatures in message/rfc822 attachement! Initial Comment: Mailman _must_ not touch MIME-parts which are nested more deeply in the mail. As tested with Mailman 2.1.2, header lines will be sometimes reformatted in message/rfc822 attachments which will break the OpenPGP signature (also conforming to the PGP/MIME standard) on that part. I'm attaching a simple email with on long header. Forward this as MIME part and sign it sending it through Mailman, the signature will be broken. This is an email security affecting bug, because if people start believing that a *BAD* signature does not mean much, because they get many broken by mailman, they will not react to a seriously manipulated email anymore! ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2004-05-10 20:15 Message: Logged In: YES user_id=113859 There is another possibility when mailman breaks the signature and that is when the signed part contains an empty header with _two_ spaces after the colon, like forward and sign an email with X-Empty-Header-with-two-spaces: patch 933757 does not remedy this, though. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-04-12 19:17 Message: Logged In: YES user_id=113859 I have created a patch to address the problem. [ 933757 ] fix for [815297] signatures break https://sourceforge.net/tracker/index.php?func=detail&aid=933757&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Marc Mutz (mmutz) Date: 2003-10-03 17:54 Message: Logged In: YES user_id=82377 This is not limited to message/rfc822 at all: As a specific example, create a message with an attachment and add the header Content-Disposition: attachment; filename="more-than-70-chars. txt" (all in a single line), then send it through a mailman-managed ml. Result: mailman "fixes" the message to look like Content-Disposition: attachment; \tfilename="more-than-70-chars.txt" It even does that inside a multipart/signed part, and this is where it breaks the signature verification. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-09-30 19:46 Message: Logged In: YES user_id=113859 Here is the email signed by myself and broken after delivery through mailman. Check the "To:" header line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103 From noreply at sourceforge.net Mon May 10 15:47:43 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 10 15:48:16 2004 Subject: [ mailman-Patches-746728 ] ssl support for list administration Message-ID: Patches item #746728, was opened at 2003-05-31 20:27 Message generated for change (Comment added) made by donnc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=746728&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: matze (indygena) Assigned to: Nobody/Anonymous (nobody) Summary: ssl support for list administration Initial Comment: adds ssl support for the administration interface. via the boolean configuration parameter DEFAULT_ADMIN_USE_SSL can be defined that the list administration interface is accessed oven a ssl encrypted connection ---------------------------------------------------------------------- Comment By: Donn Cave (donnc) Date: 2004-05-10 19:47 Message: Logged In: YES user_id=42839 Would it make sense to add `secure' to the authentication cookie? (c[key]['secure'] = 'ok', ca. line 243 SecurityManager.py.) This instructs the browser to send the cookie to https only. Otherwise it will send it for every URL at the site, including but not limited to the admin pages. I have done this at our site, for all cookie authentication. I needed to modify the source a lot more, but I needed to do it for the sake of our single login hacks. Even for the standard release version, though, I believe it's a good idea. For one thing, `user' passwords will frequently be identical to the ones used for more sensitive authorization. To make this work without requiring SSL even for listinfo, I believe you have to make Utils.py recognize whether it's already talking to an SSL user so that it can decide URLs (for example to the archives) at run-time, but also give the system a way to require some (like admin) to be https anyway. (Sorry to chime in so late, but from here it looks like this hasn't gone very far anyway.) ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2003-10-23 17:18 Message: Logged In: YES user_id=581680 It work`s well and should be included into the normal Mailman as soon as possible. But it would be better, if Mailman produces a HTTP 301 redirect to https, if the admin login page is accessed via http instead of https. That would take care of having no admin password transferred to mailman without using an encrypted connection. And -- this patch should procude a similar 301-redirect if /mailman/create ist accessed via http. :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=746728&group_id=103 From noreply at sourceforge.net Wed May 12 14:10:57 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 12 14:11:01 2004 Subject: [ mailman-Bugs-948064 ] email address will slashes Message-ID: Bugs item #948064, was opened at 2004-05-04 15:39 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=948064&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael (ciberous) Assigned to: Nobody/Anonymous (nobody) Summary: email address will slashes Initial Comment: The mailing list login/(un)subscribe form does not accept email addresses with slashes in the name. In particular, the user has a LotusNotes email address which contains slashes. For example, an email address such as foo_bar/myschool/mydoe@notes.k12.hi.us will not be accepted by the form. It responds that the email address is illegal. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-05-12 11:10 Message: Logged In: NO I can confirm this bug on Mailman 2.1.4. Addresses with slashes are rejected as hostile although they conform to rfc822. Such addresses are also used on some systems to deliver mail to subfolders, e.g.: user+folder/subfolder@domain ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=948064&group_id=103 From noreply at sourceforge.net Thu May 13 10:32:49 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 13 10:32:54 2004 Subject: [ mailman-Bugs-953320 ] bad handling From header in archiver Message-ID: Bugs item #953320, was opened at 2004-05-13 16:32 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953320&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Tibor Pittich (phuture) Assigned to: Nobody/Anonymous (nobody) Summary: bad handling From header in archiver Initial Comment: 2.1.4 mailman version - there is problem with archiver. when body of message contains blank line and continued with text 'From ' at beggining of line, then archiver thing that this is a new message and split it. i see, there is a cleanarch script, which can escape non-header From line but why i must change original post adding "escape character"? is there possibility to check only header of message instead of whole message including body? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953320&group_id=103 From noreply at sourceforge.net Thu May 13 13:04:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 13 13:06:17 2004 Subject: [ mailman-Bugs-953320 ] bad handling From header in archiver Message-ID: Bugs item #953320, was opened at 2004-05-13 14:32 Message generated for change (Comment added) made by desrod You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953320&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Tibor Pittich (phuture) Assigned to: Nobody/Anonymous (nobody) Summary: bad handling From header in archiver Initial Comment: 2.1.4 mailman version - there is problem with archiver. when body of message contains blank line and continued with text 'From ' at beggining of line, then archiver thing that this is a new message and split it. i see, there is a cleanarch script, which can escape non-header From line but why i must change original post adding "escape character"? is there possibility to check only header of message instead of whole message including body? ---------------------------------------------------------------------- Comment By: David A. Desrosiers (desrod) Date: 2004-05-13 17:04 Message: Logged In: YES user_id=3078 I can confirm this bug in 2.1.4, and that it is also in 2.1.5c2.. MAJOR BLOCKER! Please assign to someone and fix! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953320&group_id=103 From noreply at sourceforge.net Thu May 13 20:10:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 13 20:10:36 2004 Subject: [ mailman-Bugs-953665 ] Email not going trough Message-ID: Bugs item #953665, was opened at 2004-05-13 20:10 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953665&group_id=103 Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: boballgood (boballgood) Assigned to: Nobody/Anonymous (nobody) Summary: Email not going trough Initial Comment: The email for my mailing list is not going through. The list email address is Btf@bibletruthforum.org hosted by Stormwire. The domain name is BibleTruthForum.org. Here is the message Stormwire gave me about a serious bug in the Mailman. Hello Bob, I have checked the issue in detail and found that the Mailman version 2.1.3 has been hit by a serious bug. This error might be due to 8-bit-characters in the message headers. As it is a third party software it would be nice if Mailman could handle that a bit more gracefully (even if the sending client/server is at fault here). I hope you undertand this. Please submit a request at Mailman forums and you should be all set. I hope the following link might help you: http://mail.python.org/mailman/listinfo/mailman-users. Please keep us updated on this issue. Thank you. Regards. --Tom Here is the message I get when looking at the Overview of Mailman Bug in Mailman version 2.1.3 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/cpanel/3rdparty/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/cpanel/3rdparty/mailman/Mailman/Cgi/listin fo.py", line 42, in main listinfo_overview() File "/usr/local/cpanel/3rdparty/mailman/Mailman/Cgi/listin fo.py", line 87, in listinfo_overview mlist = MailList.MailList(name, lock=0) File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList. py", line 128, in __init__ self.Load() File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList. py", line 602, in Load raise Errors.MMCorruptListDatabaseError, e MMCorruptListDatabaseError: EOF read where object expected ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953665&group_id=103 From noreply at sourceforge.net Fri May 14 10:31:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri May 14 10:31:30 2004 Subject: [ mailman-Bugs-954002 ] Errors in Portuguese page translations Message-ID: Bugs item #954002, was opened at 2004-05-14 10:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=954002&group_id=103 Category: documentation Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Clyde Jones (clydec) Assigned to: Nobody/Anonymous (nobody) Summary: Errors in Portuguese page translations Initial Comment: These are corrections for the monthly text Este lembrete ?-lhe enviado, uma vez por m?s, para o lembrar da sua participa??o nas listas de discuss?o em . Inclui informa??o sobre a sua participa??o e sobre a forma de a alterar ou anular. Pode visitar as URLs para mudar o seu estatuto ou configura??o, incluindo a anula??o da inscri??o, alterar o modo de recep??o de mensagens ou simplemente suspendendo a entrega (p.ex. quando for de f?rias). Al?m da interface www, pode tamb?m usar o e-mail para efectuar essas altera??es. Para receber mais informa??es envie uma mensagem ao endere?o '-request' da lista (por exemplo mailman-request@ ) contendo unicamente a palavra help/ajuda????? no corpo da mensagem e uma mensagem ser-lhe-? enviada com mais detalhes. Se tiver quest?es, problemas, coment?rios, etc, envie-os para mailman-owner@ . Obrigado! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=954002&group_id=103 From noreply at sourceforge.net Sun May 16 08:28:27 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun May 16 08:28:31 2004 Subject: [ mailman-Bugs-954806 ] AssertionError when Web-canceling subscribtion in 2.1.5 Message-ID: Bugs item #954806, was opened at 2004-05-16 14:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=954806&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Raimund Specht (rspecht) Assigned to: Nobody/Anonymous (nobody) Summary: AssertionError when Web-canceling subscribtion in 2.1.5 Initial Comment: I subscribe to a mailing list and get the confirmation mail. I go to the web confirmation page and choose NOT to confirm but to cancel the subscription, I get the following traceback. Confirming a subscription through web works fine though. [----- Mailman Version: 2.1.5 -----] [----- Traceback ------] Traceback (most recent call last): File "/home/pacs/rsp00/mailman/scripts/driver", line 87, in run_main main() File "/home/pacs/rsp00/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/home/pacs/rsp00/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/home/pacs/rsp00/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError [----- Python Information -----] sys.version = 2.1.3 (#1, Sep 7 2002, 15:29:56) [GCC 2.95.4 20011002 (Debian prerelease)] sys.executable = /usr/bin/python sys.platform = linux2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=954806&group_id=103 From noreply at sourceforge.net Mon May 17 14:13:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 17 14:13:12 2004 Subject: [ mailman-Bugs-955381 ] True/False define missing in ListAdmin.py (2.1.5) Message-ID: Bugs item #955381, was opened at 2004-05-17 18:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=955381&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: True/False define missing in ListAdmin.py (2.1.5) Initial Comment: moderated posting is broken in python versions without True/False in Mailman 2.1.5. this is because the True/False define is missing in ListAdmin.py as far as I can tell there aren't any other scripts which miss it too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=955381&group_id=103 From noreply at sourceforge.net Mon May 17 22:18:06 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 17 22:18:12 2004 Subject: [ mailman-Bugs-955381 ] True/False define missing in ListAdmin.py (2.1.5) Message-ID: Bugs item #955381, was opened at 2004-05-17 14:13 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=955381&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: True/False define missing in ListAdmin.py (2.1.5) Initial Comment: moderated posting is broken in python versions without True/False in Mailman 2.1.5. this is because the True/False define is missing in ListAdmin.py as far as I can tell there aren't any other scripts which miss it too. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-05-17 22:18 Message: Logged In: YES user_id=12800 See attached patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=955381&group_id=103 From noreply at sourceforge.net Tue May 18 07:14:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 18 07:14:48 2004 Subject: [ mailman-Patches-955819 ] fix: [ 926034 ] Crashes on encoding errors Message-ID: Patches item #955819, was opened at 2004-05-18 13:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=955819&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K?roly Segesdi (vm303) Assigned to: Nobody/Anonymous (nobody) Summary: fix: [ 926034 ] Crashes on encoding errors Initial Comment: Actually the bug title is wrong, the problem is (I think) python not supporting windows-1250 and windows-1252. The problem can be fixed in the email library in $MAILMANDIR/pythonlib/email/Header.py I don't know if newer pythons (afaik python 2.3 contains this email package and maybe it does handle windows codepages) still suffer the same problem. So here's my solution for mailman-2.1.3 (I think it's applicable to 2.1.4 too) and python 2.2.2: --- Header.py.orig 2003-03-30 22:39:05.000000000 +0200 +++ Header.py 2004-05-18 12:01:35.000000000 +0200 @@ -284,7 +284,7 @@ outcodec = charset.output_codec or 'us-ascii' s = s.encode(outcodec, errors) break - except UnicodeError: + except (UnicodeError, LookupError): pass else: assert False, 'utf-8 conversion failed' this way if s.encode does not understand the original encoding (like windows-1250 or windows-1252) then it resorts to use utf-8 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=955819&group_id=103 From noreply at sourceforge.net Wed May 19 10:12:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 19 10:12:19 2004 Subject: [ mailman-Bugs-956734 ] Runner Error Message-ID: Bugs item #956734, was opened at 2004-05-19 16:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=956734&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Cataldo Cigliola (cataldoc) Assigned to: Nobody/Anonymous (nobody) Summary: Runner Error Initial Comment: Hi, I use mailman 2.1.5 (from an old 2.1.4 installation) when a user (flagged as moderated) send a mail to a list (with action Suspend for member moderation action) the message disappear. The same when a non member user send an email to list and generic_nonmember_action is set to Suspend. In error log I see this error May 19 16:06:47 2004 (22118) Uncaught runner exception: global name 'True' is not defined May 19 16:06:47 2004 (22118) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/Moderate.py", line 67, in process ModeratedMemberPost) File "/usr/local/mailman/Mailman/Handlers/Hold.py", line 214, in hold_for_approval id = mlist.HoldMessage(msg, reason, msgdata) File "/usr/local/mailman/Mailman/ListAdmin.py", line 180, in HoldMessage id = self.__nextid() File "/usr/local/mailman/Mailman/ListAdmin.py", line 113, in __nextid while True: NameError: global name 'True' is not defined May 19 16:06:47 2004 (22118) SHUNTING: 1084975606.540766+642ddcf41712187aa851866ce127d67069f92fb1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=956734&group_id=103 From noreply at sourceforge.net Wed May 19 12:42:37 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 19 12:42:43 2004 Subject: [ mailman-Bugs-956734 ] Runner Error Message-ID: Bugs item #956734, was opened at 2004-05-19 16:12 Message generated for change (Comment added) made by cataldoc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=956734&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Cataldo Cigliola (cataldoc) Assigned to: Nobody/Anonymous (nobody) Summary: Runner Error Initial Comment: Hi, I use mailman 2.1.5 (from an old 2.1.4 installation) when a user (flagged as moderated) send a mail to a list (with action Suspend for member moderation action) the message disappear. The same when a non member user send an email to list and generic_nonmember_action is set to Suspend. In error log I see this error May 19 16:06:47 2004 (22118) Uncaught runner exception: global name 'True' is not defined May 19 16:06:47 2004 (22118) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/Moderate.py", line 67, in process ModeratedMemberPost) File "/usr/local/mailman/Mailman/Handlers/Hold.py", line 214, in hold_for_approval id = mlist.HoldMessage(msg, reason, msgdata) File "/usr/local/mailman/Mailman/ListAdmin.py", line 180, in HoldMessage id = self.__nextid() File "/usr/local/mailman/Mailman/ListAdmin.py", line 113, in __nextid while True: NameError: global name 'True' is not defined May 19 16:06:47 2004 (22118) SHUNTING: 1084975606.540766+642ddcf41712187aa851866ce127d67069f92fb1 ---------------------------------------------------------------------- >Comment By: Cataldo Cigliola (cataldoc) Date: 2004-05-19 18:42 Message: Logged In: YES user_id=115421 fixed upgrading python from 2.2.2 to 2.3.3 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=956734&group_id=103 From noreply at sourceforge.net Wed May 19 17:07:30 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 19 17:07:34 2004 Subject: [ mailman-Patches-957054 ] Strip arbitrary headers from posts before delivery Message-ID: Patches item #957054, was opened at 2004-05-20 09:07 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=957054&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: Strip arbitrary headers from posts before delivery Initial Comment: This patch adds an extra config option under Privacy Options... / Header Munging that lets the list admin specify arbitrary headers to be removed by CookHeaders. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=957054&group_id=103 From noreply at sourceforge.net Wed May 19 18:37:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 19 18:37:58 2004 Subject: [ mailman-Feature Requests-957109 ] Want to moderate first posts Message-ID: Feature Requests item #957109, was opened at 2004-05-19 15:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=957109&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Roger Binns (rogerb) Assigned to: Nobody/Anonymous (nobody) Summary: Want to moderate first posts Initial Comment: I want to be able to moderate first posts from addresses, until eventually marking the poster as ok. It is usually the first posts from addresses that are viruses/spam/off topic/abusive etc. Yahoo Groups has this feature and it works well. (My lists are all on SF) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=957109&group_id=103 From noreply at sourceforge.net Wed May 19 20:55:14 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 19 20:55:18 2004 Subject: [ mailman-Feature Requests-957159 ] Adding POP3 to Eliminate 127.0.0.1 Message-ID: Feature Requests item #957159, was opened at 2004-05-19 17:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=957159&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: mylogon (mylogon) Assigned to: Nobody/Anonymous (nobody) Summary: Adding POP3 to Eliminate 127.0.0.1 Initial Comment: Looking to add POP3 availablity to Mailman. If SMTPHOST = 'mydomain.com' and the system can POP, this removes the extra "Received: from localhost ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.34) id 111111-000249-4x" that many ISP's and SPAM filters block. (Some mailservers even say "helo=localhost@localdomain".) I figure that if it was out in SMTPDirect.py after: "except smtplib.SMTPException:" and then restarts the send procedure that would work. (Many email servers, i.e. Exim, Qmail only need to be popped every thirty minutes or so to keep the connection alive. No sense in doing it every time.) The poplib-example-1 (attached) shows how to pop but I cannot figure out the restarting without losing messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=957159&group_id=103 From noreply at sourceforge.net Wed May 19 22:41:23 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 19 22:41:38 2004 Subject: [ mailman-Patches-957054 ] Strip arbitrary headers from posts before delivery Message-ID: Patches item #957054, was opened at 2004-05-20 09:07 Message generated for change (Comment added) made by tzs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=957054&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: Strip arbitrary headers from posts before delivery Initial Comment: This patch adds an extra config option under Privacy Options... / Header Munging that lets the list admin specify arbitrary headers to be removed by CookHeaders. ---------------------------------------------------------------------- >Comment By: Colin Palmer (tzs) Date: 2004-05-20 14:41 Message: Logged In: YES user_id=658762 This version should work a little better. Warning: messes with Defaults.py and versions.py and could cause nasty things to happen to any existing mailing list you have. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=957054&group_id=103 From cgomez at ceis.cujae.edu.cu Fri May 21 10:21:31 2004 From: cgomez at ceis.cujae.edu.cu (Carlos Antonio Gomez) Date: Fri May 21 10:19:16 2004 Subject: (no subject) Message-ID: <006c01c43f3e$e9e94e40$1b1510ac@cujae.edu.cu> Hola Lista: Soy un recien ingresado miembro pero con un problema que me tiene hace 4 meses sin dormir. El problema esta en que tengo un servidor con RedHatAS3 en el cual tengo postfix + Mailman. Luego de migrar de un redhat7.3 (tambien la version de mailman cambio al igual que el MTA pues anteriormente era sendmail) no he tenidomas paz con el server. Lo tengo perfectamente al dia con los ultimos updates de RedHat y la version del mailman que esta incluida en el Fedora mailman-1.2.4-4 compilado el srpm para RedHatAS3, tengo un total de 1300 usuarios mas o menos. El problema radica en que el server se me queda colgado, los demonios comienzan a morir y el server se queda funcionando a nivel de Kernel, pues le quitas la tarjeta de Red y te notifica a traves de la consola, se la pones y hace lo mismo, ademas si ejecutas la direccion en que esta el webmin el servidor que tra el webmin te responde y te muestra la pagina de autenticacion lo que a la hora de autenticar si falla pues el demonio encargado de esto murio al igual que los demas, le haces telnet a los puertos y se conecta lo que queda en espera de la respuesta que debe dar el server (login_baner o algo asi). Hice un script que me deja en los log la carga del server en cada minuto y mirando esto me doy cuenta de que el mailman lo pone a full, el load average se pone hasta un 60% cuando por lo general esta cuando mas a un 4%. Me puse a mirar los log del mailman y al menos en las ultimas caidas, coincide con un mensaje enviado a las listas, pero lo mas curioso esta en que lo mismo ocurre cuando se manda a una lista grande que si se hace a una pequena, yo tengo listas anidadadas como por ejemplo todos-l@ceis, dentro de esta estan trabajadores-l y estudiantes-l, dentro de estudiantes-l se encuentra 1ro-l, 2do-l , 3ro-l, 4to-l, 5to-l, dentro de 1ro-l se encuentra if11-l, if12-l, etc, dentro de 1f11-l esta pepe, juan, jose, etc, la caida del server esta ocurriendo lo mismo cuando se manbda un correo a todos-l que si se hace a if11-l, es como si se conjugaran factores para que esto suceda.... espero que me puedan ayudar en algo y darme una orientacion... Nota: Ya he vambiado de hardware completo y haciendo pruebas hemos logrado tunbar el server mando correos a estas listas Saludos ************************************************* "Para ser exitoso no tienes que hacer cosas extraordinarias. Haz cosas ordinarias extraordinariamente bien" ----------------------------------------------------------------- Carlos Antonio G?mez Brizuela. Administrador de la RED del CEIS Estudiante de Inform?tica. cgomez_81@hotmail.com ICQ # 192486535 CUJAE. ************************************************* __________________________________________ Aniversario 40 de la CUJAE Visite: XII Convencion de Ingenieria y Arquitectura http://www.cujae.edu.cu/eventos/convencion/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-coders/attachments/20040521/6b4fdfc6/attachment.html From noreply at sourceforge.net Sun May 23 03:12:39 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun May 23 03:12:43 2004 Subject: [ mailman-Bugs-958816 ] bug in 2.1.5 - can't unsubscribe (with danish lang selected) Message-ID: Bugs item #958816, was opened at 2004-05-23 09:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=958816&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Klavs Klavsen (klavs) Assigned to: Nobody/Anonymous (nobody) Summary: bug in 2.1.5 - can't unsubscribe (with danish lang selected) Initial Comment: When viewing the user page in danish (with 30% or less translated - I'll have a look a that at some point when I get the time) - it fails with this message (it works fine when using english): Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/options.py", line 239, in main loginpage(mlist, doc, user, language) File "/usr/local/mailman/Mailman/Cgi/options.py", line 813, in loginpage table.AddRow([_("""In order to change your membership option, you must File "/usr/local/mailman/Mailman/i18n.py", line 89, in _ return tns % dict ValueError: unsupported format character 'p' (0x70) at index 105 Python information: Variable Value sys.version 2.2.3 (#1, Jul 28 2003, 11:43:19) [GCC 3.2.2 20030322 (Gentoo Linux 1.4 3.2.2-r2)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /lp-nyhedsbrev CONTENT_LENGTH 100 CONTENT_TYPE application/x-www-form-urlencoded HTTP_COOKIE POSTNUKESID=5241e6345df9c0303def0d4b0749ea3a SCRIPT_FILENAME /usr/local/mailman/cgi-bin/options PYTHONPATH /usr/local/mailman SERVER_SOFTWARE Apache SERVER_ADMIN admin@EnableIT.dk SCRIPT_NAME /mailman/options SCRIPT_URI http://www.mysite.dk/mailman/options/lp-nyhedsbrev SERVER_SIGNATURE REQUEST_METHOD POST HTTP_HOST www.mysite.dk SCRIPT_URL /mailman/options/lp-nyhedsbrev SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/options/lp-nyhedsbrev HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040418 Firefox/0.8 HTTP_CONNECTION keep-alive HTTP_REFERER http://www.mysite.dk/mailman/listinfo/lp-nyhedsbrev SERVER_NAME my site REMOTE_ADDR HTTP_KEEP_ALIVE 300 REMOTE_PORT 34514 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 PATH_TRANSLATED /www/websites/mysite/html/lp-nyhedsbrev SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 192.168.1.2 DOCUMENT_ROOT /www/websites ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=958816&group_id=103 From noreply at sourceforge.net Mon May 24 17:01:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 24 17:01:53 2004 Subject: [ mailman-Bugs-959717 ] Login failure of an unregistered user Message-ID: Bugs item #959717, was opened at 2004-05-24 23:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=959717&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: edgar (dreadgar) Assigned to: Nobody/Anonymous (nobody) Summary: Login failure of an unregistered user Initial Comment: On the server where I am the owner of few mailing lists I've tried to see the list of the subscribed people on a list where I'm not subscribed. So I wrote in the fields my e-mail address and a passwd that I use for the lists I own. That's the way I got the page warning me about the bug that I attached here. I hope I helped you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=959717&group_id=103 From noreply at sourceforge.net Mon May 24 17:04:38 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 24 17:04:42 2004 Subject: [ mailman-Bugs-959720 ] Bug in version 2.1.4 on Debian testing Message-ID: Bugs item #959720, was opened at 2004-05-24 23:04 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=959720&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: edgar (dreadgar) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in version 2.1.4 on Debian testing Initial Comment: On the server where I am the owner of few mailing lists I've tried to see the list of the subscribed people on a list where I'm not subscribed. So I wrote in the fields my e-mail address and a passwd that I use for the lists I own. That's the way I got the page warning me about the bug that I attached here. Sorry for the previous posting without the attachment. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=959720&group_id=103 From noreply at sourceforge.net Mon May 24 17:28:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 24 17:29:01 2004 Subject: [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 05:07 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-05-24 21:28 Message: Logged In: YES user_id=67709 You can download the patch for 2.1.5 from http://mm.tkikuchi.net/mailman-2.1.5+patch.20040516.gz TK ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-02-08 06:10 Message: Logged In: YES user_id=67709 This patch for 2.1.3 is also applicable to 2.1.4. Though one patch fails to apply, it can safely be neglected. You can also get a newer and more convenient patch at: http://mm.tkikuchi.net/mailman-2.1.4+patch.20040123.gz Cheers, TK ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-09-29 01:21 Message: Logged In: YES user_id=67709 Now the patch includes instruction in General admin page. (in detail part). In source dir you should type: patch -p0 < /path/to/seqnum.patch ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-05-18 02:01 Message: Logged In: YES user_id=67709 Here is update of my patch for 2.1.2 ---------------------------------------------------------------------- Comment By: Mitchell Marks (jojoba2) Date: 2003-05-17 17:42 Message: Logged In: YES user_id=718482 Is there a version vor MM 2.1.2? I'm trying the older one but doesn't seem to work. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-27 05:33 Message: Logged In: YES user_id=67709 sorry for daily update but there was an error in i18n handling of '(no subject)' ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-26 01:25 Message: Logged In: YES user_id=67709 update of patch for 2.1.1 if the subject is all ascii, then cat the prefix and subject before it is instantiated. Hope to solve prefix only subject 1st line. Note: with this patch without $d, Re: [prefix] is now mungled to [prefix] Re:. This is useful if someone post new issue as follow up to old subject like; New subject bah bah was Re: [prefix] foo ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-14 11:33 Message: Logged In: YES user_id=67709 Hi, I am pleased you like this patch. Here is my current version attached. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 10:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 04:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From noreply at sourceforge.net Tue May 25 10:34:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 25 10:34:48 2004 Subject: [ mailman-Bugs-949117 ] 2.1.5rc2 upgrade dies on corrupt qfiles Message-ID: Bugs item #949117, was opened at 2004-05-06 07:16 Message generated for change (Comment added) made by jmoraragweed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=949117&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Brion Vibber (vibber) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.5rc2 upgrade dies on corrupt qfiles Initial Comment: Upgrading from 2.1.2 to 2.1.5rc2; a couple of the .pck files in qfiles/shunt were zero-length for reasons unknown. This caused the upgrade (make install) to fail with this message: updating old qfiles Traceback (most recent call last): File "bin/update", line 780, in ? errors = main() File "bin/update", line 709, in main update_qfiles() File "bin/update", line 441, in update_qfiles msg, data = dequeue(filebase) File "bin/update", line 497, in dequeue msg = cPickle.load(msgfp) EOFError make: *** [update] Error 1 Removing the zero-length files cleared that up. I did have one other problem; while investigating the first bit I dumped some info to a text file in qfiles, and the next make install failed with this error: updating old qfiles Traceback (most recent call last): File "bin/update", line 780, in ? errors = main() File "bin/update", line 709, in main update_qfiles() File "bin/update", line 434, in update_qfiles for filename in os.listdir(dirpath): OSError: [Errno 20] Not a directory: '/home/mailman/qfiles/blork' make: *** [update] Error 1 At least that had the filename in it. ;) Removed the file, and it installed/upgraded cleanly. So far so good... ---------------------------------------------------------------------- Comment By: John Mora (jmoraragweed) Date: 2004-05-25 09:34 Message: Logged In: YES user_id=605434 I have the same problem when trying to update to 2.1.5 release from Mailman version 2.1.4. I have no zero-length files in qfiles/shunt. My error is similar, but I'm not certain the two are related. I'm posting it for lack of knowing better: Updating Usenet watermarks - nothing to update here Nothing to do. updating old qfiles Traceback (most recent call last): File "bin/update", line 780, in ? errors = main() File "bin/update", line 709, in main update_qfiles() File "bin/update", line 441, in update_qfiles msg, data = dequeue(filebase) File "bin/update", line 497, in dequeue msg = cPickle.load(msgfp) EOFError make: *** [update] Error 1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=949117&group_id=103 From noreply at sourceforge.net Tue May 25 10:40:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 25 10:40:40 2004 Subject: [ mailman-Bugs-960181 ] 'make update' to 2.1.5 fails on 'Updating Usenet watermarks' Message-ID: Bugs item #960181, was opened at 2004-05-25 09:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=960181&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: John Mora (jmoraragweed) Assigned to: Nobody/Anonymous (nobody) Summary: 'make update' to 2.1.5 fails on 'Updating Usenet watermarks' Initial Comment: Updating from 2.1.4 release to 2.1.5 release, during make install, it dies on: Updating Usenet watermarks - nothing to update here Nothing to do. updating old qfiles Traceback (most recent call last): File "bin/update", line 780, in ? errors = main() File "bin/update", line 709, in main update_qfiles() File "bin/update", line 441, in update_qfiles msg, data = dequeue(filebase) File "bin/update", line 497, in dequeue msg = cPickle.load(msgfp) EOFError make: *** [update] Error 1 This should preferably die gracefully or report the invalid file for further investigation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=960181&group_id=103 From noreply at sourceforge.net Wed May 26 00:18:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 26 00:18:25 2004 Subject: [ mailman-Patches-960551 ] Plain digest with mixed charsets Message-ID: Patches item #960551, was opened at 2004-05-26 13:18 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=960551&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: Plain digest with mixed charsets Initial Comment: Plain digest including bodies: - encoded with charset not preferred by the list - including unkown characters will be shunted. This patch fixes this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=960551&group_id=103 From noreply at sourceforge.net Wed May 26 00:20:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 26 00:20:18 2004 Subject: [ mailman-Patches-960551 ] Bug: Plain digest with mixed charsets Message-ID: Patches item #960551, was opened at 2004-05-26 13:18 Message generated for change (Settings changed) made by hatukanezumi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=960551&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) >Summary: Bug: Plain digest with mixed charsets Initial Comment: Plain digest including bodies: - encoded with charset not preferred by the list - including unkown characters will be shunted. This patch fixes this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=960551&group_id=103 From noreply at sourceforge.net Wed May 26 19:12:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 26 19:12:25 2004 Subject: [ mailman-Bugs-961245 ] Embedded images using Content-ID are lost. Message-ID: Bugs item #961245, was opened at 2004-05-26 16:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961245&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stuart Donaldson (stuartd) Assigned to: Nobody/Anonymous (nobody) Summary: Embedded images using Content-ID are lost. Initial Comment: Sending e-mail with an embedded image that includes the image as a part of the message identified by Content-ID does not work. When sending a message to the list with an embedded image, the message arrives and is archived where the image intact. The MIME headers for the message reference a and there is a header on the mime component for "Content-ID: " However the message that gets delivered to the list members does not include the Content-ID. The embedded image is still included in the message, but is not displayed because of the missing header. Version 2.1.4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961245&group_id=103 From noreply at sourceforge.net Thu May 27 10:12:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 27 10:12:18 2004 Subject: [ mailman-Bugs-961587 ] Incorrect -1 or 1 messages in moderator queue Message-ID: Bugs item #961587, was opened at 2004-05-27 09:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961587&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matt Domsch (mdomsch) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect -1 or 1 messages in moderator queue Initial Comment: Mailman 2.1.5, upgraded from 2.1.4. Two different lists exhibit similar behaviour. One list gets admin notices daily that there are -1 messages in the moderator queue, when there are none displayed. A second list gets admin notices daily that there are 1 messages in the moderator queue, when there are none displayed. For this list, I have rmlist'd it and re-created it, to no avail. Please advise. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961587&group_id=103 From noreply at sourceforge.net Thu May 27 10:31:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 27 10:31:36 2004 Subject: [ mailman-Bugs-961245 ] Embedded images using Content-ID are lost. Message-ID: Bugs item #961245, was opened at 2004-05-26 16:12 Message generated for change (Comment added) made by stuartd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961245&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Stuart Donaldson (stuartd) Assigned to: Nobody/Anonymous (nobody) Summary: Embedded images using Content-ID are lost. Initial Comment: Sending e-mail with an embedded image that includes the image as a part of the message identified by Content-ID does not work. When sending a message to the list with an embedded image, the message arrives and is archived where the image intact. The MIME headers for the message reference a and there is a header on the mime component for "Content-ID: " However the message that gets delivered to the list members does not include the Content-ID. The embedded image is still included in the message, but is not displayed because of the missing header. Version 2.1.4 ---------------------------------------------------------------------- >Comment By: Stuart Donaldson (stuartd) Date: 2004-05-27 07:31 Message: Logged In: YES user_id=326269 After digging further to try and solve the problem, I found that it was a result of an old version of the Anomy Sanitizer that IT has running on the mail server. The Sanitizer was stripping the Content-ID field. Sorry for the false alarm. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961245&group_id=103 From noreply at sourceforge.net Thu May 27 10:33:05 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 27 10:33:08 2004 Subject: [ mailman-Bugs-961245 ] Embedded images using Content-ID are lost. Message-ID: Bugs item #961245, was opened at 2004-05-26 16:12 Message generated for change (Comment added) made by stuartd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961245&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Stuart Donaldson (stuartd) Assigned to: Nobody/Anonymous (nobody) Summary: Embedded images using Content-ID are lost. Initial Comment: Sending e-mail with an embedded image that includes the image as a part of the message identified by Content-ID does not work. When sending a message to the list with an embedded image, the message arrives and is archived where the image intact. The MIME headers for the message reference a and there is a header on the mime component for "Content-ID: " However the message that gets delivered to the list members does not include the Content-ID. The embedded image is still included in the message, but is not displayed because of the missing header. Version 2.1.4 ---------------------------------------------------------------------- >Comment By: Stuart Donaldson (stuartd) Date: 2004-05-27 07:33 Message: Logged In: YES user_id=326269 BTW - marked the bug as closed so it would stick around in case someone else has a similar problem, even though it is not a bug with Mailman. I have no problems with someone deleting this bug if you don't want it in your list. ---------------------------------------------------------------------- Comment By: Stuart Donaldson (stuartd) Date: 2004-05-27 07:31 Message: Logged In: YES user_id=326269 After digging further to try and solve the problem, I found that it was a result of an old version of the Anomy Sanitizer that IT has running on the mail server. The Sanitizer was stripping the Content-ID field. Sorry for the false alarm. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961245&group_id=103 From noreply at sourceforge.net Sun May 30 10:12:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun May 30 10:12:16 2004 Subject: [ mailman-Bugs-963137 ] dumpdb broken Message-ID: Bugs item #963137, was opened at 2004-05-30 10:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=963137&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Rubin (prubin) Assigned to: Nobody/Anonymous (nobody) Summary: dumpdb broken Initial Comment: In the stable 2.1.5 load dump db is broken: Traceback (most recent call last): File "/var/mailman/bin/dumpdb", line 156, in ? msg = main() File "/var/mailman/bin/dumpdb", line 126, in main d = DumperSwitchboard().read(filename) NameError: global name 'DumperSwitchboard' is not defined ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=963137&group_id=103 From noreply at sourceforge.net Sun May 30 23:33:57 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun May 30 23:34:01 2004 Subject: [ mailman-Bugs-963137 ] dumpdb broken Message-ID: Bugs item #963137, was opened at 2004-05-30 10:12 Message generated for change (Comment added) made by prubin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=963137&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Rubin (prubin) Assigned to: Nobody/Anonymous (nobody) Summary: dumpdb broken Initial Comment: In the stable 2.1.5 load dump db is broken: Traceback (most recent call last): File "/var/mailman/bin/dumpdb", line 156, in ? msg = main() File "/var/mailman/bin/dumpdb", line 126, in main d = DumperSwitchboard().read(filename) NameError: global name 'DumperSwitchboard' is not defined ---------------------------------------------------------------------- >Comment By: Paul Rubin (prubin) Date: 2004-05-30 23:33 Message: Logged In: YES user_id=91557 Appearently, yo just removed support for .db files. it works fine on the .pck files... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=963137&group_id=103