July 2018 - Mailman-users - lists.mailman3.org

Re: [Mailman-Developers] Container Images for Mailman 3.2 release
by Abhilash Raj July 27, 2018

July 27, 2018

On Fri, Jul 27, 2018, at 1:16 PM, Kamran Soomro wrote: > Hi Abhilash, > > This is great. Thank you very much. Might I make a small suggestion? I > think it might be less confusing to use tags for your images that > conform to the mailman release. E.g. 3.2 should contain mailman 3.2, 3.3 > should contain mailman 3.3 etc. At the moment it’s hard to tell which > image contains which release. Sounds like a good idea! I will push 3.2 tags as soon as I can! > > Just my two cents. > > –Kamran > > > On 27 Jul 2018, at 21:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > Hi All, > > > > I have updated and pushed releases for Container Images with 3.2 release of the suite. > > > > They are available at: > > > > docker.io/maxking/mailman-web:0.2 > > docker.io/maxking/mailman-core:0.2 > > > > A similar copy of both is also available at quay: > > > > quay.io/maxking/mailman-web:0.2 > > quay.io/maxking/mailman-core:0.2 > > > > The releases contain the following versions of components: > > > > mailman-core: > > - Mailman Core 3.2.0 > > - Mailman-hyperkitty 1.1.0 > > > > mailman-web: > > - Postorius 1.2.1 > > - Hyperkitty 1.2.0 > > - Django-mailman3 1.2.0 > > - MailmanClient 3.2.0 > > > > The upgrade process from 0.1 release should be relative painless, except for the full-text index, which needs to be rebuilt due to the migration from Python 2 to 3 of the full-text indexing library whoosh. You can run the following commands to do so, after the upgrade: > > > > $ docker exec -it mailman-web bash > > bash # python manage.py rebuild_index > > > > If you are not using the default docker-compose.yaml file provided in the repo, you need to add an extra environment variable for mailman-web container, POSTORIUS_TEMPLATE_BASE_URL, which defaults to `http://mailman-web:8000`. It should be the URL where your mailman-web container is listening on with HTTP (port 8000 by default). > > > > The rolling releases are not being rolled out right everyday now, because of broken build scripts. I'd recommend everyone use the new stable releases that I mentioned above. Going forward, I'll try to release stable versions more often, so that there isn't any need for rolling version, but fixing the rolling releases is on my TODO. > > > > Documentation for these images is available at: > > > > https://github.com/maxking/docker-mailman > > > > -- > > thanks, > > Abhilash Raj (maxking) > > _______________________________________________ > > Mailman-Developers mailing list -- mailman-developers(a)python.org > > To unsubscribe send an email to mailman-developers-leave(a)python.org > > https://mail.python.org/mm3/mailman3/lists/mailman-developers.python.org/ > > Mailman FAQ: https://wiki.list.org/x/AgA3 > > > > Security Policy: https://wiki.list.org/x/QIA9 -- thanks, Abhilash Raj (maxking)

1 0

Container Images for Mailman 3.2 release
by Abhilash Raj July 27, 2018

July 27, 2018

Hi All, I have updated and pushed releases for Container Images with 3.2 release of the suite. They are available at: docker.io/maxking/mailman-web:0.2 docker.io/maxking/mailman-core:0.2 A similar copy of both is also available at quay: quay.io/maxking/mailman-web:0.2 quay.io/maxking/mailman-core:0.2 The releases contain the following versions of components: mailman-core: - Mailman Core 3.2.0 - Mailman-hyperkitty 1.1.0 mailman-web: - Postorius 1.2.1 - Hyperkitty 1.2.0 - Django-mailman3 1.2.0 - MailmanClient 3.2.0 The upgrade process from 0.1 release should be relative painless, except for the full-text index, which needs to be rebuilt due to the migration from Python 2 to 3 of the full-text indexing library whoosh. You can run the following commands to do so, after the upgrade: $ docker exec -it mailman-web bash bash # python manage.py rebuild_index If you are not using the default docker-compose.yaml file provided in the repo, you need to add an extra environment variable for mailman-web container, POSTORIUS_TEMPLATE_BASE_URL, which defaults to `http://mailman-web:8000`. It should be the URL where your mailman-web container is listening on with HTTP (port 8000 by default). The rolling releases are not being rolled out right everyday now, because of broken build scripts. I'd recommend everyone use the new stable releases that I mentioned above. Going forward, I'll try to release stable versions more often, so that there isn't any need for rolling version, but fixing the rolling releases is on my TODO. Documentation for these images is available at: https://github.com/maxking/docker-mailman -- thanks, Abhilash Raj (maxking)

