** Branch linked: lp:~mss/mailman/2.2-sender-header
--
Add option to remove Sender header
https://bugs.launchpad.net/bugs/266824
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
** Also affects: mailman/3.0
Importance: Medium
Status: Fix Committed
** Changed in: mailman/3.0
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: mailman/3.0
Milestone: None => 3.0.0a6
--
Add option to remove Sender header
https://bugs.launchpad.net/bugs/266824
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Sender header rewriting will be gone in 3.0: http://bazaar.launchpad.net
/~mailman-coders/mailman/3.0/revision/6915
** Changed in: mailman
Status: New => Fix Committed
--
Add option to remove Sender header
https://bugs.launchpad.net/bugs/266824
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
** Branch linked: lp:~mss/mailman/2.1-sender-header
--
Add option to remove Sender header
https://bugs.launchpad.net/bugs/266824
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
When moderating messages, I'm offered the opportunity to automatically
set the disposition of all future messages from a given sender. I expect
that the common case for this is "dispose of all future messages as I
did this one". However, the corresponding options are listed in
different orders for these two related actions. The attached picture
highlights what I'm talking about.
** Affects: mailman
Importance: Undecided
Status: New
--
UI inconsistency in administrative requests - actions in different orders
https://bugs.launchpad.net/bugs/597746
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
== Steps to reproduce ==
1.
Download the xslt Archives of Aug. 2002
<URL:http://mail.gnome.org/archives/xslt/2002-August.txt.gz>.
2.
gunzip '-l' '2002-August.txt.gz'
Is:
compressed uncompressed ratio uncompressed_name
145767 2831 -5048.0% 2002-August.txt
Should be:
compressed uncompressed ratio uncompressed_name
145767 380598 (whatever) 2002-August.txt
== Workaround ==
The workaround is to gunzip the archive without listing.
== See also ==
Ark reads only the first message of a gzipped digest
<URL:https://bugs.kde.org/show_bug.cgi?id=241153>
** Affects: mailman
Importance: Undecided
Status: New
--
malformed digest archive
https://bugs.launchpad.net/bugs/596764
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
The version of Mailman distributed with Apple's Mac OS X Server has a
hacked up mailmanctl, primarily to support not daemonizing in the
launchd environment. (I think). Their hack is ugly, and it'd be nice
if it was made unnecessary.
** Affects: mailman
Importance: Undecided
Status: New
--
Need a 'no-daemonize' option for '/bin/mailman start'
https://bugs.launchpad.net/bugs/497968
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
I'm using mailman 2.1.12.cp3 and I notice that if I set max_num_recipients to say "2", then send an email to the list and one other address, then it bounces with a message which includes "Too many recipients to the message", and the moderator needs to release it, even though there were only 2 recipients. If I send the message in the same way, with max_num_recipients set to "3", then the message goes through fine.
It seems to me that, instead of max_num_recipients being the "Ceiling on acceptable number of recipients for a posting", it is more like the "point at which messages will not be accepted", and (max_num_recipients + 1) is the ceiling.
I recommend the calculation be changed. Failing that, the variable name and its description should be changed.
Thanks for your excellent software!
** Affects: mailman
Importance: Undecided
Status: New
** Tags: max-num-recipients
--
max_num_recipients is out by 1
https://bugs.launchpad.net/bugs/596169
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
To Whom It May Concern:
This is not really a bug but didn't know where to place it. I would like
a web interface for the admin pages to delete the HTML and List
Archives. having to go through 50 different command line scripts to
delete an archive is a pain.
** Affects: mailman
Importance: Undecided
Status: New
--
delete archives from web admin pages
https://bugs.launchpad.net/bugs/595766
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
The problem is that "DELAY" is translated as "DEFERIR" but this word in brasilian means "ACCEPT", so the first 2 options means the same.
The word "DELAY" must be translated into "ADIAR".
This was detected on the admin page: Outras Atividades
Administrativas/Supervisionar requisições administrativas de moderação
pendentes .
Thanks for your work!
** Affects: mailman
Importance: Undecided
Status: New
--
Bad brasilian translation for the word "delay" on the admin interface.
https://bugs.launchpad.net/bugs/588692
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.