Mailman 3 August 2003 - Mailman-coders

[ mailman-Patches-762130 ] web interface for editing archives
by SourceForge.net 11 Aug '03

11 Aug '03

Patches item #762130, was opened at 2003-06-27 18:05 Message generated for change (Comment added) made by aaboyd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=762130&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Adriane Boyd (aaboyd) Assigned to: Nobody/Anonymous (nobody) Summary: web interface for editing archives Initial Comment: This patch makes it possible for list administrators to edit their list archives through a web interface linked into the admin interface. A new cgi script called editarch allows administrators to browse by month and delete messages from the archives. The messages are immediately deleted from the mbox file, but because of the overhead in reprocessing archives, the archives aren't redone on-the-fly. Instead, a file is kept with a running list of recently edited archives and a nightly cron job does the reprocessing. The file location is configurable in mm_cfg. (Note: since it has to read through the mbox file message by message, pages will load slowly for lists with large archives.) In the mailman 2.1.2 source directory: patch -p1 < editarch-2.1.2-0.1.patch ---------------------------------------------------------------------- >Comment By: Adriane Boyd (aaboyd) Date: 2003-08-11 17:25 Message: Logged In: YES user_id=696276 Updated so that the permissions on the mbox file are set properly after editing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=762130&group_i…

1 0

[ mailman-Bugs-784888 ] Wrong domain in public archives
by SourceForge.net 11 Aug '03

11 Aug '03

Bugs item #784888, was opened at 2003-08-07 10:03 Message generated for change (Comment added) made by robbrandt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Rob Brandt (robbrandt) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong domain in public archives Initial Comment: I *think* I've found a bug in 2.12. I've had a longstanding issue with all of my mailing lists pointing to the wrong domain for mail archives. When I originally set up the server, used an initial "recreational" domain name not intended to be used widely. The intention was to switch to the real domain names later once the server went live. I did that, but all of the URLs for archives (only archives) still pointed to the stupid domain name. I intended to fix this in 2.12 by using the fix_url function while I was also fixing a bunch of other stuff. I've needed to move some of my lists to other domains anyway, so this seemed like a good time. So I ran fix_url over almost all of my domains, and tested them as I went. Everything went as planned, except some of them still had the archives pointing to the recreational domain. Then it dawned on me that the ones that didn't get fixed were all *public* archives; the ones that did get fixed were all private. I went to one of the public archives and switched it to private, and the URL to the archives was then OK! Switched it back to public and it was wrong again. So, it seems that this is a bug. Or I've missed a configuration setting somewhere. Thanks Rob ---------------------------------------------------------------------- >Comment By: Rob Brandt (robbrandt) Date: 2003-08-11 13:46 Message: Logged In: YES user_id=332197 The problem is resolved, with great help from Richard Barrett. For the sake of posterity, let the bug archives show: * Be sure you have proper virtual host mapping (add_virtualhost()) in mm_cfg.py; * Be sure that the list setting for "Host name this list prefers for email" is in fact your mail exchange address, not a base URL for browsing (which was my problem); * Run fix_url.py ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-08-11 05:15 Message: Logged In: YES user_id=67709 Have you defined your (url_host, mail_host) pair in your mm_cfg.py ? You should state like: add_virtualhost('www.virtual.dom', 'mail.virtual.dom') ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_i…

1 0

[ mailman-Bugs-669201 ] feature: unified membership allow post list.
by SourceForge.net 11 Aug '03

11 Aug '03

Bugs item #669201, was opened at 2003-01-16 10:22 Message generated for change (Comment added) made by banerian You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669201&group_i… Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: feature: unified membership allow post list. Initial Comment: i host a variety of lists that obtain posts from members and non-members alike. they also have times where the email address they send from changes. i'd like the ability to create a global list of people that are allowed to post to lists and have it be enabled/disabled on a per-list basis. eg: list1 - use list members, extra people and GLOBAL_allow_list list2 - use list members, extra people only. ---------------------------------------------------------------------- Comment By: stefani banerian (banerian) Date: 2003-08-11 10:19 Message: Logged In: YES user_id=798204 in privacy options, it would be also good if regexp or globs worked in the configuration option "Addresses of members accepted for posting to this list without implicit approval requirement" without this ability to use regexp or globs, such as .*(a)my.domain.org allowing posts from certain domains is somewhat painful. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669201&group_i…

1 0

[ mailman-Bugs-784888 ] Wrong domain in public archives
by SourceForge.net 11 Aug '03

11 Aug '03

