Mailman 3 June 2015 - Mailman-Developers

Update 2.0 - Creating threads to handle dynamic list
by Stephen J. Turnbull 04 Jun '15

04 Jun '15

Hi all, I'll get to reviewing Pranjal's blog post later tonight; anybody who's going to be working on it (especially Terri), you might want to wait on mine so we don't duplicate. Steve

1 0

GSOC - Mailman Client in JS update
by Ankush Sharma 03 Jun '15

03 Jun '15

Hey, I have wrote a blog post regarding my work on the project till date. Interested people can have a look. Link : http://black-perl.me/black-perl-gsoc-with-mailman-week-i Thanks, Ankush Sharma

1 0

Re: [Mailman-Developers] can not post to the list
by Danil Smirnov 03 Jun '15

03 Jun '15

Could you please be more specific with this "activate Hyperkytty on ..."? Link to the manual would be okay... (Sorry for the topposting). 03.06.2015 11:18 пользователь "Aurelien Bompard" <aurelien(a)bompard.org> написал: > > Probably last one is because of misconfiguration of > > api_key: SecretArchiverAPIKey ? > > If the first URL does not match, it means that HyperKitty is not > activated in the virtualhost for 127.0.0.1. > You should get a message in HyperKitty's logs stating that the > connection was refused because the IP address is not allowed. > You have two options: > - activate HyperKitty for 127.0.0.1 > - in HyperKitty's settings file (production.py), edit the > MAILMAN_ARCHIVER_FROM variable to allow you local IP. This IP address > must not change. > > Aurélien > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)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.… > > Security Policy: http://wiki.list.org/x/QIA9

1 0

Re: [Mailman-Developers] can not post to the list
by Aurelien Bompard 03 Jun '15

03 Jun '15

> Probably last one is because of misconfiguration of > api_key: SecretArchiverAPIKey ? If the first URL does not match, it means that HyperKitty is not activated in the virtualhost for 127.0.0.1. You should get a message in HyperKitty's logs stating that the connection was refused because the IP address is not allowed. You have two options: - activate HyperKitty for 127.0.0.1 - in HyperKitty's settings file (production.py), edit the MAILMAN_ARCHIVER_FROM variable to allow you local IP. This IP address must not change. Aurélien

1 0

Update 2.0 - Creating threads to handle dynamic list
by Pranjal Yadav 02 Jun '15

02 Jun '15

After adding "dlist_enabled" attribute to mailing list object and adding relevant doctest and unittest, the most important part of the dlist project is threads. I have talked about all the details including introduction, implementation, requirements and the code in my blog. Its in initial stage so everything is not working yet, however I'm planning to finish this implementation along with tests by next weekend. I need your reviews on the blog to better understand problems (if any) in the implementation. I'm also updating everything on daily basis in my gitlab repo which is also mentioned below along with the blog. Blog: prany.github.io code: giitlab.com/godricglow/mailman PS: A lot of details regarding message table, member and subscription model etc are missing from this blog and will be updated in the coming blog by weekend. -- cheers *Pranjal Yadav (PranY)*

1 0

Re: [Mailman-Developers] can not post to the list
by Danil Smirnov 01 Jun '15

01 Jun '15

