Mailman 3 January 2010 - Mailman-coders

[Bug 266760] Re: moderation approval should send email notification
by Raphaël Barrois Jan. 7, 2010

Jan. 7, 2010

--- Acknowledge.py.orig 2010-01-07 15:50:01.000000000 +0100 +++ Acknowledge.py 2010-01-07 15:50:43.000000000 +0100 @@ -38,7 +38,8 @@ if not ack: return except Errors.NotAMemberError: - return + if not mlist.notify_nonmembers_post_approved: + return # Okay, they want acknowledgement of their post. Give them their original # subject. BAW: do we want to use the decoded header? origsubj = msgdata.get('origsubj', msg.get('subject', _('(no subject)'))) -- moderation approval should send email notification https://bugs.launchpad.net/bugs/266760 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 266760] Re: moderation approval should send email notification
by Raphaël Barrois Jan. 7, 2010

Jan. 7, 2010

I think this functionnality would be quite useful for mailing lists used with "non-tech" users, who don't understand why they aren't notified of their message being approved... -- moderation approval should send email notification https://bugs.launchpad.net/bugs/266760 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 265965] Re: url parse (probably) cannot handle port number
by Mark Sapiro Jan. 7, 2010

Jan. 7, 2010

The original bug is invalid. If the site is properly configured with the appropriate port in DEFAULT_URL_PATTERN and PUBLIC_ARCHIVE_URL in mm_cfg.py the web interface works fine. E.g. DEFAULT_URL_PATTERN = 'http://%s:8080/mailman PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:8080/pipermail/%(listname)s' After making such a change in mm_cfg.py, you need to run fix_url to update existing lists. See the FAQs at <http://wiki.list.org/x/gIA9> and <http://wiki.list.org/x/mIA9>. The issue in the comment from Raphael Mankin is probably because the list's host_name attribute has a port. It should not. This in turn probably results from having a port appended to DEFAULT_EMAIL_HOST or the host in an add_virtualhost() directive. This is a misconfiguration. Note that the list's host_name is exposed and can be changed on the list's General Options admin page. ** Changed in: mailman Status: New => Invalid -- url parse (probably) cannot handle port number https://bugs.launchpad.net/bugs/265965 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 265965] Re: url parse (probably) cannot handle port number
by Raphael Mankin Jan. 6, 2010

Jan. 6, 2010

In particular, all mails sent from mailman have the port number on the end of the reply address. This causes certain mail servers to reject the messagges. A workaround is to have two web listeners, one on port 80 and one on the real port e.g. 8080. One then redirects all mailman requests on port 80 to the other port. I do this because I have to have my main web server and my mailman web server running as different users. The problem is current in 2.1.12 -- url parse (probably) cannot handle port number https://bugs.launchpad.net/bugs/265965 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 490602] Re: sourcecode/mailman/configure.in does not support group names with spaces
by Barry Warsaw Jan. 6, 2010

Jan. 6, 2010

This is not worth fixing. Mailman 3 doesn't use the same mechanism, and in all the years of MM2 development, this is the first such complaint about this I've seen. I didn't even know spaces in group names on *nix was allowed <wink>. ** Changed in: mailman Status: Confirmed => Won't Fix -- sourcecode/mailman/configure.in does not support group names with spaces https://bugs.launchpad.net/bugs/490602 You received this bug notification because you are a member of Mailman Coders, which is a direct subscriber.

1 0

[Bug 502022] [NEW] RFE: provide option to email displayed message to email address
by Aaron Whitehouse Jan. 1, 2010

Jan. 1, 2010

Public bug reported: Very often, I will come across a new piece of information on a topic that has previously been discussed on the list. I will then search through my email accounts to try and find a copy of an email in that thread and reply to it, so that the message is correctly archived in the list manager etc. Quite a lot of times, I will have deleted the relevant message. I then have to find it on the list, which is not a problem. Because I don't have a copy of the email to reply to, I can't reply to the thread and make it come up as part of the thread. At best, I can create a new email and add a permalink to the original thread. This would not, however, allow people browsing the old thread in the archives to see the newer information. What would be ideal (and which I have seen implemented in other list managers, but cannot remember where) would be if, after finding a post in the archives, one could click a button and enter an email address to have that message (with all thread headers etc.) emailed to that email address again. Then the user could simply reply to the new email to have the threading properly maintained. A second, related use-case is for people who aren't on the list and find a "hanging" thread in the archives. I often Google and find threads that end with something like "I will provide an update on this soon" with no following update. It would be nice, even if I wasn't on the mailing list, to have that one email sent to me so that I could reply and maintain threads. ** Affects: mailman Importance: Undecided Status: New -- RFE: provide option to email displayed message to email address https://bugs.launchpad.net/bugs/502022 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 2