From mark at msapiro.net  Fri Apr  1 12:13:53 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 01 Apr 2016 16:13:53 -0000
Subject: [Bug 1104498] Re: Member contact requests
References: <20130124220904.6802.86776.malonedeb@soybean.canonical.com>
Message-ID: <20160401161353.13892.80349.malone@gac.canonical.com>

This doesn't apply to Mailman 2.1

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

** Changed in: mailman
     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/1104498

Title:
  Member contact requests

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

From mark at msapiro.net  Fri Apr  1 12:47:06 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 01 Apr 2016 16:47:06 -0000
Subject: [Bug 1565002] [NEW] RFC 2047 encoded display name in From: header not
 decoded in digests.
Message-ID: <20160401164707.32512.38001.malonedeb@wampee.canonical.com>

Public bug reported:

When a message contains a From: header like

From: =?utf-8?b?Sm9obiBEb2U=?= <jdoe at example.com>

the display name is shown as  '=?utf-8?b?Sm9obiBEb2U=?=' in the digest
TOC and in the pseudo From: header in the plain text digest instead of
being decoded as "John Doe".

** 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/1565002

Title:
  RFC 2047 encoded display name in From: header not decoded in digests.

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

From mark at msapiro.net  Fri Apr  1 12:53:20 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 01 Apr 2016 16:53:20 -0000
Subject: [Bug 557955] Re: usenet threading improvements
References: <20100408090318.1687.99577.launchpad@loganberry.canonical.com>
Message-ID: <20160401165320.17751.33701.malone@chaenomeles.canonical.com>

I don't intend to replace the Message-ID: in CookHeaders.py as suggested
in this patch, but I will put the original Message-ID in References: and
perhaps make other modifications in NewsRunner.py for the posts actually
gated to Usenet.

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

** Changed in: mailman
    Milestone: None => 2.1.22

** Changed in: mailman
     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/557955

Title:
  usenet threading improvements

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

From 557955 at bugs.launchpad.net  Sun Apr  3 02:20:41 2016
From: 557955 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 03 Apr 2016 06:20:41 -0000
Subject: [Bug 557955] Re: usenet threading improvements
References: <20100408090318.1687.99577.launchpad@loganberry.canonical.com>
Message-ID: <20160403062045.27964.81862.launchpad@ackee.canonical.com>

** 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/557955

Title:
  usenet threading improvements

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

From mark at msapiro.net  Sun Apr  3 02:28:03 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 03 Apr 2016 06:28:03 -0000
Subject: [Bug 557955] Re: usenet threading improvements
References: <20100408090318.1687.99577.launchpad@loganberry.canonical.com>
Message-ID: <20160403062804.19389.14357.malone@soybean.canonical.com>

The fix adds the original Message-ID: to References: and also adds X
-Mailman-Original-Message-ID: and X-Mailman-Original-References: headers
for 'forensics'. Hopefully this will help at least partially mitigate
threading issues that result from Message-ID: munging.

Also note that Munging the Message-ID in CookHeaders.py as suggested
here is not a full solution as there still may be direct To: or Cc:
recipients from 'reply all' and these are people likely to generate
additional replies so the issue of multiple Message-ID:s is not solved
by that approach.

** 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/557955

Title:
  usenet threading improvements

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

From mark at msapiro.net  Mon Apr  4 00:44:45 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 04 Apr 2016 04:44:45 -0000
Subject: [Bug 1565002] Re: RFC 2047 encoded display name in From: header not
 decoded in digests.
References: <20160401164707.32512.38001.malonedeb@wampee.canonical.com>
Message-ID: <20160404044445.17969.13601.malone@chaenomeles.canonical.com>

It turns out this issue is a broken MUA composing the message. The
encoded word in the header was quoted. The actual From: was like

From: "=?utf-8?b?Sm9obiBEb2U=?=" <jdoe at example.com>

The quotes caused the encoded word to be taken literally which is the
proper behavior. This could be defended against by checking if the name
looks like an RFC 2047 encoded word and trying to decode it, but I don't
think it's worth it so I'm marking this invalid.

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

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

** Changed in: mailman
    Milestone: 2.1.22 => None

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

