Public bug reported:
The List-Post header should be retained by default in messages in the
MIME format digest to facilitate 'reply list' with MUAs that have that
feature.
** Affects: mailman
Importance: Undecided
Status: New
--
List-Post header should be retained in MIME digest messages
https://bugs.launchpad.net/bugs/526143
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
409 Conflict is probably a better HTTP response code for the REST API
when trying to subscribe an already subscribed member. Add some content
body to explain the situation.
** Affects: mailman
Importance: Undecided
Assignee: Barry Warsaw (barry)
Status: Confirmed
** Affects: mailman/3.0
Importance: Undecided
Assignee: Barry Warsaw (barry)
Status: Confirmed
** Tags: mailman3
** Changed in: mailman
Milestone: None => 3.0.0a6
** Changed in: mailman
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: mailman
Status: New => Confirmed
** Tags added: mailman3
** Also affects: mailman/3.0
Importance: Undecided
Assignee: Barry Warsaw (barry)
Status: Confirmed
--
Subscribing an already subscribed member via REST should 409
https://bugs.launchpad.net/bugs/552917
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
Mailman in pypi depends on munepy, but munepy has been renamed to
flufl.enum. Therefore no munepy-package exists in pypi, and the mailman
installation fails because of the dependency.
** Affects: mailman
Importance: Undecided
Status: New
--
Mailman package in pypi won't install
https://bugs.launchpad.net/bugs/593029
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
Mailman 3 development needs more isolation from system Python. Two
recent reports are semi-related:
* On Ubuntu systems that have been upgraded from Karmic to Lucid, there
is a bug in python-setuptools that causes buildout to fail with cryptic
error messages. See bug 576434 and bug 585188 for related failures
(though not in Mailman).
* Strange import conflicts with system installed Mailman that are hard
to debug. This is related to mailman.testing.i18n giving TypeErrors on
incorrect number of arguments when initializing flufl.i18n.
I think the fix is to make sure the build works with virtualenv. Then
we have to decide whether it's still worth keeping the buildout
infrastructure for testing purposes.
** Affects: mailman
Importance: High
Assignee: Barry Warsaw (barry)
Status: Confirmed
** Affects: mailman/3.0
Importance: High
Assignee: Barry Warsaw (barry)
Status: Confirmed
** Changed in: mailman
Status: New => Confirmed
** Changed in: mailman
Importance: Undecided => High
** Changed in: mailman
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: mailman
Milestone: None => 3.0.0a6
** Also affects: mailman/3.0
Importance: High
Assignee: Barry Warsaw (barry)
Status: Confirmed
--
Set up virtualenv (and ditch buildout?)
https://bugs.launchpad.net/bugs/585512
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
When a message from Mailman gets routed to an IMAP server (e.g. for
archiving or administration), we need a sieve rule to do proper routing.
E.g. for dovecot.
** Affects: mailman
Importance: High
Assignee: Barry Warsaw (barry)
Status: Confirmed
** Changed in: mailman
Status: New => Confirmed
** Changed in: mailman
Importance: Undecided => High
** Changed in: mailman
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: mailman
Milestone: None => 3.0.0a6
--
Add sieve rules to route messages properly to IMAP server
https://bugs.launchpad.net/bugs/582525
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
For every mailing list we expose to IMAP, we'll want to create a few
folders. Hook in the IMAP folder creation to the list creation hooks.
** Affects: mailman
Importance: High
Assignee: Barry Warsaw (barry)
Status: Confirmed
** Changed in: mailman
Status: New => Confirmed
** Changed in: mailman
Importance: Undecided => High
** Changed in: mailman
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: mailman
Milestone: None => 3.0.0a6
--
Use IMAP CREATE to add folders to IMAP archiver on list creation
https://bugs.launchpad.net/bugs/582524
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
Dovecot beta supports delivery via LMTP. Mailman 3 should implement a
generic archive delivery implementation that delivers via LMTP.
** Affects: mailman
Importance: High
Assignee: Barry Warsaw (barry)
Status: Confirmed
** Changed in: mailman
Status: New => Confirmed
** Changed in: mailman
Milestone: None => 3.0.0a6
** Changed in: mailman
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: mailman
Importance: Undecided => High
--
Implement archive delivery via LMTP
https://bugs.launchpad.net/bugs/582522
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
Contrary to "src/mailman/docs/START.txt" which says
Run the ``bin/mailman info`` command to see which configuration file Mailman
will use, and where it will put its database file. The first time you run
this, Mailman will also create any necessary run-time directories and log
files.
neither the mailman command alone nor running it with option "info"
creates the initial directory structure.
If you go with the default settings in mailman.cfg you probably won't
notice because you are within the correct directory structure. But if
you set "var_dir: /opt/mailman" in e.g. /etc/mailman.cfg things break.
I believe fixing this would also fix ticket #543620.
** Affects: mailman
Importance: Undecided
Status: New
--
mailman command does not initialize directory structure on first run
https://bugs.launchpad.net/bugs/543627
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Malte S. Stretz has proposed merging lp:~mss/mailman/2.1-sender-header into lp:mailman/2.1.
Requested reviews:
Mailman Coders (mailman-coders)
Related bugs:
#266824 Add option to remove Sender header
https://bugs.launchpad.net/bugs/266824
Adds the long due option to disable the generation of the Sender header. The patch is quite simple, the changes in behaviour essentially being what some people already use for ages. But I don't know if I made an error in the GUI integration. Already prediscussed here <http://www.mail-archive.com/mailman-developers%40python.org/msg11948.html>.
--
https://code.launchpad.net/~mss/mailman/2.1-sender-header/+merge/28901
Your team Mailman Coders is requested to review the proposed merge of lp:~mss/mailman/2.1-sender-header into lp:mailman/2.1.