From 266821 at bugs.launchpad.net  Mon Oct  1 08:51:37 2012
From: 266821 at bugs.launchpad.net (trampster)
Date: Mon, 01 Oct 2012 06:51:37 -0000
Subject: [Bug 266821] Re: privacy hole in password reminder
References: <20080905194256.1806.8914.launchpad@forster.canonical.com>
Message-ID: <20121001065137.29018.78770.malone@wampee.canonical.com>

It is completely unacceptable that such a widely used opensource tool as
this has such a major security flaw in it.

You should not be able to send me my password in plaintext. Because
passwords should be stored using an non reversible salted hash.

This is a major PR disaster just waiting to happen. Mainman would become
a laughing stock of the software world.

How has this gone unfixed for 6 years.

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266821

Title:
  privacy hole in password reminder

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266821/+subscriptions

From 266821 at bugs.launchpad.net  Mon Oct  1 16:20:25 2012
From: 266821 at bugs.launchpad.net (Barry Warsaw)
Date: Mon, 01 Oct 2012 14:20:25 -0000
Subject: [Bug 266821] Re: privacy hole in password reminder
References: <20080905194256.1806.8914.launchpad@forster.canonical.com>
	<20121001065137.29018.78770.malone@wampee.canonical.com>
Message-ID: <20121001102025.60684c07@limelight.wooz.org>

On Oct 01, 2012, at 06:51 AM, trampster wrote:

>You should not be able to send me my password in plaintext. Because
>passwords should be stored using an non reversible salted hash.

There are many documented ways to disable password reminders on a per-user,
per-list, or per-site basis.  Please read the FAQ.

Mailman 3 removes password reminders and hashes passwords with a configurable
hash algorithm (by default salted sha512).

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266821

Title:
  privacy hole in password reminder

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266821/+subscriptions

From mark at msapiro.net  Mon Oct  1 19:49:27 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 01 Oct 2012 17:49:27 -0000
Subject: [Bug 266821] Re: privacy hole in password reminder
References: <20080905194256.1806.8914.launchpad@forster.canonical.com>
Message-ID: <20121001174928.5702.28166.launchpad@wampee.canonical.com>

*** This bug is a duplicate of bug 265179 ***
    https://bugs.launchpad.net/bugs/265179

** This bug has been marked a duplicate of bug 265179
   Security hole: passwords mailed in clear

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266821

Title:
  privacy hole in password reminder

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266821/+subscriptions

From 266821 at bugs.launchpad.net  Mon Oct  1 22:51:48 2012
From: 266821 at bugs.launchpad.net (trampster)
Date: Mon, 01 Oct 2012 20:51:48 -0000
Subject: [Bug 266821] Re: privacy hole in password reminder
References: <20080905194256.1806.8914.launchpad@forster.canonical.com>
	<20121001174928.5702.28166.launchpad@wampee.canonical.com>
Message-ID: <CAC5vxh34ELkDPsDRgSxWHWO+5SwfVb1Bvh1HiAuu0p=ZP6rAPQ@mail.gmail.com>

*** This bug is a duplicate of bug 265179 ***
    https://bugs.launchpad.net/bugs/265179

Are you aware that the bug you made this a duplicate of is marked as
invalid.

On Tue, Oct 2, 2012 at 6:49 AM, Mark Sapiro <mark at msapiro.net> wrote:

> *** This bug is a duplicate of bug 265179 ***
>     https://bugs.launchpad.net/bugs/265179
>
> ** This bug has been marked a duplicate of bug 265179
>    Security hole: passwords mailed in clear
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/266821
>
> Title:
>   privacy hole in password reminder
>
> Status in GNU Mailman:
>   Triaged
>
> Bug description:
>   Mailman sends me password reminders in plain text. I
>   can disable this feature, but other users can manually
>   make it send a reminder just as if I had forgot the
>   password, with no other question being asked. If smart
>   enough to intercept that message, the attacker could:
>
>   1) Get my password;
>   2) get my IP in the mail header.
>
>   Possible solutions:
>
>   1) Some sites and programs use a "secret question"
>   which right answer would give the user the chance to
>   get a password reminder.
>
>   2) The password could be prompted in a secure html
>   page. I find this safer, as compared to plain text mails.
>
>   [
> http://sourceforge.net/tracker/index.php?func=detail&aid=1441723&group_id=103&atid=350103
> ]
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mailman/+bug/266821/+subscriptions
>


** Bug watch added: SourceForge.net Tracker #1441723
   http://sourceforge.net/support/tracker.php?aid=1441723

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266821

Title:
  privacy hole in password reminder

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266821/+subscriptions

From mark at msapiro.net  Mon Oct  1 23:56:33 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 01 Oct 2012 21:56:33 -0000
Subject: [Bug 265179] Re: Security hole: passwords mailed in clear
References: <20080905191826.27052.96947.launchpad@forster.canonical.com>
Message-ID: <20121001215633.15431.69109.malone@chaenomeles.canonical.com>

Won't fix applies to Mailman 2.1. Mailman 3 does not store clear text
passwords.

** Changed in: mailman
       Status: Invalid => Won't Fix

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/265179

Title:
  Security hole: passwords mailed in clear

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/265179/+subscriptions

From mark at msapiro.net  Mon Oct  1 23:58:27 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 01 Oct 2012 21:58:27 -0000
Subject: [Bug 266821] Re: privacy hole in password reminder
References: <20080905194256.1806.8914.launchpad@forster.canonical.com>
	<20121001174928.5702.28166.launchpad@wampee.canonical.com>
	<CAC5vxh34ELkDPsDRgSxWHWO+5SwfVb1Bvh1HiAuu0p=ZP6rAPQ@mail.gmail.com>
Message-ID: <PC195201210011458270515ae2cfd9e@MSAPIRO>

*** This bug is a duplicate of bug 265179 ***
    https://bugs.launchpad.net/bugs/265179

trampster wrote:
>
>Are you aware that the bug you made this a duplicate of is marked as
>invalid.


Yes. Whether or not that bug is invalid is irrelevant. That bug applies
to Mailman 2.1 and we have already said many times that this was a
design decision for Mailman 2.1, we recognize it was a bad decision,
it is finally fixed in Mailman 3 and will not be fixed in Mailman 2.1.

