Mailman 3 February 2016 - Mailman-Developers

Accessing the members of a list
by Aditya Divekar 23 Feb '16

23 Feb '16

Hi, This is in regard to postorius. Is there a way by which I can access all the members of a list using its 'list_id' in the list.py file with/without creating a new client? The approach I tried was creating a client in the list.py file for this purpose and calling on the 'members()' function from the Client class defined in client.py. The doubt I had here is that the members() function uses the self parameter to decide which list is being referred to. For this, I think I need to pass the exact url to the list I wish to search for as a parameter while creating the client and then call on the members() function on it. Here, how do I figure out the url for this purpose? Thanks! Aditya

1 0

Let's try to package mailman3 in Debian!
by Pierre-Elliott Bécue 22 Feb '16

22 Feb '16

Hey, As a Debian fanboy and also a mailman addict, I'd like to try packaging it in Debian. As I'm not a DD and as I'm not in a hurry, I'd like to take some time to think about what would be relevant. For that, I'd like to have some help. And I was suggested to come here and ask. I decided to use https://gitlab.com/groups/mailman as a basis for my work. First of all, to create the source package, I've to think about what to put in it. It seems that if I want to have a good source package, I need 5 repos : - Mailman - HyperKitty - Postorius - HyperKitty - MailMan Plugin - MailmanClient My first question is "Am I right?". And the second one is whould I consider looking into mailman-suite-doc and also have it in the source package? On another way, I also see that there is a standalone postorius repo and also some django project files for HyperKitty in another one. I have the impression it is more designed for people to work on as standalone - forkable projects for other features, and so I wouldn't need them in a Debian package. Am I also right? Thanks for your answer, I hope I'll be able to make this package look as you'd like. :) Cheers, -- PEB

5 13

Re: [Mailman-Developers] ARC module implementation [was: GSOC 2016]
by Stephen J. Turnbull 20 Feb '16

20 Feb '16

Aditya Divekar writes: > I have taken your suggestion, and started working on a separate > branch to generate the ams from the original dkimpy package. Student applications will be opening shortly. You should finish up anything that is in your head but not in a file soon, and start preparing your application. We will want to see a reviewable patch on the tracker as part of that application (it can be something trivial like a doc patch). Exactly what is required isn't set yet (most of us are also busy with PSF org admin details as well as Mailman stuff), but it won't be related to this project because this project is "too big" to seriously consider reviewing soon. And you don't have to worry about whether we get around to actually merging it; it just has to be in good enough shape to review. The scheduling part is important, and you probably haven't done anything like it before (scheduling a project you design is very different from picking classes from a course catalog!) Steve

1 0

Re: [Mailman-Developers] ARC module implementation [was: GSOC 2016]
by Stephen J. Turnbull 19 Feb '16

19 Feb '16

Aditya Divekar writes: > I have read through the dkimpy library functions and it seems that the code > needs to be modified to generate the ARC headers, and I have started making > some changes. I don't think it's a great idea to change the dkimpy library if you can avoid it. The design I had in mind would add a file for performing ARC operations such as generating fields, and for dkimpy to simply provide the functions for generating the signatures. This probably requires some refactoring of dkimpy. It might also require generalizing the canonicalization functions to handle the ARC-specific field sets if there are any hard-coded headers in the DKIM code. You might also look at the alternatives to see if they are better factored for this purpose. > I have hosted the code at github here. > <https://github.com/adityadivekar03/dkimpy>, I haven't done cross-host work before, but you will surely need a gitlab account eventually to file the merge request. I will try to take a look at the code over the weekend. I did want to make the comments on the factoring of the code ASAP, before you do too much work.

2 1

Re: [Mailman-Developers] can't login with Google/Yahoo (last mailman-bundler)
by Danil Smirnov 18 Feb '16

18 Feb '16

