Mailman-Developers July 2012

mailman-developers@python.org

19 participants
31 discussions

Exposing not advertised lists via nntp archiver

by Alexander Sulfrian

Hi, I have a conceptional problem: There are mailinglists with a pubic archive but that not be advertised by the server. The nntp archiver now have to supply a list of all available archives. If this list does not contain a mailing list, in most news clients you do not have a chance to subscribe to that group and read the posts. How to solve that? The only possibility I could think of uses the filter mechanism of the available newsgroups. The clients could supply a regexp like filter. I would implement a mechanism, that shows unadvertized lists with an archive only if the supplied filter is equal to the newsgroup name. Any other idea? Alex

9 years, 6 months

Re: [Mailman-Developers] [GSoC 2012] Metrics

by Stephen J. Turnbull

George Chatzisofroniou writes: > Author > > This model represents an author of the mailing list. It mostly keeps > track of the number of postings and number of threads started. It has > the following fields: > > - authorid – IntegerField AFAIK every Django object has an internal ID. Why do authors need a separate, human-unfriendly "authorid"? > - authormail – CharField Authors are people. They typically have names<wink/> and often multiple email addresses. There may also be other information (organization, etc) that is available from the headers. > - totalmails – IntegerField > - totalthreads – IntegerField > - firstmsgdate – DateTimeField > - lastmsgdate – DateTimeField > > MailingList > > This model counts the total number of postings and threads started. > > - totalmails – IntegerField > - totalthreads – IntegerField longestthread? > > Month > > Year > > Views > > To display the metrics the Django template system will be used. To > output the charts i will create some custom tags. The three following > views will be used: > > - General page – On top, there will be general metrics about total > authors, total mails and total threads and below three charts (AJAX > based) "AJAX based" doesn't belong in the spec; it's an implementation detail. > that represent number of posts per author, number of threads > per author and mailing list’s yearly usage. Even below there will be a > number of charts (equal to the number of years of list’s existence) > that output monthly usage. Why multiple charts? If you can afford a 640x480 chart area, with 4 pixel wide bars you can have 160 months > 13 years in one chart. I personally wouldn't hesitate to go to pixel width bars, which gives you > 53 years. I don't think people will be looking at charts for precision, but rather to get an overview. > At the end, there will be tabular data representing the authors > > - Author page – Each user will have his own page with his own metrics. > > Django Admin page – A ‘Generate’ button will be added to the Django admin page. > Settings > > The Django app should handle the following configuration parameters: > > - Host – Message store data host > - Port – Message store data port > - Masking – A multi-state variable (None, abbreviated, full) for > masking email addresses at the results (we don’t want the emails to be > spammed) (1) If at all possible, this should be inherited from the list configuration (DRY). It's not useful if the addresses are available from the archives or by subscribing to the list. (Actually, a really sophisticated spammer might want to attack by spoofing frequent posters on the assumption they're more trusted and more read, but that seems second-order to me.) (2) It would be preferable if authors could supply nicknames, full names, or avatars for this purpose. > Interface to the Mailman core > > - Metrics class > > - Generate class

9 years, 6 months

Re: [Mailman-Developers] URGENT: Google Summer of Code status report and code due

by Stephen J. Turnbull