However, to be somewhat more consistent, I have marked #265179 as Won't
Fix for Mailman 2.1.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266821

Title:
  privacy hole in password reminder

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266821/+subscriptions

From 418457 at bugs.launchpad.net  Wed Oct  3 04:28:43 2012
From: 418457 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 03 Oct 2012 02:28:43 -0000
Subject: [Bug 418457] Re: buildout fails: can't install Jinja2
References: <20090825063846.10124.87944.malonedeb@gangotri.canonical.com>
Message-ID: <20121003022843.5242.89790.malone@wampee.canonical.com>

This is a test; please ignore.

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/418457

Title:
  buildout fails: can't install Jinja2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/418457/+subscriptions

From aurelien at bompard.org  Wed Oct  3 15:25:32 2012
From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=)
Date: Wed, 03 Oct 2012 13:25:32 -0000
Subject: [Bug 1060951] [NEW] Bug getting i18n'ed attachment filenames (RFC2231)
References: <20121003132533.14222.802.malonedeb@gac.canonical.com>
Message-ID: <20121003132533.14222.802.malonedeb@gac.canonical.com>

Public bug reported:

RFC 2231 allows filenames to have non-ascii characters. The
get_filename() method in Python's Message class handles this by calling
email.utils.collapse_rfc2231_value() at the end of get_filename. This
method returns the filename in Unicode.

This fails in Mailman because the mailman.email.message.Message class
has a wrapper around get() and __getitem__() to return unicode headers.
As a result, the collapse_rfc2231_value() tries to transforms into
unicode an already unicode string, and I get the following exception:

  File "/usr/lib/python2.7/email/utils.py", line 319, in collapse_rfc2231_value
    return unicode(rawval, charset, errors)
TypeError: decoding Unicode is not supported

A possible solution to this would be to make Mailman's Message
get_filename() method be more than just an exception-catching wrapper,
and re-implement the original get_filename() method, inserting a
conversion to str before calling collapse_rfc2231_value().

Does this make sense ? Any other idea for a possible solution ?

** Affects: mailman
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1060951

Title:
  Bug getting i18n'ed attachment filenames (RFC2231)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1060951/+subscriptions

From 1060951 at bugs.launchpad.net  Wed Oct  3 16:00:04 2012
From: 1060951 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 03 Oct 2012 14:00:04 -0000
Subject: [Bug 1060951] Re: Bug getting i18n'ed attachment filenames (RFC2231)
References: <20121003132533.14222.802.malonedeb@gac.canonical.com>
Message-ID: <20121003140005.15183.4254.launchpad@chaenomeles.canonical.com>

** Tags added: mailman3

** Also affects: mailman/2.1
   Importance: Undecided
       Status: New

** Also affects: mailman/3.0
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1060951

Title:
  Bug getting i18n'ed attachment filenames (RFC2231)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1060951/+subscriptions

From aurelien at bompard.org  Wed Oct  3 16:31:55 2012
From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=)
Date: Wed, 03 Oct 2012 14:31:55 -0000
Subject: [Bug 1060951] Re: Bug getting i18n'ed attachment filenames (RFC2231)
References: <20121003132533.14222.802.malonedeb@gac.canonical.com>
Message-ID: <20121003143155.17425.100.malone@soybean.canonical.com>

See the TestMessageSubclass testcase I've added to the attached testsuite for a way to reproduce it.
It's actually a little harder that I first thought, encoding the filename in the middle of the method is not enough.

** Attachment added: "extended testsuite"
   https://bugs.launchpad.net/mailman/+bug/1060951/+attachment/3368374/+files/test_message.py

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1060951

Title:
  Bug getting i18n'ed attachment filenames (RFC2231)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1060951/+subscriptions

From mark at msapiro.net  Wed Oct  3 17:56:06 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 03 Oct 2012 15:56:06 -0000
Subject: [Bug 1060951] Re: Bug getting i18n'ed attachment filenames (RFC2231)
References: <20121003132533.14222.802.malonedeb@gac.canonical.com>
Message-ID: <20121003155606.15264.47416.malone@chaenomeles.canonical.com>

This works for me with Mailman 2.1.15 and email 4.0.1. Does it fail for
you with Mailman 2.1.x? If so, what Mailman and email versions?


[msapiro at MSAPIRO ~]$ python
Python 2.6.5 (r265:79063, Jun 12 2010, 17:07:01)
[GCC 4.3.4 20090804 (release) 1] on cygwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import email
>>> email.__version__
'4.0.1'
>>> import sys
>>> sys.path.insert('/cygdrive/f/test-mailman/')
>>> from Mailman import Message
>>> msg = email.message_from_string("""Message-ID: <blah at example.com>
... Content-Type: multipart/mixed; boundary="------------050607040206050605060208"
...
... This is a multi-part message in MIME format.
... --------------050607040206050605060208
... Content-Type: text/plain; charset=UTF-8
... Content-Transfer-Encoding: quoted-printable
...
... Test message containing an attachment with an accented filename
...
... --------------050607040206050605060208
... Content-Type: text/plain; charset=UTF-8;
...     name="=?UTF-8?B?dG9kby1kw6lqZXVuZXIudHh0?="
... Content-Transfer-Encoding: base64
... Content-Disposition: attachment;
...     filename*=UTF-8''%74%6F%64%6F%2D%64%C3%A9%6A%65%75%6E%65%72%2E%74%78%74
...
... VmlhbmRlCk1lbnRoZQpQYWluClZpbgoKQ3Vpc2luZTogcHLDqXBhcmVyIGwnYXDDqXJvLCBj
... b3VwZXIgZXQgZmFpcmUgcmlzc29sZXIgbGVzIHBhdGF0ZXMsIGV0IGZhaXJlIGxlcyBjb29r
... aWVzCg==
... --------------050607040206050605060208--
... """, Message.Message)
>>> msg
>From nobody Wed Oct  3 08:43:13 2012
Message-ID: <blah at example.com>
Content-Type: multipart/mixed; boundary="------------050607040206050605060208"

This is a multi-part message in MIME format.
--------------050607040206050605060208
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Test message containing an attachment with an accented filename