Title:
  RFC 2047 encoded display name in From: header not decoded in digests.

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

From mark at msapiro.net  Sat Apr  9 17:45:44 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 09 Apr 2016 21:45:44 -0000
Subject: [Bug 1568398] [NEW] DMARC mitigation can be incorrectly (not) applied
 for a sub-domain.
Message-ID: <20160409214544.1804.18493.malonedeb@wampee.canonical.com>

Public bug reported:

In determining if dmarc_moderation_action should be applied, if a sub-
domain of an 'organizational domain' has no _dmarc policy record and the
organizational domain does have a _dmarc record, the policy that should
apply to the sub-domain is the organizational domain's sp= policy if any
and the p= policy if not.

Through Mailman 2.1.21, only the organizational domain's p= policy is
applied even if there is an sp= policy.

** 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/1568398

Title:
  DMARC mitigation can be incorrectly (not) applied for a sub-domain.

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

From 1568398 at bugs.launchpad.net  Sat Apr  9 18:45:47 2016
From: 1568398 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 09 Apr 2016 22:45:47 -0000
Subject: [Bug 1568398] Re: DMARC mitigation can be incorrectly (not) applied
 for a sub-domain.
References: <20160409214544.1804.18493.malonedeb@wampee.canonical.com>
Message-ID: <20160409224550.12942.19469.launchpad@ackee.canonical.com>

** 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/1568398

Title:
  DMARC mitigation can be incorrectly (not) applied for a sub-domain.

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

From mark at msapiro.net  Sat Apr  9 18:53:42 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 09 Apr 2016 22:53:42 -0000
Subject: [Bug 1568398] Re: DMARC mitigation can be incorrectly (not) applied
 for a sub-domain.
References: <20160409214544.1804.18493.malonedeb@wampee.canonical.com>
Message-ID: <20160409225342.3718.68810.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/1568398

Title:
  DMARC mitigation can be incorrectly (not) applied for a sub-domain.

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

From mark at msapiro.net  Sun Apr 10 00:34:51 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 10 Apr 2016 04:34:51 -0000
Subject: [Bug 1568445] [NEW] DMARC mitigation can check an invalid domain if
 the From: local part contains a quoted '@'.
Message-ID: <20160410043451.31921.66839.malonedeb@chaenomeles.canonical.com>

Public bug reported:

A message with a From: address with an '@' in a quoted local part has
been observed. While this is probably bogus, it confuses the DMARC
mitigation code that splits off the domain at the first '@'. The code
should probably split at the first '@' from the right.

** 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/1568445

Title:
  DMARC mitigation can check an invalid domain if the From: local part
  contains a quoted '@'.

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

From 1568445 at bugs.launchpad.net  Sun Apr 10 00:54:56 2016
From: 1568445 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 10 Apr 2016 04:54:56 -0000
Subject: [Bug 1568445] Re: DMARC mitigation can check an invalid domain if the
 From: local part contains a quoted '@'.
References: <20160410043451.31921.66839.malonedeb@chaenomeles.canonical.com>
Message-ID: <20160410045456.4768.59216.launchpad@ackee.canonical.com>

** 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/1568445

Title:
  DMARC mitigation can check an invalid domain if the From: local part
  contains a quoted '@'.

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

From mark at msapiro.net  Sun Apr 10 00:55:02 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 10 Apr 2016 04:55:02 -0000
Subject: [Bug 1568445] Re: DMARC mitigation can check an invalid domain if the
 From: local part contains a quoted '@'.
References: <20160410043451.31921.66839.malonedeb@chaenomeles.canonical.com>
Message-ID: <20160410045502.32096.24976.launchpad@chaenomeles.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/1568445

Title:
  DMARC mitigation can check an invalid domain if the From: local part
  contains a quoted '@'.

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

From rob at ubutton.com  Sun Apr 10 11:54:46 2016
From: rob at ubutton.com (Rob Button)
Date: Sun, 10 Apr 2016 15:54:46 -0000
Subject: [Bug 1568547] [NEW] admindb POST fails due to absolute addressing
Message-ID: <20160410155446.1187.22027.malonedeb@wampee.canonical.com>

Public bug reported:

