Mailman-coders April 2004

mailman-coders@python.org

1 participants
57 discussions

[ mailman-Patches-931515 ] Provides more documentation for mass subscribing to the list
by SourceForge.net 08 Apr '04

08 Apr '04

Patches item #931515, was opened at 2004-04-08 01:15 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=931515&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Darrell Duane (progressd) Assigned to: Nobody/Anonymous (nobody) Summary: Provides more documentation for mass subscribing to the list Initial Comment: I've added documentation so that administrators who are mass subscribing members know the proper formats for associating names with e-mail addresses. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=931515&group_i…

1 0

[ mailman-Feature Requests-930969 ] Duplicated storage of attachments with MM 2.1
by SourceForge.net 07 Apr '04

07 Apr '04

Feature Requests item #930969, was opened at 2004-04-07 10:26 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=930969&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Duplicated storage of attachments with MM 2.1 Initial Comment: In Mailman 2.1.4 the process() function in $prefix/Mailman/ Handlers/Scrubber.py is called by instances of the ArchiverMailbox class ($prefix/Mailman/Mailbox.py) and by the process() function for the ToDigest handler ($prefix/Mailman/Handlers/ToDigest.py) via the send_digests() and send_i18n_digests() functions. In former case the function may extract attachments from a message before that message is archived by pipermail. In the latter case the function may extract attachments from a message before that message is added to a text-only digest that is being prepared. If extraction is done in both situations for the same message, this appears to lead to two copies of the same attachment being stored in different files in the relevant $prefix/archives/private/ <listname>/attachments/ directory. While not suggesting this is an easy problem to fix, the increase in disc storage for busy lists whose messages carry large attachments can be a problem. Optimising so that only one copy is saved seems appropriate. Incorporating a solution to this in Mailman 3 seems like a good thing. The problem can be ameliorated by setting the 'digestable' attribute of affected lists to No. As an aside, digests for digestable lists are constructed even if no list subscriber is a digest member. Again, an optimisation to avoid this wasted processing might be appropriate for Mailman 3. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=930969&group_i…

1 0

[ mailman-Bugs-930881 ] Messages being overwritten in PiperMail
by SourceForge.net 07 Apr '04

07 Apr '04

Bugs item #930881, was opened at 2004-04-07 09:46 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=930881&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Alek Andreev (aandreev) Assigned to: Nobody/Anonymous (nobody) Summary: Messages being overwritten in PiperMail Initial Comment: New messages sent to the mailing list do not appear as new messages in the Pipermail archive, but instead overwrite the latest, 12th message. So now in the archives there are the first 11 messages and the latest message at number 12. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930881&group_i…

1 0

[ mailman-Bugs-930819 ] Focus form entry onload in admlogin.html
by SourceForge.net 07 Apr '04

07 Apr '04

Bugs item #930819, was opened at 2004-04-07 00:13 Message generated for change (Comment added) made by kiko_async You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930819&group_i… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Christian Reis (kiko_async) Assigned to: Nobody/Anonymous (nobody) Summary: Focus form entry onload in admlogin.html Initial Comment: I run quite a few mailing lists, and boy is it annoying to have to click on each and every password box in the administration login page. So here's a patch that fixes the pages to use DOM-compliant javascript to focus the field (which is provably harmless in JS-deprived situations) ---------------------------------------------------------------------- >Comment By: Christian Reis (kiko_async) Date: 2004-04-07 00:14 Message: Logged In: YES user_id=222305 Tested and working locally: http://www.async.com.br/mailman/admin/kiwi ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930819&group_i…

1 0

[ mailman-Bugs-930819 ] Focus form entry onload in admlogin.html
by SourceForge.net 07 Apr '04

07 Apr '04

Bugs item #930819, was opened at 2004-04-07 00:13 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=930819&group_i… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Christian Reis (kiko_async) Assigned to: Nobody/Anonymous (nobody) Summary: Focus form entry onload in admlogin.html Initial Comment: I run quite a few mailing lists, and boy is it annoying to have to click on each and every password box in the administration login page. So here's a patch that fixes the pages to use DOM-compliant javascript to focus the field (which is provably harmless in JS-deprived situations) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930819&group_i…