1 0

Double footer
by Asaf Ohayon July 23, 2018

July 23, 2018

Hello Upon a clean installation of Mailman 3.2.0a1, Without any additional configuration, nor custom footers, When accepting message from the list on Gmail client for example, The footer shows twice, also in the message source I see two identical footer parts, accept for the message barrier: --===============4363779446011731395== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Info mailing list -- info(a)mailman.sysbind.biz To unsubscribe send an email to info-leave(a)mailman.sysbind.biz --===============4363779446011731395== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Info mailing list -- info(a)mailman.sysbind.biz To unsubscribe send an email to info-leave(a)mailman.sysbind.biz --===============4363779446011731395==--

3 4

Migrating from SQLite to PostgreSQL
by Joe Steeve July 20, 2018

July 20, 2018

Hello All, I have an installation on SQLite. I want to migrate it to PostgreSQL. Is that feasible? Any gotchas I need to watch for? -- Joe Steeve HiPro IT Solutions Private Limited http://www.hipro.co.in/

6 8

Creating a new list using REST from the host
by Henrik Rasmussen July 18, 2018

July 18, 2018

I am using Docker-mailman (GNU Mailman 3.2.0a1), but from the host I am trying to create a list using the REST API in the (yet, no offense) lack of a template for new list configurations. I get a nice dictionary when getting data out of Mailman, but using this exact dictionary (for debug) as payload to Mailman (my mmapiwrite), and with reference to https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/lists.html#c…, I get a response "A server error occurred. Please contact the administrator.". I don't understand the dump_json and I find the docs above hard to follow. How should I create the list using REST? <code> restapiversion = '3.1' def getlistdefaultsx(): # Exact output from Mailman, see below. listdefaultsx = { 'acceptable_aliases': [], 'admin_immed_notify': True, 'admin_notify_mchanges': False, 'administrivia': True, [SNIP] 'subscription_policy': 'confirm_then_moderate', 'volume': 1} return(listdefaultsx) def get_all_list_names(): all_list_fqdn = [] response = mmapi('lists?count=10&page=1') output = response.json() for entry in output.get('entries'): all_list_fqdn.append(entry.get('fqdn_listname')) return(all_list_fqdn) def addlist(): list_setup = getlistdefaultsx() go_create_list('abc', list_setup) def go_create_list(list_name_fqdn, list_setup): #pprint(list_setup) print('Creating list %s ...' % list_name_fqdn) response = mmapiwrite('lists', list_setup) def mmapi(apicommand): response = requests.get('http://172.19.199.2:8001/%s/%s' % (restapiversion, apicommand), auth=('restadmin', 'restpass')) def mmapiwrite(apicommand,payload): response = requests.post('http://172.19.199.2:8001/%s/%s' % (restapiversion, apicommand), data=payload, auth=('restadmin', 'restpass')) getlistdefaultsx is an actual dictionary with real output from Mailman using my mmapi from an existing test list (though domain names are masked. Of course I can't create an existing list, but when changing the list name I get the same error message. {'acceptable_aliases': [], 'admin_immed_notify': True, 'admin_notify_mchanges': False, 'administrivia': True, 'advertised': True, 'allow_list_posts': True, 'anonymous_list': False, 'archive_policy': 'never', 'autorespond_owner': 'none', 'autorespond_postings': 'none', 'autorespond_requests': 'none', 'autoresponse_grace_period': '90d', 'autoresponse_owner_text': '', 'autoresponse_postings_text': '', 'autoresponse_request_text': '', 'bounces_address': 'hertest2-bounces(a)example.ku.dk', 'collapse_alternatives': True, 'convert_html_to_plaintext': False, 'created_at': '2018-03-19T14:19:49.018252', 'default_member_action': 'defer', 'default_nonmember_action': 'hold', 'description': 'Test-domæne for Mailman 3-testlister', 'digest_last_sent_at': None, 'digest_send_periodic': True, 'digest_size_threshold': 30.0, 'digest_volume_frequency': 'monthly', 'digests_enabled': True, 'display_name': 'Hertest2', 'dmarc_mitigate_action': 'no_mitigation', 'dmarc_mitigate_unconditionally': False, 'dmarc_moderation_notice': '', 'dmarc_wrapped_message_text': '', 'filter_content': False, 'first_strip_reply_to': False, 'fqdn_listname': 'hertest2(a)example.ku.dk', 'http_etag': '"987dfgf8g569fvfd6v7"', 'include_rfc2369_headers': True, 'info': '', 'join_address': 'hertest2-join(a)example.ku.dk', 'last_post_at': None, 'leave_address': 'hertest2-leave(a)example.ku.dk', 'list_name': 'hertest2', 'mail_host': 'example.ku.dk', 'max_message_size': 40, 'moderator_password': None, 'next_digest_number': 1, 'no_reply_address': 'noreply(a)example.ku.dk', 'owner_address': 'hertest2-owner(a)example.ku.dk', 'post_id': 1, 'posting_address': 'hertest2(a)example.ku.dk', 'posting_pipeline': 'default-posting-pipeline', 'reply_goes_to_list': 'no_munging', 'reply_to_address': '', 'request_address': 'hertest2-request(a)example.ku.dk', 'send_welcome_message': True, 'subject_prefix': '[Hertest2] ', 'subscription_policy': 'confirm_then_moderate', 'volume': 1} </code>