--------------050607040206050605060208
Content-Type: text/plain; charset=UTF-8;
        name="=?UTF-8?B?dG9kby1kw6lqZXVuZXIudHh0?="
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
        filename*=UTF-8''%74%6F%64%6F%2D%64%C3%A9%6A%65%75%6E%65%72%2E%74%78%74

VmlhbmRlCk1lbnRoZQpQYWluClZpbgoKQ3Vpc2luZTogcHLDqXBhcmVyIGwnYXDDqXJvLCBj
b3VwZXIgZXQgZmFpcmUgcmlzc29sZXIgbGVzIHBhdGF0ZXMsIGV0IGZhaXJlIGxlcyBjb29r
aWVzCg==
--------------050607040206050605060208--

>>> att = msg.get_payload()[1]
>>> att
>From nobody Wed Oct  3 08:43:44 2012
Content-Type: text/plain; charset=UTF-8;
        name="=?UTF-8?B?dG9kby1kw6lqZXVuZXIudHh0?="
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
        filename*=UTF-8''%74%6F%64%6F%2D%64%C3%A9%6A%65%75%6E%65%72%2E%74%78%74

VmlhbmRlCk1lbnRoZQpQYWluClZpbgoKQ3Vpc2luZTogcHLDqXBhcmVyIGwnYXDDqXJvLCBj
b3VwZXIgZXQgZmFpcmUgcmlzc29sZXIgbGVzIHBhdGF0ZXMsIGV0IGZhaXJlIGxlcyBjb29r
aWVzCg==
>>> att.get_filename()
u'todo-d\xe9jeuner.txt'


** Changed in: mailman/2.1
   Importance: Undecided => Medium

** Changed in: mailman/2.1
       Status: New => Incomplete

** Changed in: mailman/2.1
     Assignee: (unassigned) => Mark Sapiro (msapiro)

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1060951

Title:
  Bug getting i18n'ed attachment filenames (RFC2231)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1060951/+subscriptions

From aurelien at bompard.org  Wed Oct  3 18:09:54 2012
From: aurelien at bompard.org (=?utf-8?q?Aur=C3=A9lien_Bompard?=)
Date: Wed, 03 Oct 2012 16:09:54 -0000
Subject: [Bug 1060951] Re: Bug getting i18n'ed attachment filenames (RFC2231)
References: <20121003132533.14222.802.malonedeb@gac.canonical.com>
Message-ID: <20121003160954.5621.65231.malone@wampee.canonical.com>

Sorry, I should have written it : it's with Mailman 3 HEAD.

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1060951

Title:
  Bug getting i18n'ed attachment filenames (RFC2231)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1060951/+subscriptions

From 1060951 at bugs.launchpad.net  Wed Oct  3 18:19:56 2012
From: 1060951 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 03 Oct 2012 16:19:56 -0000
Subject: [Bug 1060951] Re: Bug getting i18n'ed attachment filenames (RFC2231)
References: <20121003132533.14222.802.malonedeb@gac.canonical.com>
Message-ID: <20121003161956.14382.30099.launchpad@gac.canonical.com>

** No longer affects: mailman/2.1

** No longer affects: mailman/3.0

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1060951

Title:
  Bug getting i18n'ed attachment filenames (RFC2231)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1060951/+subscriptions

From 956384 at bugs.launchpad.net  Wed Oct 10 03:09:53 2012
From: 956384 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 10 Oct 2012 01:09:53 -0000
Subject: [Bug 956384] Re: Continuous integration and real-world testing 
References: <20120315200247.27927.89218.malonedeb@wampee.canonical.com>
Message-ID: <20121010010954.32380.4683.launchpad@soybean.canonical.com>

** Changed in: mailman
   Importance: High => Wishlist

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/956384

Title:
  Continuous integration and real-world testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/956384/+subscriptions

From dieter at handshake.de  Thu Oct 11 12:03:15 2012
From: dieter at handshake.de (Dieter Maurer)
Date: Thu, 11 Oct 2012 10:03:15 -0000
Subject: [Bug 1065447] [NEW] Feature request: REST api to verify password
References: <20121011100315.8642.7986.malonedeb@gac.canonical.com>
Message-ID: <20121011100315.8642.7986.malonedeb@gac.canonical.com>

Public bug reported:

"mailman" manages users with their individual passwords. It is supposed
to be controlled via a REST api which uses a global (user independent)
authentication. Obviously, an arbitrary user should not be allowed to
change preferences (and other settings) for a different user. This
implies that a REST client has to check user access rights and
(especially) verify the user's identity. The typical way for user
identity verification would be to check that the user knows the password
registered with this user in "mailman". However, the REST api lacks a
corresponding operation.

The REST api should probably be extended by a "verify_password" user
subresource. To avoid passwords being logged by typical webserver
logging, the password to be verified should probably be submitted via
"POST" (not transmitted as part of the "URL").

If the project does not want to go this route (password verification via
a REST operation), then it must document how a client can verify a given
cleartext password against the encrypted password information available
as user attribute.

** Affects: mailman
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1065447

Title:
  Feature request: REST api to verify password

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1065447/+subscriptions

From 1065447 at bugs.launchpad.net  Thu Oct 11 14:40:35 2012
From: 1065447 at bugs.launchpad.net (Barry Warsaw)
Date: Thu, 11 Oct 2012 12:40:35 -0000
Subject: [Bug 1065447] Re: Feature request: REST api to verify password
References: <20121011100315.8642.7986.malonedeb@gac.canonical.com>
Message-ID: <20121011124035.8203.82708.launchpad@gac.canonical.com>

** Tags added: mailman3 rest

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1065447

Title:
  Feature request: REST api to verify password

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1065447/+subscriptions

From 1006345 at bugs.launchpad.net  Fri Oct 12 22:14:19 2012
From: 1006345 at bugs.launchpad.net (Terri)
Date: Fri, 12 Oct 2012 20:14:19 -0000
Subject: [Bug 1006345] Re: No email confirmation when subscribing via the REST
	API
References: <20120530112146.17443.29580.malonedeb@chaenomeles.canonical.com>
Message-ID: <20121012201420.16277.25700.launchpad@wampee.canonical.com>

** Changed in: postorius
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1006345

Title:
  No email confirmation when subscribing via the REST API

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1006345/+subscriptions

