Bugs item #1072002, was opened at 2004-11-23 10:38
Message generated for change (Comment added) made by jonhowell
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072002&group_…
Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Mark Sapiro (msapiro)
Assigned to: Nobody/Anonymous (nobody)
Summary: admin_member_chunksize not available in GUI or config_list
Initial Comment:
admin_member_chunksize is set from
DEFAULT_ADMIN_MEMBER_CHUNKSIZE when a list is created,
but it is not visible in the admin GUI or bin/config_list.
----------------------------------------------------------------------
Comment By: Jon Howell (jonhowell)
Date: 2005-03-21 13:37
Message:
Logged In: YES
user_id=70921
"Me too."
Please add this line after the 'max_message_size' entry in
Gui/General.py:
('admin_member_chunksize', mm_cfg.Number, 7, 0,
_('''Number of members to display at a time.''')),
I was going nuts being forced to look at my membership list
in 26 steps, one bucket at a time. I finally bothered today
to find the problem, and fixing this bug would fix the
problem. Although it would be nice if the membership list
page also had a "show entire list" button, so the next guy
doesn't have to scrape the source to find this option. :v)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072002&group_…
Patches item #1167696, was opened at 2005-03-21 16:28
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=1167696&group_…
Category: None
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Joost van Baal (vanbaal)
Assigned to: Nobody/Anonymous (nobody)
Summary: handle PGP encrypted and signed posts
Initial Comment:
This patch is based upon a patch by Stefan Schlott (
http://medien.informatik.uni-ulm.de/~stefan/gpg-mailman.html )
It extends Mailman to:
- A post will be distributed only if the PGP signature on the post is from
one of the list members.
- For sending encrypted email, a list member encrypts to the public key of
the list. The post will be decrypted and re-encrypted to the public keys
of all list members.
(Later, the patch will handle RFC 2633 (S/MIME) messages too, next to RFC 2440
(OpenPGP)).
In order to achieve this, each list has a public and private key, as well
as a key passphrase. Furthermore, new list settings are defined:
gpg_postings_allowed: Is it allowed to send to this list postings which are
encrypted with the GPG list key?
gpg_msg_distribution: Are subscribers allowed (or even forced) to upload
their GPG public key in order to receive all messages encrypted?
gpg_post_sign: Should posts be GPG signed with an acknowledged subscriber key
before being distributed?
gpg_msg_sign: Should the server sign encrypted messages?
Finally, each subscriber can upload her PGP public key using the webinterface.
Latest version of the patch is available from
http://www.non-gnu.uvt.nl/pub/mailman/ .
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1167696&group_…
Patches item #1161505, was opened at 2005-03-11 16:58
Message generated for change (Settings changed) made by tkikuchi
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1161505&group_…
Category: Pipermail
Group: Mailman 2.1
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Mark Sapiro (msapiro)
Assigned to: Nobody/Anonymous (nobody)
Summary: Appropriate text for private archive login
Initial Comment:
Much of the template templates/en/private.html is based
on (copied from) the template
templates/en/admlogin.html. Thus, the language about
cookies is not appropriate for this function.
The patch changes the text to something more
appropriate for private archive login.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1161505&group_…
Bugs item #1085651, was opened at 2004-12-15 09:54
Message generated for change (Comment added) made by shevek
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_…
Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Etienne M. Gagnon (egagnon)
Assigned to: Nobody/Anonymous (nobody)
Summary: Broken PGP/MIME signature of messages with attachments
Initial Comment:
Hi,
When I send a PGP/MIME signed message *with*
attachments (in addition to the PGP signature) to a
Mailman-based mailing list, Firefox/Enigmail fails to
verify the signature of the message forwarded by mailman.
I have uploaded an example message with a broken
signature as attachment to this bug.
You can also see how Mailman's automatic archives don't
even handle such messages correctly by looking at how
it archived that message at:
http://sablecc.org/lists/sablecc-user/2004-December/000159.html
I've looked in the bugs database and found that a
somewhat related problem was reported a while ago, but
note that the current bug is different. The original
bug was about PGP/MIME signed messages without
attachments that were handled incorrectly by Enigmail.
This one is about messages with attachments, and it is
likely that the bug is Mailman's, at least accroding to
the reply I got in:
http://bugzilla.mozdev.org/show_bug.cgi?id=8466
Thanks for your help (and for the magnificient software)!
Etienne
----------------------------------------------------------------------
Comment By: Bas Wijnen (shevek)
Date: 2005-03-20 14:51
Message:
Logged In: YES
user_id=42389
That function does indeed not conserve whitespace. E-mail
doesn't say whitespace in headers (or even the message) must
be preserved, so strictly speaking it's not a bug. However,
it is a missing feature, and I think python is the place to
implement it, not mailman.
The point is that signed e-mails with attachments are sent
as two parts: One which is a complete e-mail by itself, and
one which holds the signature for that e-mail. This is
because in attachments whitespace must be preserved (as
opposed to the situation in the message itself).
It would be very convenient if such e-mail can be handled by
python programs without rewriting the things which work fine
for non-signed e-mails. If the attachment is really
changed, of course the signature will be broken. However,
if it is not, it should not be hard to write out the same
message (with whitespace preserved) as was read in. If this
is not possible, it is quite hard to do it in the program,
as python doesn't seem to support loading a part of an
e-mail which has headers of its own as a binary attachment
(without touching whitespace, in particular).
----------------------------------------------------------------------
Comment By: Jonas Berlin (xkr47)
Date: 2005-03-19 13:21
Message:
Logged In: YES
user_id=66259
from python's Message.py:
def _get_params_preserve(self, failobj, header):
# Like get_params() but preserves the quoting of values. BAW:
# should this be part of the public interface?
According to my analysis of the comment, the function in question does _not_
guarantee to preserve the header as-is, it only preserves _quoting_. Thus, I
don't think we can call this a bug in python. If there's more official
documentation elsewhere that states that it should preserve everything as-is,
then ignore this comment altogether :).
I didn't have time to grasp how mailman actually uses that Message class,
but I think mailman should be changed to use functions that don't alter the
message, and/or re-implement that work according to the requirements of
mailman (or, users of mailman :).
Anyway, an alternative could be to continue to use the Message.py functions
to parse the values while analyzing the contents of the message, and then
copypaste the original headers as-is after checking.
- xkr47
----------------------------------------------------------------------
Comment By: Etienne M. Gagnon (egagnon)
Date: 2005-01-29 18:08
Message:
Logged In: YES
user_id=15365
Dear Bas,
Thanks a lot for identifying the source of this bug and
flagging an upstream bug on Python.
Etienne
----------------------------------------------------------------------
Comment By: Bas Wijnen (shevek)
Date: 2005-01-24 12:35
Message:
Logged In: YES
user_id=42389
I checked the source, and this appears to be a bug in
Python. It can read and write e-mails, including headers,
and they are interpreted. However, it doesn't preserve
their whitespace, which is of course fatal for pgp signatures.
The bug is filed for python here:
http://sourceforge.net/tracker/index.php?func=detail&aid=968430&group_id=54…
----------------------------------------------------------------------
Comment By: Etienne M. Gagnon (egagnon)
Date: 2005-01-18 18:30
Message:
Logged In: YES
user_id=15365
I am attaching a screen shot of the content filtering
settings (see the options.png attachment I have added to
this bug report). In short, content filtering is disabled,
so I don't think it is the cause of the problem. :-/
Etienne
----------------------------------------------------------------------
Comment By: Brad Knowles (shub)
Date: 2005-01-17 01:37
Message:
Logged In: YES
user_id=18417
Look at your content filter settings. What MIME-types are you configured
to pass? At the very least, you should be configured to pass the
following:
multipart/mixed
multipart/alternative
text/plain
application/pgp-signature
multipart/signed
----------------------------------------------------------------------
Comment By: Toni Willberg (toniw)
Date: 2005-01-08 02:23
Message:
Logged In: YES
user_id=190645
I can reproduce this bug also.
Here's a diff what happened to me:
diff -u mail.valid mail.invalid
Content-Disposition: attachment;
filename=configure.in.pre-pkgconfig.patch
-Content-Type: text/x-patch;
name=configure.in.pre-pkgconfig.patch; charset=UTF-8
+Content-Type: text/x-patch;
name=configure.in.pre-pkgconfig.patch;
+ charset=UTF-8
Content-Transfer-Encoding: base64
And this was _inside_ gpg-signed block.
Mailman should not alter that section at all, right?
X-Mailman-Version: 2.1.4
Yours,
Toni Willberg <toniw(a)iki.fi>
----------------------------------------------------------------------
Comment By: Etienne M. Gagnon (egagnon)
Date: 2004-12-30 05:03
Message:
Logged In: YES
user_id=15365
Any update?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_…
Feature Requests item #786326, was opened at 2003-08-10 12:47
Message generated for change (Comment added) made by magicfab
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=786326&group_i…
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Milos Popovic (milos_popovic)
Assigned to: Nobody/Anonymous (nobody)
Summary: Rotation through moderators
Initial Comment:
A useful moderation feature in LISTSERV, when multiple
moderators are listed, is that it can deliver
moderation requests to moderators in *rotation* (only
one moderator at a time), thus reducing the individual
workload.
I've found this a useful feature to share the workload
of verifying mostly filtered spam that's held for
moderation on lists that need to accept outside posts
and need to have a quick moderator approval turnaround
time on posts. The quick turn-around time means
moderation requests are sent immediately for each post,
rather than just being bundled at the end of each day.
It would be very useful to have such a feature (option
to rotate through moderators, for the individual post
moderation requests only) in MailMan.
----------------------------------------------------------------------
Comment By: Fabián A. Rodríguez S. (magicfab)
Date: 2005-03-20 08:46
Message:
Logged In: YES
user_id=92045
I would add to this request a way to list rotation groups
for moderation. Sometimes in rotation there may be occasions
when an individual moderator is not available.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=786326&group_i…
Bugs item #1085651, was opened at 2004-12-15 10:54
Message generated for change (Comment added) made by xkr47
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_…
Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Etienne M. Gagnon (egagnon)
Assigned to: Nobody/Anonymous (nobody)
Summary: Broken PGP/MIME signature of messages with attachments
Initial Comment:
Hi,
When I send a PGP/MIME signed message *with*
attachments (in addition to the PGP signature) to a
Mailman-based mailing list, Firefox/Enigmail fails to
verify the signature of the message forwarded by mailman.
I have uploaded an example message with a broken
signature as attachment to this bug.
You can also see how Mailman's automatic archives don't
even handle such messages correctly by looking at how
it archived that message at:
http://sablecc.org/lists/sablecc-user/2004-December/000159.html
I've looked in the bugs database and found that a
somewhat related problem was reported a while ago, but
note that the current bug is different. The original
bug was about PGP/MIME signed messages without
attachments that were handled incorrectly by Enigmail.
This one is about messages with attachments, and it is
likely that the bug is Mailman's, at least accroding to
the reply I got in:
http://bugzilla.mozdev.org/show_bug.cgi?id=8466
Thanks for your help (and for the magnificient software)!
Etienne
----------------------------------------------------------------------
Comment By: Jonas Berlin (xkr47)
Date: 2005-03-19 14:21
Message:
Logged In: YES
user_id=66259
from python's Message.py:
def _get_params_preserve(self, failobj, header):
# Like get_params() but preserves the quoting of values. BAW:
# should this be part of the public interface?
According to my analysis of the comment, the function in question does _not_
guarantee to preserve the header as-is, it only preserves _quoting_. Thus, I
don't think we can call this a bug in python. If there's more official
documentation elsewhere that states that it should preserve everything as-is,
then ignore this comment altogether :).
I didn't have time to grasp how mailman actually uses that Message class,
but I think mailman should be changed to use functions that don't alter the
message, and/or re-implement that work according to the requirements of
mailman (or, users of mailman :).
Anyway, an alternative could be to continue to use the Message.py functions
to parse the values while analyzing the contents of the message, and then
copypaste the original headers as-is after checking.
- xkr47
----------------------------------------------------------------------
Comment By: Etienne M. Gagnon (egagnon)
Date: 2005-01-29 19:08
Message:
Logged In: YES
user_id=15365
Dear Bas,
Thanks a lot for identifying the source of this bug and
flagging an upstream bug on Python.
Etienne
----------------------------------------------------------------------
Comment By: Bas Wijnen (shevek)
Date: 2005-01-24 13:35
Message:
Logged In: YES
user_id=42389
I checked the source, and this appears to be a bug in
Python. It can read and write e-mails, including headers,
and they are interpreted. However, it doesn't preserve
their whitespace, which is of course fatal for pgp signatures.
The bug is filed for python here:
http://sourceforge.net/tracker/index.php?func=detail&aid=968430&group_id=54…
----------------------------------------------------------------------
Comment By: Etienne M. Gagnon (egagnon)
Date: 2005-01-18 19:30
Message:
Logged In: YES
user_id=15365
I am attaching a screen shot of the content filtering
settings (see the options.png attachment I have added to
this bug report). In short, content filtering is disabled,
so I don't think it is the cause of the problem. :-/
Etienne
----------------------------------------------------------------------
Comment By: Brad Knowles (shub)
Date: 2005-01-17 02:37
Message:
Logged In: YES
user_id=18417
Look at your content filter settings. What MIME-types are you configured
to pass? At the very least, you should be configured to pass the
following:
multipart/mixed
multipart/alternative
text/plain
application/pgp-signature
multipart/signed
----------------------------------------------------------------------
Comment By: Toni Willberg (toniw)
Date: 2005-01-08 03:23
Message:
Logged In: YES
user_id=190645
I can reproduce this bug also.
Here's a diff what happened to me:
diff -u mail.valid mail.invalid
Content-Disposition: attachment;
filename=configure.in.pre-pkgconfig.patch
-Content-Type: text/x-patch;
name=configure.in.pre-pkgconfig.patch; charset=UTF-8
+Content-Type: text/x-patch;
name=configure.in.pre-pkgconfig.patch;
+ charset=UTF-8
Content-Transfer-Encoding: base64
And this was _inside_ gpg-signed block.
Mailman should not alter that section at all, right?
X-Mailman-Version: 2.1.4
Yours,
Toni Willberg <toniw(a)iki.fi>
----------------------------------------------------------------------
Comment By: Etienne M. Gagnon (egagnon)
Date: 2004-12-30 06:03
Message:
Logged In: YES
user_id=15365
Any update?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_…
Bugs item #1166277, was opened at 2005-03-18 14:22
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=1166277&group_…
Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Roberts (timroberts)
Assigned to: Nobody/Anonymous (nobody)
Summary: Want clone_member from web interface
Initial Comment:
The single most common administrative task I have to do
is changing a user's email address. People change ISPs
today like they change their minds.
There is no good way to change an e-mail address from
the admin web interface. Unsub followed by mass
subscribe loses the settings and the real name. I can
ssh in and use clone_member, but that's tacky.
The equivalent of "clone_member -r" is missing from the
web interface.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1166277&group_…
Bugs item #1166155, was opened at 2005-03-18 19:45
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=1166155&group_…
Category: None
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Morten Brix Pedersen (mbrix)
Assigned to: Nobody/Anonymous (nobody)
Summary: Edit options doesnt work in translated page
Initial Comment:
Hello,
When the language is set to Danish (havn't tested other
languages) and I click the button on the web interface
"Unsubscribe or edit options", I get this:
Bug in Mailman version 2.1.5
We're sorry, we hit a bug!
Please inform the webmaster for this site of this
problem. Printing of traceback and other system
information has been explicitly inhibited, but the
webmaster can find this information in the Mailman
error logs.
The backtrace from the error log looks like this:
admin(1039): [----- Mailman Version: 2.1.5
-----]admin(1039): [----- Traceback ------]admin(1039):
Traceback (most recent call last):admin(1039): File
"/var/lib/mailman/scripts/driver", line 110, in
run_mainadmin(1039): main()admin(1039): File
"/usr/lib/mailman/Mailman/Cgi/options.py", line 239, in
mainadmin(1039): loginpage(mlist, doc, user,
language)admin(1039): File
"/usr/lib/mailman/Mailman/Cgi/options.py", line 813, in
loginpage
admin(1039): table.AddRow([_("""In order to change
your membership option, you must
admin(1039): File "/var/lib/mailman/Mailman/i18n.py",
line 89, in _
admin(1039): return tns % dict
admin(1039): ValueError: unsupported format character
'p' (0x70) at index 105
The problem can be reproduced on the following URL:
http://soeborggruppe.dk/cgi-bin/mailman/listinfo/bestyrelsen
Thanks.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1166155&group_…
Feature Requests item #1163610, was opened at 2005-03-15 11:28
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1163610&group_…
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Nobody/Anonymous (nobody)
Summary: monthly archives as YYYY-MM
Initial Comment:
when setting the archive_volume_frequency to "monthly"
directories like "2003-July" are generated.
as i am running some international lists (and because
of backwards compatibility issues to pre-Mailman
times), i'd prefer "2003-07".
this could be done by just adding another
archive_volume_frequency.
attached is a patch to the 2.1.5-release (since i am
using debian/testing) that provides a "month00" frequency.
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2005-03-18 14:22
Message:
Logged In: YES
user_id=564396
based on the suggestions made on mailman-usersATpythonDOTorg
i have fixed the patch and committed it via the
patch-tracker (1165916)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1163610&group_…
Patches item #1165916, was opened at 2005-03-18 14:19
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=1165916&group_…
Category: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Nobody/Anonymous (nobody)
Summary: monthly archives in YYYY-MM format
Initial Comment:
when setting the archive_volume_frequency to "monthly"
directories like "2003-July" are generated.
as i am running some international lists (and because
of backwards compatibility issues to pre-Mailman
times), i'd prefer "2003-07".
this can be done by just adding another
archive_volume_frequency.
attached is a patch to the 2.1.5-release (since i am
using debian/testing) that provides a "month00" frequency.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1165916&group_…