Mailman 3 September 2005 - Mailman-coders

[ mailman-Bugs-1293267 ] Errno 36: filename too long -- stops mail delivery
by SourceForge.net Sept. 17, 2005

Sept. 17, 2005

Bugs item #1293267, was opened at 2005-09-16 21:00 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1293267&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: Andy Riebs (ariebs) Assigned to: Nobody/Anonymous (nobody) Summary: Errno 36: filename too long -- stops mail delivery Initial Comment: A user sent a Bugzilla page with an auto-generated filename (basically, the query used to generate the page) as an attachment. Unfortunately, this filename is long enough to overwhelm the pathname limit on Linux ext3 file systems. (See below.) This, in turn, prevents subsequent mail from being delivered. Version info: mailman-2.1.4-2.3.100mdk as distributed with Mandrake Linux release 10.0 (Official) for i586 For example, $ /usr/bin/python -S /usr/lib/mailman/cron/senddigests Traceback (most recent call last): File "/usr/lib/mailman/cron/senddigests", line 94, in ? main() File "/usr/lib/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/lib/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 227, in process url = save_attachment(mlist, part, dir, filter_html=False) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 445, in save_attachment fp = open(path, 'w') IOError: [Errno 36] File name too long: '/var/lib/mailman/archives/private/xx/attachments/20050915/6cfa4267/buglist.cgiquery_formatadvancedshort_desc_typeallwordssubstrshort_desccomponentXXlong_desc_typesubstringlong_descbug_file_loc_typeallwordssubstrbug_file_locbug_statusNEWbug_statusASSIGNEDbug_statusREOPENEDemailtype1substringemail1emailassigned_to21emailreporter21emailcc21emailtype2substringemail2bugidtypeincludebug_idvoteschfieldfromchfieldtoNowchfieldvaluefield0-0-0nooptype0-0-0noopvalue0-0-0orderbugs.html' ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2005-09-17 22:02 Message: Logged In: YES user_id=75166 Upgrading to MM 2.1.6 and setting the configuration variable mm_cfg.SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = True might avoid this problem ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1293267&group_…

1 0

[ mailman-Patches-1293919 ] Streamlined mail approval interface
by SourceForge.net Sept. 17, 2005

Sept. 17, 2005

Patches item #1293919, was opened at 2005-09-17 11:58 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=1293919&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: None Status: Open Resolution: None Priority: 5 Submitted By: Skip Montanaro (montanaro) Assigned to: Nobody/Anonymous (nobody) Summary: Streamlined mail approval interface Initial Comment: (Brad asked that I submit this.) I manage 10-15 mailing lists and needed a more efficient way to plow through mail held for review. Attached is the Python script I wrote (mmfold.py). It presents the messages one per line, just the subjects, and makes the default action "discard". (I wrote this around the same time, but somewhat before, the "discard defers" checkbox was added to Mailman.) I drive it with a simple shell function: function mmcheck { for url in http://mail.python.org/mailman/admindb/python-mode http://mail.python.org/mailman/admindb/pydotorg http://mail.python.org/mailman/admindb/python-dev do python ~/tmp/mmfold.py $url done } and execute the front-end script a couple times a week. Use it in good health. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1293919&group_…

1 0

[ mailman-Bugs-1293267 ] Errno 36: filename too long -- stops mail delivery
by SourceForge.net Sept. 16, 2005

Sept. 16, 2005

Bugs item #1293267, was opened at 2005-09-16 17: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=1293267&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: Andy Riebs (ariebs) Assigned to: Nobody/Anonymous (nobody) Summary: Errno 36: filename too long -- stops mail delivery Initial Comment: A user sent a Bugzilla page with an auto-generated filename (basically, the query used to generate the page) as an attachment. Unfortunately, this filename is long enough to overwhelm the pathname limit on Linux ext3 file systems. (See below.) This, in turn, prevents subsequent mail from being delivered. Version info: mailman-2.1.4-2.3.100mdk as distributed with Mandrake Linux release 10.0 (Official) for i586 For example, $ /usr/bin/python -S /usr/lib/mailman/cron/senddigests Traceback (most recent call last): File "/usr/lib/mailman/cron/senddigests", line 94, in ? main() File "/usr/lib/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/lib/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 227, in process url = save_attachment(mlist, part, dir, filter_html=False) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 445, in save_attachment fp = open(path, 'w') IOError: [Errno 36] File name too long: '/var/lib/mailman/archives/private/xx/attachments/20050915/6cfa4267/buglist.cgiquery_formatadvancedshort_desc_typeallwordssubstrshort_desccomponentXXlong_desc_typesubstringlong_descbug_file_loc_typeallwordssubstrbug_file_locbug_statusNEWbug_statusASSIGNEDbug_statusREOPENEDemailtype1substringemail1emailassigned_to21emailreporter21emailcc21emailtype2substringemail2bugidtypeincludebug_idvoteschfieldfromchfieldtoNowchfieldvaluefield0-0-0nooptype0-0-0noopvalue0-0-0orderbugs.html' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1293267&group_…

