- Mailman-users - lists.mailman3.org

ANNOUNCE: Mailman 3.1.0 final!
by Barry Warsaw May 26, 2017

May 26, 2017

Hello Mailpeople! On behalf of the entire team and all our wonderful contributors, I'm happy to announce the release of GNU Mailman 3.1 final. My deep thanks go to all the Mailman project sprinters at Pycon 2017 for getting us over the line! Two years after the original release of Mailman 3.0, this version contains a huge number of improvements across the entire stack. Many bugs have been fixed and new features added in the Core, Postorius (web u/i), and HyperKitty (archiver). Upgrading from Mailman 2.1 should be better too. We are seeing more production sites adopt Mailman 3, and we've been getting great feedback as these have rolled out. Important: mailman-bundler, our previous recommended way of deploying Mailman 3, has been deprecated. Abhilash Raj is putting the finishing touches on Docker images to deploy everything, and he'll have a further announcement in a week or two. Feedback is welcome: https://github.com/maxking/docker-mailman What is GNU Mailman? GNU Mailman is free software for managing electronic mail discussion and e-newsletter lists. Mailman is integrated with the web, making it easy for users to manage their accounts and for list owners to administer their lists. Mailman supports built-in archiving, automatic bounce processing, content filtering, digest delivery, and more. Mailman 3 is released under the terms of the GNU General Public License, version 3. The best places to start for all things related to this release: http://docs.mailman3.org/ http://www.list.org/ https://gitlab.com/mailman (Note: due to timezone skew, some of the tarballs may not be available on PyPI until tomorrow.) Happy Mailman Day, -Your friendly neighborhood cabal An overview of what's new in Mailman 3.1 ======================================== Feature parity with Mailman 2.1 ------------------------------- * You should be able to do just about everything that you could do in Mailman 2.1 *except* for topics and sibling/umbrella lists. Core ---- * Added support for Python 3.5 and 3.6 * MySQL is now an officially supported database * Many improvements with importing Mailman 2.1 lists * DMARC mitigations have been added, based on, but different than the same feature in Mailman 2.1 * The REST API requires HTTP/1.1 * A new REST API version (3.1) has been added which changes how UUIDs are interpreted, fixing the problem for some JavaScript libraries * Many new REST resources and methods have been added * Individual mailing lists can augment the system's header matching rules * `mailman create` now creates missing domains by default * `mailman digests` now has `--verbose` and `--dry-run` options * `mailman shell` now supports readline history * `mailman members` can filter members based on their subscription roles * A new template system has been added for all messages originating from inside Mailman. * The Message-ID-Hash header replaces X-Message-ID-Hash * New placeholders have been added for headers and footers * Unsubscriptions can now be confirmed and/or moderated Postorius/HyperKitty -------------------- * General U/I and U/X improvements * Many more features from the Core's have been plumbed through * We've adopted Django social auth logins and dropped Persona (since it's no longer supported upstream). You can now log in via Facebook, Google, GitHub, and GitLab. Backward incompatibilities -------------------------- * Core/REST: Held message resources now have an `original_subject` key that is not RFC 2047 decoded. `subject` is now RFC 2047 decoded. * Core/REST: If you've run pre-release versions from git head, and stored welcome and goodbye templates via REST, the template key names have changed backward incompatibility.

2 1

Multiple header_checks in mailman.cfg. How?
by Simon Liebold May 20, 2017

May 20, 2017

Hello, What is the correct syntax if I wanted to perform multiple header checks? header_checks: X-Spam: (yes|maybe) header_checks: x-another-header: (some|any)thing or: header_checks: X-Spam: (yes|maybe) x-another-header: (some|any)thing or: header_checks: ['X-Spam: (yes|maybe)', 'x-another-header: (some|any)thing'] Or something completely different? I don't think it is the first two because "mailman conf -s antispam" shows only a single header_checks. But the 3rd variant doesn't work either. Simon Hello, What is the correct syntax if I wanted to perform multiple header checks? header_checks: X-Spam: (yes|maybe) header_checks: x-another-header: (some|any)thing or: header_checks: X-Spam: (yes|maybe) x-another-header: (some|any)thing or: header_checks: ['X-Spam: (yes|maybe)', 'x-another-header: (some|any)thing'] Or something completely different? I don't think it is the first two because "mailman conf -s antispam" shows only a single h= eader_checks. But the 3rd variant doesn't work either. Simon

2 1

Character set for postorius
by David Krantz May 18, 2017

May 18, 2017

Hi, I'd like to have my descriptions of maillists with the correct characters for my languages... Where is the character set for this determined? If I input e.g. 'è' (è) or 'ö' (ö) it is substituted with a '?'. Of course the html entities are not allowed either, the ampersand '&' is escaped somewhere between output and input. Cheers // David

2 1

HyperKitty needs regis, really?
by Simon Liebold May 15, 2017

May 15, 2017