The shared server I use employs re-directs from my domain name to their
local server domain name. This is causing form submission POSTs to fail
in the ADMINDB pages used to moderate user posts, but not in the ADMIN
pages used to manage the Mailman list. A review of the server code
reveals why -

The ADMIN pages use relative addressing in the form POST, so redirects are not an issue. 
Whereas the ADMINDB pages use absolute addressing in the form POST. See examples below from my website - 

THIS WORKS - From http://just63.justhost.com/mailman/admin/humor_noonway.com
<FORM action="../admin/humor_noonway.com/general" method="POST" >


THIS DOESN'T WORK - From http://just63.justhost.com/mailman/admindb/humor_noonway.com
<FORM action="http://noonway.com/mailman/admindb/humor_noonway.com" method="POST" >

This hasn't been an issue for the 12 years I've used Mailman to manage
user posts, but all of a sudden user post management is non-functional.
I can't tell if this is a change in my shared server setup, or an update
to Mailman 2.1.20 causing this.

There are probably Apache server settings I could change to solve this,
but I can't access the folders needed to do so on a shared server. Is
there a reason why the ADMINDB code couldn't be changed to use relative
addressing like the code in ADMIN?

** 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/1568547

Title:
  admindb POST fails due to absolute addressing

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

From mark at msapiro.net  Sun Apr 10 13:40:11 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 10 Apr 2016 17:40:11 -0000
Subject: [Bug 1568547] Re: admindb POST fails due to absolute addressing
References: <20160410155446.1187.22027.malonedeb@wampee.canonical.com>
Message-ID: <20160410174011.31955.49591.malone@chaenomeles.canonical.com>

The underlying issue is redirects lose POST data. Most mainstream
browsers when receiving a 301 or 302 in response to a POST will issue a
GET of the new URI. HTTP 1.1 defined 307 and 308  redirects to
specifically say that the browser should use the same request method for
the new URI, but if the server is issuing a 301 or 302 redirect rather
than a 307 or 308, the POST data is lost.

Your issue is not due to a Mailman change as the only change in this
area was in Mailman 2.1.12 and that change made more URLs relative, not
fewer. However, Your Mailman installation is cPanel, and this could be a
cPanel issue. See http://wiki.list.org/DOC/Mailman%20and%20CPanel , but
http://noonway.com/mailman/admindb/humor_noonway.com is definitely being
redirected to
http://just63.justhost.com/mailman/admindb/humor_noonway.com with a 301
redirect. Many other cPanel Mailman hosts don't do this redirection as
it breaks other things too.

Depending on how much access you have to the actual Mailman installation
on the server, you may be able to change things. At around line 204 in
Mailman/Cgi/admindb.py you'll see

        # Now print the results and we're done.  Short circuit for when there
        # are no pending requests, but be sure to save the results!
        admindburl = mlist.GetScriptURL('admindb', absolute=1)

if you remove the ", absolute=1" from the last of those to make it

        admindburl = mlist.GetScriptURL('admindb')

that should make the form action URL relative.

As for changing this in the upstream code, there are several places
where absolute URLs are generated in this way. I don't know the
historical reasons for this or what the unintended consequences might be
if they were changed, so I'm reluctant to do so.

It definitely appears that just63.justhost.com has made mods to the
basic cPanel Mailman, e.g. the "delegated access" on the admin(db) login
pages and the lack of a link in the footer to "Overview of all
noonway.com mailing lists" (which is another thing that wouldn't work
because of the redirect), so they ought to fix this too.

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

Title:
  admindb POST fails due to absolute addressing

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

From rob at ubutton.com  Sun Apr 10 20:50:24 2016
From: rob at ubutton.com (Rob Button)
Date: Mon, 11 Apr 2016 00:50:24 -0000
Subject: [Bug 1568547] Re: admindb POST fails due to absolute addressing
References: <20160410155446.1187.22027.malonedeb@wampee.canonical.com>
 <20160410174011.31955.49591.malone@chaenomeles.canonical.com>
Message-ID: <48100A3A-97AA-4A99-9BFF-28A17B918CEE@ubutton.com>

Mark,