2 1

Upgrading from 3.1 to 3.2
by Joe Steeve July 18, 2018

July 18, 2018

Hello All, I have a 3.1 installation. I want to upgrade to 3.2. Has anyone attempted this? Any gotchas I need to be aware of? -- Joe Steeve HiPro IT Solutions Private Limited http://www.hipro.co.in/

2 2

Mail configuration
by Darren Smith July 14, 2018

July 14, 2018

I'm not sure if this is the correct forum for this question, but I'm pretty sure if there is expertise on how to do what I want to do, it can be found here. Overview of what I am looking to do: Due to the impending shutdown (in the next 6 months) of the data center where our mailman server lives, we are being forced to move the installation. We are going to be moving it to a different location. Here is our problem... Moving things is not really a problem in and of itself - I'm confident that I can get things set up correctly elsewhere. However, our email server sends somewhere around 100,000 emails per day, and if you cut over from one IP address to another IP address, my understanding is that most ISPs will start to ban you, because they are not used to that sort of volume coming from an unknown IP. I know it would be better if we could keep the IP address, but again, due to circumstances beyond my control, this is not going to be a possibility. We have been told that "warming up" the IP is the way to go - that is, cutting over just some of the traffic a little at a time. So what I am looking for is a way for all mail on our domain to be sent to our current mailman installation, and based on some configuration (certain mailing lists?) certain emails being sent out to the list subscribers will first be forwarded to the new server and be sent from the new IP address. Does that make sense? Does anyone know a way that mailman/postfix can be configured to accomplish this? Is there a different forum where I might be able to ask experts about this? Thanks, -Darren

5 6

Triaging message non-receipt
by Eric Abrahamsen July 13, 2018

July 13, 2018

I've got a very small list (five members) for the management of a charitable organization, and we're having trouble with intermittent message delivery failure. I was running all the mailman related packages at git master from maybe two months ago, and updated everything to master again when I saw the announcement about version 3.2. Two of our subscribers intermittently don't receive emails sent to the list by the other. One is using Gmail, the other Yahoo, and they confirm that messages are not being shunted into spam folders. It happens only occasionally: apparently nearly half the messages don't go through. The rest of us get all the messages, including all sent by these two. All messages are correctly archived in hyperkitty. smtp.log always shows "for 5 recips", even for the messages that the two users aren't getting. These two users only ever miss messages sent by the other. I'm still inclined to blame Gmail and/or Yahoo, though I don't know why they would be swallowing only messages from the other, and not from other list members. Is there any way to get a better sense of where things are going wrong? Turn up the logging verbosity? Send test messages? Get more diagnostics? If anyone has any suggestions (or if this situation sounds familiar to anyone) I would love to hear about it. Thanks, Eric

2 2

Mailman3 Issue
by Danny Weddle July 13, 2018

July 13, 2018

