From noreply at sourceforge.net  Wed Feb  1 10:24:01 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 01 Feb 2006 01:24:01 -0800
Subject: [ mailman-Bugs-1421285 ] 2.1.7 (VERP) mistakes delay notice for bounce
Message-ID: <E1F4EDZ-0001w4-MJ@sc8-sf-web6.sourceforge.net>

Bugs item #1421285, was opened at 2006-02-01 10:24
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=1421285&group_id=103

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: bounce detection
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthias Andree (m-a)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.1.7 (VERP) mistakes delay notice for bounce

Initial Comment:
Greetings,

I just got the bounce action notice specified below.

I am running Mailman 2.1.7 with SF Patch #1405790 on
Python 2.3.4, SUSE Linux 9.2 i586, Postfix 2.2.9.

It appears as though Mailman 2.1.7 were not properly
detecting this apparently RFC-1894 compliant notice as
a "delayed" notice which is definitely a "soft bounce",
if it is supposed to contribute to the bounce score at
all. 
I looked at Mailman 2.1.4 or so which appeared to make
efforts to not count "delayed"/deferral notices at all,
but that didn't work at the time for Postfix deferral
notices and was IIRC fixed later.

My setup is VERP enabled, uses VERP for almost
everything and uses monthly reminders for this list.

Jan 27 20:33:47 2006 (6794) leafnode-list:
admin at example.com has stale bounce info, resetting
Jan 27 21:57:08 2006 (6794) leafnode-list:
admin at example.com already scored a bounce for date
27-Jan-2006
Jan 30 18:16:47 2006 (6794) leafnode-list:
admin at example.com current bounce score: 2.0
Jan 30 19:40:06 2006 (6794) leafnode-list:
admin at example.com already scored a bounce for date
30-Jan-2006
Feb 01 03:01:40 2006 (6794) leafnode-list:
admin at example.com current bounce score: 3.0
Feb 01 03:01:41 2006 (6794) leafnode-list:
admin at example.com disabling due to bounce score 3.0 >= 3.0
Feb 01 03:31:41 2006 (6794) leafnode-list:
admin at example.com residual bounce received

I masked the list host by ... and the subscriber's
domain by example.com and the last two components of
the IPv4 address by X, without loss of accuracy I hope,
to protect the site from spammers.

Can anyone shed any light why Mailman 2.1.7 with said
patch considers the delay notice a "hard" bounce?

I don't have time to do debugging right now (end of the
month might work), but applying a patch will probably work.

-----------

This is a Mailman mailing list bounce action notice:

    List:       leafnode-list
    Member:     admin at example.com
    Action:     Subscription deaktiviert.
    Reason:     Excessive or fatal bounces.
    


The triggering bounce notice is attached below.

Questions? Contact the Mailman site administrator at
mailman at ...
From: MAILER-DAEMON at ... (Mail Delivery System)
Subject: Delayed Mail (still being retried)
To: leafnode-list-bounces+admin=example.com at ...
Date: Wed,  1 Feb 2006 02:47:07 +0100 (CET)

This is the Postfix program at host ...

####################################################################
# THIS IS A WARNING ONLY.  YOU DO NOT NEED TO RESEND
YOUR MESSAGE. #
####################################################################

Your message could not be delivered for 4.2 hours.
It will be retried until it is 7.0 days old.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

			The Postfix program

<admin at example.com>: connect to
mail.example.com[60.234.X.X]:
    Connection timed out
Reporting-MTA: dns; ...
X-Postfix-Queue-ID: C9BC24415A
X-Postfix-Sender: rfc822;
	leafnode-list-bounces+admin=example.com at ...
Arrival-Date: Tue, 31 Jan 2006 21:55:44 +0100 (CET)

Final-Recipient: rfc822; admin at example.com
Action: delayed
Status: 4.0.0
Diagnostic-Code: X-Postfix; connect to
mail.example.com[60.234.X.X]:
	Connection timed out
Will-Retry-Until: Tue,  7 Feb 2006 21:55:44 +0100 (CET)
[5. Undelivered Message Headers --- text/rfc822-headers]

(elided)
-------------------------

I pasted from Emacs/Gnus, and this is the mime
structure as seen by Gnus, it looks intact.

 . 20060201T030141 [ 150: mailman at dt.e-tec] <* mixed>
Bounce-Benachrichtigung
 . 20060201T030141   [  14: mailman at dt.e-tec] <1 text>
 . 20060201T030141   [ 125: mailman at dt.e-tec] <2 rfc822>
 . 20060201T024707     [ 111: Mail Delivery Sy] <2.*
report> Delayed Mail (still being retried)
 . 20060201T024707       [  19: Mail Delivery Sy] <2.1
text>
 . 20060201T024707       [  13: Mail Delivery Sy] <2.2
delivery-status>
 . 20060201T024707       [  63: Mail Delivery Sy] <2.3
rfc822-headers>


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1421285&group_id=103

From noreply at sourceforge.net  Wed Feb  1 10:29:33 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 01 Feb 2006 01:29:33 -0800
Subject: [ mailman-Bugs-1363422 ] Valid E-mails Rejected as Invalid
Message-ID: <E1F4EIv-0001oO-Cl@sc8-sf-web3.sourceforge.net>