I greatly appreciate the detailed reply. I?ll see if I can get JustHost to fix this for me, although they haven?t been at all responsive which is why I posted a bug report. 
Maybe another fix would be for me to install Mailman into a directory I can access. 

Thanks again,
Rob.

> On Apr 10, 2016, at 1:40 PM, Mark Sapiro <mark at msapiro.net> wrote:
> 
> The underlying issue is redirects lose POST data. Most mainstream
> browsers when receiving a 301 or 302 in response to a POST will issue a
> GET of the new URI. HTTP 1.1 defined 307 and 308  redirects to
> specifically say that the browser should use the same request method for
> the new URI, but if the server is issuing a 301 or 302 redirect rather
> than a 307 or 308, the POST data is lost.
> 
> Your issue is not due to a Mailman change as the only change in this
> area was in Mailman 2.1.12 and that change made more URLs relative, not
> fewer. However, Your Mailman installation is cPanel, and this could be a
> cPanel issue. See http://wiki.list.org/DOC/Mailman%20and%20CPanel , but
> http://noonway.com/mailman/admindb/humor_noonway.com is definitely being
> redirected to
> http://just63.justhost.com/mailman/admindb/humor_noonway.com with a 301
> redirect. Many other cPanel Mailman hosts don't do this redirection as
> it breaks other things too.
> 
> Depending on how much access you have to the actual Mailman installation
> on the server, you may be able to change things. At around line 204 in
> Mailman/Cgi/admindb.py you'll see
> 
>        # Now print the results and we're done.  Short circuit for when there
>        # are no pending requests, but be sure to save the results!
>        admindburl = mlist.GetScriptURL('admindb', absolute=1)
> 
> if you remove the ", absolute=1" from the last of those to make it
> 
>        admindburl = mlist.GetScriptURL('admindb')
> 
> that should make the form action URL relative.
> 
> As for changing this in the upstream code, there are several places
> where absolute URLs are generated in this way. I don't know the
> historical reasons for this or what the unintended consequences might be
> if they were changed, so I'm reluctant to do so.
> 
> It definitely appears that just63.justhost.com has made mods to the
> basic cPanel Mailman, e.g. the "delegated access" on the admin(db) login
> pages and the lack of a link in the footer to "Overview of all
> noonway.com mailing lists" (which is another thing that wouldn't work
> because of the redirect), so they ought to fix this too.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1568547
> 
> Title:
>  admindb POST fails due to absolute addressing
> 
> Status in GNU Mailman:
>  New
> 
> Bug description:
>  The shared server I use employs re-directs from my domain name to
>  their local server domain name. This is causing form submission POSTs
>  to fail in the ADMINDB pages used to moderate user posts, but not in
>  the ADMIN pages used to manage the Mailman list. A review of the
>  server code reveals why -
> 
>  The ADMIN pages use relative addressing in the form POST, so redirects are not an issue. 
>  Whereas the ADMINDB pages use absolute addressing in the form POST. See examples below from my website - 
> 
>  THIS WORKS - From http://just63.justhost.com/mailman/admin/humor_noonway.com
>  <FORM action="../admin/humor_noonway.com/general" method="POST" >
> 
> 
>  THIS DOESN'T WORK - From http://just63.justhost.com/mailman/admindb/humor_noonway.com
>  <FORM action="http://noonway.com/mailman/admindb/humor_noonway.com" method="POST" >
> 
>  This hasn't been an issue for the 12 years I've used Mailman to manage
>  user posts, but all of a sudden user post management is non-
>  functional. I can't tell if this is a change in my shared server
>  setup, or an update to Mailman 2.1.20 causing this.
> 
>  There are probably Apache server settings I could change to solve
>  this, but I can't access the folders needed to do so on a shared
>  server. Is there a reason why the ADMINDB code couldn't be changed to
>  use relative addressing like the code in ADMIN?
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mailman/+bug/1568547/+subscriptions

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

Title:
  admindb POST fails due to absolute addressing

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

From mark at msapiro.net  Thu Apr 14 18:34:22 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 14 Apr 2016 22:34:22 -0000
Subject: [Bug 1570630] [NEW] Some entries in data/virtual-mailman can be
 duplicates or be missing VIRTUAL_MAILMAN_LOCAL_DOMAIN