I'm sorry if it's not right place to ask for the support but there is no information regarding the issue in Google as well as mailman-dev/mailman-user lists. So I'm stale in the issue and have no idea what to do. If you can give me just a direction to dig, it would be very helpful... 2016-02-17 14:36 GMT+02:00 Danil Smirnov <danil(a)smirnov.la>: > I suspect I need to add my httpd configuration: > > --- > > <VirtualHost 1.2.3.4:80> > SuexecUserGroup "#500" "#500" > ServerName lists.domain.tld > ServerAlias www.lists.domain.tld > ServerAlias webmail.lists.domain.tld > ServerAlias admin.lists.domain.tld > DocumentRoot /home/mailman3/domains/lists.domain.tld/public_html > ErrorLog /var/log/virtualmin/lists.domain.tld_error_log > CustomLog /var/log/virtualmin/lists.domain.tld_access_log combined > ScriptAlias /cgi-bin/ /home/mailman3/domains/lists.domain.tld/cgi-bin/ > ScriptAlias /awstats/ /home/mailman3/domains/lists.domain.tld/cgi-bin/ > DirectoryIndex index.html index.htm index.php index.php4 index.php5 > <Directory /home/mailman3/domains/lists.domain.tld/public_html> > Options -Indexes +IncludesNOEXEC +SymLinksIfOwnerMatch +ExecCGI > allow from all > AllowOverride All > Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch > Require all granted > AddType application/x-httpd-php .php > AddHandler fcgid-script .php > AddHandler fcgid-script .php5 > FCGIWrapper /home/mailman3/domains/lists.domain.tld/fcgi-bin/php5.fcgi .php > FCGIWrapper /home/mailman3/domains/lists.domain.tld/fcgi-bin/php5.fcgi > .php5 > </Directory> > <Directory /home/mailman3/domains/lists.domain.tld/cgi-bin> > allow from all > AllowOverride All > Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch > Require all granted > </Directory> > RewriteEngine on > RewriteCond %{HTTP_HOST} =webmail.lists.domain.tld > RewriteRule ^(.*) https://lists.domain.tld:20000/ [R] > RewriteCond %{HTTP_HOST} =admin.lists.domain.tld > RewriteRule ^(.*) https://lists.domain.tld:10000/ [R] > RemoveHandler .php > RemoveHandler .php5 > php_admin_value engine Off > IPCCommTimeout 31 > FcgidMaxRequestLen 1073741824 > <Files awstats.pl> > AuthName "lists.domain.tld statistics" > AuthType Basic > AuthUserFile /home/mailman3/domains/lists.domain.tld/.awstats-htpasswd > require valid-user > </Files> > > # Here, use the value of the STATIC_ROOT variable in your Django > configuration file (production.py) > Alias /robots.txt /var/spool/mailman-web/static/hyperkitty/robots.txt > Alias /favicon.ico /var/spool/mailman-web/static/hyperkitty/favicon.ico > Alias /static /var/spool/mailman-web/static > <Directory "/var/spool/mailman-web/static"> > Order deny,allow > Allow from all > Require all granted > </Directory> > > #ErrorLog /var/log/httpd/mailman-web_error.log > #CustomLog /var/log/httpd/mailman-web_access.log combined > > WSGIScriptAlias / /usr/local/src/mailman-bundler/bin/mailman-web.wsgi > WSGIDaemonProcess mailman-web display-name=mailman-web > maximum-requests=1000 processes=4 threads=4 > python-path=/usr/local/src/venv/lib/python2.7/site-packages > > <Directory "/usr/local/src/mailman-bundler/bin"> > <Files mailman-web.wsgi> > Order deny,allow > Allow from all > Require all granted > </Files> > WSGIProcessGroup mailman-web > </Directory> > > </VirtualHost> > --- > > 2016-02-17 13:48 GMT+02:00 Danil Smirnov <danil(a)smirnov.la>: > >> Hi devs! >> >> I'm still need your advices... >> Now I have the following errors when trying to authenticate with Google >> or Yahoo: >> >> --- >> ERROR 2016-02-17 05:40:44,363 base 1690 139772999759616 Internal Server >> Error: /login/google/ >> Traceback (most recent call last): >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py", >> line 132, in get_response >> response = wrapped_callback(request, *callback_args, >> **callback_kwargs) >> File >> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/views/decorators/cache.py", >> line 57, in _wrapped_view_func >> response = view_func(request, *args, **kwargs) >> File >> "/usr/local/src/venv/lib/python2.7/site-packages/social/apps/django_app/utils.py", >> line 51, in wrapper >> return func(request, backend, *args, **kwargs) >> TypeError: auth() got an unexpected keyword argument 'SSL' >> --- >> >> Please advice how to manage this... >> >> Danil >> > >