For some weird reason, the file /mailman/var/data/postfix_domains has a whitespace added to every mail domain. I checked the postfix main.cf file for any white spaces, but did not see any. I get errors every time that I try to add a list. The console shows whitespace " example.org" in the list. The web page shows: Environment: Request Method: GET Request URL: http://172.16.11.235/postorius/lists/list11.mail.example2.com/ Django Version: 2.0.5 Python Version: 3.6.5 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', 'allauth.socialaccount.providers.twitter', 'allauth.socialaccount.providers.stackexchange') Installed Middleware: ['django.middleware.security.SecurityMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware'] Traceback: File "/usr/local/lib64/python3.6/site-packages/django/core/handlers/exception.py" in inner 35. response = get_response(request) File "/usr/local/lib64/python3.6/site-packages/django/core/handlers/base.py" in _get_response 128. response = self.process_exception_by_middleware(e, request) File "/usr/local/lib64/python3.6/site-packages/django/core/handlers/base.py" in _get_response 126. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib64/python3.6/site-packages/django/views/generic/base.py" in view 69. return self.dispatch(request, *args, **kwargs) File "/home/weddled/mailman/postorius/src/postorius/views/generic.py" in dispatch 57. return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib64/python3.6/site-packages/django/views/generic/base.py" in dispatch 89. return handler(request, *args, **kwargs) File "/home/weddled/mailman/postorius/src/postorius/views/list.py" in get 219. 'hyperkitty' in self.mailing_list.archivers and File "/usr/lib64/python3.6/_collections_abc.py" in __contains__ 666. self[key] File "/usr/local/lib/python3.6/site-packages/mailmanclient-3.2.0b1-py3.6.egg/mailmanclient/restbase/base.py" in __getitem__ 151. return self._get(key) File "/usr/local/lib/python3.6/site-packages/mailmanclient-3.2.0b1-py3.6.egg/mailmanclient/restbase/base.py" in _get 90. return self.rest_data[key] File "/usr/local/lib/python3.6/site-packages/mailmanclient-3.2.0b1-py3.6.egg/mailmanclient/restbase/base.py" in rest_data 76. response, content = self._connection.call(self._url) File "/usr/local/lib/python3.6/site-packages/mailmanclient-3.2.0b1-py3.6.egg/mailmanclient/restbase/connection.py" in call 103. raise HTTPError(url, response.status, content, response, None) During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: File "/usr/local/lib64/python3.6/site-packages/django/core/handlers/exception.py" in inner 35. response = get_response(request) File "/usr/local/lib64/python3.6/site-packages/django/utils/deprecation.py" in __call__ 95. response = self.get_response(request) File "/usr/local/lib64/python3.6/site-packages/django/core/handlers/exception.py" in inner 37. response = response_for_exception(request, exc) File "/usr/local/lib64/python3.6/site-packages/django/core/handlers/exception.py" in response_for_exception 87. response = handle_uncaught_exception(request, get_resolver(get_urlconf()), sys.exc_info()) File "/usr/local/lib64/python3.6/site-packages/django/core/handlers/exception.py" in handle_uncaught_exception 122. return debug.technical_500_response(request, *exc_info) File "/usr/local/lib64/python3.6/site-packages/django/views/debug.py" in technical_500_response 89. reporter = ExceptionReporter(request, exc_type, exc_value, tb) File "/usr/local/lib64/python3.6/site-packages/django/views/debug.py" in __init__ 254. self.template_info = getattr(self.exc_value, 'template_debug', None) File "/usr/lib64/python3.6/tempfile.py" in __getattr__ 477. file = self.__dict__['file'] Exception Type: KeyError at /postorius/lists/list11.mail.example2.com/ Exception Value: 'file'

3 10

Announcing Mailman Suite 3.2 release
by Abhilash Raj July 11, 2018

July 11, 2018

I am very pleased to announce the release of Mailman Suite 3.2. This includes Mailman Core 3.2.0, MailmanClient 3.2.0, Postorius 1.2.0, Django-Mailman3 1.2.0, Hyperkitty 1.2.0. This release includes tons of new features and bug fixes. We had support from tons of new contributors and I, on behalf of the whole Mailman Core team, would like to thank each one of you. Mailman Core includes support for plugins, more attributes exposed in REST API and improved support for migrating Mailman 2.x lists. You can now migrate settings and memberships from Mailman 2.x lists to Mailman 3.1. Full change log is available here: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#la-vill… Postorius, The New Mailman Web UI, now has more settings exposed. The most noteworthy of the features include Python 3.5+ support. Also, you can now set templates for headers, footers and automatic responses inside of Postorius. Full change log is available here: https://postorius.readthedocs.io/en/latest/news.html#id1 Hyperkitty, the next-generation mailing-list archiver, has also jumped on the Python 3.5+ wagon and supports all the latest and stable versions of Django. Importing archives from Mailman 2.x is now even more improved. Full change log is available here: https://hyperkitty.readthedocs.io/en/latest/news.html#id1 All the components can be downloaded from https://pypi.org. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. The Full documentation for the Suite is available at: http://docs.mailman3.org/en/latest/ For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ https://mirror.list.org/ -- thanks, Abhilash Raj (maxking)

4 4