Bugs item #1363422, was opened at 2005-11-22 06:26
Message generated for change (Comment added) made by m-a
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1363422&group_id=103

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: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 7
Submitted By: Tim Wilde (krellis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Valid E-mails Rejected as Invalid

Initial Comment:
I ran into a problem recently with sync_members.  I was
attempting to add a list of addresses that included
"---tim--- at krellis.org", but this address was rejected:

bin/sync_members -a=no -f
/usr/local/mailinglists/lists/system-status.txt
system-status
Invalid :               ---tim--- at krellis.org
You must fix the preceding invalid addresses first.

While this is an ODD address, it is perfectly legal,
per section 3.4 of RFC 2822
(http://www.faqs.org/rfcs/rfc2822.html).  Rejecting a
valid address like this seems like a pretty major
problem to me.

This was with MailMan 2.1.6 on FreeBSD 4.  If there is
any more information I can provide, please let me know.

Regards,
Tim Wilde

----------------------------------------------------------------------

Comment By: Matthias Andree (m-a)
Date: 2006-02-01 10:29

Message:
Logged In: YES 
user_id=2788

Mailman is not alone in rejecting messages that start with a
"-" - some MTAs also do that, for instance, Postfix (but see
Postfix's "allow_min_user" option).

The reason is that too many sites mistake such addresses for
sendmail command-line options, because most sendmail users
are clueless and forget the "--" before the addresses.

For that reason, it is rather unwise to use mail addresses
that start with a "-" - while legal, it's not universally
accepted.

----------------------------------------------------------------------

Comment By: Tim Wilde (krellis)
Date: 2005-12-06 00:57

Message:
Logged In: YES 
user_id=1021966

This appears to be a problem with line 210 of Utils.py, in
the ValidateEmail function:

    if _badchars.search(s) or s[0] == '-':
        raise Errors.MMHostileAddress, s  

MailMan is explicitly rejecting e-mails that start with a
hyphen.  Why?  This is a perfectly legal e-mail address.  If
MailMan is using e-mail addresses in such an unsafe way that
they could be interpreted as command line arguments, that's
just absurd.  I can't see any other reason to forbid a
leading hyphen, though.

Can anyone tell me if I will be safe removing this check, or
if MailMan will blow up elsewhere?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1363422&group_id=103

From noreply at sourceforge.net  Wed Feb  1 19:55:21 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 01 Feb 2006 10:55:21 -0800
Subject: [ mailman-Patches-1421751 ] Add label tag around checkbox+label
Message-ID: <E1F4N8T-0004Mz-C1@sc8-sf-web5.sourceforge.net>

Patches item #1421751, was opened at 2006-02-01 18:55
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=1421751&group_id=103

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: Web UI
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Yan Morin (yanmorin)
Assigned to: Nobody/Anonymous (nobody)
Summary: Add label tag around checkbox+label

Initial Comment:
Add label tag around checkbox+label to allow a user to
click on the label, and automatically check/uncheck the
checkbox. IE needs for="checkboxID", but
mozilla/konqueror allow to put the tag around the text
and the checkbox.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1421751&group_id=103

From noreply at sourceforge.net  Thu Feb  2 03:32:00 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 01 Feb 2006 18:32:00 -0800
Subject: [ mailman-Patches-1419490 ] email.Utils.parsedate can return bogus
	date
Message-ID: <E1F4UGO-0008IM-3i@sc8-sf-web6.sourceforge.net>

Patches item #1419490, was opened at 2006-01-31 01:21
Message generated for change (Comment added) made by tkikuchi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1419490&group_id=103

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: Tokio Kikuchi (tkikuchi)
Assigned to: Tokio Kikuchi (tkikuchi)
Summary: email.Utils.parsedate can return bogus date

Initial Comment:
While the CVE entry of CVE-2005-4153 (see
http://www.securityfocus.com/bid/16248/info) is not
vulnerable for mailman-2.1.7 and newer, we should fix
the date parsing bug in email package.  In the meantime
of the package renewal, this patch may be used to
workaround the bug.


----------------------------------------------------------------------

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-02-02 02:31

Message:
Logged In: YES 
user_id=67709

Here is my revised patch.  It looks like time.strftime() has
stricter value check.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1419490&group_id=103

From noreply at sourceforge.net  Thu Feb  2 04:00:59 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 01 Feb 2006 19:00:59 -0800
Subject: [ mailman-Feature Requests-1422113 ] Admin notification on address
	change
Message-ID: <E1F4UiR-0005r3-F4@sc8-sf-web2.sourceforge.net>

Feature Requests item #1422113, was opened at 2006-02-01 22:00
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=1422113&group_id=103

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: Bryan Fullerton (fehwalker)
Assigned to: Nobody/Anonymous (nobody)
Summary: Admin notification on address change

Initial Comment:
Currently when a user changes their address on the
options page there is no notification email sent to the
list owner or moderators of affected lists. It would be
more consistent to have this function generate email
according to the admin_notify_mchanges list setting,
though perhaps the content of the email should be
different to distinguish between the two actions.

Thanks,
Bryan


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1422113&group_id=103

From noreply at sourceforge.net  Thu Feb  2 04:08:09 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 01 Feb 2006 19:08:09 -0800
Subject: [ mailman-Patches-1422117 ] Fix: change globally even if options
	aren't changed
Message-ID: <E1F4UpN-00072J-JN@sc8-sf-web5.sourceforge.net>

Patches item #1422117, was opened at 2006-02-02 12:08
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=1422117&group_id=103

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: Web UI
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix: change globally even if options aren't changed

Initial Comment:
When 'change globally' option(s) are enabled, member
options (fullname, delivery, remind, nodupes & mime)
also may be changed globally, even if value(s) on the
page aren't changed.




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1422117&group_id=103

From noreply at sourceforge.net  Thu Feb  2 15:34:58 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 02 Feb 2006 06:34:58 -0800
Subject: [ mailman-Bugs-1411656 ] 2.1.7 not available from gnu or list.org
Message-ID: <E1F4fY2-0007qX-Bv@sc8-sf-web3.sourceforge.net>

Bugs item #1411656, was opened at 2006-01-21 14:23
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1411656&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: karl berry (kberry)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.1.7 not available from gnu or list.org

Initial Comment:
list.org/download.html has links to retrieve the latest
release from "GNU" and "list.org", but neither of these
are up to date.  ftp.gnu.org has only 2.1.5, and the
list.org mailman.tar.gz unpacked into 2.1.6.

Best,
Karl


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2006-02-02 09:34

Message:
Logged In: YES 
user_id=12800

I've uploaded the 2.1.7 tarball to list.org and fixed the
symlink.  I've also gone through the ftp upload dance at
ftp.gnu.org, but as that's an automated process with delay,
I can't test it yet.  Barring any problems, 2.1.7 should now
be uploaded to both sites.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1411656&group_id=103

From noreply at sourceforge.net  Fri Feb  3 20:40:33 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 03 Feb 2006 11:40:33 -0800
Subject: [ mailman-Patches-1352333 ] New Unified XMLRPC Patch
Message-ID: <E1F56nJ-0002xg-U4@sc8-sf-web2.sourceforge.net>

Patches item #1352333, was opened at 2005-11-09 11:07
Message generated for change (Comment added) made by jaginsberg
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1352333&group_id=103

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: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Joshua Ginsberg (jaginsberg)
Assigned to: Nobody/Anonymous (nobody)
Summary: New Unified XMLRPC Patch

Initial Comment:
This is the unified XMLRPC patch coauthored by myself
and Joseph Tate. It supercedes the patch in 1244799.

-jag

----------------------------------------------------------------------

>Comment By: Joshua Ginsberg (jaginsberg)
Date: 2006-02-03 14:40

Message:
Logged In: YES 
user_id=638741

jtate and myself are continuing to work on this patch. We've
established a project on Savannah for our work:

http://savannah.nongnu.org/projects/mailman-xmlrpc/


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1352333&group_id=103

From noreply at sourceforge.net  Tue Feb  7 23:19:26 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 07 Feb 2006 14:19:26 -0800
Subject: [ mailman-Feature Requests-1426719 ] Limit number of subscribers
Message-ID: <E1F6bBG-0007OD-DE@sc8-sf-web3.sourceforge.net>

Feature Requests item #1426719, was opened at 2006-02-07 15:19
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=1426719&group_id=103

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: Nick Voth (nvoth)
Assigned to: Nobody/Anonymous (nobody)
Summary: Limit number of subscribers

Initial Comment:
Having the ability to limit the number of subscribers
on a per-list basis would really help. That way we can
assure customers are not exceeding specific limits.

Likewise, limiting the number of message posts per day
would be very handy as well.

Thanks,

-Nick Voth

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1426719&group_id=103

From noreply at sourceforge.net  Wed Feb  8 15:53:33 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 08 Feb 2006 06:53:33 -0800
Subject: [ mailman-Patches-1427594 ] Unsubscribe problems on Debian
Message-ID: <E1F6qhJ-0003yX-Ia@sc8-sf-web3.sourceforge.net>

Patches item #1427594, was opened at 2006-02-08 14:53
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=1427594&group_id=103

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: brendan_lynch (brendan_lynch)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unsubscribe problems on Debian

Initial Comment:
People can not unsubscribe online. They get an email
msg saying that a sneaky attemp to subscribe them agian
took place. This was on Debian stable mailman ver
2.1.5-8. I upgraded to testing mailman ver 2.1.6 but I
still have the same problem.   

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1427594&group_id=103

From noreply at sourceforge.net  Wed Feb  8 16:34:29 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 08 Feb 2006 07:34:29 -0800
Subject: [ mailman-Patches-1427594 ] Unsubscribe problems on Debian
Message-ID: <E1F6rKv-0004IG-0e@sc8-sf-web3.sourceforge.net>

Patches item #1427594, was opened at 2006-02-08 06:53
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1427594&group_id=103

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: Closed
>Resolution: Invalid
Priority: 5
Submitted By: brendan_lynch (brendan_lynch)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unsubscribe problems on Debian

Initial Comment:
People can not unsubscribe online. They get an email
msg saying that a sneaky attemp to subscribe them agian
took place. This was on Debian stable mailman ver
2.1.5-8. I upgraded to testing mailman ver 2.1.6 but I
still have the same problem.   

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-08 07:34

Message:
Logged In: YES 
user_id=1123998

This is not a patch. If anything it should be in the bug
tracker, BUT

Are you sure you don't have a locally modified version of
the unsub.txt template? I don't think the message you
describe is anywhere in standard Mailman.

If this is not caused by your own modified template, then it
is a problem with the Debian package and should be reported
to Debian, not here.

Are you sure this comes from an unsub attempt. There is an
email that begins:

"""An attempt was made to subscribe your address to the
mailing list %(listaddr)s.  You are already subscribed to
this mailing list."""

This is sent when a user who is already a list member
attempts to subscribe again. Perhaps you have modified the
listinfo.html template and not properly arranged the
<MM-*-form-start> tags so the unsubscribe button actually
submits the subscribe form.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1427594&group_id=103

From noreply at sourceforge.net  Thu Feb  9 06:12:24 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 08 Feb 2006 21:12:24 -0800
Subject: [ mailman-Patches-1419490 ] email.Utils.parsedate can return bogus
	date
Message-ID: <E1F746S-0005bb-OO@sc8-sf-web2.sourceforge.net>

Patches item #1419490, was opened at 2006-01-30 20:21
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1419490&group_id=103

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: Out of Date
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Tokio Kikuchi (tkikuchi)
Summary: email.Utils.parsedate can return bogus date

Initial Comment:
While the CVE entry of CVE-2005-4153 (see
http://www.securityfocus.com/bid/16248/info) is not
vulnerable for mailman-2.1.7 and newer, we should fix
the date parsing bug in email package.  In the meantime
of the package renewal, this patch may be used to
workaround the bug.


----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2006-02-09 00:12

Message:
Logged In: YES 
user_id=12800

With email 2.5.7 this will no longer be necessary.

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-02-01 21:31

Message:
Logged In: YES 
user_id=67709

Here is my revised patch.  It looks like time.strftime() has
stricter value check.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1419490&group_id=103

From noreply at sourceforge.net  Thu Feb  9 16:51:12 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 09 Feb 2006 07:51:12 -0800
Subject: [ mailman-Bugs-1428410 ] admin login and logout screens lack favicon
Message-ID: <E1F7E4e-00034w-V3@sc8-sf-web5.sourceforge.net>

Bugs item #1428410, was opened at 2006-02-09 10:51
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=1428410&group_id=103

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: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Josh Kelley (yeshua)
Assigned to: Nobody/Anonymous (nobody)
Summary: admin login and logout screens lack favicon

Initial Comment:
The admin login and logout screens lack a favicon.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1428410&group_id=103

From noreply at sourceforge.net  Sun Feb 12 19:17:51 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 12 Feb 2006 10:17:51 -0800
Subject: [ mailman-Bugs-1430209 ] Detatch from email
Message-ID: <E1F8LnD-0004f9-0f@sc8-sf-web1.sourceforge.net>

Bugs item #1430209, was opened at 2006-02-12 13: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=1430209&group_id=103

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: Full Decent (fulldecent)
Assigned to: Nobody/Anonymous (nobody)
Summary: Detatch from email

Initial Comment:
Please allow posting from the website. And downloading
content via RSS.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430209&group_id=103

From noreply at sourceforge.net  Sun Feb 12 20:02:59 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 12 Feb 2006 11:02:59 -0800
Subject: [ mailman-Bugs-1430236 ] bin/arch fails with TypeError
Message-ID: <E1F8MUt-0007jG-6T@sc8-sf-web2.sourceforge.net>

Bugs item #1430236, was opened at 2006-02-12 19:02
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=1430236&group_id=103

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: command line scripts
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Andreas Thienemann (ixsnet)
Assigned to: Nobody/Anonymous (nobody)
Summary: bin/arch fails with TypeError

Initial Comment:
[root at bender mailman]# bin/arch -s 15965 -e 15965
bawue-net-admin
archives/private/bawue-net-admin.mbox/bawue-net-admin.mbox 
Pickling archive state into
/opt/mailman-2.1.7/archives/private/bawue-net-admin/pipermail.pck
Traceback (most recent call last):
  File "bin/arch", line 200, in ?
    main()
  File "bin/arch", line 188, in main
    archiver.processUnixMailbox(fp, start, end)
  File
"/opt/mailman-2.1.7/Mailman/Archiver/pipermail.py",
line 569, in processUnixMailbox
    m = mbox.next()
  File "/usr/lib/python2.2/mailbox.py", line 34, in next
    return self.factory(_Subfile(self.fp, start, stop))
  File "/opt/mailman-2.1.7/Mailman/Mailbox.py", line
89, in scrubber
    return mailbox.scrub(msg)
  File "/opt/mailman-2.1.7/Mailman/Mailbox.py", line
109, in scrub
    return self._scrubber(self._mlist, msg)
  File
"/opt/mailman-2.1.7/Mailman/Handlers/Scrubber.py", line
352, in process
    t = part.get_payload(decode=decode)
  File "/opt/mailman-2.1.7/pythonlib/email/Message.py",
line 213, in get_payload
    return Utils._qdecode(payload)
  File "/usr/lib/python2.2/quopri.py", line 161, in
decodestring
    return a2b_qp(s, header = header)
TypeError: argument 1 must be string or read-only
buffer, not None


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430236&group_id=103

From noreply at sourceforge.net  Mon Feb 13 20:43:06 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 13 Feb 2006 11:43:06 -0800
Subject: [ mailman-Bugs-1430919 ] edithtml.py missing 'import re' (version
	2.1.7)
Message-ID: <E1F8jbG-0003Bk-Mb@sc8-sf-web2.sourceforge.net>

Bugs item #1430919, was opened at 2006-02-13 14:43
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=1430919&group_id=103

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: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Sydelko (sydelko)
Assigned to: Nobody/Anonymous (nobody)
Summary: edithtml.py missing 'import re' (version 2.1.7)

Initial Comment:
Line 160 of .../Mailman/Cgi/edithtml.py calls the re
module which is never imported. Adding 'import re' at
the top of the file makes it work.

This is with version 2.1.7 of mailman.

--andy.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430919&group_id=103

From noreply at sourceforge.net  Mon Feb 13 20:47:22 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 13 Feb 2006 11:47:22 -0800
Subject: [ mailman-Bugs-1430919 ] edithtml.py missing 'import re' (version
	2.1.7)
Message-ID: <E1F8jfO-00046i-Rw@sc8-sf-web5.sourceforge.net>

Bugs item #1430919, was opened at 2006-02-13 14:43
Message generated for change (Comment added) made by sydelko
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430919&group_id=103

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: Web/CGI
Group: 2.1 (stable)
>Status: Closed
Resolution: Duplicate
Priority: 5
Submitted By: Andrew Sydelko (sydelko)
Assigned to: Nobody/Anonymous (nobody)
Summary: edithtml.py missing 'import re' (version 2.1.7)

Initial Comment:
Line 160 of .../Mailman/Cgi/edithtml.py calls the re
module which is never imported. Adding 'import re' at
the top of the file makes it work.

This is with version 2.1.7 of mailman.

--andy.

----------------------------------------------------------------------

>Comment By: Andrew Sydelko (sydelko)
Date: 2006-02-13 14:47

Message:
Logged In: YES 
user_id=290934

duplicate

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430919&group_id=103

From noreply at sourceforge.net  Wed Feb 15 12:14:58 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 15 Feb 2006 03:14:58 -0800
Subject: [ mailman-Bugs-1432090 ] Emails not entered in the filter rules very
	well
Message-ID: <E1F9Kcc-0000X6-GM@sc8-sf-web2.sourceforge.net>

Bugs item #1432090, was opened at 2006-02-15 12:14
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=1432090&group_id=103

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: gw- (gw-)
Assigned to: Nobody/Anonymous (nobody)
Summary: Emails not entered in the filter rules very well

Initial Comment:
When accepting an email from a non-subscriber (in a
closed mailing list) and selecting the option that the
sender should be added to the filter list of allowed
senders - this is not done very well, because it adds a
plain string representation of the email address, not
an regular expression (as which everything in that
filter-field is interpreted).

(mailman from Debian-i386, 2.1.5-8)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_id=103

From noreply at sourceforge.net  Wed Feb 15 12:15:25 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 15 Feb 2006 03:15:25 -0800
Subject: [ mailman-Bugs-1432090 ] Emails not entered in the filter rules very
	well
Message-ID: <E1F9Kd3-0003FQ-0f@sc8-sf-web6.sourceforge.net>

Bugs item #1432090, was opened at 2006-02-15 12:14
Message generated for change (Settings changed) made by gw-
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_id=103

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: 2
Submitted By: gw- (gw-)
Assigned to: Nobody/Anonymous (nobody)
Summary: Emails not entered in the filter rules very well

Initial Comment:
When accepting an email from a non-subscriber (in a
closed mailing list) and selecting the option that the
sender should be added to the filter list of allowed
senders - this is not done very well, because it adds a
plain string representation of the email address, not
an regular expression (as which everything in that
filter-field is interpreted).

(mailman from Debian-i386, 2.1.5-8)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_id=103

From noreply at sourceforge.net  Wed Feb 15 16:21:57 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 15 Feb 2006 07:21:57 -0800
Subject: [ mailman-Bugs-1432090 ] Emails not entered in the filter rules very
	well
Message-ID: <E1F9OTd-0001qo-6S@sc8-sf-web5.sourceforge.net>

Bugs item #1432090, was opened at 2006-02-15 03:14
Message generated for change (Settings changed) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_id=103

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: Closed
>Resolution: Invalid
Priority: 2
Submitted By: gw- (gw-)
Assigned to: Nobody/Anonymous (nobody)
Summary: Emails not entered in the filter rules very well

Initial Comment:
When accepting an email from a non-subscriber (in a
closed mailing list) and selecting the option that the
sender should be added to the filter list of allowed
senders - this is not done very well, because it adds a
plain string representation of the email address, not
an regular expression (as which everything in that
filter-field is interpreted).

(mailman from Debian-i386, 2.1.5-8)

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-15 07:21

Message:
Logged In: YES 
user_id=1123998

It works as designed and as it should.

Entries in *_these_nonmembers are only interpreted as
regular expressions if they begin with '^'. Anything else is
an exact plain string match (case insensitive).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_id=103

From noreply at sourceforge.net  Wed Feb 15 16:58:32 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 15 Feb 2006 07:58:32 -0800
Subject: [ mailman-Bugs-1432090 ] Emails not entered in the filter rules very
	well
Message-ID: <E1F9P32-00052n-TC@sc8-sf-web1.sourceforge.net>

Bugs item #1432090, was opened at 2006-02-15 12:14
Message generated for change (Comment added) made by gw-
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_id=103

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: Closed
Resolution: Invalid
Priority: 2
Submitted By: gw- (gw-)
Assigned to: Nobody/Anonymous (nobody)
Summary: Emails not entered in the filter rules very well

Initial Comment:
When accepting an email from a non-subscriber (in a
closed mailing list) and selecting the option that the
sender should be added to the filter list of allowed
senders - this is not done very well, because it adds a
plain string representation of the email address, not
an regular expression (as which everything in that
filter-field is interpreted).

(mailman from Debian-i386, 2.1.5-8)

----------------------------------------------------------------------

>Comment By: gw- (gw-)
Date: 2006-02-15 16:58

Message:
Logged In: YES 
user_id=1334052

Oh, thanks for the explanation.

Than this means that the Slovene translation is invalid.

The current:
"Sporo??ila s katerega od teh naslovov bodo samodejno
odobrena, brez dodatne modifikacije. Dodajte naslove ??lanov,
vsakega v svojo vrstico; ki jo za??nete z znakom ^, ki
predstavlja regularni izraz za iskanje ujemanj."
should be replaced with:
"Sporo??ila prejeta s katerega od teh naslovov bodo samodejno
odobrena, brez dodatne modifikacije. Naslove ??lanov dodajte
vsakega v svojo vrstico. ??e ??elite pri tem uporabljati
regularne izraze za iskanje ujemanj, morate vrstico za??eti z ^."

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-15 16:21

Message:
Logged In: YES 
user_id=1123998

It works as designed and as it should.

Entries in *_these_nonmembers are only interpreted as
regular expressions if they begin with '^'. Anything else is
an exact plain string match (case insensitive).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_id=103

From noreply at sourceforge.net  Wed Feb 15 17:31:07 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 15 Feb 2006 08:31:07 -0800
Subject: [ mailman-Bugs-1432090 ] Emails not entered in the filter rules very
	well
Message-ID: <E1F9PYZ-0001zo-5Q@sc8-sf-web5.sourceforge.net>

Bugs item #1432090, was opened at 2006-02-15 03:14
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_id=103

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: Closed
Resolution: Invalid
Priority: 2
Submitted By: gw- (gw-)
Assigned to: Nobody/Anonymous (nobody)
Summary: Emails not entered in the filter rules very well

Initial Comment:
When accepting an email from a non-subscriber (in a
closed mailing list) and selecting the option that the
sender should be added to the filter list of allowed
senders - this is not done very well, because it adds a
plain string representation of the email address, not
an regular expression (as which everything in that
filter-field is interpreted).

(mailman from Debian-i386, 2.1.5-8)

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-15 08:31

Message:
Logged In: YES 
user_id=1123998

I can't read the Slovene translation, but it may be an
accurate rendition of the English which is a bit ambiguous.
It says:
"In the text boxes below, add one address per line; start
the line with a ^ character to designate a Python regular
expression. When entering backslashes, do so as if you were
using Python raw strings (i.e. you generally just use a
single backslash)."

It means "you may start the line ...".

The next paragraph says:
"Note that non-regexp matches are always done first."

which implies you don't need regexps.

The 'details' for these say:
"Add member addresses one per line; start the line with a ^
character to designate a regular expression match."

Perhaps these should say "optionally start the line ..." or
something similar.


----------------------------------------------------------------------

Comment By: gw- (gw-)
Date: 2006-02-15 07:58

Message:
Logged In: YES 
user_id=1334052

Oh, thanks for the explanation.

Than this means that the Slovene translation is invalid.

The current:
"Sporo??ila s katerega od teh naslovov bodo samodejno
odobrena, brez dodatne modifikacije. Dodajte naslove ??lanov,
vsakega v svojo vrstico; ki jo za??nete z znakom ^, ki
predstavlja regularni izraz za iskanje ujemanj."
should be replaced with:
"Sporo??ila prejeta s katerega od teh naslovov bodo samodejno
odobrena, brez dodatne modifikacije. Naslove ??lanov dodajte
vsakega v svojo vrstico. ??e ??elite pri tem uporabljati
regularne izraze za iskanje ujemanj, morate vrstico za??eti z ^."

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-15 07:21

Message:
Logged In: YES 
user_id=1123998

It works as designed and as it should.

Entries in *_these_nonmembers are only interpreted as
regular expressions if they begin with '^'. Anything else is
an exact plain string match (case insensitive).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_id=103

From noreply at sourceforge.net  Fri Feb 17 01:03:19 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 16 Feb 2006 16:03:19 -0800
Subject: [ mailman-Patches-1433262 ] Spanish i18n corrections
Message-ID: <E1F9t5j-0001Yn-Uz@sc8-sf-web1.sourceforge.net>

Patches item #1433262, was opened at 2006-02-16 16:03
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=1433262&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: internationalization
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Brion Vibber (vibber)
Assigned to: Nobody/Anonymous (nobody)
Summary: Spanish i18n corrections

Initial Comment:
Here's a patch with some corrections for the Spanish 
translations noticed by one of our users. Some are 
outright typos, a couple are changes to odd phrasings.

Info from our bug tracker:
http://bugzilla.wikimedia.org/show_bug.cgi?id=4961


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1433262&group_id=103

From noreply at sourceforge.net  Fri Feb 17 06:19:11 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 16 Feb 2006 21:19:11 -0800
Subject: [ mailman-Bugs-1430236 ] bin/arch fails with TypeError
Message-ID: <E1F9y1P-0006pq-E4@sc8-sf-web2.sourceforge.net>

Bugs item #1430236, was opened at 2006-02-12 11:02
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430236&group_id=103

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: command line scripts
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Andreas Thienemann (ixsnet)
Assigned to: Nobody/Anonymous (nobody)
Summary: bin/arch fails with TypeError

Initial Comment:
[root at bender mailman]# bin/arch -s 15965 -e 15965
bawue-net-admin
archives/private/bawue-net-admin.mbox/bawue-net-admin.mbox 
Pickling archive state into
/opt/mailman-2.1.7/archives/private/bawue-net-admin/pipermail.pck
Traceback (most recent call last):
  File "bin/arch", line 200, in ?
    main()
  File "bin/arch", line 188, in main
    archiver.processUnixMailbox(fp, start, end)
  File
"/opt/mailman-2.1.7/Mailman/Archiver/pipermail.py",
line 569, in processUnixMailbox
    m = mbox.next()
  File "/usr/lib/python2.2/mailbox.py", line 34, in next
    return self.factory(_Subfile(self.fp, start, stop))
  File "/opt/mailman-2.1.7/Mailman/Mailbox.py", line
89, in scrubber
    return mailbox.scrub(msg)
  File "/opt/mailman-2.1.7/Mailman/Mailbox.py", line
109, in scrub
    return self._scrubber(self._mlist, msg)
  File
"/opt/mailman-2.1.7/Mailman/Handlers/Scrubber.py", line
352, in process
    t = part.get_payload(decode=decode)
  File "/opt/mailman-2.1.7/pythonlib/email/Message.py",
line 213, in get_payload
    return Utils._qdecode(payload)
  File "/usr/lib/python2.2/quopri.py", line 161, in
decodestring
    return a2b_qp(s, header = header)
TypeError: argument 1 must be string or read-only
buffer, not None


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-16 21:19

Message:
Logged In: YES 
user_id=1123998

The underlying cause of this problem is the fact that the
original message contains a subpart of type
message/delivery-status which in turn contains a text/plain
'returned message'. The reason this is a problem is that the
Python email library parses message/delivery-status parts
differently from other MIME parts. It considers groups of
lines separated from each other by empty lines to each be
the headers of a sub-part of the message/delivery-status
part, and these sub-parts all have only headers and no bodies.

One of these sub-parts in this case has headers with
content-type text/plain which causes scrubber to try to
include the decoded body of this part in the flattened
text/plain message which causes the error.

The attached patch will catch the exception in this case and
allow the message to be added to the archive, but the entire
message/delivery-status part will not be in the archived
message because the parser treats it as all headers and no body.

Please try the patch and report whether you think this is
satisfactory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430236&group_id=103

From noreply at sourceforge.net  Fri Feb 17 17:02:48 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 17 Feb 2006 08:02:48 -0800
Subject: [ mailman-Bugs-1433666 ] News to mail gateway: Outlook Express broke
	uuenc.attachment
Message-ID: <E1FA84G-0004IL-3q@sc8-sf-web1.sourceforge.net>

Bugs item #1433666, was opened at 2006-02-17 16:02
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=1433666&group_id=103

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: nntp/news
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: D?niel Fraga (danielfraga)
Assigned to: Nobody/Anonymous (nobody)
Summary: News to mail gateway: Outlook Express broke uuenc.attachment

Initial Comment:
When someone posts on my nntp server a message with an
uuencoded attachment using Outlook Express, the message
appears broken in mailman.

For example:

Original message:
news://news.abusar.org/drq50u$gmp$2 at servicos.netuno.com.br

Mailman message (corrupted):

http://core.abusar.org/pipermail/u-br.lazer.humor/2006-February/000346.html?t

I think the problem is related to how mailman handles
the end of lines...

Thank you.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433666&group_id=103

From noreply at sourceforge.net  Fri Feb 17 17:24:35 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 17 Feb 2006 08:24:35 -0800
Subject: [ mailman-Bugs-1417678 ] Dutch translation wrong
Message-ID: <E1FA8PL-0002ca-9d@sc8-sf-web6.sourceforge.net>

Bugs item #1417678, was opened at 2006-01-29 00:56
Message generated for change (Comment added) made by schoinobates
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1417678&group_id=103

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: (un)subscribing
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Koen Martens (gmc2000)
Assigned to: Nobody/Anonymous (nobody)
Summary: Dutch translation wrong

Initial Comment:
On some versions i've seen 'Uw bent' in the dutch
translation of certain messages, this should be 'U
bent' (uw is possesive):

# grep "Uw bent" * -r
messages/nl/LC_MESSAGES/mailman.po:"Uw bent op deze
lijst aangemeld met het adres met niet te wijzigen You
are "
messages/nl/LC_MESSAGES/mailman.po:msgstr "Uw bent
afgemeld van de %(realname)s maillijst"
Binary file messages/nl/LC_MESSAGES/mailman.mo matches

Solution is simple: just s/Uw bent/U bent/g


----------------------------------------------------------------------

Comment By: Schoinobates Volans (schoinobates)
Date: 2006-02-17 17:24

Message:
Logged In: YES 
user_id=41822

More generally, Debian ships with a patched Dutch
translation (contributed by a user). SourceForge deems it
adequate to forbid me to attach it here, so contact the
maintainers at pkg-mailman-hackers at lists.alioth.debian.org
or take it from any Debian mirror.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1417678&group_id=103

From noreply at sourceforge.net  Fri Feb 17 17:25:40 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 17 Feb 2006 08:25:40 -0800
Subject: [ mailman-Patches-1418016 ] Dutch translation update
Message-ID: <E1FA8QO-0002d5-TB@sc8-sf-web6.sourceforge.net>

Patches item #1418016, was opened at 2006-01-29 17:04
Message generated for change (Comment added) made by schoinobates
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1418016&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: internationalization
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Schoinobates Volans (schoinobates)
Assigned to: Nobody/Anonymous (nobody)
Summary: Dutch translation update

Initial Comment:
A Debian user, Luc Stroobant, has contributed this
update to the Dutch translation.

----------------------------------------------------------------------

>Comment By: Schoinobates Volans (schoinobates)
Date: 2006-02-17 17:25

Message:
Logged In: YES 
user_id=41822

Slightly updated version.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1418016&group_id=103

From noreply at sourceforge.net  Sat Feb 18 02:22:04 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 17 Feb 2006 17:22:04 -0800
Subject: [ mailman-Bugs-1433666 ] News to mail gateway: Outlook Express broke
	uuenc.attachment
Message-ID: <E1FAGnU-00067E-NA@sc8-sf-web1.sourceforge.net>

Bugs item #1433666, was opened at 2006-02-17 08:02
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433666&group_id=103

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: nntp/news
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: D?niel Fraga (danielfraga)
Assigned to: Nobody/Anonymous (nobody)
Summary: News to mail gateway: Outlook Express broke uuenc.attachment

Initial Comment:
When someone posts on my nntp server a message with an
uuencoded attachment using Outlook Express, the message
appears broken in mailman.

For example:

Original message:
news://news.abusar.org/drq50u$gmp$2 at servicos.netuno.com.br

Mailman message (corrupted):

http://core.abusar.org/pipermail/u-br.lazer.humor/2006-February/000346.html?t

I think the problem is related to how mailman handles
the end of lines...

Thank you.


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-17 17:22

Message:
Logged In: YES 
user_id=1123998

Are you talking only of archived messages or individual
received messages as well?

In the case of the archived message you point to, the
problem is that you have configured the archiver to obscure
email addresses so that every '@' character in the uuencoded
data is rewritten as ' em '.

The issue is compounded by Outlook Express, because when
Outlook Express sends a uuencoded attachment, it does not
actually encapsulate the uuencoded attachment in a separate
MIME part. If it did, Scrubber would store it separately and
put a link to it in the archived message, but in the Outlook
Express case, the 'attachment' is not an attachment at all,
but rather just a uuencoded file in the body of the message.
Thus, it is just more text subject to munging by email
address obscuring.

I was going to close this report with the above explanation,
but I am waiting to hear if you also have a problem with
individual messages or digests. I know my explanation is
correct for the archives because I took the uuencoded data
from your archive page and replaced all the ' em ' with '@',
and I was then able to uudecode the file into a valid jpeg.

So, do you have a problem with messages or digests from the
list, and if so, can you provide an example message for
analysis?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433666&group_id=103

From noreply at sourceforge.net  Sun Feb 19 22:48:59 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 19 Feb 2006 13:48:59 -0800
Subject: [ mailman-Bugs-1433673 ] Wrong timezone in list archive index pages
Message-ID: <E1FAwQN-0003rm-7t@sc8-sf-web5.sourceforge.net>

Bugs item #1433673, was opened at 2006-02-17 08:08
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433673&group_id=103

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: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Schoinobates Volans (schoinobates)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong timezone in list archive index pages

Initial Comment:
This is Debian bug #352876 (see
http://bugs.debian.org/352876)

The timezone used on the list archive index pages for
the starting, ending, last message and archived on
dates is wrong. All these times are given in GMT (the
standard timezone for the UK) but are claimed to be BST
(British Summer Time, the daylight saving time used
between March and October, equivalent to GMT+1).

For example, the last message to one of my lists was
sent at Fri, 10 Feb 2006 10:07:40 +0000, but according
to the archives by thread page, the ending and last
message dates are "Fri Feb 10 10:07:40 BST 2006". The
timezone is correct in the archive page for the message
though, where it is given as "Fri Feb 10 10:07:40 GMT 2006"

The times given during the summer are correct, where
everything is in BST.

Original submitter claims timezone data and clock is
correct on the machine.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-19 13:48

Message:
Logged In: YES 
user_id=1123998

Patch has been committed to CVS.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-17 19:35

Message:
Logged In: YES 
user_id=1123998

The underlying problem is a bug in i18n.ctime().

When i18n.ctime is passed a time string, it uses
time.strptime() to convert the string into a struct_time. If
the string doesn't contain a time zone, strptime() returns
tm_isdst = -1 which the following code treats as 1 rather
than unknown.

The attached patch (2.1.7 base) will use the phrase "Server
Local Time" translated into the list language instead of BST
or whatever.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433673&group_id=103

From noreply at sourceforge.net  Sun Feb 19 22:50:11 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 19 Feb 2006 13:50:11 -0800
Subject: [ mailman-Bugs-1430236 ] bin/arch fails with TypeError
Message-ID: <E1FAwRX-0000ok-Db@sc8-sf-web1.sourceforge.net>

Bugs item #1430236, was opened at 2006-02-12 11:02
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430236&group_id=103

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: command line scripts
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Andreas Thienemann (ixsnet)
Assigned to: Nobody/Anonymous (nobody)
Summary: bin/arch fails with TypeError

Initial Comment:
[root at bender mailman]# bin/arch -s 15965 -e 15965
bawue-net-admin
archives/private/bawue-net-admin.mbox/bawue-net-admin.mbox 
Pickling archive state into
/opt/mailman-2.1.7/archives/private/bawue-net-admin/pipermail.pck
Traceback (most recent call last):
  File "bin/arch", line 200, in ?
    main()
  File "bin/arch", line 188, in main
    archiver.processUnixMailbox(fp, start, end)
  File
"/opt/mailman-2.1.7/Mailman/Archiver/pipermail.py",
line 569, in processUnixMailbox
    m = mbox.next()
  File "/usr/lib/python2.2/mailbox.py", line 34, in next
    return self.factory(_Subfile(self.fp, start, stop))
  File "/opt/mailman-2.1.7/Mailman/Mailbox.py", line
89, in scrubber
    return mailbox.scrub(msg)
  File "/opt/mailman-2.1.7/Mailman/Mailbox.py", line
109, in scrub
    return self._scrubber(self._mlist, msg)
  File
"/opt/mailman-2.1.7/Mailman/Handlers/Scrubber.py", line
352, in process
    t = part.get_payload(decode=decode)
  File "/opt/mailman-2.1.7/pythonlib/email/Message.py",
line 213, in get_payload
    return Utils._qdecode(payload)
  File "/usr/lib/python2.2/quopri.py", line 161, in
decodestring
    return a2b_qp(s, header = header)
TypeError: argument 1 must be string or read-only
buffer, not None


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-19 13:50

Message:
Logged In: YES 
user_id=1123998

Patch is commited to CVS.

----------------------------------------------------------------------

Comment By: Andreas Thienemann (ixsnet)
Date: 2006-02-19 07:16

Message:
Logged In: YES 
user_id=1450459

Thanks a lot.
The patch works so far as arch does not traceback anymore.

The attachment gets handled as follows:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: /
Size: 0 bytes
Desc: not available
Url : blabla

So yes, it's satisfactory.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-16 21:19

Message:
Logged In: YES 
user_id=1123998

The underlying cause of this problem is the fact that the
original message contains a subpart of type
message/delivery-status which in turn contains a text/plain
'returned message'. The reason this is a problem is that the
Python email library parses message/delivery-status parts
differently from other MIME parts. It considers groups of
lines separated from each other by empty lines to each be
the headers of a sub-part of the message/delivery-status
part, and these sub-parts all have only headers and no bodies.

One of these sub-parts in this case has headers with
content-type text/plain which causes scrubber to try to
include the decoded body of this part in the flattened
text/plain message which causes the error.

The attached patch will catch the exception in this case and
allow the message to be added to the archive, but the entire
message/delivery-status part will not be in the archived
message because the parser treats it as all headers and no body.

Please try the patch and report whether you think this is
satisfactory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430236&group_id=103

From noreply at sourceforge.net  Tue Feb 21 09:41:59 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 21 Feb 2006 00:41:59 -0800
Subject: [ mailman-Bugs-1435722 ] Subscription fails with some Language
	combinations
Message-ID: <E1FBT5r-00036H-6n@sc8-sf-web6.sourceforge.net>

Bugs item #1435722, was opened at 2006-02-21 09:41
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1435722&group_id=103

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: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Klaus Steinberger (kst)
Assigned to: Nobody/Anonymous (nobody)
Summary: Subscription fails with some Language combinations

Initial Comment:
I have some list with both english(USA) and german
language enabled. If somebody tries to subscribe and
selects german language, they get the "We hit a bug
message". This does not happen if german is the only
option, just if both english and german are enabled.
Also english must be the default to hit the bug.

Here are the error log details:

admin(4095): [----- Mailman Version: 2.1.7 -----]
admin(4095): [----- Traceback ------]
admin(4095): Traceback (most recent call last):
admin(4095):   File "/var/mailman/scripts/driver", line
101, in run_main
admin(4095):     main()
admin(4095):   File
"/var/mailman/Mailman/Cgi/subscribe.py", line 96, in main
admin(4095):     process_form(mlist, doc, cgidata,
language)
admin(4095):   File
"/var/mailman/Mailman/Cgi/subscribe.py", line 176, in
process_form
admin(4095):     mlist.AddMember(userdesc, remote)
admin(4095):   File "/var/mailman/Mailman/MailList.py",
line 899, in AddMember
admin(4095):     msg['Subject'] =
self.GetConfirmJoinSubject(realname, cookie)
admin(4095):   File "/var/mailman/Mailman/MailList.py",
line 216, in GetConfirmJoinSubject
admin(4095):     cset, header_name='subject')
admin(4095):   File
"/var/tmp/mailman-root/var/mailman/pythonlib/email/Header.py",
line 188, in __init__
admin(4095):   File
"/var/tmp/mailman-root/var/mailman/pythonlib/email/Header.py",
line 272, in append
admin(4095): UnicodeError: ASCII decoding error:
ordinal not in range(128)
admin(4095): [----- Python Information -----]
admin(4095): sys.version     =   2.2.2 (#1, Feb 24
2003, 19:13:11)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)]
admin(4095): sys.executable  =   /usr/bin/python
admin(4095): sys.prefix      =   /usr
admin(4095): sys.exec_prefix =   /usr
admin(4095): sys.path        =   /usr
admin(4095): sys.platform    =   linux2
admin(4095): [----- Environment Variables -----]
admin(4095):    PATH_INFO: /test
admin(4095):    CONTENT_LENGTH: 140
admin(4095):    SERVER_PORT: 443
admin(4095):    HTTP_COOKIE:
site=2802000000691dc6fa43732800000063323164313562353536396239393738616631303133646639393034626532623334636264363564
admin(4095):    SCRIPT_FILENAME:
/var/mailman/cgi-bin/subscribe
admin(4095):    PYTHONPATH: /var/mailman
admin(4095):    SERVER_SOFTWARE: Apache/2.0.51 (Fedora)
admin(4095):    SERVER_ADMIN:
Rechnergruppe at Physik.Uni-Muenchen.DE
admin(4095):    SCRIPT_NAME: /mailman/subscribe
admin(4095):    SCRIPT_URI:
https://lists.physik.uni-muenchen.de/mailman/subscribe/test
admin(4095):    SERVER_SIGNATURE:
<address>Apache/2.0.51 (Fedora) Server at
lists.physik.uni-muenchen.de Port 443</address>
admin(4095):
admin(4095):    REQUEST_METHOD: POST
admin(4095):    HTTP_HOST: lists.physik.uni-muenchen.de
admin(4095):    SCRIPT_URL: /mailman/subscribe/test
admin(4095):    HTTPS: on
admin(4095):    SERVER_PROTOCOL: HTTP/1.1
admin(4095):    QUERY_STRING:
admin(4095):    PATH_TRANSLATED:
/var/www/sites1/lists.physik.uni-muenchen.de/test
admin(4095):    REQUEST_URI: /mailman/subscribe/test
admin(4095):    HTTP_ACCEPT:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
admin(4095):    HTTP_ACCEPT_CHARSET:
ISO-8859-1,utf-8;q=0.7,*;q=0.7
admin(4095):    HTTP_USER_AGENT: Mozilla/5.0 (X11; U;
Linux i686; en-US; rv:1.7.12) Gecko/20050927
Fedora/1.0.7-1.1.fc3.mll.1 Firefox/1.0.7
admin(4095):    HTTP_CONNECTION: keep-alive
admin(4095):    HTTP_REFERER:
https://lists.physik.uni-muenchen.de/mailman/listinfo/test
admin(4095):    SERVER_NAME: lists.physik.uni-muenchen.de
admin(4095):    REMOTE_ADDR: 141.84.29.17
admin(4095):    REMOTE_PORT: 44945
admin(4095):    HTTP_ACCEPT_LANGUAGE:
de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
admin(4095):    UNIQUE_ID: s6td58A2KoEAAHdvB6gAAAAB
admin(4095):    CONTENT_TYPE:
application/x-www-form-urlencoded
admin(4095):    GATEWAY_INTERFACE: CGI/1.1
admin(4095):    DOCUMENT_ROOT:
/var/www/sites1/lists.physik.uni-muenchen.de/
admin(4095):    HTTP_ACCEPT_ENCODING: gzip,deflate
admin(4095):    SERVER_ADDR: 192.54.42.132
admin(4095):    HTTP_KEEP_ALIVE: 300


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1435722&group_id=103

From noreply at sourceforge.net  Tue Feb 21 19:17:31 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 21 Feb 2006 10:17:31 -0800
Subject: [ mailman-Bugs-1435722 ] Subscription fails with some Language
	combinations
Message-ID: <E1FBc4p-0007VH-7B@sc8-sf-web1.sourceforge.net>

Bugs item #1435722, was opened at 2006-02-21 00:41
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1435722&group_id=103

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: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Klaus Steinberger (kst)
Assigned to: Nobody/Anonymous (nobody)
Summary: Subscription fails with some Language combinations

Initial Comment:
I have some list with both english(USA) and german
language enabled. If somebody tries to subscribe and
selects german language, they get the "We hit a bug
message". This does not happen if german is the only
option, just if both english and german are enabled.
Also english must be the default to hit the bug.

Here are the error log details:

admin(4095): [----- Mailman Version: 2.1.7 -----]
admin(4095): [----- Traceback ------]
admin(4095): Traceback (most recent call last):
admin(4095):   File "/var/mailman/scripts/driver", line
101, in run_main
admin(4095):     main()
admin(4095):   File
"/var/mailman/Mailman/Cgi/subscribe.py", line 96, in main
admin(4095):     process_form(mlist, doc, cgidata,
language)
admin(4095):   File
"/var/mailman/Mailman/Cgi/subscribe.py", line 176, in
process_form
admin(4095):     mlist.AddMember(userdesc, remote)
admin(4095):   File "/var/mailman/Mailman/MailList.py",
line 899, in AddMember
admin(4095):     msg['Subject'] =
self.GetConfirmJoinSubject(realname, cookie)
admin(4095):   File "/var/mailman/Mailman/MailList.py",
line 216, in GetConfirmJoinSubject
admin(4095):     cset, header_name='subject')
admin(4095):   File
"/var/tmp/mailman-root/var/mailman/pythonlib/email/Header.py",
line 188, in __init__
admin(4095):   File
"/var/tmp/mailman-root/var/mailman/pythonlib/email/Header.py",
line 272, in append
admin(4095): UnicodeError: ASCII decoding error:
ordinal not in range(128)
admin(4095): [----- Python Information -----]
admin(4095): sys.version     =   2.2.2 (#1, Feb 24
2003, 19:13:11)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)]
admin(4095): sys.executable  =   /usr/bin/python
admin(4095): sys.prefix      =   /usr
admin(4095): sys.exec_prefix =   /usr
admin(4095): sys.path        =   /usr
admin(4095): sys.platform    =   linux2
admin(4095): [----- Environment Variables -----]
admin(4095):    PATH_INFO: /test
admin(4095):    CONTENT_LENGTH: 140
admin(4095):    SERVER_PORT: 443
admin(4095):    HTTP_COOKIE:
site=2802000000691dc6fa43732800000063323164313562353536396239393738616631303133646639393034626532623334636264363564
admin(4095):    SCRIPT_FILENAME:
/var/mailman/cgi-bin/subscribe
admin(4095):    PYTHONPATH: /var/mailman
admin(4095):    SERVER_SOFTWARE: Apache/2.0.51 (Fedora)
admin(4095):    SERVER_ADMIN:
Rechnergruppe at Physik.Uni-Muenchen.DE
admin(4095):    SCRIPT_NAME: /mailman/subscribe
admin(4095):    SCRIPT_URI:
https://lists.physik.uni-muenchen.de/mailman/subscribe/test
admin(4095):    SERVER_SIGNATURE:
<address>Apache/2.0.51 (Fedora) Server at
lists.physik.uni-muenchen.de Port 443</address>
admin(4095):
admin(4095):    REQUEST_METHOD: POST
admin(4095):    HTTP_HOST: lists.physik.uni-muenchen.de
admin(4095):    SCRIPT_URL: /mailman/subscribe/test
admin(4095):    HTTPS: on
admin(4095):    SERVER_PROTOCOL: HTTP/1.1
admin(4095):    QUERY_STRING:
admin(4095):    PATH_TRANSLATED:
/var/www/sites1/lists.physik.uni-muenchen.de/test
admin(4095):    REQUEST_URI: /mailman/subscribe/test
admin(4095):    HTTP_ACCEPT:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
admin(4095):    HTTP_ACCEPT_CHARSET:
ISO-8859-1,utf-8;q=0.7,*;q=0.7
admin(4095):    HTTP_USER_AGENT: Mozilla/5.0 (X11; U;
Linux i686; en-US; rv:1.7.12) Gecko/20050927
Fedora/1.0.7-1.1.fc3.mll.1 Firefox/1.0.7
admin(4095):    HTTP_CONNECTION: keep-alive
admin(4095):    HTTP_REFERER:
https://lists.physik.uni-muenchen.de/mailman/listinfo/test
admin(4095):    SERVER_NAME: lists.physik.uni-muenchen.de
admin(4095):    REMOTE_ADDR: 141.84.29.17
admin(4095):    REMOTE_PORT: 44945
admin(4095):    HTTP_ACCEPT_LANGUAGE:
de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
admin(4095):    UNIQUE_ID: s6td58A2KoEAAHdvB6gAAAAB
admin(4095):    CONTENT_TYPE:
application/x-www-form-urlencoded
admin(4095):    GATEWAY_INTERFACE: CGI/1.1
admin(4095):    DOCUMENT_ROOT:
/var/www/sites1/lists.physik.uni-muenchen.de/
admin(4095):    HTTP_ACCEPT_ENCODING: gzip,deflate
admin(4095):    SERVER_ADDR: 192.54.42.132
admin(4095):    HTTP_KEEP_ALIVE: 300


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-21 10:17