1 0

Dropping Persona
by Simon Hanna 17 Feb '16

17 Feb '16

Hi, Mozilla is dropping Persona and shutting it down later this year [1]. Postorius and Hyperkitty will have to drop it, and use something else as a default login mechanism. I propose using the django authentication system by default and making it easy for people to add other authentication methods. If we go with django authentication we can either build everything ourselves (I did it for a couple of projects myself) or use some provided project. This is because django doesn't offer registration views and email confirmation. Also password changing and password resetting will have to be added. I know of two projects that do that already: django-user-accounts [2] It's part of the pinax platform, but can be used independently of the other components. It comes with everything we need and not much more. Note that the profiles of django-user-accounts can contain additional emails, which we probably don't want. It's officially supporting django 1.8 and 1.9. I'm not sure about our django dependency policy but since upstream has marked all pre 1.8 as being out of date, I think that we can move on as well... django-userena [3] Pretty much the same as django-user-accounts but it has additional "features" like messaging which we definitely don't need. It's not yet django 1.9 compatible but there is a merge request that adds support for it. Since we have two projects to maintain, I'd rather go with an external app. I guess it would be easiest to have exactly the same configurations for Postorius and Hyperkitty. In order to not duplicate any templates and other code, I'd propose to create a third project that has all the account functionality and put everything we need in there. In case we go with doing everything ourselves, I guess it's still better to create a separate app for that. My personal favorite is django-user-accounts for which I have some basic functionality in a merge request for Postorius so you can have a look at what needs to be changed. [4] Regardless of what approach we choose, we should also think of migrations. Existing internal django accounts can be easily migrated. We'll have to choose if we want to migrate the "social" accounts as well or just tell people to sign up again. We still have time for the transition, but I'd prefer dropping persona before the 3.1 release if that happens to come before the shutdown. What do you think? Simon [1]: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers [2]: https://github.com/pinax/django-user-accounts [3]: https://github.com/bread-and-pepper/django-userena [4]: https://gitlab.com/mailman/postorius/merge_requests/73

6 11

Re: [Mailman-Developers] can't login with Google/Yahoo (last mailman-bundler)
by Danil Smirnov 17 Feb '16

17 Feb '16