Hi I am seeing a whole bunch of error messages in mailmansuite.log whenever a new message is sent to be archived: ERROR 2017-05-14 15:41:41,261 13634 django.request Internal Server Error: /hyperkitty/api/mailman/archive ... File "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/redis/connection.py", line 442, in connect raise ConnectionError(self._error_message(e)) ConnectionError: Error 111 connecting to localhost:6379. Connection refused. I didn't see this mentioned anywhere. Does HyperKitty need a running regis server to work? What am I missing? Simon

2 2

So, why are css & js files only served with "DEBUG = yes" ?
by Simon Liebold May 7, 2017

May 7, 2017

Hello List, I did see this discussed in #180 <https://gitlab.com/mailman/postorius/issues/180>, but I didn't quite understand if this is an issue or not. Why is it that I can run the development server just fine. [07/May/2017 13:23:47] "GET /static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/css/style.css HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/django-mailman3/js/main.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/django-mailman3/css/main.css HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/js/script.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 304 0 And as soon as I comment out # SECURITY WARNING: don't run with debug turned on in production! # DEBUG = True in mailman-suite/mailman-suite_project/settings.py and restart it 404s on me. [07/May/2017 13:41:36] "GET /static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 404 127 [07/May/2017 13:41:36] "GET /static/django-mailman3/css/main.css HTTP/1.1" 404 109 [07/May/2017 13:41:36] "GET /static/postorius/css/style.css HTTP/1.1" 404 104 [07/May/2017 13:41:36] "GET /static/django-mailman3/js/main.js HTTP/1.1" 404 107 [07/May/2017 13:41:36] "GET /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 404 125 [07/May/2017 13:41:36] "GET /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 404 123 [07/May/2017 13:41:36] "GET /static/postorius/js/script.js HTTP/1.1" 404 103 [07/May/2017 13:41:36] "GET /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 404 123 So the choice is insecure vs. ugly? Neither of those sounds very tempting. I guess, I am missing something, or no? Simon

3 3

reason for breaching max_message_size is "N/A"
by David Krantz May 1, 2017

May 1, 2017

Hi. Today I learned to things: The default max_message_size is 40kB. Messages larger than that are blocked (expected) with the reason "N/A" (not expected). The reason would be helpful to me as admin. Also: Is there any way to set a server default for this as it is a bit of a hassle to change it from the command line for each new list. I can of course find where in the code to change but that seems the wrong way to me. Cheers // David

2 1

Any good ideas on how to troubleshoot django allauth
by David Krantz April 27, 2017

April 27, 2017

Hi again. Allauth works for me... sometimes... For google logins it works most of the time. For facebook it almost never works. When it does not work, I get an error page with the error "An error occurred while attempting to login via your social network account." (or the equivalent in my locale). If I then reload the page, I get logged in! In some cases I get the error and the little green popup saying that I am logged in at the same time. Strange. So... If there is any documentation for how to set up or how to troubleshoot django allauth I am all ears (eyes, really). I have tested the "missing howto..." and updated version of that without enough success. Cheers // David The only thing I find is in the Apache log: (I have removed all cryptovalues and other things that should be uninteresting to others) [LOCAL_IP] - - [19/Apr/2017:00:00:39 +0000] "GET /accounts/facebook/login/?process=login&next=%2Farchives%2F HTTP/1.1" 302 706 "https://lists.example.com/accounts/login/?next=/archives/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063" [LOCAL_IP] - - [19/Apr/2017:00:00:53 +0000] "GET /accounts/facebook/login/callback/?code=[LONG CRYPTO-LOOKING STRING] HTTP/1.1" 200 2129 "https://www.facebook.com/login/reauth.php?app_id=[MY_APP_ID_I_THINK]&signed…" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063"

3 5

Patch/kludge suggestion and a question on adding accepted addresses
by David Krantz April 25, 2017

April 25, 2017

Hi. I found out that I had a broken email in one of my held messages queues). That gave a HTTP 500 error although that should be fixed . After some digging I found out that where the error occured. I'd suggest adding a catch for AttributeError similar to the one for KeyError in _HeldMessageBase in rest/post_moderation.py. It solved my immediate problem at least. I run the version from git with the tag 263711b3b7988c7c474e3b8952dc7e0f02f04fa2 The message causing this was probably one where I had sent a minimal email via telnet to the SMTP port and forgot the MessageID-header or something similarily silly. But it prevented me from seeing the held messages-list in postorius. I have another question: In the old mailman you could add accepted senders without adding them to the list. Is that possible in Mailman 3/Postorius? cheers. // David

3 3

502 Bad Gateway??? Trying to change stuff
by am April 23, 2017

April 23, 2017

I am trying to change my email address, but forgot password. The screen for reset gets 502 Bad Gateway ------------------------------ nginx/1.4.6 (Ubuntu) any way someone can fix this????

2 2

Remove footer link
by David Terni April 23, 2017

April 23, 2017

Hi, I need to remove footer message like "to unsubscribe etc etc" from all lists. How i can do it or edit text? Thanks alot for any suggestion. David

2 1