Bugs item #784888, was opened at 2003-08-07 17:03 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Rob Brandt (robbrandt) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong domain in public archives Initial Comment: I *think* I've found a bug in 2.12. I've had a longstanding issue with all of my mailing lists pointing to the wrong domain for mail archives. When I originally set up the server, used an initial "recreational" domain name not intended to be used widely. The intention was to switch to the real domain names later once the server went live. I did that, but all of the URLs for archives (only archives) still pointed to the stupid domain name. I intended to fix this in 2.12 by using the fix_url function while I was also fixing a bunch of other stuff. I've needed to move some of my lists to other domains anyway, so this seemed like a good time. So I ran fix_url over almost all of my domains, and tested them as I went. Everything went as planned, except some of them still had the archives pointing to the recreational domain. Then it dawned on me that the ones that didn't get fixed were all *public* archives; the ones that did get fixed were all private. I went to one of the public archives and switched it to private, and the URL to the archives was then OK! Switched it back to public and it was wrong again. So, it seems that this is a bug. Or I've missed a configuration setting somewhere. Thanks Rob ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-08-11 12:15 Message: Logged In: YES user_id=67709 Have you defined your (url_host, mail_host) pair in your mm_cfg.py ? You should state like: add_virtualhost('www.virtual.dom', 'mail.virtual.dom') ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_i…

1 0

[ mailman-Feature Requests-786326 ] Rotation through moderators
by SourceForge.net 10 Aug '03

10 Aug '03

Feature Requests item #786326, was opened at 2003-08-10 16:47 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=786326&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Milos Popovic (milos_popovic) Assigned to: Nobody/Anonymous (nobody) Summary: Rotation through moderators Initial Comment: A useful moderation feature in LISTSERV, when multiple moderators are listed, is that it can deliver moderation requests to moderators in *rotation* (only one moderator at a time), thus reducing the individual workload. I've found this a useful feature to share the workload of verifying mostly filtered spam that's held for moderation on lists that need to accept outside posts and need to have a quick moderator approval turnaround time on posts. The quick turn-around time means moderation requests are sent immediately for each post, rather than just being bundled at the end of each day. It would be very useful to have such a feature (option to rotate through moderators, for the individual post moderation requests only) in MailMan. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=786326&group_i…

1 0

[ mailman-Bugs-785450 ] scripts/driver bug
by SourceForge.net 08 Aug '03

08 Aug '03

Bugs item #785450, was opened at 2003-08-08 10:37 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=785450&group_i… Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kevin N Carpenter (kevinc_63366) Assigned to: Nobody/Anonymous (nobody) Summary: scripts/driver bug Initial Comment: One of my primary list is broke. The other lists appear to be fine. Any help would be greatly appreciated! Note that this occurred in 2.1.0 - I upgraded to 2.1.2 but the problem still exist. Bug in Mailman version 2.1.2 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/admindb.py", line 85, in main mlist = MailList.MailList(listname, lock=0) File "/usr/local/mailman/Mailman/MailList.py", line 124, in __init__ self.Load() File "/usr/local/mailman/Mailman/MailList.py", line 583, in Load dict, e = self.__load(file) File "/usr/local/mailman/Mailman/MailList.py", line 556, in __load dict = loadfunc(fp) UnpicklingError: invalid load key, 'n'. ------------------------------------------------------------- ------------------- Python information: Variable Value sys.version 2.2.3 (#1, Aug 7 2003, 19:30:01) [GCC 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------------- ------------------- Environment variables: Variable Value PYTHONPATH /usr/local/mailman SERVER_SOFTWARE Apache/1.3.27 (Unix) (Gentoo/Linux) PHP/4.3.1 SCRIPT_FILENAME /home/mailman/cgi-bin/admindb SERVER_ADMIN root@localhost SCRIPT_NAME /mailman/admindb SERVER_SIGNATURE Apache/1.3.27 Server at mail.seaplace.org Port 80 REQUEST_METHOD GET HTTP_HOST www.seaplace.org PATH_INFO /reefkeepers SERVER_PROTOCOL HTTP/1.0 QUERY_STRING REQUEST_URI /mailman/admindb/reefkeepers HTTP_ACCEPT */* PATH_TRANSLATED /home/httpd/htdocs/reefkeepers HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Mon_AutoConfig_v1.02_STL; .NET CLR 1.0.3705; .NET CLR 1.1.4322) HTTP_CONNECTION keep-alive SERVER_NAME mail.seaplace.org REMOTE_ADDR 199.89.234.122 HTTP_X_FORWARDED_FOR 10.133.116.235 REMOTE_PORT 21100 HTTP_ACCEPT_LANGUAGE en-us HTTP_VIA 1.1 ics_server.monsanto.com (ICS 2.2.76) SERVER_ADDR 66.128.118.35 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip, deflate UNIQUE_ID PzPApEKAdiMAAF4RtrM DOCUMENT_ROOT /home/httpd/htdocs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=785450&group_i…