1 0

[ mailman-Bugs-930469 ] Include text for held notification
by SourceForge.net 06 Apr '04

06 Apr '04

Bugs item #930469, was opened at 2004-04-06 07:17 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=930469&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stephen Samuel (darkonc) Assigned to: Nobody/Anonymous (nobody) Summary: Include text for held notification Initial Comment: When an email is held for moderation, the message sent should include the body of themessage itself (or, at least , the first few lines_ if it is text. This is simpy to hel identify the message... If nothing tlse, the text should be displayed for the 'delete message' dialogue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930469&group_i…

1 0

[ mailman-Bugs-930410 ] Error when using list info page to view a non-existant user
by SourceForge.net 06 Apr '04

06 Apr '04

Bugs item #930410, was opened at 2004-04-06 12:34 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=930410&group_i… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Andrew Yager (yogel) Assigned to: Nobody/Anonymous (nobody) Summary: Error when using list info page to view a non-existant user Initial Comment: After you have been logged in as an admin, and go back to the list info page to view a user profile, and you enter a user email address that doesn't exist, the following error occurs: Bug in Mailman version 2.1.4 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 "/home/mailmandir/mailman/scripts/driver", line 87, in run_main main() File "/home/mailmandir/mailman/Mailman/Cgi/options.py", line 226, in main password, user): File "/home/mailmandir/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/home/mailmandir/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/home/mailmandir/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/home/mailmandir/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/home/mailmandir/mailman/Mailman/ OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: user(a)somewhere.com Python information: Variable Value sys.version 2.3.2 (#1, Nov 7 2003, 22:27:17) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_COOKIE info+admin= SERVER_SOFTWARE Apache/2.0.48 (Unix) mod_ssl/2.0.48 OpenSSL/0.9.7a PHP/4.3.4 SCRIPT_NAME /mailman/options SERVER_SIGNATURE Apache/2.0.48 (Unix) mod_ssl/2.0.48 OpenSSL/0.9.7a PHP/4.3.4 Server at lists.mailmandir.org.au Port 80 REQUEST_METHOD POST PATH_INFO /info SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 78 HTTP_USER_AGENT Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/124 (KHTML, like Gecko) Safari/125.1 HTTP_CONNECTION close HTTP_REFERER http://lists.mailmandir.org.au/mailman/listinfo/info SERVER_NAME lists.mailmandir.org.au REMOTE_ADDR 211.30.19.65 PATH_TRANSLATED /home/mailmandir/mailman/www/info SERVER_PORT 80 SERVER_ADDR 192.168.2.99 DOCUMENT_ROOT /home/mailmandir/mailman/www/ PYTHONPATH /home/mailmandir/mailman SCRIPT_FILENAME /home/mailmandir/mailman/cgi-bin/options SERVER_ADMIN user(a)somewhere.com HTTP_HOST lists.mailmandir.org.au REQUEST_URI /mailman/options/info HTTP_ACCEPT */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 61245 HTTP_ACCEPT_LANGUAGE en-us, ja;q=0.33, en;q=0.67 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip, deflate;q=1.0, identity;q=0.5, *;q=0 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930410&group_i…

1 0

[ mailman-Bugs-930055 ] respond_to_post_requests is not configurable but should be
by SourceForge.net 05 Apr '04

05 Apr '04

Bugs item #930055, was opened at 2004-04-05 23:55 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=930055&group_i… Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Steffen Mueller (mixonx) Assigned to: Nobody/Anonymous (nobody) Summary: respond_to_post_requests is not configurable but should be Initial Comment: One can choose to send mail to poster when their posting is held for approval. To turn this on/off, respond_to_post_requests is set or unset. According to the comments in mailman/Mailman/MailList.py, respond_to_post_requests is configurable (as list default in Defaults.py as well as in mm_cfg.py), but it isn't. <--- snip 288 # This stuff is configurable 289 self.respond_to_post_requests = 1 ---> snap See attached patches to fix this. Using Mailman version 2.1.4 from Debian Backport 2.1.4-1.backports.org.1 But this appears in the latest 2.x CVS-tree, too. Thank you for mailman development. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930055&group_i…