Message-ID: <20160414223423.16928.63112.malonedeb@soybean.canonical.com>

Public bug reported:

If VIRTUAL_MAILMAN_LOCAL_DOMAIN is non-empty it should also be appended
to the addresses in the SITE ADDRESSES stanza.

If the site list's host_name attribute is in
POSTFIX_STYLE_VIRTUAL_DOMAINS the site list posting address will be in
both the SITE ADDRESSES stanza an in the list's virtual mapping stanza.
This causes postmap to warn about the duplication.

** 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/1570630

Title:
  Some entries in data/virtual-mailman can be duplicates or be missing
  VIRTUAL_MAILMAN_LOCAL_DOMAIN

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

From 1570630 at bugs.launchpad.net  Thu Apr 14 19:27:33 2016
From: 1570630 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 14 Apr 2016 23:27:33 -0000
Subject: [Bug 1570630] Re: Some entries in data/virtual-mailman can be
 duplicates or be missing VIRTUAL_MAILMAN_LOCAL_DOMAIN
References: <20160414223423.16928.63112.malonedeb@soybean.canonical.com>
Message-ID: <20160414232733.14668.34491.launchpad@ackee.canonical.com>

** 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/1570630

Title:
  Some entries in data/virtual-mailman can be duplicates or be missing
  VIRTUAL_MAILMAN_LOCAL_DOMAIN

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

From mark at msapiro.net  Thu Apr 14 19:28:21 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 14 Apr 2016 23:28:21 -0000
Subject: [Bug 1570630] Re: Some entries in data/virtual-mailman can be
 duplicates or be missing VIRTUAL_MAILMAN_LOCAL_DOMAIN
References: <20160414223423.16928.63112.malonedeb@soybean.canonical.com>
Message-ID: <20160414232822.24386.37488.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/1570630

Title:
  Some entries in data/virtual-mailman can be duplicates or be missing
  VIRTUAL_MAILMAN_LOCAL_DOMAIN

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

From mark at msapiro.net  Tue Apr 19 00:44:37 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 04:44:37 -0000
Subject: [Bug 1570630] Re: Some entries in data/virtual-mailman can be
 duplicates or be missing VIRTUAL_MAILMAN_LOCAL_DOMAIN
References: <20160414223423.16928.63112.malonedeb@soybean.canonical.com>
Message-ID: <20160419044439.25286.88494.launchpad@wampee.canonical.com>

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

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

Title:
  Some entries in data/virtual-mailman can be duplicates or be missing
  VIRTUAL_MAILMAN_LOCAL_DOMAIN

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

From mark at msapiro.net  Tue Apr 19 00:44:16 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 04:44:16 -0000
Subject: [Bug 1568445] Re: DMARC mitigation can check an invalid domain if the
 From: local part contains a quoted '@'.
References: <20160410043451.31921.66839.malonedeb@chaenomeles.canonical.com>
Message-ID: <20160419044417.17539.5468.launchpad@soybean.canonical.com>

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

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

Title:
  DMARC mitigation can check an invalid domain if the From: local part
  contains a quoted '@'.

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

From mark at msapiro.net  Tue Apr 19 00:44:06 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 04:44:06 -0000
Subject: [Bug 1568398] Re: DMARC mitigation can be incorrectly (not) applied
 for a sub-domain.
References: <20160409214544.1804.18493.malonedeb@wampee.canonical.com>
Message-ID: <20160419044406.24579.34060.launchpad@gac.canonical.com>

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

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

Title:
  DMARC mitigation can be incorrectly (not) applied for a sub-domain.

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

From mark at msapiro.net  Tue Apr 19 00:43:54 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 04:43:54 -0000
Subject: [Bug 1562408] Re: German translation typo 'letzte'
References: <20160326221209.3705.81196.malonedeb@chaenomeles.canonical.com>
Message-ID: <20160419044355.25147.96056.launchpad@wampee.canonical.com>

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

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

Title:
  German translation typo 'letzte'

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

From mark at msapiro.net  Tue Apr 19 00:43:28 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 04:43:28 -0000
Subject: [Bug 1555798] Re: bin/arch can throw ValueError on bad Date: headers
References: <20160310201353.31618.427.malonedeb@gac.canonical.com>
Message-ID: <20160419044329.5462.92641.launchpad@chaenomeles.canonical.com>

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

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

