Public bug reported:
If the original message is multipart but not multipart/alternative and
content filtering removes all but one part, the message is left as a
multipart message with only the one sub-part instead of being recast as
just the sub-part.
This can cause msg_header and/or msg_footer to be added as separate
parts to a text/plain message instead of being added to the text/plain
body part.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: Triaged
** Changed in: mailman
Importance: Undecided => Medium
** Changed in: mailman
Status: New => Triaged
** Changed in: mailman
Milestone: None => 2.1.15
** Changed in: mailman
Assignee: (unassigned) => Mark Sapiro (msapiro)
** Description changed:
- If the original message in multipart but not multipart/alternative and
+ If the original message is multipart but not multipart/alternative and
content filtering removes all but one part, the message is left as a
multipart message with only the one sub-part instead of being recast as
just the sub-part.
This can cause msg_header and/or msg_footer to be added as separate
- parts to a text/plain message instead if being added to the text/plain
+ parts to a text/plain message instead of being added to the text/plain
body part.
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/701558
Title:
Content filtering leaves a single sub-part in a multipart message.
Public bug reported:
Collapsing multipart/alternative parts to just the first alternative
only works if the message itself is multipart/alternative, or the
multipart/alternative part is at the first sub-level.
For example, given this structure:
multipart/mixed
| multipart/related
| | multipart/alternative
| | | text/plain
| | | text/html
| | image/jpeg
| application/msword
The multipart/alternative part will not be collapsed.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: In Progress
** Changed in: mailman
Importance: Undecided => Medium
** Changed in: mailman
Status: New => In Progress
** Changed in: mailman
Milestone: None => 2.1.14
** Changed in: mailman
Assignee: (unassigned) => Mark Sapiro (msapiro)
--
Content filtering fails to collapse alternatives.
https://bugs.launchpad.net/bugs/576675
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
If the case of the filename extension in the message doesn't agree with
that in *_filename_extension, they won't match. Matching should be case
insensitive.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: In Progress
** Affects: mailman/2.1
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: Fix Released
** Affects: mailman/3.0
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: In Progress
** Tags: mailman3
** Also affects: mailman/3.0
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: Fix Released
** Also affects: mailman/2.1
Importance: Undecided
Status: New
** Changed in: mailman/3.0
Status: Fix Released => In Progress
** Changed in: mailman/3.0
Milestone: mailman-2.1 => 3.0.0b2
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/978351
Title:
Content Filtering *_filename_extension matches are case sensitive.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/978351/+subscriptions
Public bug reported:
If Content filtering accepts both message/rfc822 and
multipart/alternative MIME parts, and a message/rfc822 part contains a
message whose content type is multipart/alternative and
collapse_alternatives is Yes, the headers of the message in the
message/rfc822 part will be lost.
** Affects: mailman
Importance: Low
Assignee: Mark Sapiro (msapiro)
Status: In Progress
** 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/757062
Title:
Content filtering can remove the headers from a message/rfc822 part.
Public bug reported:
On non ascii locale and DISABLE_COMMAND_LOCALE_CSET = yes,
bin/add_members get NameError because of uninitialized variable
Mailman.i18n._ctype_charset, which is used by Mailman.i18n.tolocale().
When DISABLE_COMMAND_LOCALE_CSET = yes, the function tolocale() is used
by bin/add_members only, so this affect only bin/add_members script.
** Affects: mailman
Importance: Undecided
Status: New
** Patch added: "least fix patch"
https://bugs.launchpad.net/bugs/1647450/+attachment/4787690/+files/i18n.py.…
** Branch linked: lp:mailman/2.1
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1647450
Title:
bin/add_members causes NameError when DISABLE_COMMAND_LOCALE_CSET =
yes
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1647450/+subscriptions
Public bug reported:
This may not occur in a normal installation, but on a test list I had an
accumulated digest.mbox with non-ascii characters in some message
subjects. I then changed the list's preferred_language from English to
Japanese and during some subsequent testing, a digest was triggered. The
creation of the digest would throw UnicodeError in attempting to create
the MIME toc part and in attempting to set the plain (RFC 1133) digest
payload.
This may be due only to the change to a language with a different
character set or it may be due to the fact that Mailman's character set
for Japanese is euc-jp, but the email modules output characterset for
euc-jp is iso-2022-jp. The exception thrown was due to unicodes not
representable in iso-2022-jp.
** 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/1644356
Title:
UnicodeError when attempting to send digests
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1644356/+subscriptions
Public bug reported:
There is a typo in the logging of an error condition that would result
in a NameError and a shunted message if a domain being checked for DMARC
moderation published multiple 'v=DMARC1;' txt records.
** 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/1637745
Title:
DMARC moderation could throw NameError in logging.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1637745/+subscriptions
Public bug reported:
This info is useful for systems (Debian/Ubuntu and maybe others) that
use insserv or a similar process to determin boot sequence.
** 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/1620121
Title:
The provided SYSV init script for mailman in missing LSB INIT INFO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1620121/+subscriptions
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