1 0

[ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1
by SourceForge.net Sept. 14, 2005

Sept. 14, 2005

Patches item #839386, was opened at 2003-11-10 13:04 Message generated for change (Comment added) made by adrianwi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&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: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Kev Green (kyrian) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL MemberAdaptor for Mailman 2.1 Initial Comment: A MemberAdaptor "plugin" which should allow Mailman list members to be loaded from a MySQL database, rather than just a Mailman "pickle" file. Provided as-is, and without warranty, this "plugin" may destroy your server, soul, scalp, house, and life. Please use it with caution. Kev Green, oRe Net. http://www.orenet.co.uk/ ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-09-14 14:32 Message: Logged In: YES user_id=1175103 Thank you for developing this adaptor! So far it's working well with the limited testing I've done. There seems to be a minor bug in the addNewMember method of this adaptor (version 1.61). At lines 579-584, there are SQL statements which add a new row in the MySQL database for a new member. In those statements, the column 'delivery_status' is given the value of MemberAdaptor.UNKNOWN. MemberAdaptor.py defines: # Delivery statuses ENABLED = 0 # enabled UNKNOWN = 1 # legacy disabled BYUSER = 2 # disabled by user choice BYADMIN = 3 # disabled by admin choice BYBOUNCE = 4 # disabled by bounces So, it appears that the SQL statements should be changed to use the value of MemberAdaptor.ENABLED instead of MemberAdaptor.UNKNOWN (which is "legacy disabled"). Making this change prevents "nomail [reason]" ? from being set in the user's options for new members (as seen in the web interface). This was tested with Mailman 2.1.6. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-07-27 07:38 Message: Logged In: YES user_id=99923 Folks, For my own sanity I have decided to create a dedicated area of my business website for various opensource projects, and put this project among others under there, so please refer to this location for updates to this patch in future: http://www.orenet.co.uk/opensource/ I will still be reading bug reports via sourceforge, but if nothing else, their user interface is much more fiddly and time consuming to publish files than a quick tar -czvf and an scp, so I'll be using my own environment to host the files at least for the time being. The latest version at this time is 1.61, I belive it still requires substantial testing which I'll get around to one of these days. K. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-05-31 13:57 Message: Logged In: YES user_id=99923 Folks, Well, I've finally gotten around to releasing an update to this thing, after a phone conversation with the client who are using it, and I've incorporated a couple of cosmetic fixes, fairly substantial changes to make the bounce processing work properly (the ability to set people to NOMAIL now exists, and real world testing is commencing soon), and incorporated the flat vs. wide table archivecture types with various bugfixes. Main notes: * It would be a good idea to change all your delivery_status fields from VARCHAR(255) to INT(10) or similar, so that they will work properly, and not bomb out on this new version (they should be okay I think, but I'd advise the change). * The missing-'AND' typo has been rectified. Any suggestions and bugs should be sent to my sourceforge account address, which ends up in the right place. K. ---------------------------------------------------------------------- Comment By: Gergely EGERVARY (egervary) Date: 2005-04-09 05:14 Message: Logged In: YES user_id=1255996 Thank you for your good work. FYI: there's a missing "AND" in MysqlMemberships.py in line 494. ---------------------------------------------------------------------- Comment By: simboforge (simboforge) Date: 2005-03-11 18:22 Message: Logged In: YES user_id=1226150 excellent. can you please give me a list of the files modified from the original distro? grep sees six that grep have msyql in them. thx ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-03-11 17:56 Message: Logged In: YES user_id=99923 The flat file databases are unused when you put the MySQL adaptor in place, and they are untouched (and indeed not deleted) by it, the MySQL adaptor only queries the MySQL tables for membership information, without trying to force you into using it fulltime by deleting anything, etc. Once you unconfigure the MySQL adaptor, Mailman should revert back to your existing flat file databases. Of course, I could have missed something, etc. so do back up your flat file databases before installing the MySQL adaptor, and then you can just migrate back to them by restoring the backups. Either way, you have come up with a good question for an FAQ on the SQL adaptor :-) K. ---------------------------------------------------------------------- Comment By: simboforge (simboforge) Date: 2005-03-11 17:42 Message: Logged In: YES user_id=1226150 neat. just what i was looking for. i have a couple of live lists running on version version 2.1.5. i am a bit leary about unzipping this distrobution over the top of my working mailman as i am not sure how to backup the existing flat file databases. i would prefer to experiment with dropping the adapter into my existing installation. any pointers as to where to start? thx ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-12-13 13:34 Message: Logged In: YES user_id=99923 Oh, btw. v1.57 hasn't been tested yet, so it might kill your server, eat your dog, and stick your wife in the oven. Be careful using it! ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-12-13 13:33 Message: Logged In: YES user_id=99923 Version 1.57: 2004/12/13 * Merge in Daniel Shriver patch/code for a flat table architecture. [ Suggested by Kevin McCann <kmccann(at)bellanet.org>, but I hadn't found time to do it myself... ] * Add bugfix information from Jinhyok Heo <novembre(a)NOSPAM.ournature.org> * Add in mksqlmailman script from TheSin <thesin(a)SPAMNOTHANKS.southofheaven.org> * Follow Barry Warsaw's suggestion on delivery status timestamp. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-01-08 06:38 Message: Logged In: YES user_id=99923 Latest version incorporates automated generation of the necessary tables, cleaner error reporting, and updated documentation. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2003-11-11 06:14 Message: Logged In: YES user_id=99923 Bit of an oops in version 1.49, 1.50 now uploaded, which should fix it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_i…

1 0

[ mailman-Feature Requests-843141 ] No date in archive overview
by SourceForge.net Sept. 13, 2005

Sept. 13, 2005

Feature Requests item #843141, was opened at 2003-11-16 08:28 Message generated for change (Comment added) made by ryanczak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=843141&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: Open Resolution: None Priority: 5 Submitted By: Bernhard Kuemel (darsie) Assigned to: Nobody/Anonymous (nobody) Summary: No date in archive overview Initial Comment: There is no date displayed for each message in the archive overview: http://rainbow.bksys.at/pipermail/test/2003-July/thread.html It may be argued if that's a bug or a feature - I prefer to see the dates. Bernhard ---------------------------------------------------------------------- Comment By: Matt Ryanczak (ryanczak) Date: 2005-09-13 13:46 Message: Logged In: YES user_id=1343484 Bernhard, I wrote a patch for mailman 2.1.6 that adds this functionality. It can be found here: http://sourceforge.net/tracker/index.php?func=detail&aid=1290317&group_id=1… Regards, Matt ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-11-24 16:42 Message: Logged In: YES user_id=12800 This is a feature request. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=843141&group_i…

1 0

[ mailman-Patches-1290317 ] add date field to the mail list archive index page
by SourceForge.net Sept. 13, 2005

Sept. 13, 2005

Patches item #1290317, was opened at 2005-09-13 13: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=1290317&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: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matt Ryanczak (ryanczak) Assigned to: Nobody/Anonymous (nobody) Summary: add date field to the mail list archive index page Initial Comment: I was asked to make the date for each message in a mailman archive be visible in the index for that month. This required that I modify HyperArch.py and the template file archidxentry.html. I thought others might find this useful so here is the relevant patch for the mailman-2.1.6 source tree. Apply the following patch to your mailman-2.1.6 source tree and build as usual. patch -p0 < date-in-archive-index.patch. This patch will modify the following files: mailman-2.1.6/Mailman/Archiver/HyperArch.py mailman-2.1.6/templates/ca/archidxentry.html mailman-2.1.6/templates/en/archidxentry.html mailman-2.1.6/templates/es/archidxentry.html mailman-2.1.6/templates/eu/archidxentry.html mailman-2.1.6/templates/fr/archidxentry.html mailman-2.1.6/templates/hr/archidxentry.html mailman-2.1.6/templates/hu/archidxentry.html mailman-2.1.6/templates/it/archidxentry.html mailman-2.1.6/templates/ja/archidxentry.html mailman-2.1.6/templates/lt/archidxentry.html mailman-2.1.6/templates/pl/archidxentry.html mailman-2.1.6/templates/pt/archidxentry.html mailman-2.1.6/templates/pt_BR/archidxentry.html mailman-2.1.6/templates/ro/archidxentry.html mailman-2.1.6/templates/ru/archidxentry.html mailman-2.1.6/templates/sl/archidxentry.html mailman-2.1.6/templates/sr/archidxentry.html mailman-2.1.6/templates/tr/archidxentry.html mailman-2.1.6/templates/uk/archidxentry.html mailman-2.1.6/templates/zh_CN/archidxentry.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1290317&group_…

1 0

[ mailman-Patches-1287546 ] Remove DomainKeys (and similar) header lines
by SourceForge.net Sept. 12, 2005

Sept. 12, 2005

Patches item #1287546, was opened at 2005-09-11 03:08 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287546&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: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Joe Peterson (skyrush) Assigned to: Nobody/Anonymous (nobody) Summary: Remove DomainKeys (and similar) header lines Initial Comment: This simple patch removes the header lines containing keys used in DomainKeys (Yahoo) and DKIM. The keys, if left in the header, will make the email seem forged or altered to the recipient, since Mailman alters header/body info. If the keys are removed, the MTA will generate new keys (if this is installed on the host). -Joe ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-09-12 17:59 Message: Logged In: YES user_id=12800 Applied to both Mailman 2.1 branch and trunk (2.2) ---------------------------------------------------------------------- Comment By: Joe Peterson (skyrush) Date: 2005-09-11 03:09 Message: Logged In: YES user_id=738814 Attached is the patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287546&group_…

1 0

[ mailman-Feature Requests-1286301 ] Feature Request: Mass Subscribe in Digest mode
by SourceForge.net Sept. 12, 2005

Sept. 12, 2005

Feature Requests item #1286301, was opened at 2005-09-09 13:25 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1286301&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: Dennis Behrens (djbehrens) Assigned to: Nobody/Anonymous (nobody) Summary: Feature Request: Mass Subscribe in Digest mode Initial Comment: I'd like to be able to do a mass subscribe to a mailman list and have all users in that mass subscribe to be placed into digest mode--especially if the list's default is set to individual messages. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-12 11:21 Message: Logged In: YES user_id=1123998 I agree that an additional radio selection for Regular/Digest (if the list allows both) on the Mass Subscribe page would be useful and convenient. Currently, whatever the setting is for digest_is_default, if you want to mass subscribe users for the other delivery mode, you have to change the digest_is_default setting, submit the mass subscribe and then change it back. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1286301&group_…

1 0

[ mailman-Patches-1287921 ] post log entries show envelope sender, not From:
by SourceForge.net Sept. 11, 2005

Sept. 11, 2005

Patches item #1287921, was opened at 2005-09-11 11:00 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=1287921&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: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: post log entries show envelope sender, not From: Initial Comment: The interpolation dictionary used with the SMTPDirect.py log messages includes 'sender' which is obtained with the Message.get_sender() method. If mm_cfg.USE_ENVELOPE_SENDER is Yes, this method returns the envelope sender which, since this is an outgoing message, is always the listname-bounces address. Since 'listname' is already in the dictionary, this is redundant. It would be more useful, at least for lists which aren't anonymous, to override this behavior and get the sender with get_sender(use_envelope=0) which would return the From: address. The patch makes this change. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287921&group_…

1 0

[ mailman-Patches-1287546 ] Remove DomainKeys (and similar) header lines
by SourceForge.net Sept. 11, 2005

Sept. 11, 2005

Patches item #1287546, was opened at 2005-09-11 01:08 Message generated for change (Comment added) made by skyrush You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287546&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: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Joe Peterson (skyrush) Assigned to: Nobody/Anonymous (nobody) Summary: Remove DomainKeys (and similar) header lines Initial Comment: This simple patch removes the header lines containing keys used in DomainKeys (Yahoo) and DKIM. The keys, if left in the header, will make the email seem forged or altered to the recipient, since Mailman alters header/body info. If the keys are removed, the MTA will generate new keys (if this is installed on the host). -Joe ---------------------------------------------------------------------- >Comment By: Joe Peterson (skyrush) Date: 2005-09-11 01:09 Message: Logged In: YES user_id=738814 Attached is the patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287546&group_…

1 0