Message:
Logged In: YES 
user_id=1123998

There are two ways to deal with this bug in your case.

You can avoid it by changing the character set for 'en' in
the language table from 'us-ascii' to 'iso-8859-1'. You
would do this by putting:

add_language('en', 'English (USA)', 'iso-8859-1')

in mm_cfg.py.

Or, you can actually fix it with the attached patch to
Mailman/MailList.py. If possible, try the patch and let us
know how it works for you.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1435722&group_id=103

From noreply at sourceforge.net  Tue Feb 21 22:24:28 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 21 Feb 2006 13:24:28 -0800
Subject: [ mailman-Bugs-1435722 ] Subscription fails with some Language
	combinations
Message-ID: <E1FBezk-0003xg-DD@sc8-sf-web3.sourceforge.net>

Bugs item #1435722, was opened at 2006-02-21 09:41
Message generated for change (Comment added) made by kst
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1435722&group_id=103

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: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Klaus Steinberger (kst)
Assigned to: Nobody/Anonymous (nobody)
Summary: Subscription fails with some Language combinations

Initial Comment:
I have some list with both english(USA) and german
language enabled. If somebody tries to subscribe and
selects german language, they get the "We hit a bug
message". This does not happen if german is the only
option, just if both english and german are enabled.
Also english must be the default to hit the bug.