I suspect I need to add my httpd configuration: --- <VirtualHost 1.2.3.4:80> SuexecUserGroup "#500" "#500" ServerName lists.domain.tld ServerAlias www.lists.domain.tld ServerAlias webmail.lists.domain.tld ServerAlias admin.lists.domain.tld DocumentRoot /home/mailman3/domains/lists.domain.tld/public_html ErrorLog /var/log/virtualmin/lists.domain.tld_error_log CustomLog /var/log/virtualmin/lists.domain.tld_access_log combined ScriptAlias /cgi-bin/ /home/mailman3/domains/lists.domain.tld/cgi-bin/ ScriptAlias /awstats/ /home/mailman3/domains/lists.domain.tld/cgi-bin/ DirectoryIndex index.html index.htm index.php index.php4 index.php5 <Directory /home/mailman3/domains/lists.domain.tld/public_html> Options -Indexes +IncludesNOEXEC +SymLinksIfOwnerMatch +ExecCGI allow from all AllowOverride All Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch Require all granted AddType application/x-httpd-php .php AddHandler fcgid-script .php AddHandler fcgid-script .php5 FCGIWrapper /home/mailman3/domains/lists.domain.tld/fcgi-bin/php5.fcgi .php FCGIWrapper /home/mailman3/domains/lists.domain.tld/fcgi-bin/php5.fcgi .php5 </Directory> <Directory /home/mailman3/domains/lists.domain.tld/cgi-bin> allow from all AllowOverride All Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch Require all granted </Directory> RewriteEngine on RewriteCond %{HTTP_HOST} =webmail.lists.domain.tld RewriteRule ^(.*) https://lists.domain.tld:20000/ [R] RewriteCond %{HTTP_HOST} =admin.lists.domain.tld RewriteRule ^(.*) https://lists.domain.tld:10000/ [R] RemoveHandler .php RemoveHandler .php5 php_admin_value engine Off IPCCommTimeout 31 FcgidMaxRequestLen 1073741824 <Files awstats.pl> AuthName "lists.domain.tld statistics" AuthType Basic AuthUserFile /home/mailman3/domains/lists.domain.tld/.awstats-htpasswd require valid-user </Files> # Here, use the value of the STATIC_ROOT variable in your Django configuration file (production.py) Alias /robots.txt /var/spool/mailman-web/static/hyperkitty/robots.txt Alias /favicon.ico /var/spool/mailman-web/static/hyperkitty/favicon.ico Alias /static /var/spool/mailman-web/static <Directory "/var/spool/mailman-web/static"> Order deny,allow Allow from all Require all granted </Directory> #ErrorLog /var/log/httpd/mailman-web_error.log #CustomLog /var/log/httpd/mailman-web_access.log combined WSGIScriptAlias / /usr/local/src/mailman-bundler/bin/mailman-web.wsgi WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 processes=4 threads=4 python-path=/usr/local/src/venv/lib/python2.7/site-packages <Directory "/usr/local/src/mailman-bundler/bin"> <Files mailman-web.wsgi> Order deny,allow Allow from all Require all granted </Files> WSGIProcessGroup mailman-web </Directory> </VirtualHost> --- 2016-02-17 13:48 GMT+02:00 Danil Smirnov <danil(a)smirnov.la>: > Hi devs! > > I'm still need your advices... > Now I have the following errors when trying to authenticate with Google or > Yahoo: > > --- > ERROR 2016-02-17 05:40:44,363 base 1690 139772999759616 Internal Server > Error: /login/google/ > Traceback (most recent call last): > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py", > line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File > "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/views/decorators/cache.py", > line 57, in _wrapped_view_func > response = view_func(request, *args, **kwargs) > File > "/usr/local/src/venv/lib/python2.7/site-packages/social/apps/django_app/utils.py", > line 51, in wrapper > return func(request, backend, *args, **kwargs) > TypeError: auth() got an unexpected keyword argument 'SSL' > --- > > Please advice how to manage this... > > Danil >

1 0

can't login with Google/Yahoo (last mailman-bundler)
by Danil Smirnov 17 Feb '16

17 Feb '16

Hi devs! I'm still need your advices... Now I have the following errors when trying to authenticate with Google or Yahoo: --- ERROR 2016-02-17 05:40:44,363 base 1690 139772999759616 Internal Server Error: /login/google/ Traceback (most recent call last): File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/views/decorators/cache.py", line 57, in _wrapped_view_func response = view_func(request, *args, **kwargs) File "/usr/local/src/venv/lib/python2.7/site-packages/social/apps/django_app/utils.py", line 51, in wrapper return func(request, backend, *args, **kwargs) TypeError: auth() got an unexpected keyword argument 'SSL' --- Please advice how to manage this... Danil

1 0

Re: [Mailman-Developers] OfflineGenerationError after mailman-bundler install
by Danil Smirnov 17 Feb '16

17 Feb '16

