Mailman 3 December 2012 - Mailman-Users

RELEASED: GNU Mailman 3.0 beta 3
by Barry Warsaw 31 Dec '12

31 Dec '12

Hello friends of Mailman! I said I played this song so many times before That the melody keeps repeating Time for my usual "sneak one in before the new year" release! I'm happy to announce the third beta release of the core Mailman 3.0 engine. Mailman 3.0b3 is code named "Here Again". You can download GNU Mailman 3.0b3 from Launchpad or the Python Cheeseshop: https://launchpad.net/mailman http://pypi.python.org/pypi/mailman The GNU Mailman documentation is available online at: http://packages.python.org/mailman Alpha releases of Postorius, our new web ui are available at: https://launchpad.net/postorius http://pypi.python.org/pypi/postorius You might also like to take a look at the new archiver project called Hyperkitty: https://launchpad.net/hyperkitty GNU Mailman, Postorius, and Hyperkitty are all distributed under the GNU General Public License version 3 or later. Detailed changes in Mailman 3.0b3 are available here: http://tinyurl.com/adgeuwg Here's a summary of the most user and developer visible changes: * Python 2.7 is now required. Python 2.6 is no longer officially supported. * The canonical resource for a mailing list in the REST API now uses its list-id by default instead of its posting address. For backward compatibility, you can still reference a mailing list by its posting address. However the list-id is more stable since it will not change. * REST API change: The JSON representation for held messages has changed to a more flat representation. * You can now specify a list style to use when creating a mailing list through the REST API. * The `subject_prefix` attribute of mailing lists can be get/set through the REST API. Thanks to Terri Oda. * Membership change moderation (subscriptions and unsubscription requests) are available through the REST API. * `list_id` is added to the JSON representation for a mailing list. Thanks to Jimmy Bergman. * User resources are expanded in the REST API. You can change a user's display name or password, and you can now verify their password through REST by posting the plain text password and checking the HTTP response code. * Addresses can now be verified and unverified through the REST API. * Some changes have been made to the configuration file format. - [passlib]path is renamed to [passlib]configuration - [mta]configuration names a separate file to configure Postfix - The default style is now called `legacy-default`, and a `legacy-announce` style has been added. You can select the system default style through via the [styles]default configuration. * More database schema cleanups, in both the ban table and the mailinglist table. * Changes in the options for the `bin/mailman aliases` command. * Lots of other bug fixes. Enjoy, and Happy New Year, -Barry

1 0

Re: [Mailman-Users] log errors after restart
by Mark Sapiro 24 Dec '12

24 Dec '12

Con Wieland wrote: > >The system got restarted again to return ait to it;s original power >source before I got the original error tracked down. So when it >restarted this time I got this error. I was assuming I would find it in >the in queue and just remove it but there was nothing in the in >directory > >con > > >Dec 21 12:57:12 2012 (826) Ignoring unparseable message: 1350498399.3898871+2cdf0127ff3b85695d03ea16c34571045d928788 >Dec 21 12:57:12 2012 (826) Uncaught runner exception: No terminating boundary and no trailing empty line >Dec 21 12:57:12 2012 (826) Traceback (most recent call last): Even in 2.1.9, these messages are removed when you see the "Ignoring unparseable message:" entry. If you continue to see these, they are probably malformed spam messages tha have nothing to do with the outage and restart. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 9

Adding backup to multi-server config
by Jeff Taylor 23 Dec '12

23 Dec '12

I have been running mailman 2.1 from three servers with NFS sharing for the past couple years, but due to a recent issue I did some digging and found the suggestions for clustering at http://mail.python.org/pipermail/mailman-users/2008-March/060753.html (the post by Mark Sapiro detailing how to set up qrunner slices). It turns out the problem I was having was user error, so apparently mailman *can* run on a low traffic site without issue... however since I now have the proper changes made for qrunner, I have a new question. My network consists of three primary servers running postfix and mailman. These are each essentially redundant machines, and I am in the process of setting up a fourth machine in a VM for processing SMTP. What I am wondering about is if there would be a way to configure qrunner on this VM so that it only processes messages which have been in the queue for more than X minutes... basically a backup machine so that if the server processes one of the slices goes offline for an extended period, this backup server would make sure the message gets sent out. >From an initial glance, I was thinking of having a configurable Delay variable in mm_cfg.py, specified in seconds, then qrunner could use the timestamp on the queued messages and only process the ones which were older than Delay. This backup machine would *not* have the qrunner slices patch applied to it, as it should be processing any message that doesn't get handled by the primary servers. Does this sound plausible? Unfortunately I know nothing about python, nor the specifics of mailman's code, so I'm not sure if this would be an easy change that someone could give me the code for... but any help is appreciated.