From 1006356 at bugs.launchpad.net  Fri Oct 12 22:18:46 2012
From: 1006356 at bugs.launchpad.net (Terri)
Date: Fri, 12 Oct 2012 20:18:46 -0000
Subject: [Bug 1006356] Re: message acceptance settings for list ignored
References: <20120530115536.4422.77788.malonedeb@gac.canonical.com>
Message-ID: <20121012201846.15474.85884.malone@wampee.canonical.com>

I suspect this may be a Mailman3 bug, though, since the other settings
I've checked were being set correctly in REST.

Note to self: verify that these settings are actually being set
correctly via the rest API / check to see if the bug occurs in Mailman3

** Changed in: postorius
       Status: New => Triaged

** Also affects: mailman
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1006356

Title:
  message acceptance settings for list ignored

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1006356/+subscriptions

From 1006345 at bugs.launchpad.net  Fri Oct 12 22:40:23 2012
From: 1006345 at bugs.launchpad.net (Barry Warsaw)
Date: Fri, 12 Oct 2012 20:40:23 -0000
Subject: [Bug 1006345] Re: No email confirmation when subscribing via the REST
	API
References: <20120530112146.17443.29580.malonedeb@chaenomeles.canonical.com>
Message-ID: <20121012204023.18996.12069.launchpad@gac.canonical.com>

** Tags added: rest

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1006345

Title:
  No email confirmation when subscribing via the REST API

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1006345/+subscriptions

From 1006356 at bugs.launchpad.net  Fri Oct 12 22:47:45 2012
From: 1006356 at bugs.launchpad.net (Barry Warsaw)
Date: Fri, 12 Oct 2012 20:47:45 -0000
Subject: [Bug 1006356] Re: message acceptance settings for list ignored
References: <20120530115536.4422.77788.malonedeb@gac.canonical.com>
Message-ID: <20121012204745.19037.32520.launchpad@gac.canonical.com>

** Tags added: mailman3 rest

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1006356

Title:
  message acceptance settings for list ignored

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1006356/+subscriptions

From 1062963 at bugs.launchpad.net  Fri Oct 12 23:45:07 2012
From: 1062963 at bugs.launchpad.net (Terri)
Date: Fri, 12 Oct 2012 21:45:07 -0000
Subject: [Bug 1062963] Re: Admin notification not received
References: <20121006182248.14546.68625.malonedeb@gac.canonical.com>
Message-ID: <20121012214507.14823.71985.malone@soybean.canonical.com>

Need to confirm that the setting is being set correctly in REST, but
this may be a Mailman3 bug.

** Also affects: mailman
   Importance: Undecided
       Status: New

** Changed in: postorius
       Status: New => Triaged

** Changed in: postorius
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1062963

Title:
  Admin notification not received

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1062963/+subscriptions

From 1062957 at bugs.launchpad.net  Fri Oct 12 23:53:26 2012
From: 1062957 at bugs.launchpad.net (Terri)
Date: Fri, 12 Oct 2012 21:53:26 -0000
Subject: [Bug 1062957] Re: No welcome message
References: <20121006181017.17992.53015.malonedeb@soybean.canonical.com>
Message-ID: <20121012215326.15546.67759.malone@wampee.canonical.com>

Mostly a note to self: I need to check that this was not a function of
the test setup used on gimli.

** Also affects: mailman
   Importance: Undecided
       Status: New

** No longer affects: mailman

** Changed in: postorius
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1062957

Title:
  No welcome message

To manage notifications about this bug go to:
https://bugs.launchpad.net/postorius/+bug/1062957/+subscriptions

From sophron at latthi.com  Sat Oct 13 20:18:19 2012
From: sophron at latthi.com (George Chatzisofroniou)
Date: Sat, 13 Oct 2012 18:18:19 -0000
Subject: [Merge] lp:~sophron/postorius/create_users into lp:postorius
Message-ID: <20121013181819.5572.1064.launchpad@ackee.canonical.com>

George Chatzisofroniou has proposed merging lp:~sophron/postorius/create_users into lp:postorius.

Requested reviews:
  Florian Fuchs (flo-fuchs)

For more details, see:
https://code.launchpad.net/~sophron/postorius/create_users/+merge/129567

I worked on this bug: https://bugs.launchpad.net/postorius/+bug/1058445

I added the feature to create a mailman user account, but in order to edit the basic user data via the web interface, some additions to mailman client are required. See, https://bugs.launchpad.net/mailman.client/+bug/1066352 and https://bugs.launchpad.net/mailman.client/+bug/1066343.

We also need an icon for the new entry on the menu: https://bugs.launchpad.net/postorius/+bug/1066340

I think it's better to divide the whole 'edit user' feature into smaller ones (delete user, register addresses to a user, basic data edit, etc).
-- 
https://code.launchpad.net/~sophron/postorius/create_users/+merge/129567
Your team Mailman Coders is subscribed to branch lp:postorius.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: review-diff.txt
Type: text/x-diff
Size: 6969 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-coders/attachments/20121013/7630ceb1/attachment.diff>

From 1062963 at bugs.launchpad.net  Sat Oct 13 20:43:45 2012
From: 1062963 at bugs.launchpad.net (Barry Warsaw)
Date: Sat, 13 Oct 2012 18:43:45 -0000
Subject: [Bug 1062963] Re: Admin notification not received
References: <20121006182248.14546.68625.malonedeb@gac.canonical.com>
Message-ID: <20121013184346.16454.80046.launchpad@wampee.canonical.com>

** Tags added: mailman3

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1062963

Title:
  Admin notification not received

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1062963/+subscriptions

From 1066465 at bugs.launchpad.net  Sun Oct 14 11:35:12 2012
From: 1066465 at bugs.launchpad.net (rm87)
Date: Sun, 14 Oct 2012 09:35:12 -0000
Subject: [Bug 1066465] [NEW] Remove e-mail adresses from html attachments
References: <20121014093513.18788.16882.malonedeb@gac.canonical.com>
Message-ID: <20121014093513.18788.16882.malonedeb@gac.canonical.com>

Public bug reported:

As some mail clients add previous messages to email as html attachments,
an option to remove (or scramble) e-mail adresses from these would be
nice.

