Mailman 3 April 2006 - Mailman-coders

[ mailman-Bugs-1469962 ] Attachments with ' just hang
by SourceForge.net April 13, 2006

April 13, 2006

Bugs item #1469962, was opened at 2006-04-13 12:36 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=1469962&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: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: cpkevin (xprt5) Assigned to: Nobody/Anonymous (nobody) Summary: Attachments with ' just hang Initial Comment: If someone sends an email with the character ' in the subject or attachment name mailman hangs. after deleting the ' in the attachment name in /usr/local/cpanel/3rdparty/mailman/lists/list_name/digest.mbox the next message is delivered (but this message isn't delivered!) Apr 11 23:04:22 2006 (60899) Uncaught runner exception: need more than 2 values to unpack This was working fine before a recent upgrade with mailman/python and still works fine on other servers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1469962&group_…

1 0

[ mailman-Bugs-1461054 ] Wrong domain used in moderation message
by SourceForge.net April 13, 2006

April 13, 2006

Bugs item #1461054, was opened at 03/29/06 16:44 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1461054&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: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Eric Smith (brouhaha) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong domain used in moderation message Initial Comment: Mailman 2.1.7 is running on host foo.example.com, with a mailing list on virtual domain bar.example.com. If a posting will be moderated, an email is sent to the poster offering a chance to cancel the message. However, the cancel URL is on foo.example.com, rather than bar.example.com. The cancel URL works, but it exposes the real hostname, whereas it should only show the virtual domain. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 04/12/06 19:20 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 03/29/06 17:14 Message: Logged In: YES user_id=1123998 The most likely cause of this is that the list attribute web_page_url has the foo.example.com host name instead of bar.example.com. This in turn is caused by creating the list with the wrong or the default host. If this is the case, links in the web interface will likely also be to foo.example.com, and the list won't appear on the bar.example.com admin and listinfo overview pages. You can fix this (assuming your VIRTUAL_HOSTS dictionary is correct - add_virtualhost() directives in mm_cfg.py - by running bin/fix_url.py on the list (just run bin/fix_url.py for instructions). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1461054&group_…

1 0

[ mailman-Feature Requests-1469343 ] Per-user Reply-To mungling for sent mails
by SourceForge.net April 12, 2006

April 12, 2006

Feature Requests item #1469343, was opened at 2006-04-12 15:16 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=1469343&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: Timo Sirainen (cras) Assigned to: Nobody/Anonymous (nobody) Summary: Per-user Reply-To mungling for sent mails Initial Comment: This feature request isn't the same as the existing ones about per-user reply-to mungling (eg. 788314). I like the ability for users to be able to select if they want to get both private and list replies (highly useful in big traffic lists) or only list replies (if you're going to read all the mails in the list anyway). Now this is already possible assuming that everyone hits Reply-to-all, which I think is what most people do. However for those who want only the list replies, they need to set "Reply-To: list" header for their own mails. This is impossible or difficult to configure to be automatic in most email clients. So, a user-specific option to specify if the Reply-To header should be added to mails the user himself sends would be nice. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1469343&group_…

1 0

[ mailman-Patches-1469076 ] Updated Vietnamese translation 2.1.8rc1
by SourceForge.net April 12, 2006

April 12, 2006

Patches item #1469076, was opened at 2006-04-12 17:24 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=1469076&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: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Clytie Siddall (clytie) Assigned to: Nobody/Anonymous (nobody) Summary: Updated Vietnamese translation 2.1.8rc1 Initial Comment: Here's the updated translation. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1469076&group_…

1 0

[ mailman-Patches-1464767 ] XMLRPC patch for Mailman 2.1.7
by SourceForge.net April 5, 2006

April 5, 2006

Patches item #1464767, was opened at 2006-04-05 10:43 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=1464767&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: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Rafal Krzewski (rkrzewsk) Assigned to: Nobody/Anonymous (nobody) Summary: XMLRPC patch for Mailman 2.1.7 Initial Comment: The patch is based on the work of Joshua Ginsberg and Joseph Tate hosted at http://savannah.nongnu.org/projects/mailman-xmlrpc/ + modifications developed by Caltha: - New methods added to the interface: getLocales, getPendingMessages, getPendingSubscriptions, getNewPendingTasks, getPendingTask, getPendingTaskType, handleModerationRequest, postmessage (documentation included in the respective methods) - XMLRPC.py was split into XMLRPCHandler class, XMPRPC (CGI server endpoint), StandaloneXMLRPC (standalone/daemon server endpoint) - added configuration option for performing site admin authentication on all methods. By default the methods operating on a specific list require list admin authentication. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1464767&group_…

1 0

[ mailman-Patches-1463918 ] Make password mailing RFC 3834 compliant
by SourceForge.net April 4, 2006

April 4, 2006

