Mailman 3 June 2006 - Mailman-coders

[ mailman-Feature Requests-567096 ] list_members script export Name+Address
by SourceForge.net 10 Jun '06

10 Jun '06

Feature Requests item #567096, was opened at 2002-06-10 15:13 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=567096&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Rodolfo Pilas (alkalino) Assigned to: Nobody/Anonymous (nobody) Summary: list_members script export Name+Address Initial Comment: I uses MM 2.1b2+ (from CVS this month -June 2002) The mass subscription (web) option enables me to put one user address form each line with this format: Name Surname <name(a)address.com> and works ok. However the $PREFIX/bin/list_members script do not export with this format, it list name(a)address.com only. Please, add to list_members a complete user data exportation. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-06-10 12:47 Message: Logged In: YES user_id=1123998 Actually implemented in 2.1b4 (Oct 2002) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=567096&group_i…

1 0

[ mailman-Patches-1502441 ] newlist mail without prompt
by SourceForge.net 08 Jun '06

08 Jun '06

Patches item #1502441, was opened at 2006-06-07 12:06 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1502441&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: None >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Patrick Bogen (pdbogen) >Assigned to: Mark Sapiro (msapiro) Summary: newlist mail without prompt Initial Comment: bin/newlist should have an option to send a mail to the administrator without requiring the user to ansewr a prompt. The attached patch adds a '-a/--automate' option to accomplish this. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-06-08 08:34 Message: Logged In: YES user_id=1123998 Applied (somewhat differently because of new framework for bin/ and cron/ commands) to Subversion trunk for 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1502441&group_…

1 0

[ mailman-Patches-762130 ] web interface for editing archives
by SourceForge.net 07 Jun '06

07 Jun '06

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… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. 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: 2006-06-07 23:45 Message: Logged In: YES user_id=696276 The nightly cron script just runs "bin/arch --wipe" for any list with edited archives, so the pipermail URLs for particular messages in a list archive may change. Because of the way pipermail works, there's no easy solution that keeps the URLs the same and removes messages from mailman's mbox archives. (There might be a solution that keeps URLs the same if unwanted messages were replaced with empty placeholder messages instead, but I'm not sure you'd want empty messages cluttering up your archives, either.) Even if you haven't edited the mbox file, badly formed date stamps will also cause your pipermail URLs to change if you ever run "bin/arch --wipe" because messages with bad dates get thrown into the current month. ---------------------------------------------------------------------- Comment By: Paul Wise (pabs3) Date: 2006-06-06 23:22 Message: Logged In: YES user_id=35028 How does this handle the changing of pipermail URLs when you delete messages? ---------------------------------------------------------------------- Comment By: Adriane Boyd (aaboyd) Date: 2006-06-02 19:57 Message: Logged In: YES user_id=696276 Updated patch to work with 2.1.8: fixed problems with mailbox.py and updated to patch cleanly against 2.1.8. ---------------------------------------------------------------------- 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-Patches-1502441 ] newlist mail without prompt
by SourceForge.net 07 Jun '06

07 Jun '06

Patches item #1502441, was opened at 2006-06-07 14:06 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=1502441&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Patrick Bogen (pdbogen) Assigned to: Nobody/Anonymous (nobody) Summary: newlist mail without prompt Initial Comment: bin/newlist should have an option to send a mail to the administrator without requiring the user to ansewr a prompt. The attached patch adds a '-a/--automate' option to accomplish this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1502441&group_…

1 0

[ mailman-Patches-762130 ] web interface for editing archives
by SourceForge.net 06 Jun '06

06 Jun '06

Patches item #762130, was opened at 2003-06-28 06:05 Message generated for change (Comment added) made by pabs3 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=762130&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. 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: Paul Wise (pabs3) Date: 2006-06-07 11:22 Message: Logged In: YES user_id=35028 How does this handle the changing of pipermail URLs when you delete messages? ---------------------------------------------------------------------- Comment By: Adriane Boyd (aaboyd) Date: 2006-06-03 07:57 Message: Logged In: YES user_id=696276 Updated patch to work with 2.1.8: fixed problems with mailbox.py and updated to patch cleanly against 2.1.8. ---------------------------------------------------------------------- Comment By: Adriane Boyd (aaboyd) Date: 2003-08-12 05: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-Feature Requests-1501086 ] Make confirm links in email optional
by SourceForge.net 05 Jun '06

