From barry at list.org Sat May 2 03:39:54 2015 From: barry at list.org (Barry Warsaw) Date: Fri, 1 May 2015 21:39:54 -0400 Subject: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation In-Reply-To: <5541A727.7000907@msapiro.net> References: <553FE3BF.10203@hamaralinux.org> <20150428190310.225615af@limelight.wooz.org> <3d3101d0828d$9dab1920$d9014b60$@emwd.com> <45d001d082ba$b97ded30$2c79c790$@emwd.com> <55418898.80703@msapiro.net> <4acb01d082f8$1466dc10$3d349430$@emwd.com> <5541A727.7000907@msapiro.net> Message-ID: <20150501213954.34558fae@anarchist.wooz.org> On Apr 29, 2015, at 08:53 PM, Mark Sapiro wrote: >That's wrong. I was conflating Mailman and Python Releases. Mailman 3.0 >nominally requires Python 2.7 and Python 3.4. It may run with earlier >Python 3.x releases, but no guarantees and probably not as old as 3.0 or >even 3.1 in any case. Nobody should be using Python 3 earlier than 3.2 for *anything* :), but the core probably will not work on Pythons earlier than 3.4. I haven't tested it, but I suspect we're using some newer standard library modules. As we go forward, I hope we'll get some CI in place. Even after Python 3.5 is released I'd like to support 3.4 as a minimum version. Cheers, -Barry From terri at toybox.ca Mon May 4 10:11:58 2015 From: terri at toybox.ca (Terri Oda) Date: Mon, 04 May 2015 01:11:58 -0700 Subject: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation In-Reply-To: <4acb01d082f8$1466dc10$3d349430$@emwd.com> References: <553FE3BF.10203@hamaralinux.org> <20150428190310.225615af@limelight.wooz.org> <3d3101d0828d$9dab1920$d9014b60$@emwd.com> <45d001d082ba$b97ded30$2c79c790$@emwd.com> <55418898.80703@msapiro.net> <4acb01d082f8$1466dc10$3d349430$@emwd.com> Message-ID: <554729CE.8090905@toybox.ca> >>> Is there a recommended server environment to run Mailman 3? >> It should install and run on any *nix server that supports both Python >> 2.7 and Python 3.0, an MTA capable of LMTP delivery to Mailman >> (currently configurations for Postfix and Exim are provided) and a web >> server compatible with Django. In addition to what Mark said: I know we've tested it on Fedora (20 and 22, I think?) and I have a script for docker install that uses Ubuntu 14.04 that may work for other apt-based systems. Incidentally, if anyone's interested in doing packaging for the Mailman 3.0 Suite pieces for some common distributions, I think that would be really awesome. Terri From barry at list.org Tue May 5 02:07:57 2015 From: barry at list.org (Barry Warsaw) Date: Mon, 4 May 2015 20:07:57 -0400 Subject: [Mailman-Developers] Please consider donating to the GNU Mailman project Message-ID: <20150504200757.546be47a@anarchist.wooz.org> I should have included this in our release announcement. I'd like to remind everyone that GNU Mailman has a directed donation fund set up at the Free Software Foundation. Please consider donating! http://wiki.list.org/x/4816967 This year, we used a portion of our fund to sponsor Abhilash coming to PyCon 2015. Abhilash has been a core developer since his participation in GSoC, and has proven himself to be indispensable across a wide range of the project. We were beyond happy to be able to meet him in person and work with him over the course of the sprints, and we reached the 3.0 release in large part because of his participation at the sprints. Your donations can help with future sprints, user testing, hosting, and more. We're a small team of volunteers and every dollar can help. A portion of your donation also goes to the Free Software Foundation, so you can help two great organizations with one donation. Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From barry at list.org Tue May 5 02:16:42 2015 From: barry at list.org (Barry Warsaw) Date: Mon, 4 May 2015 20:16:42 -0400 Subject: [Mailman-Developers] Moving to git and gitlab Message-ID: <20150504201642.2d0a9e17@anarchist.wooz.org> With the release of Mailman 3.0, it's time to take a look at our project management, with an eye toward making it easier for core developers, easier for non-core contributors, and providing improved quality, all while staying true to the GNU project's principles. There's a lot to like about Bazaar, and it's served us well over the years, but it's also pretty clear that this round of version control systems has been won by git. We have converted the Core's vcs to git, and will soon convert Postorius and mailman.client. HyperKitty is already managed under git. There's a lot to like about Launchpad. It's free software, and it has some nice features, including one of my favorites: bug tasks, which allow us to report a bug affecting more than one project or series, and track each task as it's resolved. Launchpad has even announced git support: http://blog.launchpad.net/general/git-code-hosting-beta There are also reasons why we might want to move off of Launchpad. Most compelling is that Launchpad is difficult or impossible to use for code hosting by our Indian colleagues. We have therefore decided to move to Gitlab. The Core is now hosted here: https://gitlab.com/mailman/mailman Postorius and mailman.client will follow after Florian has had some time to work through the existing Launchpad merge proposals. HyperKitty may move at some point soon. We currently have no plans to move any hosting of Mailman 2.1. For now, its code will continue to live in Bazaar on Launchpad, its bugs will continue to be managed on Launchpad, as will merge proposals. Q: What about the existing lp:mailman Bazaar branch? A: Let's leave it there for now, effectively keeping it around read-only. Q: What about existing LP bugs for Mailman 3? A: Abhilash is working on transferring them to Gitlab. It won't be a perfect conversions since we can't match users on the two systems, but if/when we do transfer them, we'll keep a link to the LP bug report in the Gitlab issue. We will only be moving the bugs tagged 'mailman3' on LP. If you own a Mailman 3 bug on Launchpad, feel free to close it there and open a new one on Gitlab. In the meantime, or if the transfer doesn't work well enough, we'll just close bugs on LP as we fix them. Please report all new bugs on Gitlab. Q: What about existing LP merge proposals? A: These are much tougher to transfer. If you have an open merge proposal on LP, feel free to update it to the latest git head and submit a new merge request on Gitlab. If you do, please close your mp on LP. In the meantime, I'll work my way through the existing LP merge proposals, applying diffs by hand if necessary. Q: What about CI? A: This is definitely one of the exciting features of Gitlab we're eager to start using. Our plans are to requisition a VM from python.org and set up CI on it. I'd like for us to never commit directly to the official project branches. Q: Why Gitlab and not Github or Bitbucket? A: Gitlab has an edition that is free software. If for some reason we have to leave gitlab.com, we could potentially stand up our own Gitlab and have an easier time transferring our projects to it. Plus we have to be a *little* different don't we? :) Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From himbeere at meine-oma.de Tue May 5 09:53:03 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Tue, 05 May 2015 09:53:03 +0200 Subject: [Mailman-Developers] python error when try to save a setting Message-ID: <554876DF.4030401@meine-oma.de> Hello. When i try to save a setting --schnipp-- Settings / Message Acceptance Default action to take when a member posts to the list ---> Accept --schnapp-- via pistorius i get: UnboundLocalError at /mailman3/lists/hoppla.domain/settings/message_acceptance local variable 'HTTPError' referenced before assignment Request Method: POST Request URL: http://127.0.0.1:8000/mailman3/lists/hoppla.domain/settings/message_acceptance Django Version: 1.7.8 Exception Type: UnboundLocalError Exception Value: local variable 'HTTPError' referenced before assignment Exception Location: /var/www/mailman/eggs/postorius-1.0.1-py2.7.egg/postorius/views/list.py in list_settings, line 787 Python Executable: /var/www/mailman/venv/bin/python2.7 Python Version: 2.7.9 Python Path: ['/var/www/mailman/eggs/Django-1.7.8-py2.7.egg', '/var/www/mailman/eggs/postorius-1.0.1-py2.7.egg', '/var/www/mailman/eggs/HyperKitty-1.0.0-py2.7.egg', '/var/www/mailman/eggs/Whoosh-2.7.0-py2.7.egg', '/var/www/mailman/eggs/mock-1.0.1-py2.7.egg', '/var/www/mailman/eggs/beautifulsoup4-4.3.2-py2.7.egg', '/var/www/mailman/eggs/djangorecipe-1.11-py2.7.egg', '/var/www/mailman/eggs/zc.recipe.egg-2.0.1-py2.7.egg', '/var/www/mailman/venv/lib/python2.7/site-packages', '/var/www/mailman/eggs/numpy-1.9.2-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/lockfile-0.10.2-py2.7.egg', '/var/www/mailman/eggs/django_extensions-1.5.2-py2.7.egg', '/var/www/mailman/eggs/django_haystack-2.3.1-py2.7.egg', '/var/www/mailman/eggs/enum34-1.0.4-py2.7.egg', '/var/www/mailman/eggs/networkx-1.9.1-py2.7.egg', '/var/www/mailman/eggs/python_dateutil-1.5-py2.7.egg', '/var/www/mailman/eggs/mailmanclient-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_browserid-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_compressor-1.5-py2.7.egg', '/var/www/mailman/eggs/django_paintstore-0.2-py2.7.egg', '/var/www/mailman/eggs/pytz-2015.2-py2.7.egg', '/var/www/mailman/eggs/robot_detection-0.3-py2.7.egg', '/var/www/mailman/eggs/cssmin-0.2.0-py2.7.egg', '/var/www/mailman/eggs/rjsmin-1.0.10-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/django_crispy_forms-1.4.0-py2.7.egg', '/var/www/mailman/eggs/djangorestframework-3.1.1-py2.7.egg', '/var/www/mailman/eggs/python_social_auth-0.2.7-py2.7.egg', '/var/www/mailman/eggs/django_gravatar2-1.3.0-py2.7.egg', '/var/www/mailman/eggs/six-1.9.0-py2.7.egg', '/var/www/mailman/eggs/decorator-3.4.2-py2.7.egg', '/var/www/mailman/eggs/httplib2-0.9.1-py2.7.egg', '/var/www/mailman/eggs/requests-2.6.2-py2.7.egg', '/var/www/mailman/eggs/django_appconf-1.0.1-py2.7.egg', '/var/www/mailman/eggs/PyJWT-1.1.0-py2.7.egg', '/var/www/mailman/eggs/requests_oauthlib-0.4.2-py2.7.egg', '/var/www/mailman/eggs/oauthlib-0.7.2-py2.7.egg', '/var/www/mailman/eggs/python_openid-2.2.5-py2.7.egg', '/var/www/mailman', '/var/www/mailman/bin', '/var/www/mailman/venv/lib64/python27.zip', '/var/www/mailman/venv/lib64/python2.7', '/var/www/mailman/venv/lib64/python2.7/plat-linux2', '/var/www/mailman/venv/lib64/python2.7/lib-tk', '/var/www/mailman/venv/lib64/python2.7/lib-old', '/var/www/mailman/venv/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7', '/usr/lib/python2.7/plat-linux2'] How can i repair this? Thanks and cheers t. From himbeere at meine-oma.de Tue May 5 09:53:34 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Tue, 05 May 2015 09:53:34 +0200 Subject: [Mailman-Developers] error when trying to register via hyperkitty Message-ID: <554876FE.9070006@meine-oma.de> Hello. When i try to signup via hyperkitty i get: KeyError at /archives/accounts/register/ 'email' Request Method: POST Request URL: http://127.0.0.1:8000/archives/accounts/register/?next=/archives/ Django Version: 1.7.8 Exception Type: KeyError Exception Value: 'email' Exception Location: /var/www/mailman/eggs/HyperKitty-1.0.0-py2.7.egg/hyperkitty/views/forms.py in clean_username, line 57 Python Executable: /var/www/mailman/venv/bin/python2.7 Python Version: 2.7.9 Python Path: ['/var/www/mailman/eggs/Django-1.7.8-py2.7.egg', '/var/www/mailman/eggs/postorius-1.0.1-py2.7.egg', '/var/www/mailman/eggs/HyperKitty-1.0.0-py2.7.egg', '/var/www/mailman/eggs/Whoosh-2.7.0-py2.7.egg', '/var/www/mailman/eggs/mock-1.0.1-py2.7.egg', '/var/www/mailman/eggs/beautifulsoup4-4.3.2-py2.7.egg', '/var/www/mailman/eggs/djangorecipe-1.11-py2.7.egg', '/var/www/mailman/eggs/zc.recipe.egg-2.0.1-py2.7.egg', '/var/www/mailman/venv/lib/python2.7/site-packages', '/var/www/mailman/eggs/numpy-1.9.2-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/lockfile-0.10.2-py2.7.egg', '/var/www/mailman/eggs/django_extensions-1.5.2-py2.7.egg', '/var/www/mailman/eggs/django_haystack-2.3.1-py2.7.egg', '/var/www/mailman/eggs/enum34-1.0.4-py2.7.egg', '/var/www/mailman/eggs/networkx-1.9.1-py2.7.egg', '/var/www/mailman/eggs/python_dateutil-1.5-py2.7.egg', '/var/www/mailman/eggs/mailmanclient-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_browserid-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_compressor-1.5-py2.7.egg', '/var/www/mailman/eggs/django_paintstore-0.2-py2.7.egg', '/var/www/mailman/eggs/pytz-2015.2-py2.7.egg', '/var/www/mailman/eggs/robot_detection-0.3-py2.7.egg', '/var/www/mailman/eggs/cssmin-0.2.0-py2.7.egg', '/var/www/mailman/eggs/rjsmin-1.0.10-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/django_crispy_forms-1.4.0-py2.7.egg', '/var/www/mailman/eggs/djangorestframework-3.1.1-py2.7.egg', '/var/www/mailman/eggs/python_social_auth-0.2.7-py2.7.egg', '/var/www/mailman/eggs/django_gravatar2-1.3.0-py2.7.egg', '/var/www/mailman/eggs/six-1.9.0-py2.7.egg', '/var/www/mailman/eggs/decorator-3.4.2-py2.7.egg', '/var/www/mailman/eggs/httplib2-0.9.1-py2.7.egg', '/var/www/mailman/eggs/requests-2.6.2-py2.7.egg', '/var/www/mailman/eggs/django_appconf-1.0.1-py2.7.egg', '/var/www/mailman/eggs/PyJWT-1.1.0-py2.7.egg', '/var/www/mailman/eggs/requests_oauthlib-0.4.2-py2.7.egg', '/var/www/mailman/eggs/oauthlib-0.7.2-py2.7.egg', '/var/www/mailman/eggs/python_openid-2.2.5-py2.7.egg', '/var/www/mailman', '/var/www/mailman/bin', '/var/www/mailman/venv/lib64/python27.zip', '/var/www/mailman/venv/lib64/python2.7', '/var/www/mailman/venv/lib64/python2.7/plat-linux2', '/var/www/mailman/venv/lib64/python2.7/lib-tk', '/var/www/mailman/venv/lib64/python2.7/lib-old', '/var/www/mailman/venv/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7', '/usr/lib/python2.7/plat-linux2'] I used no special characters for username and email. Any ideas? ciao t. From aurelien at bompard.org Wed May 6 09:58:08 2015 From: aurelien at bompard.org (Aurelien Bompard) Date: Wed, 6 May 2015 09:58:08 +0200 Subject: [Mailman-Developers] error when trying to register via hyperkitty In-Reply-To: <554876FE.9070006@meine-oma.de> References: <554876FE.9070006@meine-oma.de> Message-ID: Hello, and thanks for your report. > When i try to signup via hyperkitty i get: Using the internal auth/registration system isn't really tested & supported, it's better to use the Persona button. However, that's a real bug and I just pushed a commit to fix it: https://github.com/hyperkitty/hyperkitty/commit/1068b3f04faed99a16521c75c13232698208e338 Thanks for reporting! Aur?lien From f at florianfuchs.com Wed May 6 18:40:04 2015 From: f at florianfuchs.com (Florian Fuchs) Date: Wed, 6 May 2015 18:40:04 +0200 Subject: [Mailman-Developers] python error when try to save a setting In-Reply-To: <554876DF.4030401@meine-oma.de> References: <554876DF.4030401@meine-oma.de> Message-ID: <20150506164004.GA10681@soc2> On Tue, May 05, 2015 at 09:53:03AM +0200, Thomas Stein wrote: >Hello. > >When i try to save a setting > >--schnipp-- >Settings / Message Acceptance > >Default action to take when a member posts to the list ---> Accept The list of acceptable aliases isn't handled properly. I am working on a fix. As a work-around (if you don't need to define acceptable aliases), you can empty the acceptable aliases form field before submitting the form. Florian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: From rini17 at gmail.com Thu May 7 22:51:30 2015 From: rini17 at gmail.com (Juraj Variny) Date: Thu, 07 May 2015 22:51:30 +0200 Subject: [Mailman-Developers] Storing extra data during pipeline processing Message-ID: <8046717.sbI3iWB512@bluesky> Hello, I am adapting the GPG patch for mailman 2.1.x for our project and want to gather some related data in Approve and Scrubber handlers and use them in the archiver. Can you please advise me how to attach some metadata to a message to use it in later stages? Also noticed Scrubber being called multiple times per message (from normal pipeline, from digester, from archiver). I want to verify GPG signatures of the attachments in scrubber and redoing it multiple time is wasteful of system resources, I want to attach some metadata after the first checking to prevent it, too. I have tried already to use msgdata parameter or adding headers to message itself, but was not successful so far. I was thinking about adding external database and putting the data there by message ID, but sure there must be a better way? I hope to publish the code some day, too. Juraj From barry at list.org Thu May 7 22:59:05 2015 From: barry at list.org (Barry Warsaw) Date: Thu, 7 May 2015 16:59:05 -0400 Subject: [Mailman-Developers] Storing extra data during pipeline processing In-Reply-To: <8046717.sbI3iWB512@bluesky> References: <8046717.sbI3iWB512@bluesky> Message-ID: <20150507165905.0480da91@limelight.wooz.org> On May 07, 2015, at 10:51 PM, Juraj Variny wrote: >I have tried already to use msgdata parameter or adding headers to message >itself, but was not successful so far. I was thinking about adding external >database and putting the data there by message ID, but sure there must be a >better way? I hope to publish the code some day, too. Can you give some details on what didn't work about using the msgdata parameter? This always flows with the message through the pipeline and is preserved in the pickle files as the message moves from runner to runner. It's the way handlers are supposed to record information on the message as its being processed. This is even more important in Mailman 3 where we've split the pipeline into rules and handlers. Rules are run to determine moderation behavior and rules are never supposed to modify the message. They communicate state to (possible) later handlers via the msgdata dictionary. Cheers, -Barry From mark at msapiro.net Thu May 7 23:31:01 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 May 2015 14:31:01 -0700 Subject: [Mailman-Developers] Storing extra data during pipeline processing In-Reply-To: <8046717.sbI3iWB512@bluesky> References: <8046717.sbI3iWB512@bluesky> Message-ID: <554BD995.5080302@msapiro.net> On 05/07/2015 01:51 PM, Juraj Variny wrote: > > I am adapting the GPG patch for mailman 2.1.x for our project and want to gather > some related data in Approve and Scrubber handlers and use them in the archiver. > Can you please advise me how to attach some metadata to a message to use it in > later stages? Store it in the msgdata which is intended exactly for this purpose and is passed as a separate object in the queue entry when the message is queued for downstream runners. Except this may not work - see below. > Also noticed Scrubber being called multiple times per message (from normal pipeline, > from digester, from archiver). I want to verify GPG signatures of the attachments in > scrubber and redoing it multiple time is wasteful of system resources, I want to attach > some metadata after the first checking to prevent it, too. Yes. The scrubber can actually process the same message more than once, but never more than twice. The purpose of the scrubber is to flatten the message to plain text and store aside any message parts that can't be converted to plain text. This must be done for both the pipermail archive and for the plain format digest. Since archiving and digesting are separate asynchronous processes, scrubbing is normally done twice; once in each process. Also, the two processes are independent and asynchronous so either one may process a given message before the other. You can set scrub_nondigest to Yes, in which case, scrubbing is done in the incoming pipeline and has nothing to do when called during digesting or archiving. This may or may not be desirable depending on the list because even message and MIME digest subscribers receive a scrubbed message. > I have tried already to use msgdata parameter or adding headers to message itself, > but was not successful so far. I was thinking about adding external database and > putting the data there by message ID, but sure there must be a better way? I hope to > publish the code some day, too. The msgdata metadata doesn't work for passing message data from the incoming pipeline to the digest process, because at the time the digester is processing and maybe scrubbing messages for the digest, it is reading the messages from digest.mbox and there is no metadata. Adding headers to the message in Handlers before ToDigest should work. ArchRunner does have the metadata when processing a message for the archive, but it doesn't pass it to the archiver. But, if you are using Scrubber.process to do the GPG stuff, it probably won't do anything if scrub_nondigest is No, and then because archiving and digesting are working with different copies of the message, they can't communicate via message headers either. I suggest you look at verifying signatures in Scrubber.process prior to the point at which at which it returns if scrub_nondigest is No, or better still, just add a custom handler between MimeDel and Scrubber in the pipeline to verify sigs and set the result in a message header that can be used by later processes. (See ). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu May 7 23:40:53 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 May 2015 14:40:53 -0700 Subject: [Mailman-Developers] Storing extra data during pipeline processing In-Reply-To: <20150507165905.0480da91@limelight.wooz.org> References: <8046717.sbI3iWB512@bluesky> <20150507165905.0480da91@limelight.wooz.org> Message-ID: <554BDBE5.7090206@msapiro.net> On 05/07/2015 01:59 PM, Barry Warsaw wrote: > On May 07, 2015, at 10:51 PM, Juraj Variny wrote: > >> I have tried already to use msgdata parameter or adding headers to message >> itself, but was not successful so far. I was thinking about adding external >> database and putting the data there by message ID, but sure there must be a >> better way? I hope to publish the code some day, too. > > Can you give some details on what didn't work about using the msgdata > parameter? This always flows with the message through the pipeline and is > preserved in the pickle files as the message moves from runner to runner. > It's the way handlers are supposed to record information on the message as its > being processed. See my reply in this thread. I think I understand. > This is even more important in Mailman 3 where we've split the pipeline into > rules and handlers. Rules are run to determine moderation behavior and rules > are never supposed to modify the message. They communicate state to > (possible) later handlers via the msgdata dictionary. In MM 3 one can have a rule which checks and verifies signatures and stores results in the msgdata. Than a handler can use that data to add a message header both for recipient info and to inform other bits that might run after there's no longer any msgdata dictionary traveling with the message. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From himbeere at meine-oma.de Fri May 8 08:45:15 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Fri, 08 May 2015 08:45:15 +0200 Subject: [Mailman-Developers] python error when try to save a setting In-Reply-To: <20150506164004.GA10681@soc2> References: <554876DF.4030401@meine-oma.de> <20150506164004.GA10681@soc2> Message-ID: <554C5B7B.6030706@meine-oma.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 06.05.15 um 18:40 schrieb Florian Fuchs: > On Tue, May 05, 2015 at 09:53:03AM +0200, Thomas Stein wrote: >> Hello. >> >> When i try to save a setting >> >> --schnipp-- Settings / Message Acceptance >> >> Default action to take when a member posts to the list ---> >> Accept > > The list of acceptable aliases isn't handled properly. I am working > on a fix. > > As a work-around (if you don't need to define acceptable aliases), > you can empty the acceptable aliases form field before submitting > the form. Yes that worked. Did not see the [] in the aliases field. Thanks. t. > Florian > > > > > _______________________________________________ Mailman-Developers > mailing list Mailman-Developers at python.org > https://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: > https://mail.python.org/mailman/options/mailman-developers/himbeere%40 meine-oma.de > > Security Policy: http://wiki.list.org/x/QIA9 > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) iQEcBAEBAgAGBQJVTFt7AAoJEDoNDMVwb47fYVcIAKn3NNYJoKDi5rIk4qIptnQD /A4haibnuvrC1ynlbPRke7zS6hbUcN5teLQin/wVX9K8WeLqoQLJ25R5LsQ0KFxW kIDp2CWgDxpLdlTSwdTLN9DbHA3fBJ+jZlZ+7W7WSuj9d83RhXIGErcB6aoKlcZV DqJrUifI60GiqhP52YKtG4KSPdzxrQkqSXx4anoqVPHvCak0xNiTlE/178CforVc v38iORoOHHh7FQdfW/4VYMQjIbPGFaAX1Rp8dYv80M2xDAScMM8z45JSwV2VQGEf fy7GvgWvOATrMJMbYV3KUFgVGdV+scrlU6KfND81OpsSWcP1FohWVPV3on7WZTA= =QvNF -----END PGP SIGNATURE----- From juraj at blava.eu Mon May 11 21:48:05 2015 From: juraj at blava.eu (Juraj Variny) Date: Mon, 11 May 2015 21:48:05 +0200 Subject: [Mailman-Developers] Storing extra data during pipeline processing In-Reply-To: <554BDBE5.7090206@msapiro.net> References: <8046717.sbI3iWB512@bluesky> <20150507165905.0480da91@limelight.wooz.org> <554BDBE5.7090206@msapiro.net> Message-ID: <1499815.X0Jyx7z1jG@bluesky> Thanks, it helped me to clear the confusion. I have decided to modify Scrubber so that its work is split, when in normal pipeline it only saves the attachments to disk, does gpg stuff, but keeps message unchanged(only headers added). Message is then processed when called from archiver. The change came out quite trivial and I wonder why it was not done that way in the first place. Juraj On Thursday 07 May 2015 14:40:53 Mark Sapiro wrote: > On 05/07/2015 01:59 PM, Barry Warsaw wrote: > > On May 07, 2015, at 10:51 PM, Juraj Variny wrote: > >> I have tried already to use msgdata parameter or adding headers to > >> message > >> itself, but was not successful so far. I was thinking about adding > >> external > >> database and putting the data there by message ID, but sure there must be > >> a > >> better way? I hope to publish the code some day, too. > > > > Can you give some details on what didn't work about using the msgdata > > parameter? This always flows with the message through the pipeline and is > > preserved in the pickle files as the message moves from runner to runner. > > It's the way handlers are supposed to record information on the message as > > its being processed. > > See my reply in this thread. I think I understand. > > > This is even more important in Mailman 3 where we've split the pipeline > > into rules and handlers. Rules are run to determine moderation behavior > > and rules are never supposed to modify the message. They communicate > > state to (possible) later handlers via the msgdata dictionary. > > In MM 3 one can have a rule which checks and verifies signatures and > stores results in the msgdata. Than a handler can use that data to add a > message header both for recipient info and to inform other bits that > might run after there's no longer any msgdata dictionary traveling with > the message. From rini17 at gmail.com Mon May 11 21:49:46 2015 From: rini17 at gmail.com (Juraj Variny) Date: Mon, 11 May 2015 21:49:46 +0200 Subject: [Mailman-Developers] Storing extra data during pipeline processing In-Reply-To: <554BDBE5.7090206@msapiro.net> References: <8046717.sbI3iWB512@bluesky> <20150507165905.0480da91@limelight.wooz.org> <554BDBE5.7090206@msapiro.net> Message-ID: <1893113.KFWEz2IFZF@bluesky> Thanks, it helped me to clear the confusion. I have decided to modify Scrubber so that its work is split, when in normal pipeline it only saves the attachments to disk, does gpg stuff, but keeps message unchanged(only headers added). Message is then processed when called from archiver. The change came out quite trivial and I wonder why it was not done that way in the first place. Juraj On Thursday 07 May 2015 14:40:53 Mark Sapiro wrote: > On 05/07/2015 01:59 PM, Barry Warsaw wrote: > > On May 07, 2015, at 10:51 PM, Juraj Variny wrote: > >> I have tried already to use msgdata parameter or adding headers to > >> message > >> itself, but was not successful so far. I was thinking about adding > >> external > >> database and putting the data there by message ID, but sure there must be > >> a > >> better way? I hope to publish the code some day, too. > > > > Can you give some details on what didn't work about using the msgdata > > parameter? This always flows with the message through the pipeline and is > > preserved in the pickle files as the message moves from runner to runner. > > It's the way handlers are supposed to record information on the message as > > its being processed. > > See my reply in this thread. I think I understand. > > > This is even more important in Mailman 3 where we've split the pipeline > > into rules and handlers. Rules are run to determine moderation behavior > > and rules are never supposed to modify the message. They communicate > > state to (possible) later handlers via the msgdata dictionary. > > In MM 3 one can have a rule which checks and verifies signatures and > stores results in the msgdata. Than a handler can use that data to add a > message header both for recipient info and to inform other bits that > might run after there's no longer any msgdata dictionary traveling with > the message. From syst3m.w0rm at gmail.com Tue May 12 04:44:30 2015 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Tue, 12 May 2015 11:44:30 +0900 Subject: [Mailman-Developers] Moving to git and gitlab In-Reply-To: <20150504201642.2d0a9e17@anarchist.wooz.org> References: <20150504201642.2d0a9e17@anarchist.wooz.org> Message-ID: On Tue, May 5, 2015 at 9:16 AM, Barry Warsaw wrote: > With the release of Mailman 3.0, it's time to take a look at our project > management, with an eye toward making it easier for core developers, easier > for non-core contributors, and providing improved quality, all while > staying > true to the GNU project's principles. > > There's a lot to like about Bazaar, and it's served us well over the years, > but it's also pretty clear that this round of version control systems has > been > won by git. We have converted the Core's vcs to git, and will soon convert > Postorius and mailman.client. HyperKitty is already managed under git. > > There's a lot to like about Launchpad. It's free software, and it has some > nice features, including one of my favorites: bug tasks, which allow us to > report a bug affecting more than one project or series, and track each > task as > it's resolved. Launchpad has even announced git support: > > http://blog.launchpad.net/general/git-code-hosting-beta > > There are also reasons why we might want to move off of Launchpad. Most > compelling is that Launchpad is difficult or impossible to use for code > hosting by our Indian colleagues. > Reason being bzr is too slow, right? Or, are there more reasons to it? > We have therefore decided to move to Gitlab. > > The Core is now hosted here: https://gitlab.com/mailman/mailman > > Postorius and mailman.client will follow after Florian has had some time to > work through the existing Launchpad merge proposals. HyperKitty may move > at > some point soon. > > We currently have no plans to move any hosting of Mailman 2.1. For now, > its > code will continue to live in Bazaar on Launchpad, its bugs will continue > to > be managed on Launchpad, as will merge proposals. > > Q: What about the existing lp:mailman Bazaar branch? > A: Let's leave it there for now, effectively keeping it around read-only. > > Q: What about existing LP bugs for Mailman 3? > A: Abhilash is working on transferring them to Gitlab. It won't be a > perfect > conversions since we can't match users on the two systems, but if/when > we > do transfer them, we'll keep a link to the LP bug report in the Gitlab > issue. We will only be moving the bugs tagged 'mailman3' on LP. > > If you own a Mailman 3 bug on Launchpad, feel free to close it there and > open a new one on Gitlab. > > In the meantime, or if the transfer doesn't work well enough, we'll just > close bugs on LP as we fix them. Please report all new bugs on Gitlab. > > Q: What about existing LP merge proposals? > A: These are much tougher to transfer. If you have an open merge proposal > on > LP, feel free to update it to the latest git head and submit a new merge > request on Gitlab. If you do, please close your mp on LP. > > In the meantime, I'll work my way through the existing LP merge > proposals, > applying diffs by hand if necessary. > > Q: What about CI? > A: This is definitely one of the exciting features of Gitlab we're eager to > start using. Our plans are to requisition a VM from python.org and > set up > CI on it. I'd like for us to never commit directly to the official > project > branches. > > Q: Why Gitlab and not Github or Bitbucket? > A: Gitlab has an edition that is free software. If for some reason we > have to > leave gitlab.com, we could potentially stand up our own Gitlab and have > an easier time transferring our projects to it. Plus we have to be a > *little* different don't we? :) > > Cheers, > -Barry > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > https://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: > https://mail.python.org/mailman/options/mailman-developers/syst3m.w0rm%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 > -- Regards, Aamir From stephen at xemacs.org Tue May 12 15:03:04 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 12 May 2015 22:03:04 +0900 Subject: [Mailman-Developers] Moving to git and gitlab In-Reply-To: References: <20150504201642.2d0a9e17@anarchist.wooz.org> Message-ID: <87egmm2bjr.fsf@uwakimon.sk.tsukuba.ac.jp> Aamir Khan writes: > > There are also reasons why we might want to move off of Launchpad. Most > > compelling is that Launchpad is difficult or impossible to use for code > > hosting by our Indian colleagues. > > Reason being bzr is too slow, right? Or, are there more reasons to > it? Lack of HTTPS support. Apparently many[1] Indian organizations block outgoing connections to port 22, so ssh connections aren't feasible. Footnotes: [1] FVO "many" == at least the University one of our frequent contributors attends. :-) From raj.abhilash1 at gmail.com Tue May 12 17:23:39 2015 From: raj.abhilash1 at gmail.com (Abhilash Raj) Date: Tue, 12 May 2015 20:53:39 +0530 Subject: [Mailman-Developers] Moving to git and gitlab In-Reply-To: <87egmm2bjr.fsf@uwakimon.sk.tsukuba.ac.jp> References: <20150504201642.2d0a9e17@anarchist.wooz.org> <87egmm2bjr.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <20150512205339.40430ef0@angel.angel.in> On Tue, 12 May 2015 22:03:04 +0900 "Stephen J. Turnbull" wrote: > Aamir Khan writes: > > > > There are also reasons why we might want to move off of > > > Launchpad. Most compelling is that Launchpad is difficult or > > > impossible to use for code hosting by our Indian colleagues. > > > > Reason being bzr is too slow, right? Or, are there more reasons to > > it? > > Lack of HTTPS support. Apparently many[1] Indian organizations block > outgoing connections to port 22, so ssh connections aren't feasible. There were some other reasons for which I insisted on the transition from launchpad to gitlab too. * Webhooks: Gitlab has webhooks for each pushes and we use it to build documentation automatically on readthedocs, which inturn notifies us(for now just me) about the build failures if any. (Earlier, I used to run a cron that updated the git repo on gitlab using git-remote-bzr every few hours) * CI: Gitlab CI, though needs a separate host to run builds on, has a very good integration with gitlab with current build status and notification when tests fails. Also, it is automatic and testing merge requests would probably help Barry a lot in filtering out MRs that *Needs Fixing*. * HTTPS: First of all, I agree this is an issue[1] that should be taken up with the universities. But all the code sharing platforms have done *something* by now to bypass this. Github had a proxy listening at 443 for ssh traffic even before it introduced support for push/pull over HTTPS. I did put up this on launchpad bug tracker, like 1 or 2 years back, but haven't heard any response back yet. Footnotes: [1]: They basically block ALL ports except the ones which have special use cases. All the university servers are inside the firewall and hence are easily accessible through SSH or FTP for anything. And they are too stubborn to consider the special use cases for developers like IRC(6667), SSH(22), FTP(21) or others. OTOH, there might be some security concerns related to internal LAN since we don't have a direct internet access, but only through a proxy server, so I can't really tell the real reason. > > > Footnotes: > [1] FVO "many" == at least the University one of our frequent > contributors attends. :-) Well now it is "used to attend" ;-) (yayy!!) -- thanks, Abhilash Raj From mark at msapiro.net Tue May 12 19:22:15 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 May 2015 10:22:15 -0700 Subject: [Mailman-Developers] Storing extra data during pipeline processing In-Reply-To: <1499815.X0Jyx7z1jG@bluesky> References: <8046717.sbI3iWB512@bluesky> <20150507165905.0480da91@limelight.wooz.org> <554BDBE5.7090206@msapiro.net> <1499815.X0Jyx7z1jG@bluesky> Message-ID: <555236C7.8090101@msapiro.net> On 05/11/2015 12:48 PM, Juraj Variny wrote: > > I have decided to modify Scrubber so that its work is split, when in normal > pipeline it only saves the attachments to disk, does gpg stuff, but keeps > message unchanged(only headers added). Message is then processed when called > from archiver. > > The change came out quite trivial and I wonder why it was not done that way in > the first place. The scrubber only job is to flatten a message to plain text for the archive and the plain format digest. Adding it to the pipeline to OPTIONALLY process all messages is a relatively recent change. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sumanah at panix.com Thu May 14 16:48:45 2015 From: sumanah at panix.com (Sumana Harihareswara) Date: Thu, 14 May 2015 10:48:45 -0400 Subject: [Mailman-Developers] DjangoCon ideas? Message-ID: <5554B5CD.5050909@panix.com> DjangoCon North America is in Austin, Texas, USA, September 6-11. They're looking for talks and the call for proposals ends tomorrow. https://2015.djangocon.us/speaking/cfp/ Is there anything we're doing with Django that would be of interest to the Django community, either to people who hack on Django or people who write and deploy Django applications? If so, I'd be open to submitting a proposal and speaking there. -- Sumana Harihareswara http://brainwane.net From daniel at ziegenberg.at Thu May 14 16:34:52 2015 From: daniel at ziegenberg.at (Daniel Ziegenberg) Date: Thu, 14 May 2015 16:34:52 +0200 Subject: [Mailman-Developers] Installing Mailman3 with mailman bundler fails: Couldn't install: python-social-auth 0.2.9 Message-ID: <026f01d08e53$23d166a0$6b7433e0$@ziegenberg.at> Hello! I tried to install Mailman 3 and its companions (Hyperkitty, Postorius) on a Ubuntu 14.04.2 LTS using the mailman-bundler. I followed the docs: http://mailman-bundler.readthedocs.org/en/latest/ It fails while trying to install 'python-social-aut': (venv)mailman at jiffy02:~/mailman-bundler$ buildout Getting distribution for 'python-social-auth>=0.2.3'. No eggs found in /tmp/easy_install-LK6bYy/python-social-auth-0.2.9/egg-dist-tmp-FzLeGP (setup script problem?) While: Installing mailman-web. Getting distribution for 'python-social-auth>=0.2.3'. Error: Couldn't install: python-social-auth 0.2.9 Any ideas? Greetings, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4863 bytes Desc: not available URL: From bhavesh.goyal093 at gmail.com Sat May 16 16:35:53 2015 From: bhavesh.goyal093 at gmail.com (Bhavesh Goyal) Date: Sat, 16 May 2015 20:05:53 +0530 Subject: [Mailman-Developers] [GSoc Project] Error Creating a New Model for The Database Message-ID: Hi ! I am trying to create a basic working prototype for one of the widgets in my project , 'Dashboard For Admins' and need some help implementing the same. I created a new 'Task' model which is supposed to show the list of pending tasks which require admin's attention. There exists two classes 'Task' , and 'TaskManager' inside the model for which I 've also created two required interfaces. I 've included a new Task class in postorius/models.py and created one inside Client too for handling rest queries... But, whenever I try to query an object from the 'task' table, I get an sql error : no such table 'task'. I ve tried doing makemigrations and migrate but it doesn't seem to recognize the newly created table. What can it be that I may be missing which is preventing me to query the table. Really desperate for any hep on this :) Thanks... -- Regards, Bhavesh Goyal, Computer Science Engineering, IIIT Hyderabad From barry at list.org Sat May 16 17:09:46 2015 From: barry at list.org (Barry Warsaw) Date: Sat, 16 May 2015 11:09:46 -0400 Subject: [Mailman-Developers] [GSoc Project] Error Creating a New Model for The Database In-Reply-To: References: Message-ID: <20150516110946.6326f423@anarchist.wooz.org> On May 16, 2015, at 08:05 PM, Bhavesh Goyal wrote: >What can it be that I may be missing which is preventing me to query the >table. Really desperate for any hep on this :) Thanks... Can you post a link to the branch? Cheers, -Barry From bhavesh.goyal093 at gmail.com Sat May 16 17:26:18 2015 From: bhavesh.goyal093 at gmail.com (Bhavesh Goyal) Date: Sat, 16 May 2015 20:56:18 +0530 Subject: [Mailman-Developers] [GSoc Project] Error Creating a New Model for The Database In-Reply-To: <20150516110946.6326f423@anarchist.wooz.org> References: <20150516110946.6326f423@anarchist.wooz.org> Message-ID: Links for the Repo(s) : Core : https://code.launchpad.net/~bhavesh-goyal093/mailman/DashboardTasks Client : https://code.launchpad.net/~bhavesh-goyal093/mailman.client/DashboardTasks Postorius : https://code.launchpad.net/~bhavesh-goyal093/postorius/DashboardTasks On Sat, May 16, 2015 at 8:39 PM, Barry Warsaw wrote: > On May 16, 2015, at 08:05 PM, Bhavesh Goyal wrote: > > >What can it be that I may be missing which is preventing me to query the > >table. Really desperate for any hep on this :) Thanks... > > Can you post a link to the branch? > > Cheers, > -Barry > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > https://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: > https://mail.python.org/mailman/options/mailman-developers/bhavesh.goyal093%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 > -- Regards, Bhavesh Goyal, B.Tech Computer Science Engineering, IIIT Hyderabad From stephen at xemacs.org Sun May 17 02:15:28 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sun, 17 May 2015 09:15:28 +0900 Subject: [Mailman-Developers] [GSoc Project] Error Creating a New Model for The Database In-Reply-To: References: Message-ID: <87382w12lb.fsf@uwakimon.sk.tsukuba.ac.jp> Bhavesh Goyal writes: > But, whenever I try to query an object from the 'task' table, I get > an sql error : no such table 'task'. Are you doing attribute access in Python code for Django, or are you writing direct SQL queries? My first guess for either case is that you haven't done the sync operation on the database (Django doesn't do it automatically), and so the table hasn't been created. My second guess is that the names that Django chooses for the table are munged (some kind of prefixing is done to make them unique and unlikely to conflict with table names chosen by the programmer). My third guess is that you're trying to access a Django table from Mailman; that isn't going to work terribly well. From stephen at xemacs.org Sun May 17 02:21:48 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sun, 17 May 2015 09:21:48 +0900 Subject: [Mailman-Developers] "How to Ask" -- reading list for GSoC students, part I Message-ID: <871tig12ar.fsf@uwakimon.sk.tsukuba.ac.jp> I don't mean to single out a particular student, or even students in general. We've all done this early in our careers. That said, > What can it be that I may be missing which is preventing me to > query the table. Really desperate for any hep on this :) Thanks... is a poor problem report. We shouldn't have to guess so much, or have to ask for simple things like "show us the code". Please read http://www.catb.org/esr/faqs/smart-questions.html The advice about how to communicate your issue in ways that get useful answers fast in that page (and in several linked pages) is very good. Eric and Rick (the authors) show a lot of attitude (and they do in real life, too! :-), which you generally won't see on this list and definitely not on mailman-users. But there are places where you will see the "snappy answers" style of response, or "desperate" queries that go completely ignored, as they describe. (One of them is graduate school, in case you're thinking about getting an advanced degree!) It's good to get in the habit of writing well-formed problem reports early. From aurelien at bompard.org Mon May 18 13:44:22 2015 From: aurelien at bompard.org (Aurelien Bompard) Date: Mon, 18 May 2015 13:44:22 +0200 Subject: [Mailman-Developers] Installing Mailman3 with mailman bundler fails: Couldn't install: python-social-auth 0.2.9 In-Reply-To: <026f01d08e53$23d166a0$6b7433e0$@ziegenberg.at> References: <026f01d08e53$23d166a0$6b7433e0$@ziegenberg.at> Message-ID: Hey! > No eggs found in > /tmp/easy_install-LK6bYy/python-social-auth-0.2.9/egg-dist-tmp-FzLeGP (setup > script problem?) I'm getting the same error, this does not look like a problem in the bundler but rather in the latest version of python-social-auth. It works if you insert "python-social-auth<0.2.9" on line 48 in buildout.cfg. Aur?lien From daniel at ziegenberg.at Mon May 18 13:50:06 2015 From: daniel at ziegenberg.at (Daniel Ziegenberg) Date: Mon, 18 May 2015 13:50:06 +0200 Subject: [Mailman-Developers] Installing Mailman3 with mailman bundler fails: Couldn't install: python-social-auth 0.2.9 In-Reply-To: References: <026f01d08e53$23d166a0$6b7433e0$@ziegenberg.at> Message-ID: <032c01d09160$c932ec30$5b98c490$@ziegenberg.at> > Hey! > > > No eggs found in > > /tmp/easy_install-LK6bYy/python-social-auth-0.2.9/egg-dist-tmp-FzLeGP > (setup > > script problem?) > > I'm getting the same error, this does not look like a problem in the > bundler but rather in the latest version of python-social-auth. It > works if you insert "python-social-auth<0.2.9" on line 48 in > buildout.cfg. > > Aur?lien I "solved" the problem with issuing the command: $ pip install python-social-auth And it installed the egg without problems. So the current python-social-auth is not buildout compatible? Is it my turn to file a bug in the python-social-auth bug tracker? Greetings, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4863 bytes Desc: not available URL: From aurelien at bompard.org Mon May 18 13:54:21 2015 From: aurelien at bompard.org (Aurelien Bompard) Date: Mon, 18 May 2015 13:54:21 +0200 Subject: [Mailman-Developers] Installing Mailman3 with mailman bundler fails: Couldn't install: python-social-auth 0.2.9 In-Reply-To: <032c01d09160$c932ec30$5b98c490$@ziegenberg.at> References: <026f01d08e53$23d166a0$6b7433e0$@ziegenberg.at> <032c01d09160$c932ec30$5b98c490$@ziegenberg.at> Message-ID: > So the current python-social-auth is not buildout compatible? It seems so, yeah. I did not investigate further to see what buildout was choking on. > Is it my turn to file a bug in the python-social-auth bug tracker? That would be great! Thanks Aur?lien From daniel at ziegenberg.at Mon May 18 14:44:47 2015 From: daniel at ziegenberg.at (Daniel Ziegenberg) Date: Mon, 18 May 2015 14:44:47 +0200 Subject: [Mailman-Developers] Installing Mailman3 with mailman bundler fails: Couldn't install: python-social-auth 0.2.9 In-Reply-To: References: <026f01d08e53$23d166a0$6b7433e0$@ziegenberg.at> <032c01d09160$c932ec30$5b98c490$@ziegenberg.at> Message-ID: <038301d09168$6ccd13f0$46673bd0$@ziegenberg.at> > > So the current python-social-auth is not buildout compatible? > > It seems so, yeah. I did not investigate further to see what buildout > was choking on. > > > Is it my turn to file a bug in the python-social-auth bug tracker? > > That would be great! Thanks > > Aur?lien Here's your bug report: https://github.com/omab/python-social-auth/issues/623 I hope it's specific enough. If they need more information, maybe you can help. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4863 bytes Desc: not available URL: From bhavesh.goyal093 at gmail.com Sat May 23 22:13:31 2015 From: bhavesh.goyal093 at gmail.com (Bhavesh Goyal) Date: Sun, 24 May 2015 01:43:31 +0530 Subject: [Mailman-Developers] [Project Discussion] Assigining Default Priority levels to user tasks Message-ID: Brief Introduction to Related Project content: The To - Do List proposed in the project , 'Dashboard for Admins' gives the admin, a list of pending tasks which require his immediate attention. The tasks particularly include those of 'Held Messages' (pending for moderation) and 'Subscription Requests'. Now, among the pile of pending tasks, some Tasks may be of higher importance than the others to the admin which he can quickly mark to get them completed first, the next time he sets up to clear the pending list. Thus color supported Priority Levels have been given and can be set with each of the tasks, sorting the important ones out from others. Discussion Statement : Whenever a new task gets added automatically ( when someone makes a subscription request for instance), what priority level should it be assigned. ? One Approach can be to keep a separate level of 'unprioritised' tasks and assigning a specific color value to this level (uncolored may be), separating them out from the others as the ones with 'priority level not set'. Other Solutions which I think can exist can be, choosing a default priority value for the newly added ones from among low/medium/high (only), limiting the number of colors to 3 instead of 4 for may be a more simpler (memorable) operation. Project Link: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/bhaveshgoyal093/5676830073815040 -- Regards, Bhavesh Goyal, Computer Science Engineering, IIIT Hyderabad From dandrews at visi.com Sun May 24 00:56:26 2015 From: dandrews at visi.com (David Andrews) Date: Sat, 23 May 2015 17:56:26 -0500 Subject: [Mailman-Developers] [Project Discussion] Assigining Default Priority levels to user tasks In-Reply-To: References: Message-ID: At 03:13 PM 5/23/2015, Bhavesh Goyal wrote: >Brief Introduction to Related Project content: > >The To - Do List proposed in the project >, >'Dashboard for Admins' gives the admin, a list of pending tasks which >require his immediate attention. The tasks particularly include those of >'Held Messages' (pending for moderation) and 'Subscription Requests'. > >Now, among the pile of pending tasks, some Tasks may be of higher >importance than the others to the admin which he can quickly mark to get >them completed first, the next time he sets up to clear the pending list. >Thus color supported Priority Levels have been given and can be set with >each of the tasks, sorting the important ones out from others. Please don't make color as the only way priorities are conveyed. A sizable percentage of the population, particularly males, are color blind, and others are blind and won't see the colors. Dave David Andrews and long white cane Harry. E-Mail: dandrews at visi.com or david.andrews at nfbnet.org From bhavesh.goyal093 at gmail.com Mon May 25 13:49:17 2015 From: bhavesh.goyal093 at gmail.com (Bhavesh Goyal) Date: Mon, 25 May 2015 17:19:17 +0530 Subject: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks Message-ID: Widget Specifications: The Tasks widget gives the admin, a list of pending tasks which require his immediate attention on the dashboard. The tasks particularly include those of 'Held Messages' (pending for moderation) and 'Subscription Requests'. A Task is added to the To - Do List for admin automatically, whenever a message sent by an user to a list is held for moderation or whenever a user makes a request for a subscription (through list-join). That Being said, I ve made a prototype for The widget 'model' which adds a 'task' entry for the admin, whenever a new message is queued for moderation or a subscription request is made (through list-join). The model can then further be iterated to create views for postorius to generate list of all tasks to be displayed on the dashboard. Approach : The 'Tasks' model and the REST API used to query the model are implemented in the core . Methods such as create and delete are implemented in the mailmanclient for communicating with core's REST API. The Corresponding class for Tasks model is created in postorius models to expose its 'objects' attribute to be used latter, for generating views for a complete list of tasks on the dashboard. Moderation tasks are added though the 'hold' chain for incoming messages and the membership command 'join' is used to make an entry for a subscription task. The Complete Prototype discussed is given in the links: https://code.launchpad.net/~bhavesh-goyal093/mailman/Tasks-Core https://code.launchpad.net/~bhavesh-goyal093/mailman.client/Tasks-REST https://code.launchpad.net/~bhavesh-goyal093/postorius/Tasks-postorius -- Regards, Bhavesh Goyal, Computer Science Engineering, IIIT Hyderabad From raj.abhilash1 at gmail.com Mon May 25 13:57:21 2015 From: raj.abhilash1 at gmail.com (Abhilash Raj) Date: Mon, 25 May 2015 17:27:21 +0530 Subject: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks In-Reply-To: References: Message-ID: <20150525172721.4fba17de@angel.angel.in> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, 25 May 2015 17:19:17 +0530 Bhavesh Goyal wrote: > Widget Specifications: > > The Tasks widget gives the admin, a list of pending tasks which > require his immediate attention on the dashboard. The tasks > particularly include those of 'Held Messages' (pending for > moderation) and 'Subscription Requests'. A Task is added to the To - > Do List for admin automatically, whenever a message sent by an user > to a list is held for moderation or whenever a user makes a request > for a subscription (through list-join). > > That Being said, > I ve made a prototype for The widget 'model' which adds a 'task' > entry for the admin, whenever a new message is queued for moderation > or a subscription request is made (through list-join). The model can > then further be iterated to create views for postorius to generate > list of all tasks to be displayed on the dashboard. > > Approach : > > The 'Tasks' model and the REST API used to query the model are > implemented in the core I think a better idea would be to keep everything in Postorius. Held messages and subscription requests are already available through the REST API, and hence can easily be used to create the `Tasks` model in Postorius. Barry, Florian thoughts? - -- thanks, Abhilash Raj -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVYw4jAAoJEJ2bK6Bh0KZ8AisP/05yxnMO0xG/Ye82QRHIm6mv 1wncgXvNL2UG7qW8pQevFQaAnhf5zrb4DZA12qFtYUGMbArWfpE5dDNyAaRrKQBT joKb9p/tvAwIS1aqH7fudcU7p60jgluoHDs4KfR39jNPgSZSkrv2z5jlZiLJew5X bZt6S/28fYH9nqYAFueoR4SnLIVCLA3SQ6tkuywPKPbPqT7DsHk1lQHcJdZVa/zu zKtgj5lsrALAMlL1vMuGll5CCPLRlzHjCud646KDQse1Vm/lzjcqtacq7LO2D4CN qEcnWfPbWtKVjiYF8le0kSlumGJ754t/drxty9ZZGEWAOinZVQ0gkiHRcNQpdo5V 4nePnLYZlx0SFY1E+3mIouqO0lpwMXY6IY1zw2gd9Uu8/XI9D3+vLcdwZF7yGYHl 7p7G03B//zg9Qd3I/PaCjDKUDAFu5otphSCylN392nPenUrznfQef/t7MQQFepqc kVP43O4rBo1OwEumuFRjs9FcC8sAi2RVoH+CvYXv36xBMALJtERm0q0gg8Xt0AIy LvkqQ+tHtcljoMwLXpe0Z3TqNO4V1VbjHMOCUIvmdGUx4r0gBD6hrEM3mgr+Xcg5 JHswGOswDiG/CDS66Ksn0PWD6EC9BvQAi+HUyD03rHYwlsbanwM+CtE9crb1GxF1 oSp4R3qdwtDO/+13Dx2z =AZeK -----END PGP SIGNATURE----- From barry at list.org Tue May 26 02:50:04 2015 From: barry at list.org (Barry Warsaw) Date: Mon, 25 May 2015 20:50:04 -0400 Subject: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks In-Reply-To: <20150525172721.4fba17de@angel.angel.in> References: <20150525172721.4fba17de@angel.angel.in> Message-ID: <20150525205004.08cbb545@anarchist.wooz.org> On May 25, 2015, at 05:27 PM, Abhilash Raj wrote: >I think a better idea would be to keep everything in Postorius. Held messages >and subscription requests are already available through the REST API, and >hence can easily be used to create the `Tasks` model in Postorius. Barry, >Florian thoughts? It was a long USA holiday weekend so I haven't had time to read the detailed proposal, but I think what Abhilash suggests has a lot of merit. The internal representation of subscription requests underwent a big change during Pycon, where the subscription policy work landed. There will be changes soon for unsubscription policy support. It's also possible that held messages will be handled differently in the future. The intent is to keep the REST API as stable as possible during all this, so if the information is available there (which it is), then it would be safest to just build on top of the existing API. Bhavesh, can you describe why a task model in the core is a better way to go? Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From stephen at xemacs.org Tue May 26 06:26:25 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 26 May 2015 13:26:25 +0900 Subject: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks In-Reply-To: <20150525205004.08cbb545@anarchist.wooz.org> References: <20150525172721.4fba17de@angel.angel.in> <20150525205004.08cbb545@anarchist.wooz.org> Message-ID: <87zj4sezgu.fsf@uwakimon.sk.tsukuba.ac.jp> Barry Warsaw writes: > On May 25, 2015, at 05:27 PM, Abhilash Raj wrote: > > >I think a better idea would be to keep everything in Postorius. +1 I really think we should reserve 3.1 for fixing major problems (and I expect to have a lot of user-noticable problems, starting with lots of Mailman 2 functionality that went unimplemented for one reason or another). I tend to sympathize with Bhavesh. There are a bunch of things that really need help from core. (Authn/z is the gaping wound: a *lot* of people have separate machines for mail and web, but as things stand that's not possible because Postorius has to live on the same host as core). > Bhavesh, can you describe why a task model in the core is a better > way to go? Yes, please do: I'm not 100% sure I agree that it would be useful later in the series, but especially in cases where the conclusion is "let's not" it's best to get a pretty solid argument "for" on record. It's also good practice. :-) From bhavesh.goyal093 at gmail.com Tue May 26 12:11:43 2015 From: bhavesh.goyal093 at gmail.com (Bhavesh Goyal) Date: Tue, 26 May 2015 15:41:43 +0530 Subject: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks Message-ID: Hi ! On Tue, May 26, 2015 at 6:20 AM, Barry Warsaw wrote: >Bhavesh, can you describe why a task model in the core is a better way to > go? > > I thought of implementing the model in core in the first place because I thought it may would have been good to have the user tasks available on hand even when one is not having access to the postorius web UI. Second: I was able to track every moderation or subscription event 'directly' through the core, making it (a little)easier to add an entry in contrast to a postorius model, for which the existing REST properties accompanied with a logic would have been used to detect a new incoming event. But, Now on a whole, Yes I agree, I should have discussed the thought before, the reason being now I get the idea of postorius and the core complementing each other always on the same machine and the 'need' of Tasks more in the web dashboard rather than in the core. Also, as Barry said, if the logic behind moderations change in coming time, Yes, It would affect the overall functionality of the tasks model too. Thus, It would rather be a better choice to use the the existing REST calls and use a postorius model instead. :) Thanks for your consideration and making the idea clear :) -- Regards, Bhavesh Goyal, Computer Science Engineering, IIIT Hyderabad From barry at list.org Tue May 26 16:12:47 2015 From: barry at list.org (Barry Warsaw) Date: Tue, 26 May 2015 10:12:47 -0400 Subject: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks In-Reply-To: <87zj4sezgu.fsf@uwakimon.sk.tsukuba.ac.jp> References: <20150525172721.4fba17de@angel.angel.in> <20150525205004.08cbb545@anarchist.wooz.org> <87zj4sezgu.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <20150526101247.0473251b@limelight.wooz.org> On May 26, 2015, at 01:26 PM, Stephen J. Turnbull wrote: >I really think we should reserve 3.1 for fixing major problems (and I expect >to have a lot of user-noticable problems, starting with lots of Mailman 2 >functionality that went unimplemented for one reason or another). +1. I do intend to do a 3.0.1 of core at some point soonish to fix a few bugs. Here's where we can start gathering high level tasks for 3.1: http://wiki.list.org/DEV/Mailman%203.1 >I tend to sympathize with Bhavesh. There are a bunch of things that >really need help from core. (Authn/z is the gaping wound: a *lot* of >people have separate machines for mail and web, but as things stand >that's not possible because Postorius has to live on the same host as >core). I'm not opposed to pulling things into the core where it makes sense. I just want a good rationale, a consistent design, and a logical organization of the API resources. > > Bhavesh, can you describe why a task model in the core is a better > > way to go? > >Yes, please do: I'm not 100% sure I agree that it would be useful >later in the series, but especially in cases where the conclusion is >"let's not" it's best to get a pretty solid argument "for" on record. There could be some good reasons to implement and expose the task model in the core. One of them might be to provide a better abstraction on top of the currently disjoint implementation of held messages and subscription requests. These currently have different types of ids/tokens and are held in different tables. There might be other benefits worth exploring. I have some thoughts about how it might be best to implement something like that in the core, but let's not go there yet. If there's a really strong reason to do it, I can outline my implementation thoughts. Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From danil at smirnov.la Wed May 27 14:39:04 2015 From: danil at smirnov.la (Danil Smirnov) Date: Wed, 27 May 2015 15:39:04 +0300 Subject: [Mailman-Developers] mailman 3 and mysql Message-ID: As I see on page https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html Mailman 3 should work with MySQL/MariaDB database. Could you please help me put right configuration to the [database] section of mailman.cfg file? Thanks. Danil From barry at list.org Wed May 27 15:28:42 2015 From: barry at list.org (Barry Warsaw) Date: Wed, 27 May 2015 09:28:42 -0400 Subject: [Mailman-Developers] mailman 3 and mysql In-Reply-To: References: Message-ID: <20150527092842.3fd82276@limelight.wooz.org> On May 27, 2015, at 03:39 PM, Danil Smirnov wrote: >As I see on page >https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html > >Mailman 3 should work with MySQL/MariaDB database. Well, that page is careful to say that SQLAlchemy, the ORM layer we use, is compatible with MySQL, but it doesn't claim that Mailman 3 actually is. Currently we only officially support SQLite and PostgreSQL. We test all the time with the former, and try to keep the latter functional (that will actually get better once our gitlab CI integration is working). TL;DR: We want to be able to support any FLOSS database backend that SQLAlchemy supports, but we need contributions and testing for databases other than SQLite and PostgreSQL. Cheers, -Barry From danil at smirnov.la Wed May 27 15:49:00 2015 From: danil at smirnov.la (Danil Smirnov) Date: Wed, 27 May 2015 16:49:00 +0300 Subject: [Mailman-Developers] mailman 3 and mysql In-Reply-To: <20150527092842.3fd82276@limelight.wooz.org> References: <20150527092842.3fd82276@limelight.wooz.org> Message-ID: Hi Barry! Thank you for your answer. I have another 2 questions. :) 1) Does this also relate to Postorius and HyperKitty db configuration set in file production.py? Can I use MySQL for them?.. 2) What is better for production - to keep SQLite use or install PostgreSQL? The manual told me that I have to use 'full-blown database server' which is not true for SQLite I think?... Danil 2015-05-27 16:28 GMT+03:00 Barry Warsaw : > On May 27, 2015, at 03:39 PM, Danil Smirnov wrote: > >>As I see on page >>https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html >> >>Mailman 3 should work with MySQL/MariaDB database. > > Well, that page is careful to say that SQLAlchemy, the ORM layer we use, is > compatible with MySQL, but it doesn't claim that Mailman 3 actually is. > Currently we only officially support SQLite and PostgreSQL. We test all the > time with the former, and try to keep the latter functional (that will > actually get better once our gitlab CI integration is working). > > TL;DR: We want to be able to support any FLOSS database backend that > SQLAlchemy supports, but we need contributions and testing for databases other > than SQLite and PostgreSQL. > > Cheers, > -Barry > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > https://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: https://mail.python.org/mailman/options/mailman-developers/danil%40smirnov.la > > Security Policy: http://wiki.list.org/x/QIA9 From barry at list.org Wed May 27 16:07:22 2015 From: barry at list.org (Barry Warsaw) Date: Wed, 27 May 2015 10:07:22 -0400 Subject: [Mailman-Developers] mailman 3 and mysql In-Reply-To: References: <20150527092842.3fd82276@limelight.wooz.org> Message-ID: <20150527100722.295ccefe@anarchist.wooz.org> On May 27, 2015, at 04:49 PM, Danil Smirnov wrote: >1) Does this also relate to Postorius and HyperKitty db configuration >set in file production.py? Can I use MySQL for them?.. Others can provide more detailed answers but it might be a good idea to keep all three components in the same database. At least that makes it easier to maintain. >2) What is better for production - to keep SQLite use or install PostgreSQL? >The manual told me that I have to use 'full-blown database server' >which is not true for SQLite I think?... I'd like for SQLite to be appropriate for production, but it might not be. Because of the way SQLite does locking (also, in the Python layer), you might get some database lock errors. We've seen a few of these reported in the past; it usually means a transaction hasn't been properly closed (aborted or committed) in one process. Remember, MM3 has no list-locks any more. None of that should happen with a client/server based DB. I guess I'd say that we'd love to get more production experience with MM3 backed by SQLite, so use that if you feel like you can help debug any problems that *might* occur. If you don't want to be bothered, stick with PG for now, or if you know MySQL well, try to adapt the PG support to it and contribute! :) Cheers, -Barry From danil at smirnov.la Wed May 27 20:44:51 2015 From: danil at smirnov.la (Danil Smirnov) Date: Wed, 27 May 2015 21:44:51 +0300 Subject: [Mailman-Developers] help with ImportError: No module named 'psycopg2' Message-ID: I'm still trying to get Mailman 3 ready for the production. I've set parameters for the production and trying to make post-update: --- (venv)[root at host mailman-bundler]# bin/mailman-post-update + '[' False == False ']' + mkdir -p /var/spool/mailman-web/static + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin collectstatic --clear --noinput --verbosity 0 + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin compress Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation_link.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_settings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/mass_removal.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/archival_options.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/unsubscribe.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/login.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscription_requests.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_subscriptions.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_tasks.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/confirm_delete.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/summary.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/settings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_mailmansettings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/members.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/mass_subscribe.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_index.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/metrics.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_profile.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscriptions.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/settings_legacy.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_subscription_preferences.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/memberoptions.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/held_messages.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation_sent.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/index.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_preferences.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/confirm_dialog.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_confirm_delete.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/site_settings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscribe.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/errors/generic.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_new.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/new.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Found 'compress' tags in: /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_posts.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/message_new.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/api.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/reattach.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_profile.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/login.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/message.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/index.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/register.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/schemaupgrade.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/404.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/overview.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/thread_list.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/500.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/private.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/base.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/search_results.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/thread.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_public_profile.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/notimplemented.html Compressing... done Compressed 3 block(s) from 20 template(s). +++ /usr/local/src/mailman-bundler/bin/django-read-settings DATABASES.default.NAME ++ dirname mailman3 + dbdir=. + mkdir -p . + syncdb_cmd='/usr/local/src/mailman-bundler/bin/mailman-web-django-admin migrate' + [[ ! -t 1 ]] + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin migrate Operations to perform: Synchronize unmigrated apps: postorius, compressor, django_extensions, paintstore, django_gravatar, rest_framework, haystack, crispy_forms Apply all migrations: sessions, admin, auth, default, contenttypes, hyperkitty Synchronizing apps without migrations: Creating tables... Installing custom SQL... Installing indexes... Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin update_index Indexing 0 emails + '[' '!' -f /usr/sbin/postmap ']' + /usr/local/src/mailman-bundler/bin/mailman aliases Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/bin/mailman", line 9, in load_entry_point('mailman==3.0.0', 'console_scripts', 'mailman')() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/bin/mailman.py", line 98, in main initialize(config_path) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/initialize.py", line 191, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/initialize.py", line 163, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/factory.py", line 59, in create database.initialize() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/base.py", line 110, in initialize self.engine = create_engine(url) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/engine/__init__.py", line 386, in create_engine return strategy.create(*args, **kwargs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/engine/strategies.py", line 75, in create dbapi = dialect_cls.dbapi(**dbapi_args) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 554, in dbapi import psycopg2 ImportError: No module named 'psycopg2' --- But: pip install psycopg2 You are using pip version 6.1.1, however version 7.0.1 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Requirement already satisfied (use --upgrade to upgrade): psycopg2 in /usr/local/src/venv/lib/python2.7/site-packages Please advice. Danil From raj.abhilash1 at gmail.com Wed May 27 21:57:58 2015 From: raj.abhilash1 at gmail.com (Abhilash Raj) Date: Thu, 28 May 2015 01:27:58 +0530 Subject: [Mailman-Developers] help with ImportError: No module named 'psycopg2' In-Reply-To: References: Message-ID: <20150528012758.37516b12@angel.angel.in> On Wed, 27 May 2015 21:44:51 +0300 Danil Smirnov wrote: > I'm still trying to get Mailman 3 ready for the production. > > I've set parameters for the production and trying to make post-update: > > --- > > (venv)[root at host mailman-bundler]# bin/mailman-post-update > + '[' False == False ']' > + mkdir -p /var/spool/mailman-web/static > + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin > collectstatic --clear --noinput --verbosity 0 > + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin compress > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation_link.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_settings.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/mass_removal.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/archival_options.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/unsubscribe.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/login.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscription_requests.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_subscriptions.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_tasks.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/confirm_delete.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/summary.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/settings.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_mailmansettings.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/members.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/mass_subscribe.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_index.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/metrics.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_profile.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscriptions.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/settings_legacy.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_subscription_preferences.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/memberoptions.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/held_messages.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation_sent.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/index.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_preferences.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/confirm_dialog.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_confirm_delete.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/site_settings.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscribe.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/errors/generic.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_new.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/new.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Found 'compress' tags in: > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_posts.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/message_new.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/api.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/reattach.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_profile.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/login.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/message.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/index.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/register.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/schemaupgrade.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/404.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/overview.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/thread_list.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/500.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/private.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/base.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/search_results.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/thread.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_public_profile.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/notimplemented.html > Compressing... done > Compressed 3 block(s) from 20 template(s). > +++ /usr/local/src/mailman-bundler/bin/django-read-settings > DATABASES.default.NAME > ++ dirname mailman3 > + dbdir=. > + mkdir -p . > + > syncdb_cmd='/usr/local/src/mailman-bundler/bin/mailman-web-django-admin > migrate' > + [[ ! -t 1 ]] > + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin migrate > Operations to perform: > Synchronize unmigrated apps: postorius, compressor, > django_extensions, paintstore, django_gravatar, rest_framework, > haystack, crispy_forms > Apply all migrations: sessions, admin, auth, default, contenttypes, > hyperkitty Synchronizing apps without migrations: > Creating tables... > Installing custom SQL... > Installing indexes... > Running migrations: > No migrations to apply. > Your models have changes that are not yet reflected in a migration, > and so won't be applied. > Run 'manage.py makemigrations' to make new migrations, and then > re-run 'manage.py migrate' to apply them. > + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin > update_index Indexing 0 emails > + '[' '!' -f /usr/sbin/postmap ']' > + /usr/local/src/mailman-bundler/bin/mailman aliases > Traceback (most recent call last): > File "/usr/local/src/mailman-bundler/venv-3.4/bin/mailman", line 9, > in > load_entry_point('mailman==3.0.0', 'console_scripts', 'mailman')() > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/bin/mailman.py", > line 98, in main initialize(config_path) > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/initialize.py", > line 191, in initialize initialize_2(propagate_logs=propagate_logs) > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/initialize.py", > line 163, in initialize_2 config.db = getUtility(IDatabaseFactory, > utility_name).create() File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/factory.py", > line 59, in create database.initialize() > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/base.py", > line 110, in initialize self.engine = create_engine(url) > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/engine/__init__.py", > line 386, in create_engine return strategy.create(*args, **kwargs) > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/engine/strategies.py", > line 75, in create dbapi = dialect_cls.dbapi(**dbapi_args) > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", > line 554, in dbapi import psycopg2 > ImportError: No module named 'psycopg2' > > --- > > But: > > pip install psycopg2 > You are using pip version 6.1.1, however version 7.0.1 is available. > You should consider upgrading via the 'pip install --upgrade pip' > command. Requirement already satisfied (use --upgrade to upgrade): > psycopg2 in /usr/local/src/venv/lib/python2.7/site-packages There are actually 2 virtualenvs for mailman. One is the default one that you are working in, another one(venv-3.4) is probably automatically created by mailman-bundler as you can see in the logs above. This should fix your problem. $ source /usr/local/src/mailman-bundler/venv-3.4/bin/activate $ pip install psycopg2 $ (reactivate your original venv) > > > Please advice. > > Danil > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > https://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: > https://mail.python.org/mailman/options/mailman-developers/raj.abhilash1%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 -- thanks, Abhilash Raj -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From danil at smirnov.la Wed May 27 22:51:09 2015 From: danil at smirnov.la (Danil Smirnov) Date: Wed, 27 May 2015 23:51:09 +0300 Subject: [Mailman-Developers] help with ImportError: No module named 'psycopg2' In-Reply-To: <20150528012758.37516b12@angel.angel.in> References: <20150528012758.37516b12@angel.angel.in> Message-ID: 2015-05-27 22:57 GMT+03:00 Abhilash Raj : > There are actually 2 virtualenvs for mailman. One is the default one > that you are working in, another one(venv-3.4) is probably automatically > created by mailman-bundler as you can see in the logs above. > This should fix your problem. > > $ source /usr/local/src/mailman-bundler/venv-3.4/bin/activate > $ pip install psycopg2 > $ (reactivate your original venv) Thanks Abhilash! It works! :) From Bill.Costa at unh.edu Thu May 28 01:17:07 2015 From: Bill.Costa at unh.edu (Bill.Costa at unh.edu) Date: Wed, 27 May 2015 19:17:07 -0400 (EDT) Subject: [Mailman-Developers] MM3 install on RHEL 5.11 Message-ID: I need to migrate off of crufty old CREN ListProc (LP). So far I have successfully installed MM2 and did some limited testing. But seeing how MM3 has come out of beta, I thought it would be better to leapfrog to MM3 rather than forcing my list owners and subscribers through two MLM migrations (LP -> MM2 -> MM3). I am installing MM on my current list host, RedHat Enterprise Server 5.11, since it will allow me to migrate the lists one by one without a list address change; I'll just replace each LP set of aliases with MM aliases as I convert the lists. (I'll move to a more modern OS after the migration is done.) While I am an experienced programmer, with extensive Perl and Bash experience, I'm totally new to the Python ecosystem so I'm not familiar with things like `pip`, `bz`, and Virtualenv. So my first question is --- am I'm crazy to try and jump into MM3 for a production system at this stage of its development? To help me install MM3 I'm using the following two resources: https://mailman-bundler.readthedocs.org/en/latest/ http://wiki.list.org/HyperKitty/DevelopmentSetupGuide So far I have successfully installed both Python 2.6 and 3.4 and upgraded to the latest version of `pip` pip 7.0.1 from /usr/local/lib/python3.4/site-packages (python 3.4) It looks like the next thing I need to install GNU Bazaar. I thought I could do it with `pip`, but ran into a problem and Google is of limited help to me. (Install Cython? Pyrex??) Any help, about this specific problem, or the wisdom of my jumping onto the MM3 wagon in general, would be appreciated. ...BC $ sudo -H pip install bzr Collecting bzr Downloading bzr-2.6.0.tar.gz (11.3MB) 100% |????????????????????????????????| 11.3MB 34kB/s Complete output from command python setup.py egg_info: No Cython, trying Pyrex... The python package 'Pyrex' is not available. If the .c files are available, they will be built, but modifying the .pyx files will not rebuild them. running egg_info creating pip-egg-info/bzr.egg-info writing top-level names to pip-egg-info/bzr.egg-info/top_level.txt writing dependency_links to pip-egg-info/bzr.egg-info/dependency_links.txt writing pip-egg-info/bzr.egg-info/PKG-INFO Traceback (most recent call last): File "", line 20, in File "/tmp/pip-build-3a5_7rap/bzr/setup.py", line 780, in setup(**ARGS) File "/usr/local/lib/python3.4/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/local/lib/python3.4/distutils/dist.py", line 955, in run_commands self.run_command(cmd) File "/usr/local/lib/python3.4/distutils/dist.py", line 974, in run_command cmd_obj.run() File "", line 14, in replacement_run File "/usr/local/lib/python3.4/site-packages/setuptools/command/egg_info.py", line 387, in write_pkg_info metadata.write_pkg_info(cmd.egg_info) File "/usr/local/lib/python3.4/distutils/dist.py", line 1108, in write_pkg_info self.write_pkg_file(pkg_info) File "/usr/local/lib/python3.4/distutils/dist.py", line 1129, in write_pkg_file long_desc = rfc822_escape(self.get_long_description()) File "/usr/local/lib/python3.4/distutils/util.py", line 470, in rfc822_escape lines = header.split('\n') TypeError: 'str' does not support the buffer interface ---------------------------------------- Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-3a5_7rap/bzr $ From stephen at xemacs.org Thu May 28 02:25:55 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 28 May 2015 09:25:55 +0900 Subject: [Mailman-Developers] Posting etiquette In-Reply-To: <20150528012758.37516b12@angel.angel.in> References: <20150528012758.37516b12@angel.angel.in> Message-ID: <87pp5lfsz0.fsf@uwakimon.sk.tsukuba.ac.jp> Abhilash Raj writes: Subject: Re: [Mailman-Developers] help with ImportError: No module named 'psycopg2' [body omitted] Abhilash, that post had a signal to noise ratio of 0.08 by line count, and it would be worse in bytes. Please trim. If you don't want to trim because you're on a handheld device, at least *top-post*, and don't forget to apologize so that people *know* it's a top-post (in contravention to ordinary practice on *this* list; see http://turnbull.sk.tsukuba.ac.jp/Teach/ESES/socsys.html for analysis). From mark at msapiro.net Thu May 28 02:37:19 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 May 2015 17:37:19 -0700 Subject: [Mailman-Developers] MM3 install on RHEL 5.11 In-Reply-To: References: Message-ID: <5566633F.9010106@msapiro.net> On 05/27/2015 04:17 PM, Bill.Costa at unh.edu wrote: > > While I am an experienced programmer, with extensive Perl and > Bash experience, I'm totally new to the Python ecosystem so > I'm not familiar with things like `pip`, `bz`, and > Virtualenv. So my first question is --- am I'm crazy to try > and jump into MM3 for a production system at this stage of > its development? A tough question. How adventuresome are you? There is a big advantage for you in going straight to MM 3 and that is you won't miss those MM 2.1 features that haven't yet been implemented in MM 3. ;) I hesitate to advise you on a path here. There are pro and con arguments for both, but I *think* if I were in your place, I would at least try MM3. > To help me install MM3 I'm using the following two resources: > > https://mailman-bundler.readthedocs.org/en/latest/ > http://wiki.list.org/HyperKitty/DevelopmentSetupGuide > > So far I have successfully installed both Python 2.6 and 3.4 and > upgraded to the latest version of `pip` > > pip 7.0.1 from /usr/local/lib/python3.4/site-packages (python 3.4) > > It looks like the next thing I need to install GNU Bazaar. I > thought I could do it with `pip`, but ran into a problem and > Google is of limited help to me. (Install Cython? Pyrex??) > > Any help, about this specific problem, or the wisdom of my > jumping onto the MM3 wagon in general, would be appreciated. I'm not sure about the pip issue, but how about yum? See -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From raj.abhilash1 at gmail.com Thu May 28 05:03:49 2015 From: raj.abhilash1 at gmail.com (Abhilash Raj) Date: Thu, 28 May 2015 08:33:49 +0530 Subject: [Mailman-Developers] Posting etiquette In-Reply-To: <87pp5lfsz0.fsf@uwakimon.sk.tsukuba.ac.jp> References: <20150528012758.37516b12@angel.angel.in> <87pp5lfsz0.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: Hi Steve, On May 28, 2015 5:55 AM, "Stephen J. Turnbull" wrote: > Abhilash, that post had a signal to noise ratio of 0.08 by line count, I am sorry, I noticed that just now. I usually do trim messages, but I remember I was working on something while sending in the last mail and totally forgot about the length. Thanks for pointing out though, will surely keep that in mind from now on. thanks, Abhilash From Bill.Costa at unh.edu Thu May 28 17:13:13 2015 From: Bill.Costa at unh.edu (Bill.Costa at unh.edu) Date: Thu, 28 May 2015 11:13:13 -0400 (EDT) Subject: [Mailman-Developers] MM3 install on RHEL 5.11 In-Reply-To: <5566633F.9010106@msapiro.net> References: <5566633F.9010106@msapiro.net> Message-ID: Mark Sapiro kindly posted, in part... > A tough question. How adventuresome are you? Well a former boss had a saying that I've taken to heart. "Don't be first. Don't be last." Are there *any* production MM 3 sites up at this point? > There is a big advantage for you in going straight to MM 3 and > that is you won't miss those MM 2.1 features that haven't yet > been implemented in MM 3. ;) The Pareto principle (also known as the 80?20 rule) seems to apply to so many things, especially computer apps. ListProc is crufty but featureful. Yet for 15+ years it has been running here, list owners have pretty much used only a small set of all the available features. So I don't have any concerns there. And on the plus side, the Google/Yahoo Groups-like features of HyperKitty should be a real win for my list owners and subscribers. > I hesitate to advise you on a path here. There are pro and con > arguments for both, but I *think* if I were in your place, I > would at least try MM3. At this stage I agree -- it is worth trying to kick the tires on MM 3. But without a detailed install manual for a typical list admin as verses a Python developer, it looks like it is going to be a slog. > I'm not sure about the pip issue, but how about yum? See > So far I've been build stuff from source, perhaps for no good reason. ...BC -- =====================================[ Bill.Costa at unh.edu ]== Bill Costa 1 Leavitt Lane UNH IT -- 1st Floor University of New Hampshire Durham, NH 03824 USA Voice: +1-603-862-3056 No good deed... Goes unpunished. ===========================[ http://pubpages.unh.edu/~wfc ]== From danil at smirnov.la Fri May 29 14:01:19 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 29 May 2015 15:01:19 +0300 Subject: [Mailman-Developers] right adding of mailman 3 conf lines to httpd.conf Message-ID: Please help me to do this. if I put deployment/apache.conf into the virtualhost section of httpd.conf I got the following: httpd[30658]: AH00526: Syntax error on line 428 of /etc/httpd/conf/httpd.conf: httpd[30658]: WSGISocketPrefix cannot occur within section If I put them just outside of any virtualhost tags they produce Server error page. It would be great if I could put them into :443 virtualhost section to use SSL connection only for the list management/archives. Centos 7, Apache 2.4.6, last mailman-bundler. Danil From stephen at xemacs.org Fri May 29 18:06:47 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sat, 30 May 2015 01:06:47 +0900 Subject: [Mailman-Developers] right adding of mailman 3 conf lines to httpd.conf In-Reply-To: References: Message-ID: <87617bv04o.fsf@uwakimon.sk.tsukuba.ac.jp> Danil Smirnov writes: > Please help me to do this. > > if I put deployment/apache.conf into the virtualhost section of > httpd.conf I got the following: > > httpd[30658]: AH00526: Syntax error on line 428 of /etc/httpd/conf/httpd.conf: > httpd[30658]: WSGISocketPrefix cannot occur within section > > If I put them just outside of any virtualhost tags they produce Server > error page. > > It would be great if I could put them into :443 virtualhost section to > use SSL connection only for the list management/archives. Is deployment/apache.conf distributed by Mailman (presumably in Mailman-Bundler)? Have you changed it in *any* way (including anything that the installation instructions tell you do do)? I'm asking because it sounds to me like apache.conf is written to be use only in a non-virtual-host setup, which I would consider a bug that we need to fix. AFAICS from the modwsgi docs, just move the WSGISocketPrefix out of apache.conf and into a non-vhost area of httpd.conf and you should be golden. From barry at list.org Fri May 29 18:10:52 2015 From: barry at list.org (Barry Warsaw) Date: Fri, 29 May 2015 12:10:52 -0400 Subject: [Mailman-Developers] MM3 install on RHEL 5.11 In-Reply-To: References: <5566633F.9010106@msapiro.net> Message-ID: <20150529121052.479b3cbb@anarchist.wooz.org> On May 28, 2015, at 11:13 AM, Bill.Costa at unh.edu wrote: >Well a former boss had a saying that I've taken to heart. "Don't >be first. Don't be last." Are there *any* production MM 3 sites >up at this point? There are, but I don't know if there are many *public* sites yet. I'm hoping we can fix this fairly soon with some dogfood lists. We're just waiting on server provisioning. >At this stage I agree -- it is worth trying to kick the tires on >MM 3. But without a detailed install manual for a typical list >admin as verses a Python developer, it looks like it is going to >be a slog. If I have some free time, I'd like to at least get Core, Hyperkitty, and Postorius into Debian. In the meantime, keep posting questions and feedback here. I'd like for MM3.1 to concentrate on three big areas (other than bug fixing of course): high fidelity conversions from MM2.1, improved installation documentation and procedures, and closing the feature gap with MM2.1. Cheers, -Barry From danil at smirnov.la Fri May 29 20:13:35 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 29 May 2015 21:13:35 +0300 Subject: [Mailman-Developers] right adding of mailman 3 conf lines to httpd.conf In-Reply-To: <87617bv04o.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87617bv04o.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: Thank you Stephen! 2015-05-29 19:06 GMT+03:00 Stephen J. Turnbull : > Is deployment/apache.conf distributed by Mailman (presumably in > Mailman-Bundler)? Have you changed it in *any* way (including > anything that the installation instructions tell you do do)? No. > AFAICS from the modwsgi docs, just move the WSGISocketPrefix out of > apache.conf and into a non-vhost area of httpd.conf and you should be > golden. It helps - I need to move these four directives outside of my virtualhost section: WSGISocketPrefix run/wsgi WSGIRestrictStdout On WSGIRestrictSignal Off WSGIPythonOptimize 1 to get working httpd.conf but I still can not access Mailman web interface. I tried https://domain.tld/ , https://domain.tld/mailman3 and both with :8000 port. "Internal Server Error" for the first couple, "Not found" for the second. Also there is nothing in the logs. If I open http://127.0.0.1:8000/mailman3 in `links` I got the error - see it in the attach. Danil From shirish at hamaralinux.org Fri May 29 20:41:01 2015 From: shirish at hamaralinux.org (shirish) Date: Sat, 30 May 2015 00:11:01 +0530 Subject: [Mailman-Developers] MM3 install on RHEL 5.11 In-Reply-To: <20150529121052.479b3cbb@anarchist.wooz.org> References: <5566633F.9010106@msapiro.net> <20150529121052.479b3cbb@anarchist.wooz.org> Message-ID: <5568B2BD.3020300@hamaralinux.org> at bottom :- On 05/29/2015 09:40 PM, Barry Warsaw wrote: > If I have some free time, I'd like to at least get Core, Hyperkitty, and > Postorius into Debian. I am guessing you would be targeting stretch, even if you are able to get something in experimental, there are and would be people willing to test it and give feedback if you are able to do that. -- Regards, Shirish Agarwal, Community Lead, Hamaralinux.org From barry at list.org Fri May 29 21:28:06 2015 From: barry at list.org (Barry Warsaw) Date: Fri, 29 May 2015 15:28:06 -0400 Subject: [Mailman-Developers] [Project Discussion] Assigining Default Priority levels to user tasks In-Reply-To: References: Message-ID: <20150529152806.6b3013db@anarchist.wooz.org> On May 24, 2015, at 01:43 AM, Bhavesh Goyal wrote: >Whenever a new task gets added automatically ( when someone makes a >subscription request for instance), what priority level should it be >assigned. ? Perhaps that should be configurable? As a list administrator, I might prefer to handle subscription requests first, but someone else may want to handle held messages first. Cheers, -Barry From danil at smirnov.la Fri May 29 23:24:37 2015 From: danil at smirnov.la (Danil Smirnov) Date: Sat, 30 May 2015 00:24:37 +0300 Subject: [Mailman-Developers] right adding of mailman 3 conf lines to httpd.conf In-Reply-To: References: <87617bv04o.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: > Also there is nothing in the logs. After I uncommented in httpd.conf the line ErrorLog /var/log/httpd/mailman-web_error.log I've got more info about the issue. It was permission error: ValueError: Unable to configure handler 'file': [Errno 13] Permission denied: '/var/log/mailman-web/mailman-web.log' After I corrected permissions for log file mentioned I can access Postorius and Hyperkitty. Everything looks working, I will test in more details later. Thanks! Danil From danil at smirnov.la Fri May 29 23:58:30 2015 From: danil at smirnov.la (Danil Smirnov) Date: Sat, 30 May 2015 00:58:30 +0300 Subject: [Mailman-Developers] Recipient address rejected: User unknown in virtual alias table Message-ID: Now I have working Postorius and I can subscribe myself to the test list and get the welcome message (with incorrect urls in it!). But I could not post to the list or mail to the list owner from outside: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table I've checked postfix/main.cf and everything looks right in it. Also I've ensured that var/data/*.db files are world-readable. Selinux is disabled. How could I debug this error? Thanks, Danil From barry at list.org Sat May 30 00:21:44 2015 From: barry at list.org (Barry Warsaw) Date: Fri, 29 May 2015 18:21:44 -0400 Subject: [Mailman-Developers] Recipient address rejected: User unknown in virtual alias table In-Reply-To: References: Message-ID: <20150529182144.553e6182@anarchist.wooz.org> On May 30, 2015, at 12:58 AM, Danil Smirnov wrote: >Now I have working Postorius and I can subscribe myself to the test >list and get the welcome message (with incorrect urls in it!). Known bug! The default templates actually need to be updated to not include those urls, because the core doesn't know what those urls would be. There is machinery to allow for two levels of indirection so that, e.g. url-containing templates could be defined in Postorius, and the core would fetch the on demand, but that needs to be fleshed out a bit more (and will be in MM3.1). >But I could not post to the list or mail to the list owner from outside: > >550 5.1.1 : Recipient address rejected: User >unknown in virtual alias table > >I've checked postfix/main.cf and everything looks right in it. >Also I've ensured that var/data/*.db files are world-readable. >Selinux is disabled. > >How could I debug this error? It sounds like a Postfix problem, so cranking up Postfix logging is probably going to be the most fruitful avenue. Cheers, -Barry From danil at smirnov.la Sat May 30 08:02:21 2015 From: danil at smirnov.la (Danil Smirnov) Date: Sat, 30 May 2015 09:02:21 +0300 Subject: [Mailman-Developers] Recipient address rejected: User unknown in virtual alias table In-Reply-To: <20150529182144.553e6182@anarchist.wooz.org> References: <20150529182144.553e6182@anarchist.wooz.org> Message-ID: 2015-05-30 1:21 GMT+03:00 Barry Warsaw : > It sounds like a Postfix problem, so cranking up Postfix logging is probably > going to be the most fruitful avenue. I understand this, of course this is the postfix issue, I see the error in maiillog: May 30 00:50:03 host postfix/smtpd[5062]: NOQUEUE: reject: RCPT from mail-wg0-f46.google.com[74.125.82.46]: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table; from= to= proto=ESMTP helo= But I have everything required by installation manual in the main.conf so I have no idea what going wrong and how to debug this wrong alias problem. Any advice? Danil From danil at smirnov.la Sat May 30 08:09:26 2015 From: danil at smirnov.la (Danil Smirnov) Date: Sat, 30 May 2015 09:09:26 +0300 Subject: [Mailman-Developers] Recipient address rejected: User unknown in virtual alias table In-Reply-To: References: <20150529182144.553e6182@anarchist.wooz.org> Message-ID: 2015-05-30 9:02 GMT+03:00 Danil Smirnov : > But I have everything required by installation manual in the main.conf > so I have no idea > what going wrong and how to debug this wrong alias problem. Found postfix misconfiguration. Have no relation to Mailman 3. Just forget about this. Danil From danil at smirnov.la Sat May 30 08:33:06 2015 From: danil at smirnov.la (Danil Smirnov) Date: Sat, 30 May 2015 09:33:06 +0300 Subject: [Mailman-Developers] can not post to the list Message-ID: I have Mailman 3 installed and Postorius and Hyperkitty seemingly working. I can subscribe, get welcome message and when I send message to the list it appears in held messages. Then when I accept the message, it does not come into the list and does not appear in the archives. Here what I found in the logs: --- May 30 09:15:30 2015 (2247) held message approved, message-id: May 30 09:15:30 2015 (2247) 127.0.0.1 - - "POST /3.0/lists/test at domain.tld/held/2 HTTP/1.1" 204 0 May 30 09:15:30 2015 (2247) 127.0.0.1 - - "GET /3.0/lists/test.domain.tld HTTP/1.1" 200 303 May 30 09:15:30 2015 (2247) 127.0.0.1 - - "GET /3.0/lists/test at domain.tld/held HTTP/1.1" 200 90 May 30 09:15:31 2015 (2243) Uncaught runner exception: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')) May 30 09:15:31 2015 (2243) Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 544, in urlopen body=body, headers=headers) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 349, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/local/lib/python3.4/http/client.py", line 1088, in request self._send_request(method, url, body, headers) File "/usr/local/lib/python3.4/http/client.py", line 1126, in _send_request self.endheaders(body) File "/usr/local/lib/python3.4/http/client.py", line 1084, in endheaders self._send_output(message_body) File "/usr/local/lib/python3.4/http/client.py", line 922, in _send_output self.send(msg) File "/usr/local/lib/python3.4/http/client.py", line 857, in send self.connect() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 155, in connect conn = self._new_conn() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 134, in _new_conn (self.host, self.port), self.timeout, **extra_kw) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 88, in create_connection raise err File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 78, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/adapters.py", line 370, in send timeout=timeout File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 597, in urlopen _stacktrace=sys.exc_info()[2]) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/retry.py", line 245, in increment raise six.reraise(type(error), error, _stacktrace) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/packages/six.py", line 309, in reraise raise value.with_traceback(tb) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 544, in urlopen body=body, headers=headers) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 349, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/local/lib/python3.4/http/client.py", line 1088, in request self._send_request(method, url, body, headers) File "/usr/local/lib/python3.4/http/client.py", line 1126, in _send_request self.endheaders(body) File "/usr/local/lib/python3.4/http/client.py", line 1084, in endheaders self._send_output(message_body) File "/usr/local/lib/python3.4/http/client.py", line 922, in _send_output self.send(msg) File "/usr/local/lib/python3.4/http/client.py", line 857, in send self.connect() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 155, in connect conn = self._new_conn() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 134, in _new_conn (self.host, self.port), self.timeout, **extra_kw) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 88, in create_connection raise err File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 78, in create_connection sock.connect(sa) requests.packages.urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 165, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 258, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/pipeline.py", line 41, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/pipelines.py", line 62, in process handler.process(mlist, msg, msgdata) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 123, in process process(mlist, msg, msgdata) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 89, in process archiver.system_archiver.list_url(mlist)) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py", line 101, in list_url return self._get_url({"mlist": mlist.fqdn_listname}) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py", line 82, in _get_url result = requests.get(url, params=params) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/api.py", line 69, in get return request('get', url, params=params, **kwargs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/api.py", line 50, in request response = session.request(method=method, url=url, **kwargs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/sessions.py", line 465, in request resp = self.send(prep, **send_kwargs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/sessions.py", line 573, in send r = adapter.send(request, **kwargs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/requests/adapters.py", line 415, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')) --- I don't understand what particular 'connection' mentioned, please advice. Thanks, Danil