1 0

[ mailman-Bugs-785174 ] uncaught bounce notification (Symantec_AntiVirus_for_SMTP_GG
by SourceForge.net 08 Aug '03

08 Aug '03

Bugs item #785174, was opened at 2003-08-08 12:14 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=785174&group_i… Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: uncaught bounce notification (Symantec_AntiVirus_for_SMTP_GG Initial Comment: mm 2.1 doesn't detect the following bounce message Perhaps in this case it should ignore it as its only a temporary failure. Date: Fri, 08 Aug 2003 08:49:31 +0800 From: Symantec_AntiVirus_for_SMTP_Gateways(a)murdoch.edu.au To: imc-perth-bounces(a)lists.indymedia.org Subject: Delivery failure notification Your message with Subject: [imc-perth] a good feature story could not be delivered to the following recipients: m.sargeant(a)student.murdoch.edu.au 30051866(a)student.murdoch.edu.au Please do not resend your original message. Delivery attempts will continue to be made for 5 day(s). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=785174&group_i…

1 0

[ mailman-Bugs-784888 ] Wrong domain in public archives
by SourceForge.net 07 Aug '03

07 Aug '03

Bugs item #784888, was opened at 2003-08-07 10:03 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=784888&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Rob Brandt (robbrandt) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong domain in public archives Initial Comment: I *think* I've found a bug in 2.12. I've had a longstanding issue with all of my mailing lists pointing to the wrong domain for mail archives. When I originally set up the server, used an initial "recreational" domain name not intended to be used widely. The intention was to switch to the real domain names later once the server went live. I did that, but all of the URLs for archives (only archives) still pointed to the stupid domain name. I intended to fix this in 2.12 by using the fix_url function while I was also fixing a bunch of other stuff. I've needed to move some of my lists to other domains anyway, so this seemed like a good time. So I ran fix_url over almost all of my domains, and tested them as I went. Everything went as planned, except some of them still had the archives pointing to the recreational domain. Then it dawned on me that the ones that didn't get fixed were all *public* archives; the ones that did get fixed were all private. I went to one of the public archives and switched it to private, and the URL to the archives was then OK! Switched it back to public and it was wrong again. So, it seems that this is a bug. Or I've missed a configuration setting somewhere. Thanks Rob ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_i…

1 0

[ mailman-Bugs-784706 ] Clarify need for genaliases in UPGRADING
by SourceForge.net 07 Aug '03

07 Aug '03

Bugs item #784706, was opened at 2003-08-07 13:33 Message generated for change (Settings changed) made by thomas_ah You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784706&group_i… Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None >Priority: 4 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: Clarify need for genaliases in UPGRADING Initial Comment: mailman-2.1.2/UPGRADING says: NOTE: When upgrading to Mailman 2.1beta1, you will need to regenerate your aliases files. There have been many changes to the alias names, the programs they map to, and the name of the wrapper script. See README.<yourMTA> for details of making Mailman work with your mail server. I've upgraded from 2.0.13 to 2.1.2, this is not 2.1beta1, so I don't need to regenerate my aliases files. And the next paragraph says: To regenerate your aliases, use the bin/genaliases script. I've just learned that I don't need to update my aliases files, therefore this is only an information just in case I want to do it, but I don't want it now. To make this clear, you could write: NOTE: You will need to regenerate your aliases files. because this file is distributed with a Mailman version which needs the genaliases step. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784706&group_i…

1 0

[ mailman-Bugs-784706 ] Clarify need for genaliases in UPGRADING
by SourceForge.net 07 Aug '03

07 Aug '03

Bugs item #784706, was opened at 2003-08-07 13:33 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=784706&group_i… Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: Clarify need for genaliases in UPGRADING Initial Comment: mailman-2.1.2/UPGRADING says: NOTE: When upgrading to Mailman 2.1beta1, you will need to regenerate your aliases files. There have been many changes to the alias names, the programs they map to, and the name of the wrapper script. See README.<yourMTA> for details of making Mailman work with your mail server. I've upgraded from 2.0.13 to 2.1.2, this is not 2.1beta1, so I don't need to regenerate my aliases files. And the next paragraph says: To regenerate your aliases, use the bin/genaliases script. I've just learned that I don't need to update my aliases files, therefore this is only an information just in case I want to do it, but I don't want it now. To make this clear, you could write: NOTE: You will need to regenerate your aliases files. because this file is distributed with a Mailman version which needs the genaliases step. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784706&group_i…

1 0