Here are the error log details:

admin(4095): [----- Mailman Version: 2.1.7 -----]
admin(4095): [----- Traceback ------]
admin(4095): Traceback (most recent call last):
admin(4095):   File "/var/mailman/scripts/driver", line
101, in run_main
admin(4095):     main()
admin(4095):   File
"/var/mailman/Mailman/Cgi/subscribe.py", line 96, in main
admin(4095):     process_form(mlist, doc, cgidata,
language)
admin(4095):   File
"/var/mailman/Mailman/Cgi/subscribe.py", line 176, in
process_form
admin(4095):     mlist.AddMember(userdesc, remote)
admin(4095):   File "/var/mailman/Mailman/MailList.py",
line 899, in AddMember
admin(4095):     msg['Subject'] =
self.GetConfirmJoinSubject(realname, cookie)
admin(4095):   File "/var/mailman/Mailman/MailList.py",
line 216, in GetConfirmJoinSubject
admin(4095):     cset, header_name='subject')
admin(4095):   File
"/var/tmp/mailman-root/var/mailman/pythonlib/email/Header.py",
line 188, in __init__
admin(4095):   File
"/var/tmp/mailman-root/var/mailman/pythonlib/email/Header.py",
line 272, in append
admin(4095): UnicodeError: ASCII decoding error:
ordinal not in range(128)
admin(4095): [----- Python Information -----]
admin(4095): sys.version     =   2.2.2 (#1, Feb 24
2003, 19:13:11)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)]
admin(4095): sys.executable  =   /usr/bin/python
admin(4095): sys.prefix      =   /usr
admin(4095): sys.exec_prefix =   /usr
admin(4095): sys.path        =   /usr
admin(4095): sys.platform    =   linux2
admin(4095): [----- Environment Variables -----]
admin(4095):    PATH_INFO: /test
admin(4095):    CONTENT_LENGTH: 140
admin(4095):    SERVER_PORT: 443
admin(4095):    HTTP_COOKIE:
site=2802000000691dc6fa43732800000063323164313562353536396239393738616631303133646639393034626532623334636264363564
admin(4095):    SCRIPT_FILENAME:
/var/mailman/cgi-bin/subscribe
admin(4095):    PYTHONPATH: /var/mailman
admin(4095):    SERVER_SOFTWARE: Apache/2.0.51 (Fedora)
admin(4095):    SERVER_ADMIN:
Rechnergruppe at Physik.Uni-Muenchen.DE
admin(4095):    SCRIPT_NAME: /mailman/subscribe
admin(4095):    SCRIPT_URI:
https://lists.physik.uni-muenchen.de/mailman/subscribe/test
admin(4095):    SERVER_SIGNATURE:
<address>Apache/2.0.51 (Fedora) Server at
lists.physik.uni-muenchen.de Port 443</address>
admin(4095):
admin(4095):    REQUEST_METHOD: POST
admin(4095):    HTTP_HOST: lists.physik.uni-muenchen.de
admin(4095):    SCRIPT_URL: /mailman/subscribe/test
admin(4095):    HTTPS: on
admin(4095):    SERVER_PROTOCOL: HTTP/1.1
admin(4095):    QUERY_STRING:
admin(4095):    PATH_TRANSLATED:
/var/www/sites1/lists.physik.uni-muenchen.de/test
admin(4095):    REQUEST_URI: /mailman/subscribe/test
admin(4095):    HTTP_ACCEPT:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
admin(4095):    HTTP_ACCEPT_CHARSET:
ISO-8859-1,utf-8;q=0.7,*;q=0.7
admin(4095):    HTTP_USER_AGENT: Mozilla/5.0 (X11; U;
Linux i686; en-US; rv:1.7.12) Gecko/20050927
Fedora/1.0.7-1.1.fc3.mll.1 Firefox/1.0.7
admin(4095):    HTTP_CONNECTION: keep-alive
admin(4095):    HTTP_REFERER:
https://lists.physik.uni-muenchen.de/mailman/listinfo/test
admin(4095):    SERVER_NAME: lists.physik.uni-muenchen.de
admin(4095):    REMOTE_ADDR: 141.84.29.17
admin(4095):    REMOTE_PORT: 44945
admin(4095):    HTTP_ACCEPT_LANGUAGE:
de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
admin(4095):    UNIQUE_ID: s6td58A2KoEAAHdvB6gAAAAB
admin(4095):    CONTENT_TYPE:
application/x-www-form-urlencoded
admin(4095):    GATEWAY_INTERFACE: CGI/1.1
admin(4095):    DOCUMENT_ROOT:
/var/www/sites1/lists.physik.uni-muenchen.de/
admin(4095):    HTTP_ACCEPT_ENCODING: gzip,deflate
admin(4095):    SERVER_ADDR: 192.54.42.132
admin(4095):    HTTP_KEEP_ALIVE: 300


