Public bug reported:
Sites sometimes want to send digests on a different schedule for one or
a few lists. This is currently difficult as it requires running
cron/senddigests with, e.g., '-l listname' or '-l list1 -l list2' for
the one or two and separately with '-l listn' for all the others, and
this needs to be updated as lists are added or removed.
With a -e/--exceptlist option, only two crons are required, one with,
e.g., '-l list1 -l list2' and one with '-e list1 -e list2'
** Affects: mailman
Importance: Low
Assignee: Mark Sapiro (msapiro)
Status: 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/1619770
Title:
cron/senddigests needs an exceptlist option
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1619770/+subscriptions
Public bug reported:
Trailing blanks on option "subject_prefix" are removed on subject lines
with non-ASCII characters. F.i., with options
preferred_language = "Français"
subject_prefix = "[prefix] "
(irrespective of encode_ascii_prefixes)
sending this (via Seamonkey Mail, LANG=en_US.UTF-8):
Subject: "[prefix] c'est du français"
results in reception of:
Subject: "[prefix]c'est du français"
** 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/1525954
Title:
mailman-2.1.20: option "subject_prefix": prefix trailing blanks are
removed when subject lines have non-ASCII characters
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1525954/+subscriptions
Public bug reported:
Dear project leader,
In the Mailman version 2.1.21, you released a fix regarding Mailman-
Postfix:
- Mailman-Postfix integration will now add mailman@domain entries in
data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS
which is a host_name of a list. This is so the addresses which are
exposed on admin and listinfo overview pages of virtual domains will
be deliverable. (LP: #1459236)
That fix was a good thing. However there is an identical problem for the
site list owner email that is exposed in email notification when you
create a new list. Indeed, when you create a new list, there is a
notification that is sent to the list owner and which state that it must
address all questions to mailman-owner@VIRTUAL_DOMAIN. Therefore, you
should considere adding that alias too in the data/virtual-mailman map.
Right now, sending mail to such address result to non-delivery.
That being said, I would want give you my personal point of view
regarding the email addresses that are exposed.
Regarding the site list address that is exposed in the listinfo overview
page:
I tend to think that exposing the site list email address in the
listinfo overview page is a mistake. End-users that visit or subscribe
to the lists shouldn't have to ask any question to the mailman site list
administrator. Think of a shared hosting environment where there is the
sysadmin and the end-users which are administrators of their own lists.
Here, my thinking is that subscribers (or visitors) of the listinfo
interface should ask their questions, not to the mailman site list
administrator, but to the list administrator which is not always the
same person. From my point of view, only the list administrators should
have to ask something to the mailman site list administrator (sysadmin).
Another thing: In the listinfo oveview page, you're also exposing the
list administrator personal email in the footer (email used while
creating the list). From my point of view, that email should be hidden
from the visitors and subscribers. That email, always from my point of
view, should be replaced by the list owner email address
(<listname>-owner@VIRTUAL_DOMAIN).
Thank you.
** Affects: mailman
Importance: Undecided
Status: New
** Affects: mailman (Ubuntu)
Importance: Undecided
Status: New
** Affects: mailman (Debian)
Importance: Undecided
Status: New
** Description changed:
Dear project leader,
In the Mailman version 2.1.21, you released a fix regarding Mailman-
Postfix:
- - Mailman-Postfix integration will now add mailman@domain entries in
- data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS
- which is a host_name of a list. This is so the addresses which are
- exposed on admin and listinfo overview pages of virtual domains will
- be deliverable. (LP: #1459236)
+ - Mailman-Postfix integration will now add mailman@domain entries in
+ data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS
+ which is a host_name of a list. This is so the addresses which are
+ exposed on admin and listinfo overview pages of virtual domains will
+ be deliverable. (LP: #1459236)
- That fix was a good thing. However there is an identical problem for the site list owner email that is exposed in email notification when you create a new list. Indeed,
- when you create a new list, there is a notification that is sent to the list owner and which state that it must address all questions to mailman-owner@VIRTUAL_DOMAIN. Therefore, you should considere adding that alias too in the virtual-mailman map. Right now, sending mail to such address result to non-delivery notification.
+ That fix was a good thing. However there is an identical problem for the
+ site list owner email that is exposed in email notification when you
+ create a new list. Indeed, when you create a new list, there is a
+ notification that is sent to the list owner and which state that it must
+ address all questions to mailman-owner@VIRTUAL_DOMAIN. Therefore, you
+ should considere adding that alias too in the virtual-mailman map. Right
+ now, sending mail to such address result to non-delivery notification.
That being said, I would want give you my personal point of view
regarding the email addresses that are exposed.
Regarding the site list address that is exposed in the listinfo overview
page:
I tend to think that exposing the site list email address in the
listinfo overview page is a mistake. End-users that visit or subscribe
to the lists shouldn't have to ask any question to the mailman site list
administrator. Think of a shared hosting environment where there is the
sysadmin and end-users which are administrators of their own lists.
Here, my thinking is that subscribers (or visitors) of the listinfo
interface should ask their questions, not to the mailman site list
administrator, but to the list administrator which is not always the
same person. From my point of view, only the list administrators should
have to ask something to the mailman site list administrator (sysadmin).
Another thing: In the listinfo oveview page, you're also exposing the
list administrator personal email in the footer (email used while
creating the list). From my point of view, that email should be hidden
from the visitors and subscribers. That email, always from my point of
view should be replaced by the list owner email address
- (<listname>-owner@VIRTUAL_DOMAIN.
+ (<listname>-owner@VIRTUAL_DOMAIN).
+
+ Thank you.
** Description changed:
Dear project leader,
In the Mailman version 2.1.21, you released a fix regarding Mailman-
Postfix:
- Mailman-Postfix integration will now add mailman@domain entries in
data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS
which is a host_name of a list. This is so the addresses which are
exposed on admin and listinfo overview pages of virtual domains will
be deliverable. (LP: #1459236)
That fix was a good thing. However there is an identical problem for the
site list owner email that is exposed in email notification when you
create a new list. Indeed, when you create a new list, there is a
notification that is sent to the list owner and which state that it must
address all questions to mailman-owner@VIRTUAL_DOMAIN. Therefore, you
- should considere adding that alias too in the virtual-mailman map. Right
- now, sending mail to such address result to non-delivery notification.
+ should considere adding that alias too in the data/virtual-mailman map.
+ Right now, sending mail to such address result to non-delivery
+ notification.
That being said, I would want give you my personal point of view
regarding the email addresses that are exposed.
Regarding the site list address that is exposed in the listinfo overview
page:
I tend to think that exposing the site list email address in the
listinfo overview page is a mistake. End-users that visit or subscribe
to the lists shouldn't have to ask any question to the mailman site list
administrator. Think of a shared hosting environment where there is the
sysadmin and end-users which are administrators of their own lists.
Here, my thinking is that subscribers (or visitors) of the listinfo
interface should ask their questions, not to the mailman site list
administrator, but to the list administrator which is not always the
same person. From my point of view, only the list administrators should
have to ask something to the mailman site list administrator (sysadmin).
Another thing: In the listinfo oveview page, you're also exposing the
list administrator personal email in the footer (email used while
creating the list). From my point of view, that email should be hidden
from the visitors and subscribers. That email, always from my point of
view should be replaced by the list owner email address
(<listname>-owner@VIRTUAL_DOMAIN).
Thank you.
** Also affects: mailman (Debian)
Importance: Undecided
Status: New
** Also affects: mailman (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Dear project leader,
In the Mailman version 2.1.21, you released a fix regarding Mailman-
Postfix:
- Mailman-Postfix integration will now add mailman@domain entries in
data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS
which is a host_name of a list. This is so the addresses which are
exposed on admin and listinfo overview pages of virtual domains will
be deliverable. (LP: #1459236)
That fix was a good thing. However there is an identical problem for the
site list owner email that is exposed in email notification when you
create a new list. Indeed, when you create a new list, there is a
notification that is sent to the list owner and which state that it must
address all questions to mailman-owner@VIRTUAL_DOMAIN. Therefore, you
should considere adding that alias too in the data/virtual-mailman map.
- Right now, sending mail to such address result to non-delivery
- notification.
+ Right now, sending mail to such address result to non-delivery.
That being said, I would want give you my personal point of view
regarding the email addresses that are exposed.
Regarding the site list address that is exposed in the listinfo overview
page:
I tend to think that exposing the site list email address in the
listinfo overview page is a mistake. End-users that visit or subscribe
to the lists shouldn't have to ask any question to the mailman site list
administrator. Think of a shared hosting environment where there is the
- sysadmin and end-users which are administrators of their own lists.
+ sysadmin and the end-users which are administrators of their own lists.
Here, my thinking is that subscribers (or visitors) of the listinfo
interface should ask their questions, not to the mailman site list
administrator, but to the list administrator which is not always the
same person. From my point of view, only the list administrators should
have to ask something to the mailman site list administrator (sysadmin).
Another thing: In the listinfo oveview page, you're also exposing the
list administrator personal email in the footer (email used while
creating the list). From my point of view, that email should be hidden
from the visitors and subscribers. That email, always from my point of
- view should be replaced by the list owner email address
+ view, should be replaced by the list owner email address
(<listname>-owner@VIRTUAL_DOMAIN).
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/1694384
Title:
Missing list owner email alias in data/virtual-mailman
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions
Public bug reported:
This feature is an anti-spam measure to automatically moderate a user
who posts more than a threshold number of times in a defined interval.
The test for threshold includes the current message so if the threshold
is 1, all users are moderated whenever they post.
** 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/1693366
Title:
Setting member_verbosity_threshold to 1 results in moderating first
post.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1693366/+subscriptions
Public bug reported:
If a list is set to be an anonymous list, and a message is sent to the
-owner address, Mailman strips any existing DKIM header.
This means that if someone from a DMARC-restricted address (e.g.
yahoo.com) is sending a message that would get forwarded to an owner at
a DMARC-checking ISP (e.g. yahoo.com), the message is rejected: it fails
the DMARC check due to non-matching SPF and missing DKIM headers. If the
DKIM header was left intact, it should work, since Mailman didn't modify
the body for an -owner message.
It makes privacy sense to always strip DKIM headers on messages that
will be posted to an anonymous list. And it can work out okay because
DMARC munging mitigation can be applied afterwards.
But it doesn't seem to make sense to do the same for -owner messages on
anonymous lists. Mailman doesn't apply other anonymous list
modifications, like hiding the "From:" header, for -owner messages, as
far as I can tell.
This happens, by the way, due to Defaults.py:
# This is the pipeline which messages sent to the -owner address go through
OWNER_PIPELINE = [
'SpamDetect',
'Replybot',
'CleanseDKIM',
'OwnerRecips',
'ToOutgoing',
]
Is 'CleanseDKIM' really helpful in this -owner flow? Removing it would
solve this problem. Alternately, perhaps CleanseDKIM could be taught to
exempt -owner addresses on anonymous lists.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: dkim 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/1645901
Title:
DKIM signatures stripped from -owner messages with anonymous lists
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1645901/+subscriptions
Public bug reported:
If the list's membership is large enough that the "letter" chunks need
multiple pages, the "view more members" links at the bottom of the page
are not correct.
** 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/1637061
Title:
Incorrect URLs in admin Membership List when chunked
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1637061/+subscriptions
Public bug reported:
Mailman's paths.py adds the path to the invoking Python's
/usr/lib/pythonx.y/site-packages directory to sys.path in case it's
missing due to Python being invoked with -S or some other reason. It
should also add /usr/lib/pythonx.y/dist-packages.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
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/1621172
Title:
paths.py should add dist-packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1621172/+subscriptions
Public bug reported:
Following a search which returned more than admin_member_chunksize hits,
the letter links on the admin Membership List are Unicodes and renderd
as u'http... which doesn't work.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: 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/1604544
Title:
Letter links on admin Membership List rendered as Unicodes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1604544/+subscriptions