Title:
  bin/arch can throw ValueError on bad Date: headers

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

From mark at msapiro.net  Tue Apr 19 00:43:13 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 04:43:13 -0000
Subject: [Bug 1553888] Re: CommandRunner shunts message with TypeError if
 message body is a null byte
References: <20160307061942.32189.99384.malonedeb@gac.canonical.com>
Message-ID: <20160419044314.23832.9679.launchpad@gac.canonical.com>

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

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

Title:
  CommandRunner shunts message with TypeError if message body is a null
  byte

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

From mark at msapiro.net  Tue Apr 19 00:42:56 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 04:42:56 -0000
Subject: [Bug 1551075] Re: Content filtering breaks some PGP Mime signed
 messages.
References: <20160229050154.1894.56042.malonedeb@wampee.canonical.com>
Message-ID: <20160419044258.5424.3740.launchpad@chaenomeles.canonical.com>

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

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

Title:
  Content filtering breaks some PGP Mime signed messages.

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

From mark at msapiro.net  Tue Apr 19 00:42:31 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 04:42:31 -0000
Subject: [Bug 557955] Re: usenet threading improvements
References: <20100408090318.1687.99577.launchpad@loganberry.canonical.com>
Message-ID: <20160419044232.24074.28333.launchpad@gac.canonical.com>

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

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

Title:
  usenet threading improvements

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

From mark at msapiro.net  Tue Apr 19 01:15:11 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 05:15:11 -0000
Subject: [Bug 1462755] Re: qrunner crashes on invalid unicode sequence
References: <20150607142830.12558.37544.malonedeb@soybean.canonical.com>
Message-ID: <20160419051511.24867.25634.malone@wampee.canonical.com>

For more information on the causes of this issue and the fallout from
what turns out to be Debian's changing of the character set for several
languages, see the thread "Encoding problem with 2.15 to 2.18 upgrade
with Finnish" beginning at <https://mail.python.org/pipermail/mailman-
users/2015-December/080221.html> and continuing at
<https://mail.python.org/pipermail/mailman-
users/2016-January/080275.html>. There is a script mentioned in that
thread at <https://www.msapiro.net/scripts/recode_list> (mirrored at
<http://fog.ccsf.edu/~msapiro/scripts/recode_list>) that can
programmatically recode the strings in a list's configuration to "fix"
this issue.

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

Title:
  qrunner crashes on invalid unicode sequence

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

From mark at msapiro.net  Tue Apr 19 18:44:45 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 22:44:45 -0000
Subject: [Bug 1572330] [NEW] RFE,
 make nonmember_rejection_notice if any the default admindb reject
 reason for a nonmember post
Message-ID: <20160419224445.24579.2909.malonedeb@gac.canonical.com>

Public bug reported:

The list attribute nonmember_rejection_notice is given as the reason for
an automatic rejection because the poster is in reject_these_nonmembers
or generic_nonmember_action is Reject.

It would be nice if this were also the default reject reason for a held
nonmember post.

** Affects: mailman
     Importance: Wishlist
     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/1572330

Title:
  RFE, make nonmember_rejection_notice if any the default admindb reject
  reason for a nonmember post

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

From 1572330 at bugs.launchpad.net  Tue Apr 19 18:54:18 2016
From: 1572330 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 19 Apr 2016 22:54:18 -0000
Subject: [Bug 1572330] Re: RFE,
 make nonmember_rejection_notice if any the default admindb reject
 reason for a nonmember post
References: <20160419224445.24579.2909.malonedeb@gac.canonical.com>
Message-ID: <20160419225420.5951.39407.launchpad@ackee.canonical.com>

** 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/1572330

Title:
  RFE, make nonmember_rejection_notice if any the default admindb reject
  reason for a nonmember post

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

From mark at msapiro.net  Tue Apr 19 18:56:48 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 19 Apr 2016 22:56:48 -0000
Subject: [Bug 1572330] Re: RFE,
 make nonmember_rejection_notice if any the default admindb reject
 reason for a nonmember post