The error was gone after several reconfigurations/reboots. Still have no idea what it was... 2016-02-17 12:22 GMT+02:00 Danil Smirnov <danil(a)smirnov.la>: > Sorry again, but the error returns after several page refresh - weird, but > it looks like not every opening of the page cause the error! > > 2016-02-17 12:12 GMT+02:00 Danil Smirnov <danil(a)smirnov.la>: > >> The error was fixed by bin/mailman-post-update, sorry. >> >> 2016-02-17 11:55 GMT+02:00 Danil Smirnov <danil(a)smirnov.la>: >> >>> Hi everybody! >>> >>> After installing last mailman-bundler I've got the following in the >>> Hyperkitty logs: >>> >>> ERROR 2016-02-17 03:42:03,804 base 1762 140633939375872 Internal Server >>> Error: /archives/ >>> Traceback (most recent call last): >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/core/handlers/base.py", >>> line 132, in get_response >>> response = wrapped_callback(request, *callback_args, >>> **callback_kwargs) >>> File >>> "/usr/local/src/venv/lib/python2.7/site-packages/hyperkitty/views/index.py", >>> line 76, in index >>> return render(request, "hyperkitty/index.html", context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/shortcuts.py", >>> line 67, in render >>> template_name, context, request=request, using=using) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/loader.py", >>> line 99, in render_to_string >>> return template.render(context, request) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/backends/django.py", >>> line 74, in render >>> return self.template.render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 210, in render >>> return self._render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 202, in _render >>> return self.nodelist.render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 905, in render >>> bit = self.render_node(node, context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 919, in render_node >>> return node.render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/loader_tags.py", >>> line 135, in render >>> return compiled_parent._render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 202, in _render >>> return self.nodelist.render(context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 905, in render >>> bit = self.render_node(node, context) >>> File >>> "/usr/local/src/mailman-bundler/eggs/Django-1.8.9-py2.7.egg/django/template/base.py", >>> line 919, in render_node >>> return node.render(context) >>> File >>> "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", >>> line 127, in render >>> return self.render_compressed(context, self.kind, self.mode, >>> forced=forced) >>> File >>> "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", >>> line 86, in render_compressed >>> return self.render_offline(context) >>> File >>> "/usr/local/src/venv/lib/python2.7/site-packages/compressor/templatetags/compress.py", >>> line 71, in render_offline >>> 'You may need to run "python manage.py compress".' % key) >>> OfflineGenerationError: You have offline compression enabled but key >>> "57d3e0fcad3f7e67ac65637e9475af43" is missing from offline manifest. You >>> may need to run "python manage.py compress". >>> >>> Please advice how to fix this error properly. >>> >>> Danil >>> >> >> >

1 0

ARC module implementation [was: GSOC 2016]
by Stephen J. Turnbull 17 Feb '16

17 Feb '16

Aditya Divekar writes: > According to the draft, here > <https://tools.ietf.org/html/draft-andersen-arc-00#section-5.2>, > the ARC-Seal header is constructed from the referenced message > signatures given by the "k" tag. I didn't understand this part > clearly. The "k" tag has been removed from the most recent version 02 (2016/02/08). Note: although I-Ds expire automatically after 6 months, they can be superseded by new versions at any time. Always check for a more recent version. The tools.ietf.org site is very nice because you can also get diffs to see what you missed (note that many URLs reference less fancy archives, so if you bookmark one of those it's useful to edit it to refer to a full-service site such as tools). > Do we need to specify the headers (i.e. the ARC-Message signature > and ARC-authentication results) that we want to seal in the "k" tag > just how we would use the "h" tag in the DKIM signature? Earlier drafts of the I-D were more than a little confusing here. I think it's much better now, but feel free to ask questions. The fields added by a particular mediator will be linked by the "i" tag, see I-D sec. 5.1.1.1.1, 5.1.2.2.3, and 5.1.3.1. Also, ARC signatures use the "h" tag in the same way as DKIM, except that the requirements for exactly which headers are are different. (This is intended to ensure that ARC headers, which by definition are *not* authorized by the sending domain, are not mistakenly used as DKIM signatures, which by definition *are* authorized by the sending domain. I'm not sure whether this makes sense, but OTOH I don't see how it can hurt.) Exactly which headers are signed in an ARC-Seal are fully specified by the protocol. > (The usage of the "k" tag isn't clear to me.) Mostly the protocol syntax and semantics of ARC are specified in RFC 6376 (see section 5.4 of the I-D). Selectors are defined in section 3.1. In the I-D, only the new ARC-Seal field is described in full. ARC-Message-Signature and ARC-Authentication-Results are described in terms of differences from the normative RFCs (RFC 6376 for signatures and RFC 7601 for authentication results). By the way, top-posting (especially without trimming) should be avoided in technical discussion. See http://turnbull.sk.tsukuba.ac.jp/Teach/ESES/socsys-1.html for the technical advantages and disadvantages of top-posting and interlinear styles. Also, note that in mature projects (and specifically Mailman and Python) most of the senior developers will be old enough to have been trained in and developed a preference for interlinear posting, and especially trimming. Nowadays untrimmed top-posts are hard to avoid so people are building up tolerance for them, but you can make friends by taking care with your posting style. Steve

2 1