----------------------------------------------------------------------

>Comment By: Klaus Steinberger (kst)
Date: 2006-02-21 22:24

Message:
Logged In: YES 
user_id=52018

Thanks! That's really fast response. I built a new RPM for 
my system with this patch and it works like a charm. 
 
Sincerly, 
Klaus 

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-21 22:04

Message:
Logged In: YES 
user_id=1123998

Revised patch.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-21 19:17

Message:
Logged In: YES 
user_id=1123998

There are two ways to deal with this bug in your case.

You can avoid it by changing the character set for 'en' in
the language table from 'us-ascii' to 'iso-8859-1'. You
would do this by putting:

add_language('en', 'English (USA)', 'iso-8859-1')

in mm_cfg.py.

Or, you can actually fix it with the attached patch to
Mailman/MailList.py. If possible, try the patch and let us
know how it works for you.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1435722&group_id=103

From noreply at sourceforge.net  Wed Feb 22 16:58:20 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 22 Feb 2006 07:58:20 -0800
Subject: [ mailman-Bugs-1433673 ] Wrong timezone in list archive index pages
Message-ID: <E1FBwNg-0008JO-6L@sc8-sf-web6.sourceforge.net>

Bugs item #1433673, was opened at 2006-02-17 16:08
Message generated for change (Comment added) made by rogerlynn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433673&group_id=103

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: 2.1 (stable)
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Schoinobates Volans (schoinobates)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong timezone in list archive index pages