References: <20160419224445.24579.2909.malonedeb@gac.canonical.com>
Message-ID: <20160419225649.25034.20013.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/1572330

Title:
  RFE, make nonmember_rejection_notice if any the default admindb reject
  reason for a nonmember post

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

From mark at msapiro.net  Thu Apr 21 10:35:00 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 21 Apr 2016 14:35:00 -0000
Subject: [Bug 1573074] [NEW] Provide a better way to enable smtplib debugging.
Message-ID: <20160421143500.5387.23276.malonedeb@chaenomeles.canonical.com>

Public bug reported:

To debug low level smtplib failures, one can modify SMTPDirect.py to
enable debugging. There should be an mm_cfg.py setting for 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/1573074

Title:
  Provide a better way to enable smtplib debugging.

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

From mark at msapiro.net  Thu Apr 21 11:01:54 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 21 Apr 2016 15:01:54 -0000
Subject: [Bug 1573074] Re: Provide a better way to enable smtplib debugging.
References: <20160421143500.5387.23276.malonedeb@chaenomeles.canonical.com>
Message-ID: <20160421150155.5831.35958.launchpad@chaenomeles.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/1573074

Title:
  Provide a better way to enable smtplib debugging.

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

From 1573074 at bugs.launchpad.net  Thu Apr 21 11:01:55 2016
From: 1573074 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 21 Apr 2016 15:01:55 -0000
Subject: [Bug 1573074] Re: Provide a better way to enable smtplib debugging.
References: <20160421143500.5387.23276.malonedeb@chaenomeles.canonical.com>
Message-ID: <20160421150156.19602.51035.launchpad@ackee.canonical.com>

** 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/1573074

Title:
  Provide a better way to enable smtplib debugging.

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

From 1573623 at bugs.launchpad.net  Fri Apr 22 09:54:29 2016
From: 1573623 at bugs.launchpad.net (Ethan Furman)
Date: Fri, 22 Apr 2016 13:54:29 -0000
Subject: [Bug 1573623] [NEW] admin screen logout link effects entire row
Message-ID: <20160422135429.5722.22556.malonedeb@chaenomeles.canonical.com>

Public bug reported:

On the admain screen the row below the "click here to reload this page"
link has a logout link, which is flush right; however, the html:

  <a href="https://mail.python.org/mailman/admindb/python-
list/logout"><div align="right"><font
size="+2"><b>Logout</b></font></div></a>

turns the entire row (not just the text) into a logout link, which means
if my cursor floats just a little too low when trying to refresh the
page I get logged out.

** Affects: mailman
     Importance: Undecided
         Status: New


** Tags: html logout

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

Title:
  admin screen logout link effects entire row

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

From 1444185 at bugs.launchpad.net  Fri Apr 22 12:48:54 2016
From: 1444185 at bugs.launchpad.net (Florian Fuchs)
Date: Fri, 22 Apr 2016 16:48:54 -0000
Subject: [Bug 1444185] Re: Implement configuration access
References: <20150414224524.30278.32361.malonedeb@gac.canonical.com>
Message-ID: <20160422164855.23766.31126.launchpad@gac.canonical.com>

** Changed in: mailman.client
       Status: In Progress => Fix Released

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

Title:
  Implement configuration access

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

From 883951 at bugs.launchpad.net  Fri Apr 22 12:49:27 2016
From: 883951 at bugs.launchpad.net (Florian Fuchs)
Date: Fri, 22 Apr 2016 16:49:27 -0000
Subject: [Bug 883951] Re: Implement MM3 preferences API resources in
 mailman.client
References: <20111030194650.8624.72163.malonedeb@gac.canonical.com>
Message-ID: <20160422164928.5188.71858.launchpad@chaenomeles.canonical.com>

** Changed in: mailman.client
       Status: In Progress => Fix Released

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

Title:
  Implement MM3 preferences API resources in mailman.client

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

From 1313912 at bugs.launchpad.net  Fri Apr 22 12:49:06 2016
From: 1313912 at bugs.launchpad.net (Florian Fuchs)
Date: Fri, 22 Apr 2016 16:49:06 -0000
Subject: [Bug 1313912] Re: Admin settings are not very well-aligned
References: <20140428204449.24989.79523.malonedeb@wampee.canonical.com>
Message-ID: <20160422164907.24237.52690.launchpad@gac.canonical.com>

