Public bug reported:
The bin/disabled.py script needs tests, documentation, and fixing in
Mailman 2.
** Affects: mailman
Importance: High
Assignee: Barry Warsaw (barry)
Status: Confirmed
** Tags: mailman3
** Changed in: mailman
Status: New => Confirmed
** Changed in: mailman
Importance: Undecided => High
** Changed in: mailman
Milestone: None => 3.0.0b1
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/937154
Title:
bin/disabled.py is nonfunctional
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/937154/+subscriptions
Public bug reported:
Digest messages are sent out with a partial set of headers for each message.
The list of headers kept for each plain-text digested message is configured by the setting:
PLAIN_DIGEST_KEEP_HEADERS = [
'Message', 'Date', 'From',
'Subject', 'To', 'Cc',
'Message-ID', 'Keywords',
'Content-Type',
]
My users are very perplexed and frustrated by the e-mail headers
included in the digest - in particular, the Message-ID and Content-Type
are meaningless, and the To header is repetitive. All this "noise"
clutters up the content and makes the digest harder to read.
Given that this is a plain-text digest, with the headers listed in the
message body, I don't really see an RFC issue here? Yet they can only
be configured using a list-wide override in mm_cfg.py
I would be willing to work on this to allow a list admin to override the plain digest headers using the web interface, but want to hear from the development team if this is a patch they would be willing to consider before I invest the time.
thanks.
** 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/889635
Title:
Per-list configurable message headers for digests
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions
Public bug reported:
When the LMTP runner or any other injection vector receives a message,
it should add a Received header to indicate the time at which Mailman
got the message. Use case: there is a spam filter between the incoming
MTA and Mailman, and the message sits in the spam filter for a while
before its administrator accepts the message.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3
** Tags added: 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/885715
Title:
Mailman should add a Received header
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/885715/+subscriptions
Public bug reported:
I am running Mailman 3 in a virtualenv with most of its package
dependencies installed through pip. In this particular configuration, if
I run `buildout`, the test script that is created cannot seem to load
zope.testrunner properly:
$ bin/test -vv
Traceback (most recent call last):
File "bin/test", line 35, in <module>
import zope.testrunner
ImportError: No module named testrunner
The workaround is to remove the eggs folder, pip install
zope.testrunner, and then re-run buildout.
** 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/869347
Title:
bin/test script fails unless zope.testrunner is pip installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/869347/+subscriptions
Public bug reported:
You can subscribe an address to a mailing list, and you can subscribe a
user to a mailing list, if the user has a preferred address. There are
two problems with this.
* You can actually end up getting doubly subscribed (i.e. same address
with the same role). Normally, the subscription mechanism prevents you
from subscribing the same address with the same role more than once, or
the same user with the same role more than once. However, if you
subscribe once by the address, and once by the user whose preferred
address is that same address, the double subscription occurs.
* The Member repr() doesn't distinguish between a member that's
subscribed via explicit address, and one that's subscribed via preferred
address. This means that the above will appear as a double address
subscription, when it's really not.
Are these substantial problems that need to be fixed? Almost certainly
the second one does, but I haven't come up with an elegant repr() for
the case of a user subscribed with their preferred address.
** Affects: mailman
Importance: Low
Status: Confirmed
** 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/837700
Title:
Issues with users subscribed via their preferred address
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/837700/+subscriptions
Public bug reported:
I have a large number of subscriptions to mailing lists on python.org.
Delivery is disabled on most of them. This is exactly how I want it --
I don't want to keep up with the day to day matters of the list, but I
do want to be able to re-anable delivery and discuss things there should
the need arise without having to create a new account.
However, when I go on vacation, what I want to do is also disable a few high volume lists that I normally want
to read every day. Thus what I would really like to see is which lists are currently enabled, so I can decide
which one(s) if any I want to disable for the vacation. I don't want to disable the low-volume ones. Given
that I am going to have to re-enable the lists I want to read when I get back one by one, I want the number of lists that get temporarily disabled to be as small as possible. And I want to be able to email me the short list of what they were so I can remember which ones to turn on again.
Interestingly, the text of the message indicates a usability
misunderstanding, and a grammatical error. The text reads:
You can view a list of all the other mailing lists at python.org for which you are a member.
Use this if you want to make the same membership option changes to this other subscriptions.
It should be 'these other subscriptions'.
And the people who want to make the same membership option changes to all the lists they are subscribed to on a site are precisely the users who don't need the feature. They can blindly go off and change things
globally. If the number of lists they are subscribed to on that site is 1 -- i.e. they do not have any other subscriptions -- then saying to do things globally will do no harm.
The reason you might want to look is to check because you might _not_ want to do things globally. And once you are dealing with that case, things you do not want to do globally, then of course you want to see the
current settings that you have. But for my use case, all I care about is changing delivery status. All the
other options I either never change, or want to change globally. I suspect that most people use mailing
lists in this way, where the only thing they need to worry about is changes due to vacation, but I haven't
conducted any polls to test this theory.
This request sent to the tracker because the automated mail I recevied when some moderator refused
to accept my mail to mailman-dev with this feature request, with the message 'why don't you just disable delivery globally and then reset them globally when you return' said that this was the place for feature requests and not the mailing list. Hope this request is clearer and explains why globally disabling is not
what I want to do.
Thank you
** 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/793669
Title:
feature request. change the 'list my other subscriptions' to also
report if the other subscriptions are enabled or disabled
Public bug reported:
In Mailman Membership Management, I would like to option to filter
search results by status viz (hide,nomail [reason], ack, not metoo,
nodupes, digest, plain)
** 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/707295
Title:
Membership Management Better Search Function
Public bug reported:
Feature request
Mailman 3 should try to fuzzily match unknown author addresses against
the member database. For example, if "turnbull(a)sk.domain.tld" is
subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same
person. This could probably be efficiently implemented by storing
domains in bigendian order, and testing for prefixes. Bonus points for
matching on full name. For example, for me personally
firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which
could not be reasonably associated by algorithm, but I always use the
same full name, which would be strong indication that it's me. Possibly
matching on mailbox would also be useful, but only as an optimization to
be confirmed by one of the other two (or maybe if the match is unique?)
Note that for the first example, the second "turnbull@shako" variant is
today used only by spammers; I haven't sent a message with that "From"
since 1995, and I doubt it's been used as "Sender" more than a very
small handful of times since 2000. For this reason, the feature should
*never* be automated. Instead, it should be part of the moderation
interface. If a match is detected, then an option should appear saying
something like "This address appears to be an alias for <member name and
address>. [ ] Add <unknown address> as an alias for <member>."
** Affects: mailman
Importance: Undecided
Status: New
** Description changed:
Feature request
Mailman 3 should try to fuzzily match unknown author addresses against
the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is
subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same
person. This could probably be efficiently implemented by storing
domains in bigendian order, and testing for prefixes. Bonus points for
matching on full name. For example, for me personally
firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which
could not be reasonably associated by algorithm, but I always use the
same full name, which would be strong indication that it's me. Possibly
matching on mailbox would also be useful, but only as an optimization to
be confirmed by one of the other two (or maybe if the match is unique?)
Note that for the first example, the second "turnbull@shako" variant is
today used only by spammers; I haven't sent a message with that "From"
since 1995, and I doubt it's been used as "Sender" more than a very
small handful of times since 2000. For this reason, the feature should
*never* be automated. Instead, it should be part of the moderation
interface. If a match is detected, then an option should appear saying
something like "This address appears to be an alias for <member name and
- address>. [ ] Add <unknown> address as an alias for <member>."
+ address>. [ ] Add <unknown address> as an alias for <member>."
** Description changed:
Feature request
Mailman 3 should try to fuzzily match unknown author addresses against
- the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is
- subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same
+ the member database. For example, if "turnbull(a)sk.domain.tld" is
+ subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same
person. This could probably be efficiently implemented by storing
domains in bigendian order, and testing for prefixes. Bonus points for
matching on full name. For example, for me personally
firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which
could not be reasonably associated by algorithm, but I always use the
same full name, which would be strong indication that it's me. Possibly
matching on mailbox would also be useful, but only as an optimization to
be confirmed by one of the other two (or maybe if the match is unique?)
Note that for the first example, the second "turnbull@shako" variant is
today used only by spammers; I haven't sent a message with that "From"
since 1995, and I doubt it's been used as "Sender" more than a very
small handful of times since 2000. For this reason, the feature should
*never* be automated. Instead, it should be part of the moderation
interface. If a match is detected, then an option should appear saying
something like "This address appears to be an alias for <member name and
address>. [ ] Add <unknown address> as an alias for <member>."
--
Mailman 3 member functions should "guess" address membership
https://bugs.launchpad.net/bugs/514625
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
In mailman 3.0.0a8, the locales directory contains actually mailman 2 translations.
The unsubscribe mail is not translated into French because the msgids are different between mailman2 and mailman3.
Do you have a script to generate a pot file and sync the po files?
I had to generate myself the French mo file from the po. It's maybe a
good idea to include mo files in the sdist, or generate mo files at
mailman startup.
** 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/881320
Title:
Mailman 3 translations
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/881320/+subscriptions
Public bug reported:
The web URL needs to be attached to the individual mailing lists and not
to the email domain.
However, for ease of configuration, and following DRY principals,
default values should be derived from the list hierarchy.
As an example use case, consider:
The mail server is run by an umbrella organization. Each of the groups
under the umbrella has its own website. Some of those might be co-hosted
from the same server, but others could be elsewhere. Each group wants it
to appear as if they are "stand alone", providing UI access to the
mailing list functions from their individual websites rather than from
that of the umbrella organization.
** 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/1042828
Title:
UI web URLs should be per-mailinglist
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1042828/+subscriptions