2015-06-01 12:27 GMT+03:00 Aurelien Bompard <aurelien(a)bompard.org>: > That's Mailman core trying to talk to HyperKitty over http to get the > list archives URL. The URL it's trying to reach is set in the > "deployment/mailman-hyperkitty.cfg". > My guess is that you need to update it because if HyperKitty is > running under Apache, the port is no longer 8000, it's 80 (so you can > remove it from the URL). > If that's the problem, I'll update the README file. Thanks, Aurelien. I tried two variants in mailman-hyperkitty.cfg: base_url: http://127.0.0.1/archives ---------- Jun 01 21:15:55 2015 (17357) held message approved, message-id: <CAMrrXbrjXySQCuW21zOSMrV=HfYPqoDDx95jM-kexZqiDcsWHg(a)mail.gmail.com> Jun 01 21:15:55 2015 (17357) 127.0.0.1 - - "POST /3.0/lists/test(a)domain.tld/held/6 HTTP/1.1" 204 0 Jun 01 21:15:56 2015 (17364) HyperKitty failure on http://127.0.0.1/archives/api/mailman/urls: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /archives/api/mailman/urls was not found on this server.</p> </body></html> (404) Jun 01 21:15:56 2015 (17364) HyperKitty failure on http://127.0.0.1/archives/api/mailman/urls: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /archives/api/mailman/urls was not found on this server.</p> </body></html> (404) Jun 01 21:15:56 2015 (17365) HyperKitty failure on http://127.0.0.1/archives/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /archives/api/mailman/archive was not found on this server.</p> </body></html> (404) Jun 01 21:15:56 2015 (17365) Broken archiver: hyperkitty Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/archive.py", line 107, in _dispose archiver.system_archiver.archive_message(mlist, msg_copy) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py", line 132, in archive_message raise ValueError(result.text) ValueError: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /archives/api/mailman/archive was not found on this server.</p> </body></html> ---------- base_url: http://lists.domain.tld/archives ---------- Jun 01 21:09:54 2015 (17357) held message approved, message-id: <CAMrrXbqtf2d-5baBmQ3dMVh34XWUKsAQkDtKotzwmVtB5DDJpw(a)mail.gmail.com> Jun 01 21:09:54 2015 (17357) 127.0.0.1 - - "POST /3.0/lists/test(a)domain.tld/held/5 HTTP/1.1" 204 0 Jun 01 21:09:55 2015 (17357) 127.0.0.1 - - "GET /3.0/lists/test.domain.tld HTTP/1.1" 200 303 Jun 01 21:09:55 2015 (17357) 127.0.0.1 - - "GET /3.0/lists/test(a)domain.tld/held HTTP/1.1" 200 90 Jun 01 21:09:55 2015 (17364) HyperKitty failure on http://lists.domain.tld/archives/api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1></body></html> (403) Jun 01 21:09:55 2015 (17364) HyperKitty failure on http://lists.domain.tld/archives/api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1></body></html> (403) Jun 01 21:09:56 2015 (17365) HyperKitty failure on http://lists.domain.tld/archives/api/mailman/archive: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1></body></html> (403) Jun 01 21:09:56 2015 (17365) Broken archiver: hyperkitty Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/archive.py", line 107, in _dispose archiver.system_archiver.archive_message(mlist, msg_copy) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty/__init__.py", line 132, in archive_message raise ValueError(result.text) ValueError: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1></body></html> ---------- Probably last one is because of misconfiguration of api_key: SecretArchiverAPIKey ? What should I put here? Danil

1 0

Re: [Mailman-Developers] mailman 3: http vs https
by Danil Smirnov 01 Jun '15

01 Jun '15

2015-06-01 17:23 GMT+03:00 Aurelien Bompard <aurelien(a)bompard.org>: > If you don't want to use HTTPS, there's a USE_SSL variable in the > Django settings file that you need to set to False. Thanks, this works.

1 0

Re: [Mailman-Developers] mailman 3: http vs https
by Aurelien Bompard 01 Jun '15

01 Jun '15

> 2) To get rid of https. > > I choose last option and have moved Mailman 3 config lines to :80 > virtualhost, commented redirection too. > > Now I can see Postorius and Hyperkitty on http connection but I can't > login - I've been redirecting to https pages right after login, which > are not accessible. If you don't want to use HTTPS, there's a USE_SSL variable in the Django settings file that you need to set to False. Otherwise, HyperKitty and Postorius will try to redirect you to HTTPS on the login page and when you're logged in to prevent credentials and session theft. Aurélien

1 0

mailman 3: http vs https
by Danil Smirnov 01 Jun '15

01 Jun '15

Please help I've got in troubles with http/https schemes of the Postorious/Hyperkitty. Initially I configured Mailman 3 in :443 virtualhost section of subdomain lists.domaint.tld with automatic redirection from :80 by mod_rewrite. I could access pages with https scheme. Then I noticed that my SSL-certificate doesn't allow wildcard-subdomains. I saw two options here: 1) To use a folder on main domain.tld instead of subdomain which does not looks like a great idea because of Hyperkitty somehow control robots.txt file which is domain-wide, not folder-wide. 2) To get rid of https. I choose last option and have moved Mailman 3 config lines to :80 virtualhost, commented redirection too. Now I can see Postorius and Hyperkitty on http connection but I can't login - I've been redirecting to https pages right after login, which are not accessible. The worst thing is that if I move Mailman 3 lines back to :443 virtualhost section, I got unbelievable redirect from https site to http one which was never configured! So I messed up completely. Danil p.s. I use 'Forget about site' feature of Firefox browser and check with Chrome so it's unlikely a cache issue.

1 0

Re: [Mailman-Developers] right adding of mailman 3 conf lines to httpd.conf
by Danil Smirnov 01 Jun '15

01 Jun '15

2015-06-01 12:17 GMT+03:00 Aurelien Bompard <aurelien(a)bompard.org>: > > Ah, right, the fact that you have to create the directory and set the > permissions for the production setup was not added in the README file. > I'll fix that. > I'm however surprised that you didn't get the error in your Apache > logs without uncommenting the ErrorLog directive. Do you have anything > in your apache error log? Thanks Aurelien! I've checked one more time - no, I have nothing related to the issue in httpd logs. Danil

1 0