Patches item #871062, was opened at 2004-01-05 12:09
Message generated for change (Comment added) made by fubarobfusco
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: K. A. Krueger (fubarobfusco)
Date: 2004-01-26 15: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 11: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 12: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…
Patches item #671057, was opened at 2003-01-20 09:02
Message generated for change (Comment added) made by chomo
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=671057&group_i…
Category: command line scripts
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Fil (filfil)
Assigned to: Nobody/Anonymous (nobody)
Summary: a shell script for lists backup
Initial Comment:
#################### mailman_save_lists.sh #####################
# v0.14 2003-01-14 11:30
#
# this script saves a copy of mailman lists and config files
# call this script regularly from the 'mailman' user
# e.g. daily from crontab
# 01 08 * * * /path/to/mailman_save_lists.sh
#
# we do save lists each time in compressed form: either they
# are big and we can imagine they change each time, or they
# are very small and we don't care
#
# comments to: <fil+mailman(a)rezo.net>
#
# please configure below: where lists are to be found,
# and where states are to be saved (must be 'mailman'-writable)
########
mailman=/home/mailman
lists=$mailman/lists/
state=/var/state/mailman/
########
----------------------------------------------------------------------
Comment By: alan johnson (chomo)
Date: 2004-01-21 21:06
Message:
Logged In: YES
user_id=943591
yes right
----------------------------------------------------------------------
Comment By: Fil (filfil)
Date: 2003-01-20 09:05
Message:
Logged In: YES
user_id=243444
Can I attach a file? Second try.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=671057&group_i…
Bugs item #715581, was opened at 2003-04-04 21:50
Message generated for change (Comment added) made by fjpb
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_i…
Category: mail delivery
Group: 2.1 (stable)
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Ricardo Kustner (rixhq)
Assigned to: Nobody/Anonymous (nobody)
Summary: plain text digest bug in appending messages
Initial Comment:
Sometimes, messages are incorrectly appended in the plain digests, which cause 2 or more messages to be attached to 1. For example, I got a digest which mentions one message in the Topic list, but at the end of this message, the next message is "glued" to the bottom of it:
(...top of first message...)
---------------------------------
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!From EMAILADDR(a)aol.com Fri Mar 28 14:04:32 2003
Return-Path: <EMAILADDR(a)aol.com>
Delivered-To: fans(a)list.miss-janet.com
(...second message continues with all it's headers and content)
As you can see, the "From..." of the second message starts directly after the last character of the first message.
Here's a second example:
(... top of first message...)
peace out:
-oscarFrom EMAILADDR(a)aol.com Tue Apr 1 15:04:42 2003
Return-Path: <EMAILADDR(a)aol.com>
Delivered-To: fans(a)list.miss-janet.com
(..second message continues...)
Again, the "From..." from the next message is glued to the previous message.
Is this a simple missing end of line issue or is it more complicated?
I can't seem to see a good pattern in it...
Ricardo.
----------------------------------------------------------------------
Comment By: Fred Bone (fjpb)
Date: 2004-01-21 18:09
Message:
Logged In: YES
user_id=956771
Is the first message originally in quoted-printable, with no
concluding blank line?
I have seen quite a lot of concatenated messages lately, and
in every instance that I've checked the first message is QP, is
multipart/alternative with the other part in html (stripped for
digest), and has the boundary immediately after the last line of
the QP part.
The problem affects MIME-digests as well as plaintext ones.
I have no clue how it might be fixed, or even where things are
going wrong, but maybe someone else can get a handle on it
from this info.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_i…
Bugs item #881369, was opened at 2004-01-21 13:42
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=881369&group_i…
Category: None
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Jouni K Seppänen (jouni)
Assigned to: Nobody/Anonymous (nobody)
Summary: Double HTML encoding of non-ASCII list description
Initial Comment:
I created in Mailman 2.1.4 a list whose description
included some non-ASCII characters, e.g. "ä". Both on
the web page and in the List-ID header these were
HTML-encoded twice. That is, the HTML source of the
listinfo page replaces the character "ä" by ten
characters: ampersand, a, m, p, semicolon, hash, 2, 2,
8, semicolon, so that the user sees ampersand, hash, 2,
2, 8, semicolon. Also the List-ID header encodes "ä"
using these ten characters.
It seems that if I change the list's preferred language
to Finnish and re-enter the description, it gets
encoded correctly: the HTML source simply uses the
character directly, and the List-ID header uses RFC
2047 encoding. However, I don't like the Finnish
translation of the Mailman pages, so I want to use
English as the preferred language.
(There seems to be a work-around: I can set the
language to Finnish, then set the description, then
change the language back to English.)
It could be argued that if the language is set to
English (USA), Mailman has no way of knowing *a priori*
which encoding to use for eight-bit characters. In this
case, would it make sense to add a language called
"English (ISO Latin 1)", or "English (West-European)",
or something similar, for those of us who like the
English user interface but communicate in other
languages? Or possibly a separate configuration option
for the character set?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=881369&group_i…
Bugs item #880543, was opened at 2004-01-20 07:57
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880543&group_i…
Category: configuring/installing
Group: 2.0.x
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Ismael Olea (olea)
Assigned to: Nobody/Anonymous (nobody)
Summary: Impossible to recover lost admin-list passwords
Initial Comment:
I couldn't find a way to set a new password for a list
for which its administrator had lost.
Passwords/admins get lots from time to time and it's
frustrating to solve it deleting and creating a new list :(
----------------------------------------------------------------------
>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2004-01-20 17:23
Message:
Logged In: YES
user_id=12800
In Mailman 2.1 the only way to reset a list admin password
is with the site password. You first have to create the
site password from the command line with bin/mmsitepass.
Then log into the list with the site password and use it to
reset the admin password.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880543&group_i…
Patches item #871062, was opened at 2004-01-05 12:09
Message generated for change (Comment added) made by fubarobfusco
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: K. A. Krueger (fubarobfusco)
Date: 2004-01-20 11: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 12: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…
Bugs item #880543, was opened at 2004-01-20 13:57
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=880543&group_i…
Category: configuring/installing
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Ismael Olea (olea)
Assigned to: Nobody/Anonymous (nobody)
Summary: Impossible to recover lost admin-list passwords
Initial Comment:
I couldn't find a way to set a new password for a list
for which its administrator had lost.
Passwords/admins get lots from time to time and it's
frustrating to solve it deleting and creating a new list :(
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880543&group_i…
Bugs item #880073, was opened at 2004-01-19 21:23
Message generated for change (Comment added) made by ber
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_i…
Category: None
Group: 2.1 (stable)
Status: Open
Resolution: None
>Priority: 6
Submitted By: Bernhard Reiter (ber)
Assigned to: Nobody/Anonymous (nobody)
Summary: list-id might violate RFC2919 and RFC2822
Initial Comment:
Code in
http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Handlers/Cook…
(as shipped with mailman 2.1.4)
will use formataddr for the List-Id:
listid_h = formataddr((desc, listid))
This will violate the RFC2919, if not(desc),
because the angle-brackets might be left out.
3. The List-Id Header Field
The List-Id header MAY optionally include a
description by including
it as a "phrase" [DRUMS] before the
angle-bracketed list identifier.
The syntax of the List-Id header follows:
list-id-header = "List-ID:" [phrase] "<"
list-id ">" CRLF
Unlike most headers in [RFC822],
the List-Id header does not allow free insertion of
whitespace and comments around tokens.
[Go inside ~mailman/bin]
python
Python 2.1.3 (#1, Sep 7 2002, 15:29:56)
[GCC 2.95.4 20011002 (Debian prerelease)] on linux2
Type "copyright", "credits" or "license" for more
information.
>>> import paths
>>> from email.Utils import formataddr
>>> formataddr(("A strange mailing
list","strange.list.org"))
'A strange mailing list <strange.list.org>'
>>> formataddr((None,"strange.list.org"))
'strange.list.org'
>>> formataddr(("","strange.list.org"))
'strange.list.org'
Solution: go back to old code and
check
http://sourceforge.net/tracker/download.php?group_id=103&atid=100103&file_i…
to limit the line length so you don't violate RFC2822
----------------------------------------------------------------------
>Comment By: Bernhard Reiter (ber)
Date: 2004-01-19 21:25
Message:
Logged In: YES
user_id=113859
I'm raising the priority to 6 because
many people get annoyed if the List-ID headers change.
Mailman 2.1.3 did better in the RFC2919 regard,
2.1.4 breaks it in an attempt to fix other bugs.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_i…
Bugs item #880073, was opened at 2004-01-19 21:23
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=880073&group_i…
Category: None
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Bernhard Reiter (ber)
Assigned to: Nobody/Anonymous (nobody)
Summary: list-id might violate RFC2919 and RFC2822
Initial Comment:
Code in
http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Handlers/Cook…
(as shipped with mailman 2.1.4)
will use formataddr for the List-Id:
listid_h = formataddr((desc, listid))
This will violate the RFC2919, if not(desc),
because the angle-brackets might be left out.
3. The List-Id Header Field
The List-Id header MAY optionally include a
description by including
it as a "phrase" [DRUMS] before the
angle-bracketed list identifier.
The syntax of the List-Id header follows:
list-id-header = "List-ID:" [phrase] "<"
list-id ">" CRLF
Unlike most headers in [RFC822],
the List-Id header does not allow free insertion of
whitespace and comments around tokens.
[Go inside ~mailman/bin]
python
Python 2.1.3 (#1, Sep 7 2002, 15:29:56)
[GCC 2.95.4 20011002 (Debian prerelease)] on linux2
Type "copyright", "credits" or "license" for more
information.
>>> import paths
>>> from email.Utils import formataddr
>>> formataddr(("A strange mailing
list","strange.list.org"))
'A strange mailing list <strange.list.org>'
>>> formataddr((None,"strange.list.org"))
'strange.list.org'
>>> formataddr(("","strange.list.org"))
'strange.list.org'
Solution: go back to old code and
check
http://sourceforge.net/tracker/download.php?group_id=103&atid=100103&file_i…
to limit the line length so you don't violate RFC2822
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_i…
Bugs item #878078, was opened at 2004-01-16 09:06
Message generated for change (Comment added) made by mkljun
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=878078&group_i…
Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Matjaz Kljun (mkljun)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unable to select Slevene language
Initial Comment:
When I try to select Slovene language for the mailing list
I get this bug report. It's odd that it happens only
with Slovene language. If I select Italian or any other
language
it doesn't complain.
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 "/usr/local/mailman/scripts/driver", line 87, in
run_main
main()
File "/usr/local/mailman/Mailman/Cgi/admin.py", line
175, in main
change_options(mlist, category, subcat, cgidata, doc)
File "/usr/local/mailman/Mailman/Cgi/admin.py", line
1296, in change_options
gui.handleForm(mlist, category, subcat, cgidata, doc)
File "/usr/local/mailman/Mailman/Gui/GUIBase.py",
line 158, in handleForm
self._setValue(mlist, property, val, doc)
File "/usr/local/mailman/Mailman/Gui/Language.py",
line 120, in _setValue
i18n.set_language(val)
File "/usr/local/mailman/Mailman/i18n.py", line 35,
in set_language
language)
File "/usr/local/lib/python2.2/gettext.py", line 248,
in translation
t = _translations.setdefault(key,
class_(open(mofile, 'rb')))
File "/usr/local/lib/python2.2/gettext.py", line 106,
in __init__
self._parse(fp)
File "/usr/local/lib/python2.2/gettext.py", line 180,
in _parse
k, v = item.split(':', 1)
ValueError: unpack list of wrong size
Python information:
Variable Value
sys.version 2.2.2 (#1, Jan 3 2003, 07:54:31) [GCC 3.2.1
[FreeBSD] 20021119 (release)]
sys.executable /usr/local/bin/python
sys.prefix /usr/local
sys.exec_prefix /usr/local
sys.path /usr/local
sys.platform freebsd5
Environment variables:
Variable Value
PATH_INFO /senat/language
HTTP_ACCEPT
application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1
CONTENT_TYPE application/x-www-form-urlencoded
HTTP_REFERER
http://www.upr.si/mailman/admin/senat/language
SERVER_SOFTWARE Apache/1.3.27 (Unix) PHP/4.2.3
PYTHONPATH /usr/local/mailman
SCRIPT_FILENAME /usr/local/mailman/cgi-bin/admin
SERVER_ADMIN andy(a)upr.si
SCRIPT_NAME /mailman/admin
SERVER_SIGNATURE
Apache/1.3.27 Server at www.upr.si Port 80
REQUEST_METHOD POST
HTTP_HOST www.upr.si
HTTP_KEEP_ALIVE 300
SERVER_PROTOCOL HTTP/1.1
QUERY_STRING
PATH_TRANSLATED /usr/local/www/data/senat/language
REQUEST_URI /mailman/admin/senat/language
CONTENT_LENGTH 118
HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7
HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT
5.0; en-US; rv:1.5) Gecko/20031007
HTTP_CONNECTION keep-alive
HTTP_COOKIE
senat+admin=280200000069efdd0640732800000061346663386238616161633832333165333334373536393030393639393637303161346334396162
SERVER_NAME www.upr.si
REMOTE_ADDR 193.2.97.204
REMOTE_PORT 2967
HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5
UNIQUE_ID QAbeNMECFgMAAC4QCZ8
SERVER_PORT 80
GATEWAY_INTERFACE CGI/1.1
HTTP_ACCEPT_ENCODING gzip,deflate
SERVER_ADDR 193.2.22.3
DOCUMENT_ROOT /usr/local/www/data
----------------------------------------------------------------------
>Comment By: Matjaz Kljun (mkljun)
Date: 2004-01-19 13:43
Message:
Logged In: YES
user_id=952444
The header of mailman.po file of slovene language in version
2.1.4 is currupted. I copied the header of english version
and inserted the slovene info and it works fine:
# Mailman
msgid ""
msgstr ""
"Project-Id-Version: mailman_new_poprn"
"POT-Creation-Date: Sat Dec 13 14:40:28 2003n"
"PO-Revision-Date: 2003-09-30 11:18+0200n"
"Last-Translator: Urska Colner <urska.colner(a)agenda.si>n"
"Language-Team: Sloven??ina <sl(a)li.org>n"
"MIME-Version: 1.0n"
"Content-Type: text/plain; charset=ISO-8859-2n"
"Content-Transfer-Encoding: 8bitn"
"X-Generator: KBabel 1.0.1n"
Thanks for your help ;)
M
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=878078&group_i…