Note: CC'ing Mailman Developers. I think this was private, so not trimming. At the bottom there's a discussion of the newsgroup naming scheme, which is an important bikeshed to paint. If you're not interested in a bunch of "me too" comments, skipp right on down there! Barry Warsaw writes: > Hi Alex. > > On Jun 28, 2012, at 02:00 AM, Alexander Sulfrian wrote: > > >Currently I am using twisted-news-11.0.0, but that just because it is > >the current stable version in gentoo. Debian contains twisted-10.1.0 > >in stable and twisted-12.0.0 in testing and unstable. I would use > >12.0.0 if you have no objections. Additional to that, I would like to > >continue to use the package manager version. This has the advantage > >that requisites are installed automatically. > > I think this is fine. We've got 11.1.0 in Ubuntu 12.04 and 12.0.0 > in Quantal. Debian Wheezy (now frozen) has 12.0.0. I can easily > spin up Debian or Gentoo instances (it's been *years* since I ran > Gentoo). Go with whichever of those will give you the easiest path > to success and we should be able to reproduce your environment. +1. I can also do both Debian and Gentoo easily. I would say stick to Gentoo for now. > >I already looked into the code examples, that comes with > >twisted-news. As far as I could see, twisted-news is manly an > >reactor-based server, that is doing some string parsing to handle > >the protocol. There are some sample back ends that use pickle > >files, the twisted dirdbm or the twisted DB-API. But for the > >project it should be necessary to write a custom back end. > > I expected a new backend might be necessary. Again, since this > isn't the most important part of the project, do only what's > necessary to show off the Mailman integration work. +1 > >My first intention would be to implement it like a runner. The > >lmtp runner is also an daemon. It could be implemented in a > >similar way. But the nntp archive daemon is not a runner in the > >first place. So it maybe would be better to put it under the > >archiving module. It could be implemented like a runner. It should > >be possible to configure it via the configuration file like the > >other modules, that are available. But I do not know where it is > >preferred to put it. > > Daemon/server control should be implemented as a runner, +1. Unless some showstopper crops up, I think all Mailman daemons should be controlled via runners. > but it can be pretty simple. The IRunner interface really just > needs to implement run() and stop() and even forking a subprocess > should be fairly easy to do. > > You have to worry about two things. First, you need a server to > vend the messages through NNTP. Second, you need some way to get > new messages into the twisted-news (or whatever) backend when they > show up on the mailing list. This is the part that you'll need an > IArchiver implementation for. Note that the only IArchiver method > you *must* implement is archive_message(). You'll have to figure > out whether you need the twisted-news server running or not for > that. IMO, make that *three* things. It ought to be possible to fire up the NNTP runner on an existing archive, and vend messages. I suppose this means a separate database for news properties like the message to message number mapping, and perhaps for newsgroup names. Newsgroup names are an issue here. It seems to me that (if not gateway'd to Usenet) they should be something like (pseudo-code) "mailman." + join(reverse(split(list-id,".")),".") Eg, this list would be "mailman.org.python.mailman-developers". I know that's considered ugly-out-the-wazoo, but these need to be UUIDs (consider mirrors), and mailman(a)python.org should not be in the same subtree as mailman(a)python.net (ie, mailman.net.python.mailman vs mailman.org.python.mailman not mailman.python.net.mailman vs mailman.python.org.mailman The top-level maybe shouldn't be "mailman", but rather something like "list-archive". Another issue with newsgroup names is that some lists *are* registered in the news hierarchy, so provision for such aliases should be allowed. Let the bikeshed-painting begin! > >The new code should be integrated into the existent test set. I know > >that a successful test is not sufficient, but it is a good > >start. Additionally to that, we should define some acceptance tests. > > +1 I was going to write something here, so remind me. (Must run off to torture would-be grad students.)

9 years, 6 months

Re: [Mailman-Developers] mailman3 instance for preview + exploration

by Florian Fuchs