05 Jun '06

Feature Requests item #1501086, was opened at 2006-06-05 08:56 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=1501086&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: John W. Baxter (jwbaxter) Assigned to: Nobody/Anonymous (nobody) Summary: Make confirm links in email optional Initial Comment: An organization which attempts to train its members or employees (or otherwise-involved critters) never to click on links in email messages should not itself send out messages containing links with suggestions to click them. In today's malware world, such an organization is acting sensibly. In the present mailman, the goal can be achieved by adjusting message templates. It would seem better--despite the desire not to have options proliferate endlessly--to provide an option in the list configuration to disable such links. (That would probably not include disabling the RFC list headers, which can already be disabled separately.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1501086&group_…

1 0

[ mailman-Patches-1482427 ] Migration 2.0.5 to 2.1.5 bug + fix
by SourceForge.net 04 Jun '06

04 Jun '06

Patches item #1482427, was opened at 2006-05-05 04:57 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1482427&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configure/install Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Markus Neteler (mneteler) Assigned to: Nobody/Anonymous (nobody) Summary: Migration 2.0.5 to 2.1.5 bug + fix Initial Comment: Hi, we are happy mailman users for many years and finally made the update yesterday. But there was a detail which needs to be fixed: ## from 2.0.5 to ## mailman-2.1.5.1-34.rhel4.2 # modify in file /usr/lib/mailman/bin/dumpdb # BAW: this probably doesn't work if there are mixed types of .db # files (i.e. some marshals, some bdbs). d = DumperSwitchboard().read(filename) to import marshal ... # BAW: this probably doesn't work if there are mixed types of .db # files (i.e. some marshals, some bdbs). fp = open(filename) d = marshal.load(fp) fp.close() Only then it will work (we were seeking for two hours to figure out... :-) This would solve this problem as well apparently: http://mail.python.org/pipermail/mailman-users/2005-February/042654.html Kind regards Markus Neteler http://grass.itc.it ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-06-04 08:46 Message: Logged In: YES user_id=1123998 Fixed in subversion trunk. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1482427&group_…

1 0

[ mailman-Patches-762130 ] web interface for editing archives
by SourceForge.net 02 Jun '06

02 Jun '06

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… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. 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: 2006-06-02 19:57 Message: Logged In: YES user_id=696276 Updated patch to work with 2.1.8: fixed problems with mailbox.py and updated to patch cleanly against 2.1.8. ---------------------------------------------------------------------- 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-Feature Requests-1497366 ] Differentiate between subscribers/others for held messages
by SourceForge.net 02 Jun '06

02 Jun '06

Feature Requests item #1497366, was opened at 2006-05-30 01:03 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1497366&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: None >Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jonas Maebe (jmaebe) Assigned to: Nobody/Anonymous (nobody) Summary: Differentiate between subscribers/others for held messages Initial Comment: I've turned off notifications about messages held for approval, since virtually all of them are spam with forged from-addresses and I don't want to inundate random people with such notifications. However, every now and then the reason is that a subscriber tried to send too big an attachment, or because a mail triggered my html regexp in the privacy filters. Therefore I would like to propose an option to only send "Message held for approval" messages to subscribers, but not to anyone else. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-06-02 15:42 Message: Logged In: YES user_id=1123998 Moved to Feature Requests because that's what it is. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1497366&group_…

1 0

[ mailman-Feature Requests-1474203 ] A junk Mail button would be great
by SourceForge.net 01 Jun '06

01 Jun '06

Feature Requests item #1474203, was opened at 2006-04-21 15:23 Message generated for change (Comment added) made by zwiskle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1474203&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Narishkup (mikekatz) Assigned to: Nobody/Anonymous (nobody) Summary: A junk Mail button would be great Initial Comment: I would love a junk mail button in the administrators review of defered messages section. That button would with one click delete the message and put the senders domain on the rejected domain list. Currently it is a 4 click proccess to put each ban people but domains are even harder to restrict. This should be a button in addition to the existing choices so that less drastic action could also be taken. Thanks so mucch fo a great product. ---------------------------------------------------------------------- Comment By: zwiskle (zwiskle) Date: 2006-06-01 21:11 Message: Logged In: YES user_id=1130747 maybe there could be some more logic in behind - e.g. feed this spam-mail to spamassassin-learn. ( or forward this to a spam-learn email-account ) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1474203&group_…

1 0