[Mailman-Developers] Trying out mailman3 (docker recipe fails)
A community I'm part of is looking for a new mailing list solution, and I thought I'd look at where mailman 3 is up to these days. In the process I found that the instructions for firing up mailman 3.0 in docker aren't currently working. I followed the recipe at: https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile But it seems that it doesn't currently work. Error messages are as follow. There were earlier warnings about missing files, but the build seemed happy to ignore those. > Getting distribution for 'postorius==1.0.3'. > no previously-included directories found matching 'src/postorius/doc/_build' > zip_safe flag not set; analyzing archive contents... > postorius.doc.conf: module references __file__ > postorius.tests.__init__: module references __file__ > While: > Installing mailman-web. > Getting distribution for 'postorius==1.0.3'. > > An internal error occurred due to a bug in either zc.buildout or in a > recipe being used: > Traceback (most recent call last): > File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", > line 1982, in main > getattr(buildout, command)(args) > File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", > line 668, in install > installed_files = self[part]._call(recipe.install) > File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", > line 1419, in _call > return f() > File > "/mailman3/mailman-bundler/eggs/djangorecipe-2.2.1-py2.7.egg/djangorecipe/recipe.py", > line 82, in install > ws = self.egg.working_set(['djangorecipe'])[1] > File > "/mailman3/mailman-bundler/eggs/zc.recipe.egg-2.0.3-py2.7.egg/zc/recipe/egg/egg.py", > line 84, in working_set > allow_hosts=self.allow_hosts) > File > "/usr/local/lib/python2.7/dist-packages/zc/buildout/easy_install.py", > line 913, in install > return installer.install(specs, working_set) > File > "/usr/local/lib/python2.7/dist-packages/zc/buildout/easy_install.py", > line 665, in install > for dist in self._get_dist(requirement, ws): > File > "/usr/local/lib/python2.7/dist-packages/zc/buildout/easy_install.py", > line 563, in _get_dist > dists = [_move_to_eggs_dir_and_compile(dist, self._dest)] > File > "/usr/local/lib/python2.7/dist-packages/zc/buildout/easy_install.py", > line 1730, in _move_to_eggs_dir_and_compile > assert newdist is not None # newloc above is missing our dist?! > AssertionError Can someone help me identify the problem here? Alternatively, is there a better way for me to review where things are up to, and what the interface is like? I'll probably be approaching this as a sysadmin before long, but just now I'm looking for a list-admin and user perspective. When I get to hosting seriously, Docker is preferred. The environments I'm working in are moving towards Docker/kubernetes. Regards, Andrew ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Mailman 3 Project discussion
Hello, Hope you are doing well. My name is Manpreet Singh. I found the Mailman project quite interesting as I have been using linux from 2-3 years and I have quite good knowledge of python3 as I am doing projects on python since last year. I have started viewing issues on the official git lab repository of Mailman and I am trying to be familiar with code base and its work flow. My question is apart from this, on what areas of coding, team will be working on specifically which python library, framework etc for this project ? And do you want us to learn specifically new technology apart from python to successfully meet the requirements of this project ? ThanksManpreet SinghB.S. Software EngineeringSan Jose State University ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] In regard to GSoc-17
On Mar 06, 2017, at 07:11 PM, Stephen J. Turnbull wrote: >Python 2.7, Python 3.5 (both 2.7 and 3.5 are currently *required*), >plus Python 3.6 if you're adventurous (GNU Mailman 3 doesn't >officially support Python 3.6 yet) Note that 3.4 is also an officially supported version for core. Mailman 3.1 will -and current core git HEAD does- officially support 3.6. Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Discourse Integration
Vaibhav Lohani writes: > There was a mention of integrating mailman 3 with discourse some > times back. I am interested in working on it. Is someone else > interested in it or already working on it ? I don't know of anyone who is currently working on it, nor do we have specific plans at the moment. What sort of integration do you have in mind? Steve ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] In regard to GSoc-17
Hi, Apart from what Abhilash wrote, I have a few ;-) additional comments. Bhavishya writes: > Hi, I saw the idea to create various kinds of encrypted lists, > Could you elaborate the following: > 1)The amount of knowledge of security (and if possible the sources > to achieve the same) You need to understand what a "threat model" is, and the structure of a mailing list as a system to know what threats can be defended against, and to decide which threats to defend against. You need to understand how mailing lists and the mail system work in some detail, and what the use cases for encrypted lists might be. For self-study, you could start with Bruce Schneier's blog, especially his famous post on "the security mindset", and with Steve Bellovin's book, _Thinking Security_. Bellovin's book has many references. The core mail security RFCs are enumerated below. The code for various encryption algorithms is already available in the standard library (OpenSSL, for example, although a lot of people deprecate it) and in 3rd-party libraries on PyPI. Writing encryption modules is not part of this task. > 2)The development environment (what else is required apart from > linux) Python 2.7, Python 3.5 (both 2.7 and 3.5 are currently *required*), plus Python 3.6 if you're adventurous (GNU Mailman 3 doesn't officially support Python 3.6 yet), modules from PyPI as-needed. Your Python(s) must be built to support OpenSSL, or some other source of implementations for encryption algorithms. git. The Mailman Suite (the subprojects mailman, mailmanclient, django-mailman3, postorius, hyperkitty, mailman-hyperkitty) from http://gitlab.com/mailman. (Dependencies for the suite will be installed automatically by the setup.py for each component.) An MTA, either Postfix (most popular among Mailman core developers) or Exim4 (supported). Sendmail and Qmail may be usable but are not advised unless you can provide support for them yourself -- there is ZERO support in Mailman 3 itself. It may not be very hard to support a new MTA (it took me 10 minutes to configure Exim4 and 30 to write the docs), but you won't get much help from us. Why risk it? It would be nice if you have a test domain where you can install Mailman on the standard SMTP port 25 or submission port 587, but testing on localhost is acceptable. > 3)Any other task for me to strengthen my application(I would try > fixing bugs on my level though) Get an account on gitlab. Read the FAQ for Mailman 2, the archives for mailman-users, mailman-developers, and mailman3-users to get some idea of the level and needs of our users. Subscribe to those lists. Take a look at RFCs 5321 (SMTP), 5322 (Internet Message Format), 4949 (security glossary), and 5598 (email architecture). Bookmark them and RFCs 2045 (MIME), 2046 (MIME), 2387 (multipart/related), 2015 (MIME/PGP), 3156 (MIME/OpenPGP), 5751 (S/MIME), and 5752 (multiple signatures). I recommend reading all the way through RFC 4949, as a complement to Schneier's blog and Bellovin's book (or similar). RFC 5598 is very important, as it is fundamental to understanding the threat models involved in email and indirect flows including mailing lists. Read the abstracts and introductions to RFCs 5321 and 5322, as understanding the basic concepts of email are going to be very important. For the rest just bookmarking is fine. We would eventually be referring to them in the implementation most likely, but you don't need to be totally familiar for the application. Steve ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
