Mailman 3 March 2006 - Mailman-coders

[ mailman-Bugs-1461279 ] Filtering content while allowing HTML messages impossible
by SourceForge.net 30 Mar '06

30 Mar '06

Bugs item #1461279, was opened at 2006-03-30 12:41 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=1461279&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: Open Resolution: None Priority: 5 Submitted By: - (psy-q) Assigned to: Nobody/Anonymous (nobody) Summary: Filtering content while allowing HTML messages impossible Initial Comment: I hope this is a genuine bug. I'll use 2.1.7 in these examples, though I verified this behavior in 2.1.5 also. I have a mailing list configured as such: filter_content = 1 filter_mime_types = '' pass_mime_types = """multipart/mixed multipart/alternative text/plain text/html""" collapse_alternatives = 0 convert_html_to_plaintext = 0 filter_action = 2 And yet all HTML messages are automatically stripped of HTML, have their attachments removed and are immediately posted to the list. The originals are sent as multipart/alternative with two attachments, one the text/plain rendition of the message and one the text/html original. It seems to be okay, user agents can render this message as intended. All that remains when delivered by Mailman is the text/plain bit, though. Shouldn't this list configuration let HTML mails through? I can't see a reason why Mailman should remove the HTML silently with these settings. If filter_content is turned off, sending HTML messages works. (I know it's not polite to send HTML messages through mailing lists, but some of my users insist.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1461279&group_…

1 0