** Affects: mailman
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1066465

Title:
  Remove e-mail adresses from html attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1066465/+subscriptions

From mark at msapiro.net  Wed Oct 17 04:09:59 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 17 Oct 2012 02:09:59 -0000
Subject: [Bug 1066465] Re: Remove e-mail adresses from html attachments
References: <20121014093513.18788.16882.malonedeb@gac.canonical.com>
Message-ID: <20121017020959.14545.31921.malone@gac.canonical.com>

I don't understand this request. It appears to be a request to remove or
obscure email addresses from quotes of prior posts in replies to the
list, but if this is the case, wouldn't the quoted information also
appear in plain text parts, so why reference only HTML.

Also, in most if not all cases, wouldn't the information have already
appeared in a prior post to the list, so what purpose is served by
obfuscating it only when the prior post is quoted in a subsequent reply.

Another possible approach is to use Mailman's content filtering to
remove HTML parts entirely.

** Changed in: mailman
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1066465

Title:
  Remove e-mail adresses from html attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1066465/+subscriptions

From cgtyoder at alum.mit.edu  Thu Oct 18 03:47:54 2012
From: cgtyoder at alum.mit.edu (Conrad Yoder)
Date: Thu, 18 Oct 2012 01:47:54 -0000
Subject: [Bug 1067953] [NEW] Request: Add HTML support for message excerpt
	preview
References: <20121018014754.5133.68860.malonedeb@chaenomeles.canonical.com>
Message-ID: <20121018014754.5133.68860.malonedeb@chaenomeles.canonical.com>

Public bug reported:

Many if not most people currently use HTML-formatted email. When list
moderators have to approve email postings on the Administrative Requests
page, only a plaintext Message Excerpt is displayed, making informed
viewing of a list member's message sometimes next to impossible.

Looking through the mailman discussion list archives, I see that this
feature was asked for as far back as 2005 - 7 years ago, so this is not
a "new" suggestion. This would be an extremely helpful feature to add.
If there are security concerns, a toggle or config option could easily
be added so HTML viewing is not the default, and/or java/javascript
could be disabled in the preview window. Thank you for your
consideration here.

** Affects: mailman
     Importance: Undecided
         Status: New


** Tags: excerpt html preview request

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1067953

Title:
  Request: Add HTML support for message excerpt preview

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1067953/+subscriptions

From 1066465 at bugs.launchpad.net  Thu Oct 18 18:20:48 2012
From: 1066465 at bugs.launchpad.net (rm87)
Date: Thu, 18 Oct 2012 16:20:48 -0000
Subject: [Bug 1066465] Re: Remove e-mail adresses from html attachments
References: <20121014093513.18788.16882.malonedeb@gac.canonical.com>
Message-ID: <20121018162048.21181.84554.malone@gac.canonical.com>

Sorry for posting a bit confusing bug report. 
An example message: http://lists.openstreetmap.org/pipermail/talk-ee/2010-June/000514.html 
and it's attachment: http://lists.openstreetmap.org/pipermail/talk-ee/attachments/20100630/325ec248/attachment.html .
As you can see e-mail adresses are obscured in message but not in attachment.

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1066465

Title:
  Remove e-mail adresses from html attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1066465/+subscriptions

From mark at msapiro.net  Fri Oct 19 02:55:41 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 19 Oct 2012 00:55:41 -0000
Subject: [Bug 1066465] Re: ARCHIVER_OBSCURES_EMAILADDRS = Yes fails to obscure
	addresses in scrubbed parts (HTML and attachments)
References: <20121014093513.18788.16882.malonedeb@gac.canonical.com>
Message-ID: <20121019005542.16699.69743.malone@wampee.canonical.com>

I have changed the title of this bug to more directly reflect the
problem.

** Summary changed:

- Remove e-mail adresses from html attachments
+ ARCHIVER_OBSCURES_EMAILADDRS = Yes fails to obscure addresses in scrubbed parts (HTML and attachments)

** Changed in: mailman
   Importance: Undecided => Low

** Changed in: mailman
       Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1066465

Title:
  ARCHIVER_OBSCURES_EMAILADDRS = Yes fails to obscure addresses in
  scrubbed parts (HTML and attachments)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1066465/+subscriptions

From mark at msapiro.net  Fri Oct 19 20:37:23 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 19 Oct 2012 18:37:23 -0000
Subject: [Bug 266678] Re: Add X-Listmember header
References: <20080905194216.1806.32087.launchpad@forster.canonical.com>
Message-ID: <20121019183723.6275.42701.malone@gac.canonical.com>

Adding such a header requires that a separate message be sent to each
user. This is no different from enabling personalization for the list
and adding the list member's address in msg_header or msg_footer. If the
adding of X-Listmember: were an option, this is essentially no different
from the personalize = Yes/No option, and if it were not optional, it
would force sending of individual messages on those installations/lists
that don't want to.

** Changed in: mailman
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266678

Title:
  Add X-Listmember header

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266678/+subscriptions

From mark at msapiro.net  Fri Oct 19 20:50:23 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 19 Oct 2012 18:50:23 -0000
Subject: [Bug 558204] Re: allow specifying another list in
	accept_these_nonmembers
References: <20100408090748.1687.80336.launchpad@loganberry.canonical.com>
Message-ID: <20121019185024.7782.69090.launchpad@gac.canonical.com>

** Changed in: mailman
       Status: New => Fix Released

** Changed in: mailman
    Milestone: None => 2.1-stable

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/558204

Title:
  allow specifying another list in accept_these_nonmembers

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/558204/+subscriptions

From mark at msapiro.net  Fri Oct 19 20:47:06 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 19 Oct 2012 18:47:06 -0000
Subject: [Bug 266756] Re: add_members command
References: <20080905194238.1806.59536.launchpad@forster.canonical.com>
Message-ID: <20121019184708.11111.3481.malone@soybean.canonical.com>

You could make bin/my_add_members containing

#!/bin/sh
cd /path/to/mailman/bin
echo $2 | add_members -r - $1

and then do

my_add_members mylist customer at address.tld


** Changed in: mailman
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266756

Title:
  add_members command

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266756/+subscriptions