Initial Comment:
This is Debian bug #352876 (see
http://bugs.debian.org/352876)

The timezone used on the list archive index pages for
the starting, ending, last message and archived on
dates is wrong. All these times are given in GMT (the
standard timezone for the UK) but are claimed to be BST
(British Summer Time, the daylight saving time used
between March and October, equivalent to GMT+1).

For example, the last message to one of my lists was
sent at Fri, 10 Feb 2006 10:07:40 +0000, but according
to the archives by thread page, the ending and last
message dates are "Fri Feb 10 10:07:40 BST 2006". The
timezone is correct in the archive page for the message
though, where it is given as "Fri Feb 10 10:07:40 GMT 2006"

The times given during the summer are correct, where
everything is in BST.

Original submitter claims timezone data and clock is
correct on the machine.

----------------------------------------------------------------------

Comment By: Roger Lynn (rogerlynn)
Date: 2006-02-22 15:58

Message:
Logged In: YES 
user_id=781651

Isn't the real problem that the time zone has been stripped
from the string in the first place?

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-19 21:48

Message:
Logged In: YES 
user_id=1123998

Patch has been committed to CVS.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-18 03:35

Message:
Logged In: YES 
user_id=1123998

The underlying problem is a bug in i18n.ctime().

When i18n.ctime is passed a time string, it uses
time.strptime() to convert the string into a struct_time. If
the string doesn't contain a time zone, strptime() returns
tm_isdst = -1 which the following code treats as 1 rather
than unknown.

The attached patch (2.1.7 base) will use the phrase "Server
Local Time" translated into the list language instead of BST
or whatever.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433673&group_id=103

From noreply at sourceforge.net  Wed Feb 22 17:29:00 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 22 Feb 2006 08:29:00 -0800
Subject: [ mailman-Bugs-1435722 ] Subscription fails with some Language
	combinations
Message-ID: <E1FBwrM-0008Pw-7B@sc8-sf-web6.sourceforge.net>

Bugs item #1435722, was opened at 2006-02-21 00:41
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1435722&group_id=103

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: (un)subscribing
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Klaus Steinberger (kst)
Assigned to: Nobody/Anonymous (nobody)
Summary: Subscription fails with some Language combinations

Initial Comment:
I have some list with both english(USA) and german
language enabled. If somebody tries to subscribe and
selects german language, they get the "We hit a bug
message". This does not happen if german is the only
option, just if both english and german are enabled.
Also english must be the default to hit the bug.

Here are the error log details:

