Public bug reported:
If the site has set 'VERP_PROBES = Yes', when a user's bounce score
reaches threshold, that user's score is reset and a probe message with a
confirmation token is sent to the user. If the probe bounces, the user's
delivery is disabled by bounce.
The issue is if the probe bounces, but for some reason, the bounce is
not returned within bounce_info_stale_after days, the user's bounce_info
can be deleted before the probe bounce is returned. Then the probe
processing gets the user's bounce_info which is None and attempts to
disable the member's delivery with bounce_info = None, and
disableBouncingMember attempts to get the cookie attribute from None
resulting in
AttributeError: 'NoneType' object has no attribute 'cookie'
** 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/1482940
Title:
A bounced probe can throw AttributeError
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1482940/+subscriptions
Public bug reported:
An address of the form mailman(a)example.com is exposed on the web admin
and listinfo overview pages where 'mailman' is the name of the site list
and 'example.com' is the 'email domain' associated with the host in the
URL of the page.
This means that the 'mailman' address should work in all Postfix virtual
domains and Mailman/MTA/Postfix.py should generate virtual mappings for
that.
** 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/1459236
Title:
Mailman/Postfix integration doesn't generate virtual maps for all site
list domains.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1459236/+subscriptions
Public bug reported:
The fix for (LP: #1082746) implemented a SUBSCRIBE_FORM_SECRET feature.
If this is enabled by a site, the subscribe form on the listinfo page
contains a hidden input field which includes a hash of various data
including the IP address that the GET of the listinfo came from. Upon
submission of the form, this hash is recomputed using the IP address
that the POST of the form came from, and if the hashes don't match, the
subscribe fails.
This can cause legitimate subscribes to fail if the user is connected
via a load balancer or other device which submits http(s) requests using
a possibly different IP for each request.
** 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/1447445
Title:
Web subscribe can fail in cases of load balancers or other devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1447445/+subscriptions
Public bug reported:
Headers DKIM-Signature:, DomainKey-Signature: and Authentication-
Results: are not removed by default from mail to an anonymous list.
These headers can reveal the sending domain.
** 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/1444673
Title:
Anonymous lists can expose the sending domain.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1444673/+subscriptions
Public bug reported:
This is just a suggestion:
The current Mailman code offers two alternative DMARC mitigation values:
"Munge From" and "Wrap Message".
I would suggest a 3rd and even simpler mitigation:
"Keep Headers"
This setting would have the following effects within Mailman:
* Preserve the Subject header intact, as well as all other headers
listed in the DKIM-Signature header of the actual post.
* Do not remove the DKIM-Signature header, even if the Mailman option to
do so is set.
* Do not add a DKIM-Signature for the mailing list, even if otherwise
configured to do so.
* If there is no DKIM-Signature in the post, none of the above applies.
* When gatewaying from NNTP to SMTP and there is no DKIM-Signature
header in the post, use the "Munge From" procedure because most NNTP
servers and newsreaders do not add the required DKIM signatures anyway.
The expected effect on message delivery would be:
+ The posting passes DKIM validation for the signature placed there by
the posters domain
+ DMARC checking recipients will therefore (according to the DMARC spec)
accept the message as validly sent by the original poster and let it
pass.
+ Because the number of DKIM-Signature headers is not increased from 1
to 2, there is no issue with the common case where buggy DMARC checkers
use only the first or last DKIM-Signature header, even though the RFC
says to check all DKIM signatures that match the From header domain and
accept if at least one is good.
+ Spoofed posts via SMTP with an invalid DKIM-Signature header will be
correctly rejected as spoofs by anyone checking the DKIM signatures
according to DMARC or ADSP.
+ Spoofed posts via SMTP with no DKIM-Signature header will be correctly
rejected as spoofs by anyone checking the DKIM signatures according to
DMARC or ADSP.
Note: Older Mailman versions happen to already do this for replies (but
not original posts) by accident because they lack the code to rearrange
the "Re: " in the Subject header.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: dmarc
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1539390
Title:
Alternative DMARC mitigation: Keep Headers
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1539390/+subscriptions
Public bug reported:
>From UX point of view subscription based preference would be much less
overwhelming if we used some form of highlighting to separate lists that
have enabled email delivery and those that have disabled delivery.
Green highlight for email delivery enabled and red highlight for email
delivery disabled would be very useful.
** Affects: postorius
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to Postorius.
https://bugs.launchpad.net/bugs/1535194
Title:
highlight enabled lists with green color and disabled with red color
To manage notifications about this bug go to:
https://bugs.launchpad.net/postorius/+bug/1535194/+subscriptions
Public bug reported:
Rejected notice message gets code defined in Errors.py as follows
---
rejection = _('Your message was rejected')
notice = _('Your message was rejected')
---
But "_" function is not used Mailman.i18n.
Defined in Errors.py as follows:
---
def _(s):
return s
---
** 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/1532399
Title:
Rejected notice message is not use i18n in Errors.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1532399/+subscriptions
Public bug reported:
Storm is currently not supporting python3
Starting from Ubuntu 16.04 (LTS) [21th April 2016] ubuntu will include
by default support for only python 3, so this is becoming a fundamental
requirement: http://summit.ubuntu.com/uos-1511/meeting/22568/python3
-only-on-the-images/
Aside from various minor code changes the main problem will be probably
in fixing the storm/cextensions.c.
This ticket if for asking for a clarification on the status of the
project in order to understand if it is abandoned or there is a plan for
porting it to python 3.
** Affects: launchpad
Importance: Undecided
Status: New
** Affects: mailman
Importance: Undecided
Status: New
** Affects: storm
Importance: Undecided
Status: New
** Also affects: mailman
Importance: Undecided
Status: New
** Also affects: launchpad
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/1530734
Title:
python3 compatibility
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1530734/+subscriptions