Patches item #1463918, was opened at 2006-04-03 17:24 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=1463918&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: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Kyle VanderBeek (kylev) Assigned to: Nobody/Anonymous (nobody) Summary: Make password mailing RFC 3834 compliant Initial Comment: RFC 3834 specifies that messages generated automatically by periodic automatic jobs should contain an Auto-Submitted header with a 'auto-generated' value; a 1-line patch does this for the cron'ed month membership reminder. This helps avoid loops and potential "sorcerers apprentice mode" when hitting well mannered vaction programs that recognize RFC 3834 headers. There is probably more work to do in mailman related to this RFC, as well. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1463918&group_…

1 0

[ mailman-Bugs-1462479 ] mailman 2.1.7 not on ftp.gnu.org
by SourceForge.net April 3, 2006

April 3, 2006

Bugs item #1462479, was opened at 2006-03-31 18:57 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1462479&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: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: mailman 2.1.7 not on ftp.gnu.org Initial Comment: the web page on list.org says that the current version of mailman is downloadable from GNU, but ftp.gnu.org doesn't actually have 2.1.7 (or 2.1.6). >From the lack of .sig files in ftp.gnu.org/gnu/mailman, I surmise your gpg keys may never have gotten registered by sysadmin to enable ftp uploads. here's the bit from maintain.texi about that procedure in case it helps: http://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html Best, Karl ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-04-03 11:14 Message: Logged In: YES user_id=12800 I've sent a new registration message to ftp-upload, with Tokio's key. Assigning this one to him so he can try to do an upload when we get a response. ---------------------------------------------------------------------- Comment By: karl berry (kberry) Date: 2006-04-01 20:07 Message: Logged In: YES user_id=33248 Hi Barry, The only way to check is to try an upload and see if it works. Since you were registered once, I know of no reason why you would have been de-registered. If it fails, I guess you should mail ftp-upload(a)gnu.org with the info from maintain.texi (which translates to GNU sysadmin). Ditto for getting Tokio registered. Regards, k ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-04-01 19:55 Message: Logged In: YES user_id=12800 At one point, my GPG key was definitely registered since I've done uploads of mailman before. I guess we should try to get Tokio registered too so he can do file uploads (I'll still have to do the ones to list.org) Is there a way to check whether my key is registered, or may have gotten lost? Or should I just re-register them? BTW, my pubkeys are always available at http://barry.warsaw.us ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1462479&group_…

1 0

[ mailman-Bugs-1462479 ] mailman 2.1.7 not on ftp.gnu.org
by SourceForge.net April 2, 2006

April 2, 2006

Bugs item #1462479, was opened at 2006-03-31 23:57 Message generated for change (Comment added) made by kberry You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1462479&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: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: mailman 2.1.7 not on ftp.gnu.org Initial Comment: the web page on list.org says that the current version of mailman is downloadable from GNU, but ftp.gnu.org doesn't actually have 2.1.7 (or 2.1.6). >From the lack of .sig files in ftp.gnu.org/gnu/mailman, I surmise your gpg keys may never have gotten registered by sysadmin to enable ftp uploads. here's the bit from maintain.texi about that procedure in case it helps: http://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html Best, Karl ---------------------------------------------------------------------- >Comment By: karl berry (kberry) Date: 2006-04-02 01:07 Message: Logged In: YES user_id=33248 Hi Barry, The only way to check is to try an upload and see if it works. Since you were registered once, I know of no reason why you would have been de-registered. If it fails, I guess you should mail ftp-upload(a)gnu.org with the info from maintain.texi (which translates to GNU sysadmin). Ditto for getting Tokio registered. Regards, k ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-04-02 00:55 Message: Logged In: YES user_id=12800 At one point, my GPG key was definitely registered since I've done uploads of mailman before. I guess we should try to get Tokio registered too so he can do file uploads (I'll still have to do the ones to list.org) Is there a way to check whether my key is registered, or may have gotten lost? Or should I just re-register them? BTW, my pubkeys are always available at http://barry.warsaw.us ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1462479&group_…

1 0

[ mailman-Bugs-1462479 ] mailman 2.1.7 not on ftp.gnu.org
by SourceForge.net April 2, 2006

April 2, 2006

Bugs item #1462479, was opened at 2006-03-31 18:57 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1462479&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: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: mailman 2.1.7 not on ftp.gnu.org Initial Comment: the web page on list.org says that the current version of mailman is downloadable from GNU, but ftp.gnu.org doesn't actually have 2.1.7 (or 2.1.6). >From the lack of .sig files in ftp.gnu.org/gnu/mailman, I surmise your gpg keys may never have gotten registered by sysadmin to enable ftp uploads. here's the bit from maintain.texi about that procedure in case it helps: http://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html Best, Karl ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2006-04-01 19:55 Message: Logged In: YES user_id=12800 At one point, my GPG key was definitely registered since I've done uploads of mailman before. I guess we should try to get Tokio registered too so he can do file uploads (I'll still have to do the ones to list.org) Is there a way to check whether my key is registered, or may have gotten lost? Or should I just re-register them? BTW, my pubkeys are always available at http://barry.warsaw.us ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1462479&group_…

1 0