admin(4095): [----- Mailman Version: 2.1.7 -----]
admin(4095): [----- Traceback ------]
admin(4095): Traceback (most recent call last):
admin(4095):   File "/var/mailman/scripts/driver", line
101, in run_main
admin(4095):     main()
admin(4095):   File
"/var/mailman/Mailman/Cgi/subscribe.py", line 96, in main
admin(4095):     process_form(mlist, doc, cgidata,
language)
admin(4095):   File
"/var/mailman/Mailman/Cgi/subscribe.py", line 176, in
process_form
admin(4095):     mlist.AddMember(userdesc, remote)
admin(4095):   File "/var/mailman/Mailman/MailList.py",
line 899, in AddMember
admin(4095):     msg['Subject'] =
self.GetConfirmJoinSubject(realname, cookie)
admin(4095):   File "/var/mailman/Mailman/MailList.py",
line 216, in GetConfirmJoinSubject
admin(4095):     cset, header_name='subject')
admin(4095):   File
"/var/tmp/mailman-root/var/mailman/pythonlib/email/Header.py",
line 188, in __init__
admin(4095):   File
"/var/tmp/mailman-root/var/mailman/pythonlib/email/Header.py",
line 272, in append
admin(4095): UnicodeError: ASCII decoding error:
ordinal not in range(128)
admin(4095): [----- Python Information -----]
admin(4095): sys.version     =   2.2.2 (#1, Feb 24
2003, 19:13:11)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)]
admin(4095): sys.executable  =   /usr/bin/python
admin(4095): sys.prefix      =   /usr
admin(4095): sys.exec_prefix =   /usr
admin(4095): sys.path        =   /usr
admin(4095): sys.platform    =   linux2
admin(4095): [----- Environment Variables -----]
admin(4095):    PATH_INFO: /test
admin(4095):    CONTENT_LENGTH: 140
admin(4095):    SERVER_PORT: 443
admin(4095):    HTTP_COOKIE:
site=2802000000691dc6fa43732800000063323164313562353536396239393738616631303133646639393034626532623334636264363564
admin(4095):    SCRIPT_FILENAME:
/var/mailman/cgi-bin/subscribe
admin(4095):    PYTHONPATH: /var/mailman
admin(4095):    SERVER_SOFTWARE: Apache/2.0.51 (Fedora)
admin(4095):    SERVER_ADMIN:
Rechnergruppe at Physik.Uni-Muenchen.DE
admin(4095):    SCRIPT_NAME: /mailman/subscribe
admin(4095):    SCRIPT_URI:
https://lists.physik.uni-muenchen.de/mailman/subscribe/test
admin(4095):    SERVER_SIGNATURE:
<address>Apache/2.0.51 (Fedora) Server at
lists.physik.uni-muenchen.de Port 443</address>
admin(4095):
admin(4095):    REQUEST_METHOD: POST
admin(4095):    HTTP_HOST: lists.physik.uni-muenchen.de
admin(4095):    SCRIPT_URL: /mailman/subscribe/test
admin(4095):    HTTPS: on
admin(4095):    SERVER_PROTOCOL: HTTP/1.1
admin(4095):    QUERY_STRING:
admin(4095):    PATH_TRANSLATED:
/var/www/sites1/lists.physik.uni-muenchen.de/test
admin(4095):    REQUEST_URI: /mailman/subscribe/test
admin(4095):    HTTP_ACCEPT:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
admin(4095):    HTTP_ACCEPT_CHARSET:
ISO-8859-1,utf-8;q=0.7,*;q=0.7
admin(4095):    HTTP_USER_AGENT: Mozilla/5.0 (X11; U;
Linux i686; en-US; rv:1.7.12) Gecko/20050927
Fedora/1.0.7-1.1.fc3.mll.1 Firefox/1.0.7
admin(4095):    HTTP_CONNECTION: keep-alive
admin(4095):    HTTP_REFERER:
https://lists.physik.uni-muenchen.de/mailman/listinfo/test
admin(4095):    SERVER_NAME: lists.physik.uni-muenchen.de
admin(4095):    REMOTE_ADDR: 141.84.29.17
admin(4095):    REMOTE_PORT: 44945
admin(4095):    HTTP_ACCEPT_LANGUAGE:
de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
admin(4095):    UNIQUE_ID: s6td58A2KoEAAHdvB6gAAAAB
admin(4095):    CONTENT_TYPE:
application/x-www-form-urlencoded
admin(4095):    GATEWAY_INTERFACE: CGI/1.1
admin(4095):    DOCUMENT_ROOT:
/var/www/sites1/lists.physik.uni-muenchen.de/
admin(4095):    HTTP_ACCEPT_ENCODING: gzip,deflate
admin(4095):    SERVER_ADDR: 192.54.42.132
admin(4095):    HTTP_KEEP_ALIVE: 300


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-22 08:29

Message:
Logged In: YES 
user_id=1123998

Patch commited in CVS.

----------------------------------------------------------------------

Comment By: Klaus Steinberger (kst)
Date: 2006-02-21 13:24

Message:
Logged In: YES 
user_id=52018

Thanks! That's really fast response. I built a new RPM for 
my system with this patch and it works like a charm. 
 
Sincerly, 
Klaus 

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-21 13:04

Message:
Logged In: YES 
user_id=1123998

Revised patch.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-21 10:17

Message:
Logged In: YES 
user_id=1123998

There are two ways to deal with this bug in your case.

You can avoid it by changing the character set for 'en' in
the language table from 'us-ascii' to 'iso-8859-1'. You
would do this by putting:

add_language('en', 'English (USA)', 'iso-8859-1')

in mm_cfg.py.

Or, you can actually fix it with the attached patch to
Mailman/MailList.py. If possible, try the patch and let us
know how it works for you.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1435722&group_id=103

From noreply at sourceforge.net  Wed Feb 22 17:47:18 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 22 Feb 2006 08:47:18 -0800
Subject: [ mailman-Bugs-1433673 ] Wrong timezone in list archive index pages
Message-ID: <E1FBx94-00063D-GX@sc8-sf-web5.sourceforge.net>

Bugs item #1433673, was opened at 2006-02-17 08:08
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433673&group_id=103

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: 2.1 (stable)
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Schoinobates Volans (schoinobates)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong timezone in list archive index pages

Initial Comment:
This is Debian bug #352876 (see
http://bugs.debian.org/352876)

The timezone used on the list archive index pages for
the starting, ending, last message and archived on
dates is wrong. All these times are given in GMT (the
standard timezone for the UK) but are claimed to be BST
(British Summer Time, the daylight saving time used
between March and October, equivalent to GMT+1).

For example, the last message to one of my lists was
sent at Fri, 10 Feb 2006 10:07:40 +0000, but according
to the archives by thread page, the ending and last
message dates are "Fri Feb 10 10:07:40 BST 2006". The
timezone is correct in the archive page for the message
though, where it is given as "Fri Feb 10 10:07:40 GMT 2006"

The times given during the summer are correct, where
everything is in BST.

Original submitter claims timezone data and clock is
correct on the machine.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-22 08:47

Message:
Logged In: YES 
user_id=1123998

>Isn't the real problem that the time zone has been
>stripped from the string in the first place?

Sort of. The problem here is that the string is produced by
time.asctime() which doesn't put a timezone in the string.
Changing this would be a significant change to the archiver
which might well break something else - at least if I did it :-)



----------------------------------------------------------------------

Comment By: Roger Lynn (rogerlynn)
Date: 2006-02-22 07:58

Message:
Logged In: YES 
user_id=781651

Isn't the real problem that the time zone has been stripped
from the string in the first place?

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-19 13:48

Message:
Logged In: YES 
user_id=1123998

Patch has been committed to CVS.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-17 19:35

Message:
Logged In: YES 
user_id=1123998

The underlying problem is a bug in i18n.ctime().

When i18n.ctime is passed a time string, it uses
time.strptime() to convert the string into a struct_time. If
the string doesn't contain a time zone, strptime() returns
tm_isdst = -1 which the following code treats as 1 rather
than unknown.

The attached patch (2.1.7 base) will use the phrase "Server
Local Time" translated into the list language instead of BST
or whatever.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433673&group_id=103

From noreply at sourceforge.net  Thu Feb 23 05:34:41 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 22 Feb 2006 20:34:41 -0800
Subject: [ mailman-Bugs-1433673 ] Wrong timezone in list archive index pages
Message-ID: <E1FC8Bd-0000Ph-Ew@sc8-sf-web4-b.sourceforge.net>

Bugs item #1433673, was opened at 2006-02-17 08:08
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433673&group_id=103

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: 2.1 (stable)
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Schoinobates Volans (schoinobates)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong timezone in list archive index pages

Initial Comment:
This is Debian bug #352876 (see
http://bugs.debian.org/352876)

The timezone used on the list archive index pages for
the starting, ending, last message and archived on
dates is wrong. All these times are given in GMT (the
standard timezone for the UK) but are claimed to be BST
(British Summer Time, the daylight saving time used
between March and October, equivalent to GMT+1).

For example, the last message to one of my lists was
sent at Fri, 10 Feb 2006 10:07:40 +0000, but according
to the archives by thread page, the ending and last
message dates are "Fri Feb 10 10:07:40 BST 2006". The
timezone is correct in the archive page for the message
though, where it is given as "Fri Feb 10 10:07:40 GMT 2006"

The times given during the summer are correct, where
everything is in BST.

Original submitter claims timezone data and clock is
correct on the machine.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-22 20:34

Message:
Logged In: YES 
user_id=1123998

I've thought about this some more and I've come up with a
different fix which will use tm_isdst from time.localtime()
in those cases where time.strptime() returns tm_isdst = -1.
Thanks to Roger Lynn for the motivation.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-22 08:47

Message:
Logged In: YES 
user_id=1123998

>Isn't the real problem that the time zone has been
>stripped from the string in the first place?

Sort of. The problem here is that the string is produced by
time.asctime() which doesn't put a timezone in the string.
Changing this would be a significant change to the archiver
which might well break something else - at least if I did it :-)



----------------------------------------------------------------------

Comment By: Roger Lynn (rogerlynn)
Date: 2006-02-22 07:58

Message:
Logged In: YES 
user_id=781651

Isn't the real problem that the time zone has been stripped
from the string in the first place?

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-19 13:48

Message:
Logged In: YES 
user_id=1123998

Patch has been committed to CVS.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-02-17 19:35

Message:
Logged In: YES 
user_id=1123998

The underlying problem is a bug in i18n.ctime().

When i18n.ctime is passed a time string, it uses
time.strptime() to convert the string into a struct_time. If
the string doesn't contain a time zone, strptime() returns
tm_isdst = -1 which the following code treats as 1 rather
than unknown.

The attached patch (2.1.7 base) will use the phrase "Server
Local Time" translated into the list language instead of BST
or whatever.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1433673&group_id=103

From noreply at sourceforge.net  Thu Feb 23 19:01:31 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 23 Feb 2006 10:01:31 -0800
Subject: [ mailman-Bugs-1437581 ] Mailman Auto-unsubscribes Bad Addresses?
Message-ID: <E1FCKmR-0001fp-CH@sc8-sf-web5.sourceforge.net>

Bugs item #1437581, was opened at 2006-02-23 13:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1437581&group_id=103

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: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Bruce Scherzinger (bascherz)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman Auto-unsubscribes Bad Addresses?

Initial Comment:
I haven't seen any settings for this, and I can only 
describe it based on the information that I have. But 
today I received bounce notices identically 
timestamped for three separate email addresses in the 
same domain. The notices all indicated the addresses 
had been unsubscribed from a specific Mailman list. I 
don't know what initiated the action, and these same 
addresses are still subscribed to other, less-
frequently used lists.

I sent emails directly to the three addresses to 
notify them of the issue, and I got back a response 
from their email server as follows (actual email 
addresses omitted or replaced for privacy reasons):

- - - - - - - - - - - - - - - -
Return-Path: <>
X-Envelope-To: <my_email_address>
X-Spam-Status: No, hits=2.4 required=5.0
	tests=AWL: -0.181,HTML_30_40: 
0.879,HTML_MESSAGE: 0.001,
	MIME_HTML_MOSTLY: 1.54,VIRUS_WARNING268B: 0.2
X-Spam-Level: **
Return-Path: <>
Delivered-To: <my_email_address>
Received: (qmail 29847 invoked by uid 399); 23 Feb 
2006 17:21:13 -0000
X-Virus-Scan: Scanned by clamdmail 0.15 (no viruses);
  Thu, 23 Feb 2006 11:21:13 -0600
Received: from unknown (HELO eastrmmtao06.cox.net) 
(68.230.240.33)
  by mail.opentransfer.com with SMTP; 23 Feb 2006 
17:21:13 -0000
To: <my_email_address> 
From: Mail Administrator <Postmaster at cox.net> 
Reply-To: <Postmaster at cox.net>
Subject: Mail System Error - Returned Mail
Date: Thu, 23 Feb 2006 12:21:06 -0500
Message-ID: <omitted>
MIME-Version: 1.0
Content-Type: multipart/report;
		report-type=delivery-status;
	
	Boundary="===========================_ _= 