Hi Jeff, I am not completely sure, but both the Traceback and the fact that it worked again after the restart seem to point in direction of the the django devserver. I'd love to help you setting up postorius with Apache/mod_wsgi if you like. That would be much more stable than the built-in server. Also, you'd have much more control over logging etc. Just email me if you'd like to do that. Florian Am 06.07.12 20:20, schrieb Jeff Marshall: > First, I restarted mailman3 and the error at > http://mailman3.jab.org:8000/persisted. Then I killed and restarted > postorius and the error cleared up. > The postorius instance is accessible again. > > > > Postorius output showed (I don't see a postorius output log file anywhere > so I don't know if I can pull up history farther back?): > > [04/Jul/2012 06:05:00] "GET / HTTP/1.1" 500 93610 > [04/Jul/2012 08:59:05] "GET / HTTP/1.1" 500 93655 > [04/Jul/2012 09:53:42] "GET / HTTP/1.0" 500 93553 > [04/Jul/2012 09:56:39] "GET / HTTP/1.1" 500 93838 > [04/Jul/2012 10:12:32] "GET / HTTP/1.1" 500 93775 > [04/Jul/2012 10:25:23] "GET / HTTP/1.1" 500 93655 > [04/Jul/2012 12:25:56] "GET / HTTP/1.1" 500 93583 > [04/Jul/2012 13:24:33] "GET / HTTP/1.1" 500 93443 > [04/Jul/2012 13:26:42] "GET / HTTP/1.1" 500 93443 > [04/Jul/2012 21:50:56] "GET /static/postorius/defaultimages/favicon.ico > HTTP/1.1" 404 1803 > [05/Jul/2012 05:39:37] "GET / HTTP/1.1" 500 93882 > Traceback (most recent call last): > File > "/usr/local/lib/python2.7/dist-packages/django/core/servers/basehttp.py", > line 284, in run > self.finish_response() > File > "/usr/local/lib/python2.7/dist-packages/django/core/servers/basehttp.py", > line 324, in finish_response > self.write(data) > File > "/usr/local/lib/python2.7/dist-packages/django/core/servers/basehttp.py", > line 420, in write > self._write(data) > File "/usr/lib/python2.7/socket.py", line 324, in write > self.flush() > File "/usr/lib/python2.7/socket.py", line 303, in flush > self._sock.sendall(view[write_offset:write_offset+buffer_size]) > error: [Errno 32] Broken pipe > ---------------------------------------- > Exception happened during processing of request from ('134.95.19.9', 26446) > Traceback (most recent call last): > File "/usr/lib/python2.7/SocketServer.py", line 284, in > _handle_request_noblock > self.process_request(request, client_address) > File "/usr/lib/python2.7/SocketServer.py", line 310, in process_request > self.finish_request(request, client_address) > File "/usr/lib/python2.7/SocketServer.py", line 323, in finish_request > self.RequestHandlerClass(request, client_address, self) > File > "/usr/local/lib/python2.7/dist-packages/django/core/servers/basehttp.py", > line 570, in __init__ > BaseHTTPRequestHandler.__init__(self, *args, **kwargs) > File "/usr/lib/python2.7/SocketServer.py", line 641, in __init__ > self.finish() > File "/usr/lib/python2.7/SocketServer.py", line 694, in finish > self.wfile.flush() > File "/usr/lib/python2.7/socket.py", line 303, in flush > self._sock.sendall(view[write_offset:write_offset+buffer_size]) > error: [Errno 32] Broken pipe > ---------------------------------------- > [05/Jul/2012 06:14:25] "GET / HTTP/1.1" 500 94198 > [05/Jul/2012 10:39:53] "GET / HTTP/1.1" 500 93559 > [05/Jul/2012 10:51:25] "GET / HTTP/1.1" 500 93882 > [05/Jul/2012 11:30:01] "GET / HTTP/1.1" 500 93538 > [05/Jul/2012 11:54:47] "GET / HTTP/1.1" 500 93655 > [05/Jul/2012 12:09:25] "GET / HTTP/1.1" 500 94323 > > > > And the mailman3 var/log/mailman.log looked like this throughout: > > Jul 04 01:17:37 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > third-list(a)mailman3.jab.org HTTP/1.1" 200 307 > Jul 04 01:17:37 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > third-list(a)mailman3.jab.org/config HTTP/1.1" 200 1647 > Jul 04 01:17:42 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > jablist(a)mailman3.jab.org HTTP/1.1" 200 295 > Jul 04 01:17:42 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > jablist(a)mailman3.jab.org HTTP/1.1" 200 295 > Jul 04 01:17:42 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > jablist(a)mailman3.jab.org/config HTTP/1.1" 200 1611 > Jul 04 01:17:48 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > public-test(a)mailman3.jab.org HTTP/1.1" 200 311 > Jul 04 01:17:48 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > public-test(a)mailman3.jab.org HTTP/1.1" 200 311 > Jul 04 01:17:48 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > public-test(a)mailman3.jab.org/config HTTP/1.1" 200 1634 > Jul 04 01:17:52 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > third-list(a)mailman3.jab.org HTTP/1.1" 200 307 > Jul 04 01:17:52 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > third-list(a)mailman3.jab.org HTTP/1.1" 200 307 > Jul 04 01:17:52 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > third-list(a)mailman3.jab.org/config HTTP/1.1" 200 1647 > Jul 04 01:17:55 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > third-list(a)mailman3.jab.org HTTP/1.1" 200 307 > Jul 04 01:17:55 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > third-list(a)mailman3.jab.org HTTP/1.1" 200 307 > Jul 04 01:17:55 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > third-list(a)mailman3.jab.org/held HTTP/1.1" 200 90 > Jul 04 01:17:58 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > third-list(a)mailman3.jab.org HTTP/1.1" 200 307 > Jul 04 01:17:58 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ > third-list(a)mailman3.jab.org HTTP/1.1" 200 307 > Jul 06 18:08:19 2012 (10046) Master watcher caught SIGTERM. Exiting. > Jul 06 18:08:20 2012 (10052) IncomingRunner runner caught SIGTERM. > Stopping. > Jul 06 18:08:20 2012 (10053) DigestRunner runner caught SIGTERM. Stopping. > Jul 06 18:08:20 2012 (10051) NewsRunner runner caught SIGTERM. Stopping. > Jul 06 18:08:20 2012 (10053) DigestRunner runner exiting. > Jul 06 18:08:20 2012 (10051) NewsRunner runner exiting. > > That's me stopping mailman on Jul 06 18:08. Nothing in the mailman3 log > showing any errors anywhere. > > Please let me know if there is other data I can pull out for you. > > Thanks > > Jeff > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/f%40state-of-mind… > > Security Policy: http://wiki.list.org/x/QIA9 >

