Public bug reported:
When a message contains an invalud unicode sequence in its header,
qrunner flat out crashes on that:
May 17 15:32:20 2015 (981) Uncaught runner exception: 'utf8' codec can't decode byte
0xe9 in position 18: invalid continuation byte
May 17 15:32:20 2015 (981) Traceback (most recent call last):
File "/var/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop
self._onefile(msg, msgdata)
File "/var/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File "/var/lib/mailman/Mailman/Handlers/CookHeaders.py", line 239, in process
i18ndesc = uheader(mlist, mlist.description, 'List-Id', maxlinelen=998)
File "/var/lib/mailman/Mailman/Handlers/CookHeaders.py", line 65, in uheader
return Header(s, charset, maxlinelen, header_name, continuation_ws)
File "/usr/lib/python2.7/email/header.py", line 183, in __init__
self.append(s, charset, errors)
File "/usr/lib/python2.7/email/header.py", line 267, in append
ustr = unicode(s, incodec, errors)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe9 in position 18: invalid
continuation byte
May 17 15:32:20 2015 (981) SHUNTING:
1431869540.389822+156779307d54473d0eb732994bb67eee95733285
A solution for this specific case is to have Mailman/Handlers/CookHeaders.py pass the erorrs='replace' parameter.
I would say that this is actually a bug in python-email, since I think it doesn't make sense to set errors to "strict" rather than something like "replace" when the intention is to parse stuff so free-formed, under-specd
and user-controlled as email. Nonetheless, Mailman already sets errors='replace' in some places so it might aswell add it here.
** 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/1462755
Title:
qrunner crashes on invalid unicode sequence
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1462755/+subscriptions
Public bug reported:
We need a script, documentation, or other procedure to help people
migrate from Mailman 2 to Mailman 3.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: 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/965532
Title:
Need a script to upgrade from MM2 to MM3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/965532/+subscriptions
Public bug reported:
Mailman 3 is essentially five projects:
Mailman Core
Postorius - The Web UI for Mailman
Mailman Client - The REST API Client
HyperKitty - The Archiver for Mailman
Mailman Bundler - Installer for Mailman Suite including all above projects
URL: https://www.gnu.org/software/mailman/
** Affects: mailman
Importance: Undecided
Status: New
** Affects: ubuntu
Importance: Undecided
Status: New
** Affects: debian
Importance: Unknown
Status: Unknown
** Tags: needs-packaging
** Bug watch added: Debian Bug tracker #799292
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799292
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799292
Importance: Unknown
Status: Unknown
** 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/1609516
Title:
[needs-packaging] GNU Mailman v3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1609516/+subscriptions
Public bug reported:
Setting localhost in postfix_lmtp works against Postfix defaults and
breaks delivery.
Reason: The Postfix lmtp client only uses dns queries by default to
search for hostnames. If the DNS server does not provide an answer for
"localhost" delivery from the lmtp client to mailman fails.
Solution: Provide "127.0.0.1" instead of "localhost". This does not
require DNS and is even faster because it saves DNS lookups.
Example:
hey2(a)mailman.state-of-mind.de
lmtp:[localhost.localdomain]:8024
** Affects: mailman
Importance: Undecided
Status: New
** Tags: 3.0 mailman
--
setting localhost in postfix_lmtp breaks delivery
https://bugs.launchpad.net/bugs/544477
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
We have seen (very rarely) cases where a recipient address has a quoted
local part such as "jr."@example.org. This results in a VERPed sender
address like list-bounces+"jr."=example.org(a)example.com which is
syntactically invalid. The VERPed sender should be "list-
bounces+jr.=example.org"@example.com in this case. I.e., the entire
VERPed sender local part should be quoted, not just the recipient local
part.
This also requires BounceRunner to recognize this and restore the
original local part.
** 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/1731604
Title:
VERP fails if the recipient address local part is quoted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1731604/+subscriptions
Public bug reported:
We have seen some massive, robotic subscribes and confirmations. In rare
cases a TypeError can be thrown. This occurs because in processing, the
CGI script retrieves the pending entry more than once. If the initial
retrieval returns None, an appropriate message is returned, but if two
clients confirm the same token at the same time, both initial retrievals
may succeed, but then subsequent processing locks the list and retrieves
the data again. The first client to get there processes the confirmation
which removes the token. Then when the list is unlocked, the second
client gets None for the pending data and throws TypeError when
retrieving things from None.
** 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/1785854
Title:
TypeError from confirm CGI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1785854/+subscriptions
Public bug reported:
Hi,
We have updated our external MTA to use OpenBSD(6.4) and opensmptd.
After we updated, mailman started to send "bounce message w/no
discernable addresses" messages to us (list admins). It seems that
mailman is not able to parse bounce messages sent from opensmtpd.
Please check an example of a bounce message from opensmtpd:
Hi!
This is the MAILER-DAEMON, please DO NOT REPLY to this email.
An error has occurred while attempting to deliver a message for
the following list of recipients:
XXXXXXXXX(a)live.com: 550 5.5.0 Requested action not taken: mailbox
unavailable. [VE1EUR02FT047.eop-EUR02.prod.protection.outlook.com]
Below is a copy of the original message:
We are using mailman 2.1.11 and I could not test the issue on version
2.1.17. But, reading the code, it seem that the problem is still there.
We managed to fix the problem by editing the file
'mailman/Mailman/Bouncers/SimpleMatch.py' and including the following
lines:
191,194d190
< # opensmtpd
< (_c('An error has occurred while attempting to deliver a message for'),
< _c('Below is a copy of the original message'),
< _c('^\s*(?P<addr>[^\s@]+@[^\s@]+)')),
patch follows attached
Regards,
Cristiano
** Affects: mailman
Importance: Undecided
Status: New
** Patch added: "SimpleMatch.py.patch"
https://bugs.launchpad.net/bugs/1805137/+attachment/5216458/+files/SimpleMa…
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1805137
Title:
Bounces sent from opensmtpd not parsed
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1805137/+subscriptions
Public bug reported:
Suggest to include a simple captcha that (unlike reCAPTCHA) does not
involve feeding data to the internet advertising and surveillance
industry.
This could be a simple arithmetic captcha entirely implemented in python without any contact
to 3rd party servers. Such a mechanism should be sufficient to keep out ordinary spambots.
** 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/1774826
Title:
Feature request: simple captcha
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1774826/+subscriptions
Public bug reported:
MM3 still uses a lot of X- headers, but some of the X- prefixes can be
removed. In general, we can just claim the Mailman- prefix for Mailman
specific headers. Candidates include:
Mailman-Rule-Hits
Mailman-Rule-Misses
Mailman-Version
Mailman-Approved-At
Mailman-LMTP-MailFrom (i.e. X-MailFrom)
Mailman-Copy (or remove this header)
Mailman-Content-Filter (from X-Content-Filtered-By)
Also, fix the outdated comments about add-dup-header in
avoid_duplicates.py and verp.py.
Probably also get rid of X-List-Administrivia (and possibly
reduced_list_headers). These seem unnecessary now.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: 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/883193
Title:
Remove the X- prefix from some headers
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/883193/+subscriptions
Public bug reported:
It looks like there is no way for a MM3 plugin to be signaled for a new
posting.
It would be great if core could provide a notification to the plugins
that have subscribed to this event when a new post occurs.
This notification should carry some interesting information, like the
number of recipients and the message size.
This request is also essential for the MM3-Metrics module
(https://launchpad.net/mm3-metrics).
** Affects: mailman
Importance: Undecided
Status: New
** Tags: events mailman3 metrics modules notification plugins post
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1094696
Title:
Event notifications on postings
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1094696/+subscriptions