[ mailman-Bugs-1459022 ] Postfix.py and aliases (#CREATED:xxx)
by SourceForge.net 30 Mar '06

30 Mar '06

Bugs item #1459022, was opened at 2006-03-26 18:30 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1459022&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: configuring/installing Group: 2.1 alpha Status: Open Resolution: Works For Me Priority: 5 Submitted By: Bob Holden (eawf) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix.py and aliases (#CREATED:xxx) Initial Comment: CentOS4.2 Installed Mailman2.1.5 via YUM. Postfix Configured Automatic aliases file creation. When creating list from ./newlist, no problems. When creating list from web, got bug page, and discovered an alias entry, "#CREATED:...". While not being a Python programmer, glancing through the Postfix.py file, it looks like when looping through the STANZA section to create the aliases file, the commented #CREATED: line isn't ignored, causing the record to be created. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-03-29 19:45 Message: Logged In: YES user_id=1123998 I think the line you're referring to is print >> fp, '# CREATED:', time.ctime(time.time()) Which occurs in two places, one for the 'aliases' file and one for the 'virtual-mailman' file if any. It writes a line like # CREATED: Wed Mar 29 19:31:24 2006 (with the current date and time) into the file. This line in the 'aliases' or 'virtual-mailman' file begins with '#' and thus is a comment in that file just as are the lines # STANZA START: listname preceding the # CREATED line and # STANZA END: listname following the actual data. Why is this "# CREATED: ..." line a problem? Going back to your original issue, what is the traceback from the "bug" from Mailman's 'error' log? I don't think this 'bug' has anything to do with the print statements you commented or with the presence or absence of the "# CREATED: ..." line in the resultant file. The "# CREATED: ..." line is documentation. The code that looks at the "# STANZA: ..." lines is figuring out what to delete from the files when you delete a list. ---------------------------------------------------------------------- Comment By: Bob Holden (eawf) Date: 2006-03-29 18:55 Message: Logged In: YES user_id=483098 Interestingly, when I commented out both of the "CREATED: print statements, the problem went away. Only thing I can figure from that is that programmatically, when creating the aliases file, the commented CREATED: line is not being ignored or skipped over. Again, glancing through the code I see checking for the STANZA lines, but not the CREATED line. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-03-26 18:59 Message: Logged In: YES user_id=1123998 Both bin/newlist and the Cgi create script invoke the exact same Mailman/MTA/Postfix.py module to update the aliases. The only difference is the user/group under which it runs. Thus, this is most likely a problem with the 'mailman' group not having write permission on data/aliases*. Both data/aliases and data/aliases.db should be group owned by the 'mailman' group and be group writable. This may be FAQ 6.9 - http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.009.htp If this is not a permissions issue, please post the traceback from the "bug" from Mailman's error log. Note that the "#CREATED:" line in the aliases file is a comment and is intended to be there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1459022&group_…

1 0

[ mailman-Bugs-1459022 ] Postfix.py and aliases (#CREATED:xxx)
by SourceForge.net 30 Mar '06

30 Mar '06

Bugs item #1459022, was opened at 2006-03-26 18:30 Message generated for change (Comment added) made by eawf You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1459022&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: configuring/installing Group: 2.1 alpha Status: Open >Resolution: Works For Me Priority: 5 Submitted By: Bob Holden (eawf) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix.py and aliases (#CREATED:xxx) Initial Comment: CentOS4.2 Installed Mailman2.1.5 via YUM. Postfix Configured Automatic aliases file creation. When creating list from ./newlist, no problems. When creating list from web, got bug page, and discovered an alias entry, "#CREATED:...". While not being a Python programmer, glancing through the Postfix.py file, it looks like when looping through the STANZA section to create the aliases file, the commented #CREATED: line isn't ignored, causing the record to be created. ---------------------------------------------------------------------- >Comment By: Bob Holden (eawf) Date: 2006-03-29 18:55 Message: Logged In: YES user_id=483098 Interestingly, when I commented out both of the "CREATED: print statements, the problem went away. Only thing I can figure from that is that programmatically, when creating the aliases file, the commented CREATED: line is not being ignored or skipped over. Again, glancing through the code I see checking for the STANZA lines, but not the CREATED line. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-03-26 18:59 Message: Logged In: YES user_id=1123998 Both bin/newlist and the Cgi create script invoke the exact same Mailman/MTA/Postfix.py module to update the aliases. The only difference is the user/group under which it runs. Thus, this is most likely a problem with the 'mailman' group not having write permission on data/aliases*. Both data/aliases and data/aliases.db should be group owned by the 'mailman' group and be group writable. This may be FAQ 6.9 - http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.009.htp If this is not a permissions issue, please post the traceback from the "bug" from Mailman's error log. Note that the "#CREATED:" line in the aliases file is a comment and is intended to be there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1459022&group_…

1 0

[ mailman-Bugs-1461054 ] Wrong domain used in moderation message
by SourceForge.net 30 Mar '06

30 Mar '06

Bugs item #1461054, was opened at 2006-03-29 16:44 Message generated for change (Comment added) made by msapiro 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: Pending 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: Mark Sapiro (msapiro) Date: 2006-03-29 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-Bugs-1461054 ] Wrong domain used in moderation message
by SourceForge.net 30 Mar '06

30 Mar '06

Bugs item #1461054, was opened at 2006-03-29 16:44 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=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: Open 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1461054&group_…

1 0

[ mailman-Feature Requests-1460796 ] Add option to remove Sender header
by SourceForge.net 29 Mar '06

29 Mar '06

Feature Requests item #1460796, was opened at 2006-03-29 12:04 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=1460796&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: Myke Olson (xpl0re) Assigned to: Nobody/Anonymous (nobody) Summary: Add option to remove Sender header Initial Comment: When sending messages through mailman with Postfix, it adds a new header called "Sender" in addition to the Errors-To and Return-Path headers. Outlook (probably mistakenly) sees the Sender header and treats it like gold. All messages show up in the user's mailbox as from list-bounces on behalf of therealperson. What's worse is that the rules/filters will only work on the list-bounces part and not therealperson. If we could selectively turn off the addition of the Sender header (and be able to keep the other two), then we should still be able to use bounces but have Outlook be able to filter messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1460796&group_…

1 0

[ mailman-Bugs-1460792 ] Held message for administrivia unclear
by SourceForge.net 29 Mar '06

29 Mar '06

Bugs item #1460792, was opened at 2006-03-29 12: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=1460792&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: Open Resolution: None Priority: 5 Submitted By: Joshua Ginsberg (jaginsberg) Assigned to: Nobody/Anonymous (nobody) Summary: Held message for administrivia unclear Initial Comment: My employer suggested that the error message: "Message may contain administrivia" presented in a "message held" email is unclear and does not adequately present the poster with his/her options. He suggests it read: > The reason it is being held: > > Message looks like a request to subscribe or unsubscribe > from the list. Such requests should not go to the whole list. > > It could also say how to contact the moderator. Regardless of whether you accept his specific recommendation, this language could certainly be clearer for those unfamiliar with the administrivia filter or even the term administrivia. -jag ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1460792&group_…

1 0

[ mailman-Patches-1460655 ] Howto info for Internationalization page
by SourceForge.net 29 Mar '06

29 Mar '06

Patches item #1460655, was opened at 2006-03-29 23:37 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=1460655&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: Howto info for Internationalization page Initial Comment: Here is a basic Howto for translating Mailman. This file is HTML, so I hope you can simply insert it into your Internationalization page at your GNU homepage. The only edit required will be an anchor to the Mailman Language Champions table, unless it is simply below this text. Otherwise, it's basic, but it answers the questions new translators will probably ask. Anyone is welcome to edit it. I hope it is useful. :) from Clytie, Vietnamese translator ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1460655&group_…

1 0

[ mailman-Patches-1460471 ] New Vietnamese translation (2.1.8b1)
by SourceForge.net 29 Mar '06

29 Mar '06

Patches item #1460471, was opened at 2006-03-29 17:01 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=1460471&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: New Vietnamese translation (2.1.8b1) Initial Comment: Here is the Vietnamese translation of the interface file (/messages) for Mailman 2.1.8b1. I will be working through the html templates gradually. Enjoy! :) Please also add me, as requested, to the Mailman language champions. Thankyou. Clytie, Vietnamese translator ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1460471&group_…

1 0

[ mailman-Patches-1459818 ] New Arabic translation
by SourceForge.net 28 Mar '06

28 Mar '06

Patches item #1459818, was opened at 2006-03-28 10:38 Message generated for change (Comment added) made by munzirtaha You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1459818&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: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Munzir Taha (munzirtaha) Assigned to: Nobody/Anonymous (nobody) Summary: New Arabic translation Initial Comment: Attached is an Arabic translation of mailman. ---------------------------------------------------------------------- >Comment By: Munzir Taha (munzirtaha) Date: 2006-03-28 13:21 Message: Logged In: YES user_id=1044850 I would close it since somehow it posted twice while attaching the translation. Duplicate of http://sourceforge.net/tracker/index.php?func=detail&aid=1459897&group_id=1… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1459818&group_…

1 0