9 years, 6 months

Re: [Mailman-Developers] GSoC midterm evaluations start Monday July 9th!

by Alexander Sulfrian

Hi, sorry for delaying my report until now, but I just wanted to finish some basic parts. So now here comes my summary what I have done during the past weeks: After the first steps of checking out a copy of Mailman 3 and Twisted, building it and executing the test suites, I started with a install of Mailman 3, to get a public test system. My Mailman 3 instance is public available [1] and is working after first tests. Additional to that, I created a blog post describing the setup and the difficulties I encountered during the installation[2]. After that I read some main parts of the NNTP RFC (RFC3977[3]) and identified major problems with the twisted nntp module. Apart from the missing documentation there are some problems, that were discussed recently on the mailing list. So I decided to write my own implementation of the NNTP protocol based on asyncore. I recently pushed a basic runner, protocol parser and handler to my personal mailman branch[4]. I also created some basic unit tests, that could be executed for example with "bin/test -m mailman.archiving.nntp". I also reviewed the posts about different archiving backends from the mailing list. I think that KittyStore as proposed, should be sufficient to access the stored mails by the NNTP daemon. But the daemon needs to keep additional information in its on database. It should be possible to use the database of the mailman backend for that purpose. The next steps in the next few days, would be the identification and basic implementation if the required NNTP commands. Basic browsing of available lists should be possible until tomorrow. The required configuration options in the backend, the required REST API changes and the required changes in Postorius would be the next step afterwards. Thanks, Alex 1: http://mailman3.animux.de/ 2: http://blog.animux.de/mailman-3-installation.html 3: http://tools.ietf.org/html/rfc3977 4: https://code.launchpad.net/~alexander-sd4c/mailman/mailman

9 years, 6 months

Re: [Mailman-Developers] Adding a new list attribute

by Danci Emanuel