1 0

[ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership
by SourceForge.net 05 Apr '04

05 Apr '04

Patches item #871062, was opened at 2004-01-05 17:09 Message generated for change (Comment added) made by the_olo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- Comment By: Aleksander Adamowski (the_olo) Date: 2004-04-05 13:47 Message: Logged In: YES user_id=244001 I suggest this patch to allow senders use any source address they might have set in LDAP (the 'mail' attribute can have multiple values!) --- LDAPMemberships.py.orig 2004-04-01 12:31:54.000000000 +0200 +++ LDAPMemberships.py 2004-04-05 15:40:03.000000000 +0200 @@ -115,7 +115,9 @@ # mail is unique mail = attrs['mail'][0].strip() self.__members.append(mail) - self.__member_map[mail] = mail + # mail can have multiple values + for secondarymail in attrs['mail']: + self.__member_map[secondarymail.strip()] = mail if attrs.has_key('mailalternateaddress'): malts = attrs['mailalternateaddress'] for malt in malts: ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-03-31 03:59 Message: Logged In: YES user_id=944208 Well, Mailman does a lot more than just keep track of who's subscribed -- for instance, restricted posters, list moderation, archiving. LDAPMemberships is not meant to be useful for Internet mailing lists with people signing up for them, but rather for institutional or enterprise lists. These have a lot of the same requirements (moderation etc.) as Internet lists, but don't need subscription/unsubscription -- since employees are usually required to be on them. My workplace is using this (well, actually a later version than the one I've uploaded here) as a replacement for an LDAP mailing-list feature in Netscape SuiteSpot now that we have migrated away from that system. We -also- use LDAP-based aliases (in Postfix, not Sendmail, actually) -- but for some things we need the moderation and other facilities that Mailman has. For instance, we have an announcements list that goes to all regular employees. A simple alias would allow anyone to send stuff to it, and certain senior scientists would love to send big PDFs to everyone. A Mailman list with LDAPMemberships can have sender restrictions so that only our IT Director and our mail systems admin can approve posts to it. Archiving is also quite useful for announcements lists. ---------------------------------------------------------------------- Comment By: Chris Drumgoole (cdrum) Date: 2004-03-31 03:38 Message: Logged In: YES user_id=429400 why use this when you can just use Sendmail's LDAP -> Alias functions? No need for a mailing list program like mailman.. right? ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-26 20:35 Message: Logged In: YES user_id=944208 Yet another new version (0.3) of LDAPMemberships.py. This one fixes some ambiguities with LDAP record handling, particularly for users with multiple "cn" values, and those who send mail as their "mailalternateaddress" field address rather than their "mail" field. If anyone is actually using this, please email me and let me know :) ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-20 16:53 Message: Logged In: YES user_id=944208 I've uploaded a new version (0.2) of LDAPMemberships.py. This one is some ungodly number of times faster, as it does not do redundant LDAP queries in a single load. ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 17:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_i…

1 0

[ mailman-Feature Requests-928714 ] "sender" variable substitutions in header/footer
by SourceForge.net 05 Apr '04

05 Apr '04

Feature Requests item #928714, was opened at 2004-04-02 19:58 Message generated for change (Comment added) made by jnewborn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=928714&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jason (jnewborn) Assigned to: Nobody/Anonymous (nobody) Summary: "sender" variable substitutions in header/footer Initial Comment: I want two new "sender" variable substitutions in for the header/footer. One should be the Sender's name and the other should be the sender's email address. For example: %(sender_name)s %(sender_email)s Adding this functonality will allow the headers/footers to contain links that point to the sender's information, bio, or public key (based on their name/email address). This is different than personalization because the sender's address is the same for all emails. ---------------------------------------------------------------------- >Comment By: Jason (jnewborn) Date: 2004-04-04 15:21 Message: Logged In: YES user_id=1012659 After a very brief glance at the code, this may be as simple as adding to the SafeDict definition in the decorate function of Mailman/Handlers/Decorate.py, although I'm not sure if or where the variables/arrays that I want are populated. Perhaps "msg.get_sender()" would work. Just trying to give someone a head start if they decide to take this on. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=928714&group_i…

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders April 2004