From mark at msapiro.net  Fri Oct 19 22:23:48 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 19 Oct 2012 20:23:48 -0000
Subject: [Bug 1068837] [NEW] Automatic rejects of incoming posts are not
	logged.
References: <20121019202348.6449.11563.malonedeb@gac.canonical.com>
Message-ID: <20121019202348.6449.11563.malonedeb@gac.canonical.com>

Public bug reported:

When a message is rejected by a pipeline handler raising
Errors.RejectMessage, the message is bounced to the sender with an
appropriate message, but nothing is logged. This should be logged in the
vette log.

** Affects: mailman
     Importance: Medium
     Assignee: Mark Sapiro (msapiro)
         Status: In Progress

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1068837

Title:
  Automatic rejects of incoming posts are not logged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1068837/+subscriptions

From stephen at xemacs.org  Sat Oct 20 05:58:28 2012
From: stephen at xemacs.org (Stephen Turnbull)
Date: Sat, 20 Oct 2012 03:58:28 -0000
Subject: [Bug 1068944] [NEW] *Everything* in the moderation interface needs to
	be batchable
References: <20121020035828.6106.31011.malonedeb@gac.canonical.com>
Message-ID: <20121020035828.6106.31011.malonedeb@gac.canonical.com>

Public bug reported:

A user of 2.1.9 reports on Mailman-Users that his server is being
hammered by automated subscription requests (including handling the
confirmation process).

He generously says it's not a big deal except that his list-owners get
inundated with subscription requests.  The issue is that such requests

** Affects: mailman
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1068944

Title:
  *Everything* in the moderation interface needs to be batchable

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1068944/+subscriptions

From stephen at xemacs.org  Sat Oct 20 06:05:38 2012
From: stephen at xemacs.org (Stephen Turnbull)
Date: Sat, 20 Oct 2012 04:05:38 -0000
Subject: [Bug 1068944] Re: *Everything* in the moderation interface needs to
	be batchable
References: <20121020035828.6106.31011.malonedeb@gac.canonical.com>
Message-ID: <20121020040538.6313.31538.malone@gac.canonical.com>

Oops, I should have checked more carefully ... it looks like this is
already batchable in mailman 2.1.15.  Closing....

** Changed in: mailman
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1068944

Title:
  *Everything* in the moderation interface needs to be batchable

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1068944/+subscriptions

From noreply at launchpad.net  Sat Oct 20 08:48:20 2012
From: noreply at launchpad.net (noreply at launchpad.net)
Date: Sat, 20 Oct 2012 06:48:20 -0000
Subject: [Merge] lp:~wacky/postorius/django_1_5 into lp:postorius
In-Reply-To: <20120928203419.19095.49857.launchpad@ackee.canonical.com>
Message-ID: <20121020064820.1950.93828.launchpad@ackee.canonical.com>

The proposal to merge lp:~wacky/postorius/django_1_5 into lp:postorius has been updated.

    Status: Needs review => Merged

For more details, see:
https://code.launchpad.net/~wacky/postorius/django_1_5/+merge/127060
-- 
https://code.launchpad.net/~wacky/postorius/django_1_5/+merge/127060
Your team Mailman Coders is subscribed to branch lp:postorius.

From flo.fuchs at gmail.com  Sat Oct 20 08:47:18 2012
From: flo.fuchs at gmail.com (Florian Fuchs)
Date: Sat, 20 Oct 2012 06:47:18 -0000
Subject: [Merge] lp:~wacky/postorius/django_1_5 into lp:postorius
In-Reply-To: <20120928203419.19095.49857.launchpad@ackee.canonical.com>
Message-ID: <20121020064624.11199.8086.codereview@soybean.canonical.com>

Review: Approve

Hi Richard,

thank you very much for taking the time and changing all those url names in the templates! This makes great sense!

I'm merging your branch into the trunk now.

Florian

-- 
https://code.launchpad.net/~wacky/postorius/django_1_5/+merge/127060
Your team Mailman Coders is subscribed to branch lp:postorius.

From 1068837 at bugs.launchpad.net  Sun Oct 21 22:35:59 2012
From: 1068837 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 21 Oct 2012 20:35:59 -0000
Subject: [Bug 1068837] Re: Automatic rejects of incoming posts are not logged.
References: <20121019202348.6449.11563.malonedeb@gac.canonical.com>
Message-ID: <20121021203602.21557.86159.launchpad@ackee.canonical.com>

** Branch linked: lp:mailman/2.2

** Branch linked: lp:mailman/2.1

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1068837

Title:
  Automatic rejects of incoming posts are not logged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1068837/+subscriptions

From mark at msapiro.net  Sun Oct 21 22:37:55 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 21 Oct 2012 20:37:55 -0000
Subject: [Bug 1068837] Re: Automatic rejects of incoming posts are not logged.
References: <20121019202348.6449.11563.malonedeb@gac.canonical.com>
Message-ID: <20121021203756.16699.34663.launchpad@wampee.canonical.com>

** Changed in: mailman
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1068837

Title:
  Automatic rejects of incoming posts are not logged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1068837/+subscriptions

From 1070064 at bugs.launchpad.net  Tue Oct 23 01:01:44 2012
From: 1070064 at bugs.launchpad.net (Barry Warsaw)
Date: Mon, 22 Oct 2012 23:01:44 -0000
Subject: [Bug 1070064] [NEW] Add a 'policy' command
References: <20121022230145.16655.54092.malonedeb@wampee.canonical.com>
Message-ID: <20121022230145.16655.54092.malonedeb@wampee.canonical.com>

Public bug reported:

It would be kind of nice for MM3 to implement a 'policy' command.  If
you issue this email command, you would receive a response containing an
admin supplied policy text.  This response should adhere to the general
grace period timeouts, and the text should be retrieved via the
generalized url retrieval and caching machinery.  This way, the same
policy text could be retrievable via email command or web ui.

There should be a way to request policy documents in multiple languages.

** Affects: mailman
     Importance: Wishlist
         Status: New


** Tags: mailman3

** Changed in: mailman
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1070064

Title:
  Add a 'policy' command

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1070064/+subscriptions