9638061(9108)1140715266"


--===========================_ _= 9638061(9108)
1140715266
Content-Type: text/plain 
  
 This Message was undeliverable due to the following 
reason: 
  
 Each of the following recipients was rejected by a 
remote mail server. The reasons given by the server 
are included to help you determine why each recipient 
was rejected.

    Recipient: <addr1 at erols.com>
    Reason:    #5.1.1 bad address addr1 at erols.com

    Recipient: <addr2 at erols.com>
    Reason:    #5.1.1 bad address addr2 at erols.com

    Recipient: <addr3 at erols.com>
    Reason:    #5.1.1 bad address addr3 at erols.com
- - - - - - - - - - - - - - - -

So, all three addresses are bad. Does Mailman 
automatically unsubscribe addresses if it can't 
deliver to them? Or, is there a way to spoof it to 
get it to delete addresses? Is it possible the email 
server (erols.com in this case) can determine that 
there are messages being sent from a Mailman email 
list and send unsubscribe requests to the Mailman 
server to make them stop?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1437581&group_id=103

From noreply at sourceforge.net  Thu Feb 23 19:10:48 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 23 Feb 2006 10:10:48 -0800
Subject: [ mailman-Bugs-1437581 ] Mailman Auto-unsubscribes Bad Addresses?
Message-ID: <E1FCKvQ-0007OH-Js@sc8-sf-web1.sourceforge.net>

Bugs item #1437581, was opened at 2006-02-23 13:01
Message generated for change (Comment added) made by bascherz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1437581&group_id=103

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: (un)subscribing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Bruce Scherzinger (bascherz)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman Auto-unsubscribes Bad Addresses?

Initial Comment:
I haven't seen any settings for this, and I can only 
describe it based on the information that I have. But 
today I received bounce notices identically 
timestamped for three separate email addresses in the 
same domain. The notices all indicated the addresses 
had been unsubscribed from a specific Mailman list. I 
don't know what initiated the action, and these same 
addresses are still subscribed to other, less-
frequently used lists.

I sent emails directly to the three addresses to 
notify them of the issue, and I got back a response 
from their email server as follows (actual email 
addresses omitted or replaced for privacy reasons):

- - - - - - - - - - - - - - - -
Return-Path: <>
X-Envelope-To: <my_email_address>
X-Spam-Status: No, hits=2.4 required=5.0
	tests=AWL: -0.181,HTML_30_40: 
0.879,HTML_MESSAGE: 0.001,
	MIME_HTML_MOSTLY: 1.54,VIRUS_WARNING268B: 0.2
X-Spam-Level: **
Return-Path: <>
Delivered-To: <my_email_address>
Received: (qmail 29847 invoked by uid 399); 23 Feb 
2006 17:21:13 -0000
X-Virus-Scan: Scanned by clamdmail 0.15 (no viruses);
  Thu, 23 Feb 2006 11:21:13 -0600
Received: from unknown (HELO eastrmmtao06.cox.net) 
(68.230.240.33)
  by mail.opentransfer.com with SMTP; 23 Feb 2006 
17:21:13 -0000
To: <my_email_address> 
From: Mail Administrator <Postmaster at cox.net> 
Reply-To: <Postmaster at cox.net>
Subject: Mail System Error - Returned Mail
Date: Thu, 23 Feb 2006 12:21:06 -0500
Message-ID: <omitted>
MIME-Version: 1.0
Content-Type: multipart/report;
		report-type=delivery-status;
	
	Boundary="===========================_ _= 
9638061(9108)1140715266"


--===========================_ _= 9638061(9108)
1140715266
Content-Type: text/plain 
  
 This Message was undeliverable due to the following 
reason: 
  
 Each of the following recipients was rejected by a 
remote mail server. The reasons given by the server 
are included to help you determine why each recipient 
was rejected.

    Recipient: <addr1 at erols.com>
    Reason:    #5.1.1 bad address addr1 at erols.com

    Recipient: <addr2 at erols.com>
    Reason:    #5.1.1 bad address addr2 at erols.com

    Recipient: <addr3 at erols.com>
    Reason:    #5.1.1 bad address addr3 at erols.com
- - - - - - - - - - - - - - - -

So, all three addresses are bad. Does Mailman 
automatically unsubscribe addresses if it can't 
deliver to them? Or, is there a way to spoof it to 
get it to delete addresses? Is it possible the email 
server (erols.com in this case) can determine that 
there are messages being sent from a Mailman email 
list and send unsubscribe requests to the Mailman 
server to make them stop?

----------------------------------------------------------------------

>Comment By: Bruce Scherzinger (bascherz)
Date: 2006-02-23 13:10

Message:
Logged In: YES 
user_id=1415850

I failed to mention that the webhosting company has 
Mailman v2.1.6 installed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1437581&group_id=103

From noreply at sourceforge.net  Fri Feb 24 01:36:29 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 23 Feb 2006 16:36:29 -0800
Subject: [ mailman-Bugs-1437581 ] Mailman Auto-unsubscribes Bad Addresses?
Message-ID: <E1FCQwf-0008Rd-La@sc8-sf-web1.sourceforge.net>

Bugs item #1437581, was opened at 2006-02-23 10:01
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1437581&group_id=103

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: (un)subscribing
Group: 2.1 (stable)
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Bruce Scherzinger (bascherz)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman Auto-unsubscribes Bad Addresses?

Initial Comment:
I haven't seen any settings for this, and I can only 
describe it based on the information that I have. But 
today I received bounce notices identically 
timestamped for three separate email addresses in the 
same domain. The notices all indicated the addresses 
had been unsubscribed from a specific Mailman list. I 
don't know what initiated the action, and these same 
addresses are still subscribed to other, less-
frequently used lists.

I sent emails directly to the three addresses to 
notify them of the issue, and I got back a response 
from their email server as follows (actual email 
addresses omitted or replaced for privacy reasons):

- - - - - - - - - - - - - - - -
Return-Path: <>
X-Envelope-To: <my_email_address>
X-Spam-Status: No, hits=2.4 required=5.0
	tests=AWL: -0.181,HTML_30_40: 
0.879,HTML_MESSAGE: 0.001,
	MIME_HTML_MOSTLY: 1.54,VIRUS_WARNING268B: 0.2
X-Spam-Level: **
Return-Path: <>
Delivered-To: <my_email_address>
Received: (qmail 29847 invoked by uid 399); 23 Feb 
2006 17:21:13 -0000
X-Virus-Scan: Scanned by clamdmail 0.15 (no viruses);
  Thu, 23 Feb 2006 11:21:13 -0600
Received: from unknown (HELO eastrmmtao06.cox.net) 
(68.230.240.33)
  by mail.opentransfer.com with SMTP; 23 Feb 2006 
17:21:13 -0000
To: <my_email_address> 
From: Mail Administrator <Postmaster at cox.net> 
Reply-To: <Postmaster at cox.net>
Subject: Mail System Error - Returned Mail
Date: Thu, 23 Feb 2006 12:21:06 -0500
Message-ID: <omitted>
MIME-Version: 1.0
Content-Type: multipart/report;
		report-type=delivery-status;
	
	Boundary="===========================_ _= 
9638061(9108)1140715266"


--===========================_ _= 9638061(9108)
1140715266
Content-Type: text/plain 
  
 This Message was undeliverable due to the following 
reason: 
  
 Each of the following recipients was rejected by a 
remote mail server. The reasons given by the server 
are included to help you determine why each recipient 
was rejected.

    Recipient: <addr1 at erols.com>
    Reason:    #5.1.1 bad address addr1 at erols.com

    Recipient: <addr2 at erols.com>
    Reason:    #5.1.1 bad address addr2 at erols.com

    Recipient: <addr3 at erols.com>
    Reason:    #5.1.1 bad address addr3 at erols.com
- - - - - - - - - - - - - - - -

So, all three addresses are bad. Does Mailman 
automatically unsubscribe addresses if it can't 
deliver to them? Or, is there a way to spoof it to 
get it to delete addresses? Is it possible the email 
server (erols.com in this case) can determine that 
there are messages being sent from a Mailman email 
list and send unsubscribe requests to the Mailman 
server to make them stop?

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-02-23 16:36

Message:
Logged In: YES 
user_id=1123998

I am closing this because mailman is doing what it should.
The users were unsubscribed by bounce processing. The
settings for this are list by list on the Bounce processing
page of the admin web interface.

Mailman registers the bounce notices that it receives in
response to post deliveries and handles them according to
bounce settings. The remote server has no direct involvement
with the unsubscribe. It just returns a notice to mailman
just like the notice returned to you when you mailed these
addresses directly. The process is described on the Bounce
processing page.

And yes, bounce notifications can be spoofed, but with
normal default settings, the spoofer would have to send 5
spoofed notices on different days, and then the member would
have list delivery disabled and be sent a warning, and be
sent two more warnings at one week intervals before being
unsubscribed. Also, you can select the option to notify the
list owner when the subscription is disabled, so
unsubscribing a user by spoofing bounces is not likely to be
successful if the user actually has any interest in the list.


----------------------------------------------------------------------

Comment By: Bruce Scherzinger (bascherz)
Date: 2006-02-23 10:10

Message:
Logged In: YES 
user_id=1415850

I failed to mention that the webhosting company has 
Mailman v2.1.6 installed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1437581&group_id=103

From noreply at sourceforge.net  Fri Feb 24 05:53:06 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 23 Feb 2006 20:53:06 -0800
Subject: [ mailman-Patches-1437867 ] Bug: canonstr() with funny character
Message-ID: <E1FCUx0-0004He-Tb@sc8-sf-web4-b.sourceforge.net>

Patches item #1437867, was opened at 2006-02-24 13:53
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=1437867&group_id=103

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: Web UI
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bug: canonstr() with funny character

Initial Comment:
Utils.canonstr() generates traceback when user's
realname contains some unconvertible characters (\ufffd
etc.).

A patch is attached.


Tracebacks (line numbers have some offsets):

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
176, in main
    change_options(mlist, category, subcat, cgidata, doc)
  File "/usr/local/mailman/Mailman/Cgi/admin.py", line
1497, in change_options
    newname = Utils.canonstr(newname,
mlist.preferred_language)
  File "/usr/local/mailman/Mailman/Utils.py", line 850,
in canonstr
    newstr = EMPTYSTRING.join(newparts)
UnicodeDecodeError: 'ascii' codec can't decode byte
0x8e in position 0: ordinal not in range(128)



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1437867&group_id=103

From noreply at sourceforge.net  Mon Feb 27 18:56:23 2006
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 27 Feb 2006 09:56:23 -0800
Subject: [ mailman-Feature Requests-1439790 ] Make all web interface pages
	XHTML compliant
Message-ID: <E1FDmbf-000355-4d@sc8-sf-web1.sourceforge.net>

Feature Requests item #1439790, was opened at 2006-02-27 09:56
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=1439790&group_id=103

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: Dragon (dragon93)
Assigned to: Nobody/Anonymous (nobody)
Summary: Make all web interface pages XHTML compliant

Initial Comment:
It would be very nice to have the web interface to 
Mailman updated to current W3C recommended standards 
for page markup. XHTML 1.0 strict with CSS Level 2 
should be the goal.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1439790&group_id=103