Indeed, I added these values to the tables, so now they should be fine. Still, now I am facing another problem. Although I suspected that in the get_configuration() is the problem, now I cannot debug that because now I get a new error. After adding the dlists_enabled field to the tables and restaring mailman, when I try to access the Postorius server on localhost:8000 I get the HTTP Error 500: HTTP Error 500: A server error occurred. Please contact the administrator. and is what shows up in the terminal when I try to access Postorious: root@zalman:/usr/local/mm3/mailman# Traceback (most recent call last): File "/usr/lib/python2.6/wsgiref/handlers.py", line 93, in run self.result = application(self.environ, self.start_response) File "/usr/local/mm3/mailman/src/mailman/database/transaction.py", line 60, in wrapper rtn = function(*args, **kws) File "/usr/local/mm3/mailman/src/mailman/rest/wsgiapp.py", line 59, in __call__ environ, start_response) File "/usr/local/mm3/mailman/eggs/restish-0.12.1-py2.6.egg/restish/app.py", line 18, in __call__ response = self.get_response(request, resource_or_response) File "/usr/local/mm3/mailman/eggs/restish-0.12.1-py2.6.egg/restish/app.py", line 65, in get_response resource_or_response = resource_or_response(request) File "/usr/local/mm3/mailman/eggs/restish-0.12.1-py2.6.egg/restish/resource.py", line 212, in __call__ return _dispatch(request, match, lambda r: callable(self, r)) File "/usr/local/mm3/mailman/eggs/restish-0.12.1-py2.6.egg/restish/resource.py", line 243, in _dispatch response = func(request) File "/usr/local/mm3/mailman/eggs/restish-0.12.1-py2.6.egg/restish/resource.py", line 212, in <lambda> return _dispatch(request, match, lambda r: callable(self, r)) File "/usr/local/mm3/mailman/src/mailman/rest/lists.py", line 202, in collection resource = self._make_collection(request) File "/usr/local/mm3/mailman/src/mailman/rest/helpers.py", line 140, in _make_collection collection = self._get_collection(request) File "/usr/local/mm3/mailman/src/mailman/rest/lists.py", line 119, in _get_collection return list(getUtility(IListManager)) File "/usr/local/mm3/mailman/src/mailman/model/listmanager.py", line 90, in __iter__ for mlist in store.find(MailingList): File "/usr/local/mm3/mailman/eggs/storm-0.19-py2.6-linux-i686.egg/storm/store.py", line 978, in __iter__ result = self._store._connection.execute(self._get_select()) File "/usr/local/mm3/mailman/eggs/storm-0.19-py2.6-linux-i686.egg/storm/database.py", line 238, in execute raw_cursor = self.raw_execute(statement, params) File "/usr/local/mm3/mailman/eggs/storm-0.19-py2.6-linux-i686.egg/storm/databases/sqlite.py", line 154, in raw_execute return Connection.raw_execute(self, statement, params) File "/usr/local/mm3/mailman/eggs/storm-0.19-py2.6-linux-i686.egg/storm/database.py", line 322, in raw_execute self._check_disconnect(raw_cursor.execute, *args) File "/usr/local/mm3/mailman/eggs/storm-0.19-py2.6-linux-i686.egg/storm/database.py", line 371, in _check_disconnect return function(*args, **kwargs) OperationalError: no such column: mailinglist.dlists_enabled Indeed, is a pretty intuitive error but still, I did not manage to find the proper solution. Thanks for your help and sorry for bugging you with so many questions, but I really want to make this work as it should. :) Thanks again, Emanuel ________________________________ From: Danci Emanuel <danci_emanuel(a)yahoo.com> To: "danci_emanuel(a)yahoo.com" <danci_emanuel(a)yahoo.com> Sent: Monday, July 2, 2012 11:45 PM Subject: asd On Jul 01, 2012, at 02:54 PM, Danci Emanuel wrote: >Secondly, I tried to modify the list attributes by adding the following: >>dlists_enabled = Attribute("""Is the Dynamic sublist feature enabled?""") - >"IMailingList" interface (/interfaces/mailinglist.py) dlists_enabled = Bool() >- "MailingList" class (/model/mailinglist.py) If you want this value to persist, it must also be added to the SQL tables, e.g. sqlite.sql and/or postgres.sql. This will make your schema incompatible with upstream Mailman, and there will be a better way to extend the default schema in the future, but for now, this should be enough to get you going again. Of course, it's not necessary to store your data in the primary database. Once you've got a REST API for your stuff, you can really map this to any backend storage you want. >dlists_enabled = GetterSetter(as_boolean) - to the ATTRIBUTES dict from >/rest/configuration.py >>mlist.dlists_enabled = True - in the "apply" method from "DefaultStyle" class >(/styles/default.py) >>Obviously I did something wrong, or I did not add all the necessary changes >because when I try to create a new lists that has the dlists feature enabled, >I get the HTTP Error 400: >>HTTP Error 400: Unknown attribute: dlists_enabled That error gets thrown on line 233 of configuration.py and it only happens if the attribute name isn't found in ATTRIBUTES. Probably the best way to debug this is to set a break point in get_configuration() and step through it when self._attribute == 'dlist_enabled'. Cheers, -Barry Emanuel DANCI

9 years, 6 months

[GSoC 2012] HyperKitty

by Aamir Khan