From mark at msapiro.net  Wed Oct 24 00:01:44 2012
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 23 Oct 2012 22:01:44 -0000
Subject: [Bug 1070574] [NEW] add_members needs a 'nomail' option
References: <20121023220144.10481.17824.malonedeb@gac.canonical.com>
Message-ID: <20121023220144.10481.17824.malonedeb@gac.canonical.com>

Public bug reported:

Some situations make it desirable to add a member to a list with mail
delivery disabled. It would be convenient if add_members had an option
to do this.

** Affects: mailman
     Importance: Low
     Assignee: Mark Sapiro (msapiro)
         Status: In Progress

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1070574

Title:
  add_members needs a 'nomail' option

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1070574/+subscriptions

From 982551 at bugs.launchpad.net  Thu Oct 25 00:49:21 2012
From: 982551 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 24 Oct 2012 22:49:21 -0000
Subject: [Bug 982551] Re: Relative paths in 'mailman start -C' are broken
References: <20120415194535.4165.41414.malonedeb@gac.canonical.com>
Message-ID: <20121024224921.12969.44784.malone@wampee.canonical.com>

Oops, cli_control does a chdir to the $VAR_DIR which is probably how
it's really broken.  So the rel->abs pathing must happen before the
chdir().  It still better to pass the absolute path down to the runners.

** Changed in: mailman
       Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/982551

Title:
  Relative paths in 'mailman start -C' are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/982551/+subscriptions

From 982551 at bugs.launchpad.net  Thu Oct 25 00:46:52 2012
From: 982551 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 24 Oct 2012 22:46:52 -0000
Subject: [Bug 982551] Re: ./mailman.cfg only used partially
References: <20120415194535.4165.41414.malonedeb@gac.canonical.com>
Message-ID: <20121024224652.9377.84421.malone@soybean.canonical.com>

The problem is that if you do 'bin/mailman -C some/relative/path' these
paths will not get passed to the runner subprocesses correctly.  I think
the fix is to make them absolute paths in cli_control.py and pass only
absolute paths to the runners command lines.

** Changed in: mailman
       Status: Triaged => Confirmed

** Changed in: mailman
   Importance: Undecided => High

** Changed in: mailman
     Assignee: (unassigned) => Barry Warsaw (barry)

** Changed in: mailman
    Milestone: None => 3.0.0b3

** Summary changed:

- ./mailman.cfg only used partially
+ Relative paths in 'mailman start -C' are broken

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/982551

Title:
  Relative paths in 'mailman start -C' are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/982551/+subscriptions

From 982551 at bugs.launchpad.net  Thu Oct 25 01:24:49 2012
From: 982551 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 24 Oct 2012 23:24:49 -0000
Subject: [Bug 982551] Re: Relative paths in 'mailman start -C' are broken
References: <20120415194535.4165.41414.malonedeb@gac.canonical.com>
Message-ID: <20121024232451.9459.74066.launchpad@soybean.canonical.com>

** Changed in: mailman
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/982551

Title:
  Relative paths in 'mailman start -C' are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/982551/+subscriptions

From noreply at launchpad.net  Thu Oct 25 10:24:21 2012
From: noreply at launchpad.net (noreply at launchpad.net)
Date: Thu, 25 Oct 2012 08:24:21 -0000
Subject: [Merge] lp:~sophron/postorius/create_users into lp:postorius
In-Reply-To: <20121013181819.5572.1064.launchpad@ackee.canonical.com>
Message-ID: <20121025082420.11586.22147.launchpad@ackee.canonical.com>

The proposal to merge lp:~sophron/postorius/create_users into lp:postorius has been updated.

    Status: Needs review => Merged

For more details, see:
https://code.launchpad.net/~sophron/postorius/create_users/+merge/129567
-- 
https://code.launchpad.net/~sophron/postorius/create_users/+merge/129567
Your team Mailman Coders is subscribed to branch lp:postorius.

From flo.fuchs at gmail.com  Thu Oct 25 10:19:21 2012
From: flo.fuchs at gmail.com (Florian Fuchs)
Date: Thu, 25 Oct 2012 08:19:21 -0000
Subject: [Merge] lp:~sophron/postorius/create_users into lp:postorius
In-Reply-To: <20121013181819.5572.1064.launchpad@ackee.canonical.com>
Message-ID: <20121025081846.13344.91473.codereview@wampee.canonical.com>

Review: Approve

Hi George, 