** Changed in: postorius
       Status: In Progress => Fix Released

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

Title:
  Admin settings are not very well-aligned

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

From 1457271 at bugs.launchpad.net  Fri Apr 22 12:50:28 2016
From: 1457271 at bugs.launchpad.net (Florian Fuchs)
Date: Fri, 22 Apr 2016 16:50:28 -0000
Subject: [Bug 1457271] Re: HTTP 500 error when saving changes to Message
 Acceptance settings
References: <20150521013843.28776.99573.malonedeb@wampee.canonical.com>
Message-ID: <20160422165029.5658.76328.launchpad@chaenomeles.canonical.com>

** Changed in: postorius
     Assignee: Florian Fuchs (flo-fuchs) => (unassigned)

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

Title:
  HTTP 500 error when saving changes to Message Acceptance settings

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

From 1573623 at bugs.launchpad.net  Fri Apr 22 13:13:36 2016
From: 1573623 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 22 Apr 2016 17:13:36 -0000
Subject: [Bug 1573623] Re: admin screen logout link effects entire row
References: <20160422135429.5722.22556.malonedeb@chaenomeles.canonical.com>
Message-ID: <20160422171338.10569.37252.launchpad@ackee.canonical.com>

** 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/1573623

Title:
  admin screen logout link effects entire row

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

From mark at msapiro.net  Fri Apr 22 13:14:43 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 22 Apr 2016 17:14:43 -0000
Subject: [Bug 1573623] Re: admin screen logout link effects entire row
References: <20160422135429.5722.22556.malonedeb@chaenomeles.canonical.com>
Message-ID: <20160422171444.17661.70647.launchpad@soybean.canonical.com>

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

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

** Changed in: mailman
    Milestone: None => 2.1.23

** Changed in: mailman
     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/1573623

Title:
  admin screen logout link effects entire row

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

From sonhadorpr at gmail.com  Sat Apr 23 15:36:56 2016
From: sonhadorpr at gmail.com (SonhadorPR)
Date: Sat, 23 Apr 2016 19:36:56 -0000
Subject: [Bug 266821] Re: privacy hole in password reminder
References: <20080905194256.1806.8914.launchpad@forster.canonical.com>
Message-ID: <20160423193656.24997.42164.malone@wampee.canonical.com>

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

Hello all! 
I don't know if this is the correct post for my problem, but while searching launchpad, the results sent me here. So, here it goes: I am one of the people "responsible", for the "birth and eventual official blessing" of www.ubuntu-pr.org, which is still in its infancy, as a wiki page, for the past 8 years, due to lack of time, experience and interest, to be honest. 
I am trying to revive the project, or find someone to hand it to, but I have forgotten the mailing list admin password. I (sonhadorpr[at]gmail) keep getting notices of spam and users wanting to connect, but I can't do anything about it. 
How can I reset the password? 
There should be a link that allows you to do that, or as mentioned above, some sort of security questions, for these problems. 
Thank you for your help!

-- 
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  Sat Apr 23 17:21:03 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 23 Apr 2016 21:21:03 -0000
Subject: [Bug 266821] Re: privacy hole in password reminder
References: <20080905194256.1806.8914.launchpad@forster.canonical.com>
Message-ID: <20160423212103.25512.97092.malone@wampee.canonical.com>

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

This bug report has nothing to do with list admin passwords. For
information on resetting a list admin password, see the FAQ article at
<https://wiki.list.org/x/4030543>. (Mailman 3 has better ways of dealing
with lost/forgotten passwords.)

-- 
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 sonhadorpr at gmail.com  Sat Apr 23 17:25:26 2016
From: sonhadorpr at gmail.com (SonhadorPR)
Date: Sat, 23 Apr 2016 21:25:26 -0000
Subject: [Bug 265179] Re: Security hole: passwords mailed in clear
References: <20080905191826.27052.96947.launchpad@forster.canonical.com>
Message-ID: <20160423212527.5864.20379.malone@chaenomeles.canonical.com>

Thank you!

-- 
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