Hi, It has been some time since the last update about HyperKitty. I have deployed[1] the latest code at mm3test.fedoraproject.org for everyone to take a look. Please file any bugs/missing features here[2] HyperKitty offer features like upvoting/downvoting of messages, adding tags (to be implemented soon!) to threads, user profiles and other user specific features. We require users to be logged in before using any of these features. So, the first task for my GSoC project was to implement login procedure for hyperkitty. It uses django-social-auth application [3] to implement login functionality. Currently, there are four ways of logging into hyperkitty test server namely, Google openid, yahoo openid, browserid, and registering the user on the site itself. I have not enabled other ways of logging in (e.g, twitter) but it should be fairly easy to enable those. I have written a blog post about the essential features an archiver should posses[4] in my opinion. The second most important thing for me is the ability to promote good content posted on the list. An archiver should be intelligent enough to suppress the "spamy" content and bring good content on the surface. For this we have implemented a feature in which a user can upvote/downvote a message. The users accessing a particular thread will be able to sort the messages based on votes of other users. I have also implemented the basic user profiles in which you can see your personal info and the messages you rated. You will be able to edit the user profiles soon. I have also started to write unit tests [5]. Best regards, Aamir [1] http://blog.aamirkhan.co.in/post/26723715431/deploying-hyperkitty-using-apa… [2] https://fedorahosted.org/hyperkitty/ [3] https://github.com/omab/django-social-auth [4] http://blog.aamirkhan.co.in/post/26555164201/hyperkitty-modern-archiver [5] http://blog.aamirkhan.co.in/post/26723628968/unit-testing-hyperkitty

9 years, 6 months

Re: [Mailman-Developers] mailman3 instance for preview + exploration

by Barry Warsaw

On Jul 06, 2012, at 11:20 AM, Jeff Marshall wrote: >First, I restarted mailman3 and the error at >http://mailman3.jab.org:8000/persisted. Then I killed and restarted >postorius and the error cleared up. > The postorius instance is accessible again. Thanks Jeff; so it does look like a bug in Postorius and not the core. -Barry

9 years, 6 months

Re: [Mailman-Developers] mailman3 instance for preview + exploration

by Jeff Marshall