3 5

How to properly nest a response from Gmail
by BA lanfest 23 Dec '12

23 Dec '12

I am a new member of a Mailman list. This feels like a stupid question, but the other day I tried to respond to a message, and it did not nest properly. It nested at the same level as the post I was responding to, rather than under it (and this was not a case of nesting limit, as other message did nest at the depth I desired). I checked the "In-Reply-To" header on my sent mail and sure enough it as replying to the Message-ID of the email I wanted to nest under. And yet it did not. Any ideas?

2 4

Re: [Mailman-Users] log errors after restart
by Con Wieland 21 Dec '12

21 Dec '12

In addition I just received this error: Dec 21 13:01:56 2012 qrunner(683): Traceback (most recent call last): Dec 21 13:01:56 2012 qrunner(683): File "/usr/local/mailman/bin/qrunner", line 278, in ? Dec 21 13:01:56 2012 qrunner(683): main() Dec 21 13:01:56 2012 qrunner(683): File "/usr/local/mailman/bin/qrunner", line 238, in main Dec 21 13:01:56 2012 qrunner(683): qrunner.run() Dec 21 13:01:56 2012 qrunner(683): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 71, in run Dec 21 13:01:56 2012 qrunner(683): filecnt = self._oneloop() Dec 21 13:01:56 2012 qrunner(683): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 100, in _oneloop Dec 21 13:01:56 2012 qrunner(683): msg, msgdata = self._switchboard.dequeue(filebase) Dec 21 13:01:56 2012 qrunner(683): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 150, in dequeue Dec 21 13:01:56 2012 qrunner(683): fp = open(filename) Dec 21 13:01:56 2012 qrunner(683): IOError : [Errno 2] No such file or directory: '/usr/local/mailman/qfiles/out/1356123714.5592401+1ec0a1f9ab8fdab3f923b9eb39d706046ac42b7b.pck' since it says there is no file I am not clear what I'm looking for here On Dec 21, 2012, at 1:01 PM, Con Wieland wrote: > Hi Mark, > > The system got restarted again to return ait to it;s original power source before I got the original error tracked down. So when it restarted this time I got this error. I was assuming I would find it in the in queue and just remove it but there was nothing in the in directory > > con > > > Dec 21 12:57:12 2012 (826) Ignoring unparseable message: 1350498399.3898871+2cdf0127ff3b85695d03ea16c34571045d928788 > Dec 21 12:57:12 2012 (826) Uncaught runner exception: No terminating boundary and no trailing empty line > Dec 21 12:57:12 2012 (826) Traceback (most recent call last): > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 100, in _oneloop > msg, msgdata = self._switchboard.dequeue(filebase) > File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 164, in dequeue > msg = email.message_from_string(msg, Message.Message) > File "/usr/local/mailman/pythonlib/email/__init__.py", line 51, in message_from_string > return Parser(_class, strict=strict).parsestr(s) > File "/usr/local/mailman/pythonlib/email/Parser.py", line 75, in parsestr > return self.parse(StringIO(text), headersonly=headersonly) > File "/usr/local/mailman/pythonlib/email/Parser.py", line 64, in parse > self._parsebody(root, fp, firstbodyline) > File "/usr/local/mailman/pythonlib/email/Parser.py", line 240, in _parsebody > msgobj = self.parsestr(part) > File "/usr/local/mailman/pythonlib/email/Parser.py", line 75, in parsestr > return self.parse(StringIO(text), headersonly=headersonly) > File "/usr/local/mailman/pythonlib/email/Parser.py", line 64, in parse > self._parsebody(root, fp, firstbodyline) > File "/usr/local/mailman/pythonlib/email/Parser.py", line 265, in _parsebody > msg = self.parse(fp) > File "/usr/local/mailman/pythonlib/email/Parser.py", line 64, in parse > self._parsebody(root, fp, firstbodyline) > File "/usr/local/mailman/pythonlib/email/Parser.py", line 206, in _parsebody > raise Errors.BoundaryError( > BoundaryError: No terminating boundary and no trailing empty line > > On Dec 21, 2012, at 12:55 PM, Mark Sapiro wrote: > >> Mark Sapiro wrote: >>> >>> Since the runner got this far, you should be able to see the actual >>> message via >>> >>> bin/show_qfiles qfiles/x/y.pck >>> >>> or >>> >>> bin/dumpdb qfiles/x/y.pck >>> >>> where x is the queue and y.pck is the entry. >> >> >> I forgot to add, and maybe it's obvious anyway, but once you find the >> offending queue entry, you can just remove it or move it aside. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >

2 1

log errors after restart
by Con Wieland 21 Dec '12

21 Dec '12

We recently had an electrical issue and had to shutdown our mailman server. It know is looping this log error. Seems like it mail be a malformed message but I am not sure how to clear it. Any ideas? thanks Con Wieland Office of Information Technology University of California at Irvine Dec 21 07:56:02 2012 (5770) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 100, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 164, in dequeue msg = email.message_from_string(msg, Message.Message) File "/usr/local/mailman/pythonlib/email/__init__.py", line 51, in message_from_string return Parser(_class, strict=strict).parsestr(s) File "/usr/local/mailman/pythonlib/email/Parser.py", line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File "/usr/local/mailman/pythonlib/email/Parser.py", line 64, in parse self._parsebody(root, fp, firstbodyline) File "/usr/local/mailman/pythonlib/email/Parser.py", line 240, in _parsebody msgobj = self.parsestr(part) File "/usr/local/mailman/pythonlib/email/Parser.py", line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File "/usr/local/mailman/pythonlib/email/Parser.py", line 64, in parse self._parsebody(root, fp, firstbodyline) File "/usr/local/mailman/pythonlib/email/Parser.py", line 265, in _parsebody msg = self.parse(fp) File "/usr/local/mailman/pythonlib/email/Parser.py", line 64, in parse self._parsebody(root, fp, firstbodyline) File "/usr/local/mailman/pythonlib/email/Parser.py", line 206, in _parsebody raise Errors.BoundaryError( BoundaryError: No terminating boundary and no trailing empty line

2 2

Re: [Mailman-Users] again postfix+aliases+virtual_domains
by ДП 19 Dec '12

19 Dec '12

Thank you all, good people, for help. One more little step made me closer to check a tick for that enormous task in my organizer. I got my list was recognized by my mail system. I`ve attached the correct mm_cfg. But. I can`t anymore start using that list because 1. mailman just becam very leery. 2. I can`t view mylist information, nor any pages with list info, admin, etc. So the behaviour is that - just after I send a letter - I receive, as admin, the approval request: "message need to be approved because contains a suspicious title". Then I confirm a message it`s going as expected to all addresses. But, when I send another one, mailman again very don`t like my letter. And again and again. And the main reason for me, to install the mailman - I want web-pages for people, so anybody can view and unsubscribe (or subscribe) the list if any. ====http://mail2.my-domain.com.ua/admindb/mylist Not Found The requested URL /admindb/mylist was not found on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. === I`ve attached output of the "config_list -o - mylist" command Also "list_members mylist" show me 4 addresses subscribed to em. Also I`ve attached the part of httpd-vhosts.conf Also, a global question, will webface of mailman work completely trough SSL? Again thank you for your advices. //DP

2 1

Simplified mailman installation setup for corporate internal list server
by Sriram Karra 18 Dec '12

18 Dec '12

Hi, I am exploring deploying a simple mailman setup for the small company I work at. By simplified I mean the following: 1. All users are authenticated already using a single sign on. No password should be required for any activity. 2. Any user should be able to create lists (only owners can administer lists). We will still have private and public lists. 3. A user on logon should be able to manage her subscriptions using a simple "on/off" click, without per-list passwords, or confirmation emails and stuff. Another way to put it is I want a "/mailman/userinfo" script in addition to the /mailman/listinfo interface. I am quite sure someone else has also thought of this sort of a deployment. Is there any code or customization sample I can look and explore. If no such instances are known, what do you think is the best way for me to start exploring my own implementation. I can hack a little python. Regards, Karra

1 1

(no subject)
by E Kogler 17 Dec '12

17 Dec '12

How are things? http://uaelaser.com/otro.html Mon, 17 Dec 2012 12:31:05

1 0

Re: [Mailman-Users] again postfix+aliases+virtual_domains
by ДП 16 Dec '12

16 Dec '12

On Sun, 16 Dec 2012 11:49:40 -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/16/2012 11:08 AM, ДП wrote: > > Thank you a lot for your responce. I`m not too strong in mail configurations - just all is working - and this is fine for me. > > > Do I understand correctly that you have made changes and now delivery of > mail to Mailman is working? No, I`ve just wrote, that postfix is working for me as expected, misregarding bugs in his configuration, that you pointed. Mailman is still not working. I though to start new changes in configuration my morning, with my fresh brain. Sorry for my English, it is not my native language. //D

1 0