thank you for your changes (and the bug reports)! I have just merged them to the trunk. I only made some very small changes and additions (adjusted the docstring in MailmanUserView, added the user icon, some PEP8 fixes...). I also made the user list and details only available to superusers (I don't think every user should be able to see who else is there...).

So now that we have a method to add new users to the core, we need a way to connect them to the users in the postorius database (the ones added through django.contrib.auth). I added some comment about that in the bug description:

https://bugs.launchpad.net/postorius/+bug/1058445

Cheers and thanks again
Florian


-- 
https://code.launchpad.net/~sophron/postorius/create_users/+merge/129567
Your team Mailman Coders is subscribed to branch lp:postorius.

From richard at nfsnet.org  Thu Oct 25 16:40:26 2012
From: richard at nfsnet.org (Richard Wackerbarth)
Date: Thu, 25 Oct 2012 14:40:26 -0000
Subject: [Merge] lp:~sophron/postorius/create_users into lp:postorius
In-Reply-To: <20121025081846.13344.91473.codereview@wampee.canonical.com>
Message-ID: <85728E0B-B4A1-4946-9D2D-E271E9B7CB12@NFSNet.org>

Isn't the visibility of the list members a per_list policy setting?

In any case, we will need to have list administrators (who are not the superuser) be able to see the membership on their list.

I think that Postorius will require a better model for roles.


Richard

On Oct 25, 2012, at 3:19 AM, Florian Fuchs <flo.fuchs at gmail.com> wrote:

> Review: Approve
> 
> Hi George, 
> 
> thank you for your changes (and the bug reports)! I have just merged them to the trunk. I only made some very small changes and additions (adjusted the docstring in MailmanUserView, added the user icon, some PEP8 fixes...). I also made the user list and details only available to superusers (I don't think every user should be able to see who else is there...).


-- 
https://code.launchpad.net/~sophron/postorius/create_users/+merge/129567
Your team Mailman Coders is subscribed to branch lp:postorius.

From flo.fuchs at gmail.com  Thu Oct 25 20:58:23 2012
From: flo.fuchs at gmail.com (Florian Fuchs)
Date: Thu, 25 Oct 2012 18:58:23 -0000
Subject: [Merge] lp:~sophron/postorius/create_users into lp:postorius
In-Reply-To: <85728E0B-B4A1-4946-9D2D-E271E9B7CB12@NFSNet.org>
Message-ID: <CAABJATuxkRv3K_6pf49oB3DTy7xAK1Sg1zgxhoRTmpcfY89LgA@mail.gmail.com>

Hi Richard,

2012/10/25 Richard Wackerbarth <richard at nfsnet.org>:
> Isn't the visibility of the list members a per_list policy setting?

Please not that users/index is not a list of members, but a list of
the users stored in Mailman's core database. The members of a list are
displayed for each list separately and can be accessed only by
superusers and list owners.

> In any case, we will need to have list administrators (who are not the superuser) be able to see the membership on their list.
>
> I think that Postorius will require a better model for roles.

Yes, this is already possible. There are two custom permission
decorators for view functions (list_owner_required and
list_moderator_required) that check if the currently logged-in user is
either the owner or the moderator of a list. Currently those
restrictions are in user on the list members page, the moderation
page, the list settings etc.

Next step is providing forms to make existing users owners and/or moderators.

Cheers
Florian

-- 
https://code.launchpad.net/~sophron/postorius/create_users/+merge/129567
Your team Mailman Coders is subscribed to branch lp:postorius.

From sunu0000 at gmail.com  Wed Oct 31 10:07:21 2012
From: sunu0000 at gmail.com (Tarashish Mishra)
Date: Wed, 31 Oct 2012 09:07:21 -0000
Subject: [Merge] lp:~sunu0000/postorius/newuser_hint into lp:postorius
Message-ID: <20121031090721.10097.6460.launchpad@ackee.canonical.com>

Tarashish Mishra has proposed merging lp:~sunu0000/postorius/newuser_hint into lp:postorius.

Requested reviews:
  Terri (terriko)
Related bugs:
  Bug #1062856 in Postorius: "It is not clear how to log in if you do not already have an account."
  https://bugs.launchpad.net/postorius/+bug/1062856

For more details, see:
https://code.launchpad.net/~sunu0000/postorius/newuser_hint/+merge/132263

Added hint for new users to sign in.
-- 
https://code.launchpad.net/~sunu0000/postorius/newuser_hint/+merge/132263
Your team Mailman Coders is subscribed to branch lp:postorius.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: review-diff.txt
Type: text/x-diff
Size: 564 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-coders/attachments/20121031/bdf50c21/attachment.diff>

From sunu0000 at gmail.com  Wed Oct 31 11:24:24 2012
From: sunu0000 at gmail.com (Tarashish Mishra)
Date: Wed, 31 Oct 2012 10:24:24 -0000
Subject: [Merge] lp:~sunu0000/postorius/general_settings into lp:postorius
Message-ID: <20121031102424.1704.32789.launchpad@ackee.canonical.com>

Tarashish Mishra has proposed merging lp:~sunu0000/postorius/general_settings into lp:postorius.

Requested reviews:
  Mailman Coders (mailman-coders)
Related bugs:
  Bug #1062877 in Postorius: "General Settings"
  https://bugs.launchpad.net/postorius/+bug/1062877

For more details, see:
https://code.launchpad.net/~sunu0000/postorius/general_settings/+merge/132284

Added placeholder text for General Settings
-- 
https://code.launchpad.net/~sunu0000/postorius/general_settings/+merge/132284
Your team Mailman Coders is requested to review the proposed merge of lp:~sunu0000/postorius/general_settings into lp:postorius.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: review-diff.txt
Type: text/x-diff
Size: 445 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-coders/attachments/20121031/dc628da8/attachment.diff>

From 1073506 at bugs.launchpad.net  Wed Oct 31 11:19:23 2012
From: 1073506 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 31 Oct 2012 10:19:23 -0000
Subject: [Bug 1073506] [NEW] Drop support for Python 2.6
References: <20121031101923.19289.16392.malonedeb@soybean.canonical.com>
Message-ID: <20121031101923.19289.16392.malonedeb@soybean.canonical.com>

Public bug reported:

Whenever the dependency stack is ported to Python 3, Mailman 3 will be
ported to Python 3.  In the meantime, making the code Python 2.7 -3
clean is an intermediate step toward Python 3 support.  In order to do
this, we really need to drop Python 2.6 support and this will also allow
us to improve the test suite, as well as other code improvements.
Besides, Python 2.6 is 4 years old and in security-only maintenance
mode, while Python 2.7 is stable and still supported for bug fixes.

** Affects: mailman
     Importance: High
     Assignee: Barry Warsaw (barry)
         Status: In Progress


** Tags: mailman3

** Changed in: mailman
       Status: New => Triaged

** Changed in: mailman
   Importance: Undecided => High

** Changed in: mailman
     Assignee: (unassigned) => Barry Warsaw (barry)

** Changed in: mailman
    Milestone: None => 3.0.0b3

** Tags added: mailman3

** Changed in: mailman
       Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1073506

Title:
  Drop support for Python 2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1073506/+subscriptions

From 1073506 at bugs.launchpad.net  Wed Oct 31 11:21:07 2012
From: 1073506 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 31 Oct 2012 10:21:07 -0000
Subject: [Bug 1073506] Re: Drop support for Python 2.6
References: <20121031101923.19289.16392.malonedeb@soybean.canonical.com>
Message-ID: <20121031102107.9729.35396.malone@wampee.canonical.com>

This task will also include work to make MM3 Python 2.7 -3 clean.

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1073506

Title:
  Drop support for Python 2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1073506/+subscriptions

From 1073506 at bugs.launchpad.net  Wed Oct 31 17:37:44 2012
From: 1073506 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 31 Oct 2012 16:37:44 -0000
Subject: [Bug 1073506] Re: Drop support for Python 2.6
References: <20121031101923.19289.16392.malonedeb@soybean.canonical.com>
Message-ID: <20121031163745.5533.6168.launchpad@gac.canonical.com>

** Changed in: mailman
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1073506

Title:
  Drop support for Python 2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1073506/+subscriptions