First, I restarted mailman3 and the error at http://mailman3.jab.org:8000/persisted. Then I killed and restarted postorius and the error cleared up. The postorius instance is accessible again. Postorius output showed (I don't see a postorius output log file anywhere so I don't know if I can pull up history farther back?): [04/Jul/2012 06:05:00] "GET / HTTP/1.1" 500 93610 [04/Jul/2012 08:59:05] "GET / HTTP/1.1" 500 93655 [04/Jul/2012 09:53:42] "GET / HTTP/1.0" 500 93553 [04/Jul/2012 09:56:39] "GET / HTTP/1.1" 500 93838 [04/Jul/2012 10:12:32] "GET / HTTP/1.1" 500 93775 [04/Jul/2012 10:25:23] "GET / HTTP/1.1" 500 93655 [04/Jul/2012 12:25:56] "GET / HTTP/1.1" 500 93583 [04/Jul/2012 13:24:33] "GET / HTTP/1.1" 500 93443 [04/Jul/2012 13:26:42] "GET / HTTP/1.1" 500 93443 [04/Jul/2012 21:50:56] "GET /static/postorius/defaultimages/favicon.ico HTTP/1.1" 404 1803 [05/Jul/2012 05:39:37] "GET / HTTP/1.1" 500 93882 Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/django/core/servers/basehttp.py", line 284, in run self.finish_response() File "/usr/local/lib/python2.7/dist-packages/django/core/servers/basehttp.py", line 324, in finish_response self.write(data) File "/usr/local/lib/python2.7/dist-packages/django/core/servers/basehttp.py", line 420, in write self._write(data) File "/usr/lib/python2.7/socket.py", line 324, in write self.flush() File "/usr/lib/python2.7/socket.py", line 303, in flush self._sock.sendall(view[write_offset:write_offset+buffer_size]) error: [Errno 32] Broken pipe ---------------------------------------- Exception happened during processing of request from ('134.95.19.9', 26446) Traceback (most recent call last): File "/usr/lib/python2.7/SocketServer.py", line 284, in _handle_request_noblock self.process_request(request, client_address) File "/usr/lib/python2.7/SocketServer.py", line 310, in process_request self.finish_request(request, client_address) File "/usr/lib/python2.7/SocketServer.py", line 323, in finish_request self.RequestHandlerClass(request, client_address, self) File "/usr/local/lib/python2.7/dist-packages/django/core/servers/basehttp.py", line 570, in __init__ BaseHTTPRequestHandler.__init__(self, *args, **kwargs) File "/usr/lib/python2.7/SocketServer.py", line 641, in __init__ self.finish() File "/usr/lib/python2.7/SocketServer.py", line 694, in finish self.wfile.flush() File "/usr/lib/python2.7/socket.py", line 303, in flush self._sock.sendall(view[write_offset:write_offset+buffer_size]) error: [Errno 32] Broken pipe ---------------------------------------- [05/Jul/2012 06:14:25] "GET / HTTP/1.1" 500 94198 [05/Jul/2012 10:39:53] "GET / HTTP/1.1" 500 93559 [05/Jul/2012 10:51:25] "GET / HTTP/1.1" 500 93882 [05/Jul/2012 11:30:01] "GET / HTTP/1.1" 500 93538 [05/Jul/2012 11:54:47] "GET / HTTP/1.1" 500 93655 [05/Jul/2012 12:09:25] "GET / HTTP/1.1" 500 94323 And the mailman3 var/log/mailman.log looked like this throughout: Jul 04 01:17:37 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ third-list(a)mailman3.jab.org HTTP/1.1" 200 307 Jul 04 01:17:37 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ third-list(a)mailman3.jab.org/config HTTP/1.1" 200 1647 Jul 04 01:17:42 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ jablist(a)mailman3.jab.org HTTP/1.1" 200 295 Jul 04 01:17:42 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ jablist(a)mailman3.jab.org HTTP/1.1" 200 295 Jul 04 01:17:42 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ jablist(a)mailman3.jab.org/config HTTP/1.1" 200 1611 Jul 04 01:17:48 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ public-test(a)mailman3.jab.org HTTP/1.1" 200 311 Jul 04 01:17:48 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ public-test(a)mailman3.jab.org HTTP/1.1" 200 311 Jul 04 01:17:48 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ public-test(a)mailman3.jab.org/config HTTP/1.1" 200 1634 Jul 04 01:17:52 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ third-list(a)mailman3.jab.org HTTP/1.1" 200 307 Jul 04 01:17:52 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ third-list(a)mailman3.jab.org HTTP/1.1" 200 307 Jul 04 01:17:52 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ third-list(a)mailman3.jab.org/config HTTP/1.1" 200 1647 Jul 04 01:17:55 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ third-list(a)mailman3.jab.org HTTP/1.1" 200 307 Jul 04 01:17:55 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ third-list(a)mailman3.jab.org HTTP/1.1" 200 307 Jul 04 01:17:55 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ third-list(a)mailman3.jab.org/held HTTP/1.1" 200 90 Jul 04 01:17:58 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ third-list(a)mailman3.jab.org HTTP/1.1" 200 307 Jul 04 01:17:58 2012 (10058) mailman3.jab.org - - "GET /3.0/lists/ third-list(a)mailman3.jab.org HTTP/1.1" 200 307 Jul 06 18:08:19 2012 (10046) Master watcher caught SIGTERM. Exiting. Jul 06 18:08:20 2012 (10052) IncomingRunner runner caught SIGTERM. Stopping. Jul 06 18:08:20 2012 (10053) DigestRunner runner caught SIGTERM. Stopping. Jul 06 18:08:20 2012 (10051) NewsRunner runner caught SIGTERM. Stopping. Jul 06 18:08:20 2012 (10053) DigestRunner runner exiting. Jul 06 18:08:20 2012 (10051) NewsRunner runner exiting. That's me stopping mailman on Jul 06 18:08. Nothing in the mailman3 log showing any errors anywhere. Please let me know if there is other data I can pull out for you. Thanks Jeff

9 years, 6 months

Re: [Mailman-Developers] [Bug 1020683] Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other).

by Richard Wackerbarth

On Jul 5, 2012, at 2:48 PM, Robert Arlt Jr. wrote: > I can as well. In my view of the issue I believe that allowing everyone > on listB to submit is the better option as I can easily make a list > composed of those allowed to send unmoderated to listB, call it listB2 > and add listB2 to listB then use listB2 as the list allowed to send to > listA (all of this assuming recursion is implemented). But that would be confusing to the members of listB. They would have to realize that they are not really a member of listB, but that they are actually a member of listB2. So, if you are going to do that, and perhaps for any inclusion that is transparent on message delivery, an attempt to change delivery preferences on listA should take the user to the listB2 preferences. However, if the delivery of listA is done by publishing a copy of the message on listB, then, for the purpose of preferences, the listB user should not be considered a member of listA.

9 years, 6 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

Mailman-Developers July 2012