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:
Various failed authentications are reported in the security log, but
there are issues:
'options' identifies itself as 'private'.
'roster' doesn't report the user if available.
'create' and 'rmlist' don't log authentication failures.
** 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/1810098
Title:
Some security log messages have missing or incorrect information
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1810098/+subscriptions
Public bug reported:
When runner qrunner with --runners=All it calls all defined runners in
an endless loop[1]. Most of the time the runners have nothing to do and
quickly reach the point where they shut down again[2]. Note that this
happens before they sleep in self._snooze(), which is intended to
prevent a busy-loop. After that, the runners get started again without
delay, in an endless loop, eating up a CPU core.
As far as I know this should happen in any mailman2.1 setup when using
qrunner with --runners=All.
[1]: https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/bin/qru…
[2]: https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman…
** 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/1818205
Title:
qrunner --runners=All blocks one CPU core
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1818205/+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:
Login to the user options page and private archives authentication fails
if the email address has trailing spaces.
** 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/1818872
Title:
Trailing spaces in the email address cause login failures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1818872/+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:
The only way to get access to the list of users for my group is via the email interface "who" request. Mailman quite properly allows me to set arbitrary passwords that may have spaces. However the email interface becomes confused when I send
who This is just one password address=someone(a)somewhere.me
It seems like the parser should correctly note the "address=" keyword
and figure out that everything (space delimited) between "who" and
"address" is password. OR it should allow shell-like quoting.
** 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/1830663
Title:
admin email interface fails w/ password holding space
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1830663/+subscriptions
Public bug reported:
Hi Support,
8560E2170B 3716 Thu May 23 00:56:21 mailman-bounces(a)mail.wso2.org
(host ASPMX.L.GOOGLE.com[173.194.204.26] said: 450-4.2.1 The user you are trying to contact is receiving mail at a rate that 450-4.2.1 prevents additional messages from being delivered. Please resend your 450-4.2.1 message at a later time. If the user is able to receive mail at that 450-4.2.1 time, your message will be delivered. For more information, please 450-4.2.1 visit 450 4.2.1 https://support.google.com/mail/?p=ReceivingRate f15si5167250qkg.48 - gsmtp (in reply to RCPT TO command))
techops(a)wso2.com
Can you please advice why we are going through this error causing mails to queue.
Thanks & Regards,
Isuru
** 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/1830182
Title:
mails getting queued "he user you are trying to contact is receiving
mail at a rate that 450-4.2.1"
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1830182/+subscriptions