- Mailman-users - lists.mailman3.org

Implicit destination
by David Krantz Aug. 28, 2018

Aug. 28, 2018

Hi, I have a spam-problem like anyone else. Most of the spam my listserver receives has some kind of impilict destination so the implicit rule catches most of the spam that way. This is fine. What is not so fine, however, is that this results in a moderation message to the sender. I'd like to stop that so that the spammer has no confirmation that the mail was received. I can probably stop this in postfix before the mail reaches mailman3, but I'd prefer changing the behaviour of the rule. Is there any setting that could be used or should I just modify the rule? Cheers. // David

4 5

Whitelist non subscriber
by Mark Ziranski Aug. 27, 2018

Aug. 27, 2018

Hello, I want to whitelist an email address on all lists to bypass moderation. The email address is not a subscriber. On google I found accept_these_nonmembers but I do not know how to use it. Please show me some examples how to whitelist someone(a)example.org. Thanks in advance. M.Z.

4 6

Configuration Question
by Ryan McClung Aug. 24, 2018

Aug. 24, 2018

Greetings, Is there a simple way to force the mailman3 install to run off of a specified config/specified db without having to enter it manually each time? I just want any administrator to be able to enter mailman without wrecking the config/db. -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

2 3

changing adverstised status
by Alexander Klotz Aug. 24, 2018

Aug. 24, 2018

Hi there, we are trying to set a once public list to private but have trouble doing so. In Postorius this doesn't seem to work - you can change "show list on index page" via the settings, but the value isn't saved. Is there a way to set advertised = False to a specific list via the shell? Thanks & Regards, Alex (Kulturserver editorial staff)

6 5

Docker release cycle maxking/mailman-core
by Johannes Winter Aug. 24, 2018

Aug. 24, 2018

Hi guys, I'd like to test out some bugfixes in the master branch, namely the merge request related to: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… But I use the maxking docker images of which the 'rolling' and 'latest' tags are apparently not really used. Might it be possible to push these a litte bit more frequently? Thank you and best regards, Johannes Winter

2 1

Avoiding welcome message when subscribing using REST API
by Henrik Rasmussen Aug. 21, 2018

Aug. 21, 2018

In Mailman 2 the site admin could add a member to a list using the -wn parameter of add_members to avoid sending a welcome message. On the host (outside the docker container) I've made an updater using the REST API to keep certain lists updated with imported addresses from one of our other systems, though respecting opt ins and opt outs. Similar to Mailman 2 I would like to avoid the welcome message to those automatic updated members, even the list is configred to send welcome message to those opting in by will, and I also like to avoid forcing the list owner/moderator to approve all new members automatically updated even the list is set for moderation of new members opting in by will. What is the payload for "no welcome message"? def add_new_members(listname_fqdn, members): [SNIP] for member in newmembers: payload['list_id'] = listname_fqdn.replace('@', '.') payload['subscriber'] = member payload['pre_verified'] = True payload['pre_confirmed'] = True payload['pre_approved'] = True response = mmapipost('members', payload) def mmapipost(apicommand,payload): response = requests.post('http://172.19.199.2:8001/%s/%s' % (restapiversion, apicommand), data=payload, auth=('restadmin', 'restpass'))

2 2

Moving from old-school install to docker
by David Krantz Aug. 19, 2018

Aug. 19, 2018

Hi, Is there any documented procedure moving from a working install of mailman3 and postorius to a docker-based version? The reason would be to get a setup that is somewhat easier to maintain and upgrade. That said much of the work is to keep a mta, web server, spamfilter, grey list solution, dkim signing etc. running and up to date. I suspect that there is no pre-made docker images for that? cheers // David

1 0

receiving digest
by Abhijith PA Aug. 14, 2018

Aug. 14, 2018

Hello. How a subscriber can receive the digest of a list ( assuming the list has enabled digests. Is there something to do for a subscriber in web interface to receive. Abhijith

2 1

Re: issue with Hyperkitty
by Mark Sapiro Aug. 8, 2018

Aug. 8, 2018

On 08/07/2018 07:14 AM, Ali Alnubani wrote: > > I'm seeing the following trace when I go to http://example.com/hyperkitty/list/dev@example.com/2018/5/: This was fixed by downgrading Django to 2.0.8. See <https://gitlab.com/mailman/hyperkitty/issues/192> for more detail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

proper update procedure for MM3 docker containers
by Fabian A. Santiago Aug. 7, 2018

Aug. 7, 2018

Hello, Can someone remind me of the proper / best way to update my docker containers for MM3 / postorius based on maxking's images? Thanks. and this for both the stable and rolling releases. -- Fabian S. OpenPGP: 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) *** 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired, still valid)

2 2

issue with Hyperkitty
by Ali Alnubani Aug. 7, 2018

Aug. 7, 2018

Hi, I'm migrating from mailman 2.1.15, I did the following: * Installed packages * Created database * ./manage.py migrate * mailman create dev(a)example.com<mailto:dev@example.com> * ./manage.py hyperkitty_import -l dev(a)example.com /usr/local/mailman2/archives/private/dev.mbox/dev.mbox (the archive includes 69 emails). * ./manage.py update_index_one_list dev(a)example.com I'm seeing the following trace when I go to http://example.com/hyperkitty/list/dev@example.com/2018/5/: ``` ERROR 2018-08-07 13:54:23,897 19997 django.request Internal Server Error: /hyperkitty/list/dev(a)example.com/2018/5/ Traceback (most recent call last): File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/core/handlers/base.py", line 126, in _get_response response = self.process_exception_by_middleware(e, request) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/core/handlers/base.py", line 124, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "venv_path/lib/python3.5/site-packages/HyperKitty-1.2.0-py3.5.egg/hyperkitty/lib/view_helpers.py", line 134, in inner return func(request, *args, **kwargs) File "venv_path/lib/python3.5/site-packages/HyperKitty-1.2.0-py3.5.egg/hyperkitty/views/mlist.py", line 94, in archives return _thread_list(request, mlist, threads, extra_context=extra_context) File "venv_path/lib/python3.5/site-packages/HyperKitty-1.2.0-py3.5.egg/hyperkitty/views/mlist.py", line 123, in _thread_list return render(request, template_name, context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/shortcuts.py", line 36, in render content = loader.render_to_string(template_name, context, request, using=using) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/backends/django.py", line 61, in render return self.template.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 171, in render return self._render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/loader_tags.py", line 62, in render result = block.nodelist.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/library.py", line 234, in render return t.render(new_context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 173, in render return self._render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/defaulttags.py", line 209, in render nodelist.append(node.render_annotated(context)) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/defaulttags.py", line 309, in render return nodelist.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/library.py", line 192, in render output = self.func(*resolved_args, **resolved_kwargs) File "venv_path/lib/python3.5/site-packages/django_mailman3-1.2.0-py3.5.egg/django_mailman3/templatetags/pagination.py", line 36, in add_to_query_string return conditional_escape(qs.urlencode()) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/http/request.py", line 524, in urlencode for v in list_ File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/http/request.py", line 524, in <genexpr> for v in list_ AttributeError: 'int' object has no attribute 'encode' ERROR 2018-08-07 13:54:23,897 19997 django.request Internal Server Error: /hyperkitty/list/dev(a)example.com/2018/5/ Traceback (most recent call last): File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/core/handlers/base.py", line 126, in _get_response response = self.process_exception_by_middleware(e, request) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/core/handlers/base.py", line 124, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "venv_path/lib/python3.5/site-packages/HyperKitty-1.2.0-py3.5.egg/hyperkitty/lib/view_helpers.py", line 134, in inner return func(request, *args, **kwargs) File "venv_path/lib/python3.5/site-packages/HyperKitty-1.2.0-py3.5.egg/hyperkitty/views/mlist.py", line 94, in archives return _thread_list(request, mlist, threads, extra_context=extra_context) File "venv_path/lib/python3.5/site-packages/HyperKitty-1.2.0-py3.5.egg/hyperkitty/views/mlist.py", line 123, in _thread_list return render(request, template_name, context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/shortcuts.py", line 36, in render content = loader.render_to_string(template_name, context, request, using=using) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/backends/django.py", line 61, in render return self.template.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 171, in render return self._render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/loader_tags.py", line 62, in render result = block.nodelist.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/library.py", line 234, in render return t.render(new_context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 173, in render return self._render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/defaulttags.py", line 209, in render nodelist.append(node.render_annotated(context)) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/defaulttags.py", line 309, in render return nodelist.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 937, in render bit = node.render_annotated(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/base.py", line 904, in render_annotated return self.render(context) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/template/library.py", line 192, in render output = self.func(*resolved_args, **resolved_kwargs) File "venv_path/lib/python3.5/site-packages/django_mailman3-1.2.0-py3.5.egg/django_mailman3/templatetags/pagination.py", line 36, in add_to_query_string return conditional_escape(qs.urlencode()) File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/http/request.py", line 524, in urlencode for v in list_ File "venv_path/lib/python3.5/site-packages/Django-2.1-py3.5.egg/django/http/request.py", line 524, in <genexpr> for v in list_ AttributeError: 'int' object has no attribute 'encode' ERROR 2018-08-07 13:54:25,721 19997 django.server "GET /hyperkitty/list/dev(a)example.com/2018/5/ HTTP/1.1" 500 317983 ``` Environment: ``` alembic==1.0.0 arrow==0.12.1 click==6.7 Django==2.1 django-haystack==2.8.1 django-mailman3==1.2.0 django-q==0.9.4 djangorestframework==3.8.2 httplib2==0.11.3 HyperKitty==1.2.0 mailman==3.2.0 mailman-hyperkitty==1.1.1 mailmanclient==3.2.0 Mako==1.0.7 postorius==1.2.0 psycopg2-binary==2.7.5 python-dateutil==2.7.3 requests==2.19.1 requests-oauthlib==1.0.0 SQLAlchemy==1.2.10 urllib3==1.23 uWSGI==2.0.17.1 Whoosh==2.7.4 ``` Some of the archives are listed fine tho. The same trace reproduced with 2 different imported archives. I'm on Debian stretch and using python 3.5.3. Can you help please? Thanks, Ali

1 0

migration subscribers from mm2 to mm3
by Mateusz Ostrzyżek Aug. 7, 2018

Aug. 7, 2018

Hello, Is there any way to migrate subscribers from mailman2 to mailman3 other than writing them to mm3? I have a fiew lists on mailman2 an i want to migrate them to mailman 3, i found a way to migrate archive but cannot find any information about subscribers. Best regards -- Mateusz Ostrzyżek (null) (null)

2 1

dedicated mailman3 list server on Ubuntu 18.04 LTS - questions after installation
by John Seifarth Aug. 6, 2018

Aug. 6, 2018

My goal is to build a stable dedicated list server using mailman3. It should use all current email authentication techniques to clearly show that it is an authentic non-spam mail list server. In the future, I may want to use the REST interface, so that’s why mailman2 is not an option. My installation: Installed Ubuntu 18.04 LTS server, with postfix, mysql and postgres. I then installed mail-stack-delivery, postfix-policyd-spf-python, OpenDKIM, and OpenDMARC. I configured SPF, DKIM, and DMARC records on my DNS server, and then configured postfix and dovecot to DKIM sign outgoing mail from local users, and check SPF, DMARC, and DKIM on incoming mail. I then installed the package mailman3-full, which provides version 3.1.1-9, using postgres 10 as the database. I have looked in Ubuntu bionic-backports and bionic-updates and do not see a more recent version. I see that version 3.2 was released in July, are debian/ubuntu mailman 3.2 packages available somewhere? I set up the /etc/mailman3 files: I added this to the end of mailman.cfg [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg In mailman-hyperkitty.cfg I copied the api_key: value from mailman-web.py MAILMAN_ARCHIVER_KEY, but removed the single quotes surrounding the value in the mailman-web.py file when writing the key in the mailman-hyperkitty.cfg file. I modified /etc/postfix/main.cf with this appended to the end: # Mailman-postfix integration owner_request_special = no # Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname, $alias_maps, hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = ${{$compatibility_level} < {2} ? {$mydestination} : {}} hash:/var/lib/mailman3/data/postfix_domains I ran /usr/share/mailman3-web/manage.py createsuperuser I ran a2enmod proxy_uwsgi I made a symbolic link from /etc/mailman3/apache.conf to /etc/apache2/conf-available/mailman3.conf, then ran a2enconf mailman3 I have read the documentation in /usr/share/docs/mailman3* along with what I could find concerning mailman3 on the web. The installation allows me to sign into the web interface, create a host, create mailing lists, and mass subscribe members. When members send email to the list address, the server sends the messages normally to the other members of the list. However, when I look at the list archives, there are no posts. I deliberately mass-subscribed an invalid address, and I can see in /var/log/mail.log that the message bounces, but I get no notification, nor do I see any bounce info when I look at the member info. My questions: 1) logging A lot of my questions would probably be answered if I could figure out hot to activate logging correctly. Currently, I see: root@mailman:/var/log/mailman3# ll -R -rw-rw---- 1 list list 0 Jul 29 20:06 bounce.log -rw-rw---- 1 list list 0 Jul 29 20:06 debug.log -rw-r----- 1 list list 3298 Aug 4 00:00 mailman.log -rw-rw---- 1 list list 34606 Jul 30 17:44 smtp.log drwxr-xr-x 2 www-data www-data 4096 Aug 3 06:25 web/ ./web: -rw-rw-r-- 1 www-data www-data 1520 Aug 3 06:25 mailman-web.log The bounce log and debug log are empty. I’ve set propagate: yes in the [logging.debian] section From /etc/mailman3/mailman.cfg # In this section, you can define defaults for all loggers, which will be # prefixed by 'mailman.'. Use subsections to override settings for specific # loggers. The names of the available loggers are: # # - archiver -- All archiver output # - bounce -- All bounce processing logs go here # - config -- Configuration issues <…snip…> Can anyone post an example of a ‘subsection’ to set archiver and bounce to debug? Do I have to create /var/log/mailman3/mailman.archiver.log and set ownership to list:list? 2) Where are posts stored? For me, this is the biggest mystery in mailman3. Local mail is delivered to ~/Maildir by dovecot. In the $var_dir hierarchy the directory messages contains just 2 messages dating to my initial tests. Anything I send to a list now, and which seems to be sent properly to the member addresses, I cannot find on the filesystem. Any clues as to what may be going on here? 3) Archival - Hyperkitty How does this work? All the parts seem to be in place, and I can see from ps /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=archive:0:1 -C /etc/mailman3/mailman.cfg How can I figure out why this is not working? In the web interface, I see that each of my lists has zero posts. But posts mailed to the list address do appear in the list members’ mailboxes! 4) Bounces I’ve deliberately put an erroneous email address as a list member. In postfix’s /var/log/mail.log I see the bounces, but get no notification, and /var/log/mailman3/bounce.log remains empty. 5) DKIM and DMARC I’ve got OpenDKIM running on inet:12345@localhost and OpenDMARC running on net:54321@localhost. How can I get mailman to use these milters and sign messages? How should DMARC munging be configured when signing? 6) Is there an overview of how mailman3 works? Is there documentation which explains the path of an incoming post through the system, including initial reception, list processing, sending to members, processing bounces, and archiving posts? Thanks in advance for help and pointers to any available documentation! John Seifarth Words & Wires SPRL Computer Consulting & Language Services Brussels, Belgium

3 2

bad ssl cert on docker guide site
by Fabian A. Santiago Aug. 6, 2018

Aug. 6, 2018

hello, On the docker deployment guide site: https://asynchronous.in/docker-mailman/ linked to from here: http://docs.mailman3.org/en/latest/prodsetup.html the ssl cert is invalid, as it's issued against CN = www.github.com. just an fyi (although I"m sure others have seen this and there's likely a perfectly valid explanation I just haven't thought of). good day. -- Fabian S. OpenPGP: 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) *** 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired, still valid)

2 1

getting spammed when sending lots of mails (>1000)
by Asaf Ohayon Aug. 6, 2018

Aug. 6, 2018

Hello Using Mailman 3.2 / Posfix 2.10.1 I have a list configured, when having only few members, all is OK, email gets to inbox (at GMail) But when sending to thousands of members, it gets to the Spam folder, Is it a matter of rate-limiting at postfix ? Thanks -- Asaf Ohayon SRE | SysBind M: +972 547920828 P: + 972 3 5096219 E: asaf(a)sysbind.co.il Rothschild 60, Bat Yam www.sysbind.co.il

2 1

"To:" header field
by Asaf Ohayon Aug. 5, 2018

Aug. 5, 2018

Hello I'm having trouble with getting into spam folder (at least at gmail), I'm suspecting to "To:" field (among other things). Comparing to Mailman 2.1, which we recently upgrading from, and didn't got spammed, the "To:" field was set to the actual reciever, While in Mailman 3.2, the "To:" field is set to the list's address. How can this be configured ? Thanks -- Asaf Ohayon SRE | SysBind M: +972 547920828 P: + 972 3 5096219 E: asaf(a)sysbind.co.il Rothschild 60, Bat Yam www.sysbind.co.il

2 1

Archiving error
by Eric Abrahamsen Aug. 3, 2018

Aug. 3, 2018

Since about two days ago, all attempts to archive messages via Hyperkitty have raised the error below. So far as I know, I haven't updated any packages, or changed any config. I don't know why this has started happening. Internal Server Error: /hyperkitty/api/mailman/archive IntegrityError at /hyperkitty/api/mailman/archive NOT NULL constraint failed: hyperkitty_attachment.size Request Method: POST Request URL: http://lists.my-domain.org/hyperkitty/api/mailman/archive?key=NotMyRealKey Django Version: 2.0.5 Python Executable: /home/eric/.local/share/virtualenvs/mailman-FH66s6f7/bin/python Python Version: 3.5.2 Traceback: File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/utils.py" in _execute 85. return self.cursor.execute(sql, params) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py" in execute 303. return Database.Cursor.execute(self, query, params) The above exception (NOT NULL constraint failed: hyperkitty_attachment.size) was the direct cause of the following exception: File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/core/handlers/exception.py" in inner 35. response = get_response(request) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/core/handlers/base.py" in _get_response 128. response = self.process_exception_by_middleware(e, request) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/core/handlers/base.py" in _get_response 126. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/hyperkitty/views/mailman.py" in _decorator 72. return func(request, *args, **kwargs) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/views/decorators/csrf.py" in wrapped_view 54. return view_func(*args, **kwargs) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/hyperkitty/views/mailman.py" in archive 119. add_to_list(mlist_fqdn, msg) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/hyperkitty/lib/incoming.py" in add_to_list 162. encoding=encoding) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/manager.py" in manager_method 82. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/query.py" in create 417. obj.save(force_insert=True, using=self.db) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/base.py" in save 729. force_update=force_update, update_fields=update_fields) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/base.py" in save_base 759. updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/base.py" in _save_table 842. result = self._do_insert(cls._base_manager, using, fields, update_pk, raw) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/base.py" in _do_insert 880. using=using, raw=raw) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/manager.py" in manager_method 82. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/query.py" in _insert 1125. return query.get_compiler(using=using).execute_sql(return_id) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/sql/compiler.py" in execute_sql 1283. cursor.execute(sql, params) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/utils.py" in execute 68. return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/utils.py" in _execute_with_wrappers 77. return executor(sql, params, many, context) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/utils.py" in _execute 85. return self.cursor.execute(sql, params) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/utils.py" in __exit__ 89. raise dj_exc_value.with_traceback(traceback) from exc_value File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/utils.py" in _execute 85. return self.cursor.execute(sql, params) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py" in execute 303. return Database.Cursor.execute(self, query, params) Exception Type: IntegrityError at /hyperkitty/api/mailman/archive Exception Value: NOT NULL constraint failed: hyperkitty_attachment.size Request information: USER: AnonymousUser GET: key = 'NotMyRealKey' POST: mlist = 'my-list(a)lists.my-domain.org' FILES: message = <InMemoryUploadedFile: message.txt ()> COOKIES: No cookie data META: CONTENT_LENGTH = '579002' CONTENT_TYPE = 'multipart/form-data; boundary=4c9a29456f514b2a9ef4f9a5d042abc6' HTTP_ACCEPT = '*/*' HTTP_ACCEPT_ENCODING = 'gzip, deflate' HTTP_CONNECTION = 'close' HTTP_HOST = 'lists.my-domain.org' HTTP_USER_AGENT = 'python-requests/2.18.4' HTTP_X_FORWARDED_FOR = 'xxx.xxx.xx.xxx' HTTP_X_FORWARDED_HOST = 'lists.my-domain.org' HTTP_X_REAL_IP = 'xxx.xxx.xx.xxx' PATH_INFO = '/hyperkitty/api/mailman/archive' QUERY_STRING = 'key=NotMyRealKey' REMOTE_ADDR = '127.0.0.1' REQUEST_METHOD = 'POST' SCRIPT_NAME = '' SERVER_NAME = '127.0.0.1' SERVER_PORT = '231742768' SERVER_PROTOCOL = 'HTTP/1.0' wsgi.errors = <_io.TextIOWrapper name='<stderr>' mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <_io.BytesIO object at 0x7f940d0055c8> wsgi.multiprocess = True wsgi.multithread = False wsgi.run_once = False wsgi.url_scheme = 'http' wsgi.version = '(1, 0)'

1 0

Removing banned emails
by Kaleb White Aug. 2, 2018

Aug. 2, 2018

I am trying to remove a banned email with a special character via the rest api and it's not working. It's also not working via the UI. Any ideas? http://localhost:8001/3.0/lists/example.com/bans/provisor#41@bankofamerica.… <Response [404]>

3 2

Re: Mailman 3 Keeps Forgettings Imported Lists
by Ryan McClung July 31, 2018

July 31, 2018

I do see the output of the script and it shows the mailing lists being created. If you put "${VARIABLE}"@domain.com it outputs correctly. Also, to that end, the output of lists changes depending on which directory I am in which makes 0 sense. On Tue, Jul 31, 2018 at 3:27 PM Ryan McClung <rmcclung(a)afilias.info> wrote: > I do see the output of the script and it shows the mailing lists being > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > On Tue, Jul 31, 2018 at 3:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 07/31/2018 07:04 AM, Ryan McClung wrote: >> > Scratch that. Ran with the corrected script and getting the following: >> > [root@mailman3(stg) archives]# mailman lists >> > No matching mailing lists found >> > >> > Any thoughts? >> >> This >> >> > for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ >> afilias.info "${DIR}"/config.pck; >> >> is still wrong. The list name for mailman create needs to be fully >> qualified as in >> >> > for DIR in $DIRS; do mailman create ${DIR}(a)afilias.info; mailman >> import21 ${DIR}(a)afilias.info ${DIR}/config.pck; >> >> (Do you look at the output from your script?) >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > > Ryan McClung > Systems Administrator @ Afilias Canada > A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 > <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> > W. www.afilias.info > T. +1.416.646.3304 x4186 > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

2 3

Mailman 3 Keeps Forgettings Imported Lists
by Ryan McClung July 31, 2018

July 31, 2018

GNU Mailman 3.2.0 (La Villa Strangiato) Python 3.6.5 (default, Apr 10 2018, 17:08:37) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] config file: /opt/mailman/var/etc/mailman.cfg db url: sqlite:////opt/mailman/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ Shortly after I run an import on a bunch of lists they all disappear. [root@mailman3(stg) mailman]# mailman lists No matching mailing lists found I have 30+ lists. Any thoughts? -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

2 4

mailman command to remove members
by Asaf Ohayon July 31, 2018

July 31, 2018

Is there command like mailman members --add, to mass-remove members from a list ? Thanks

2 1

Autorespond postings: does not seem to work on 3.2?
by Asaf Ohayon July 29, 2018

July 29, 2018

Hello Maybe I'm not understanding the meaning of this setting correctly, When I set this, I don't see any extra emails going out when I'm posting to the list Thanks

2 1

MM3 installation recommendation: Docker or individual components?
by Tom Browder July 28, 2018

July 28, 2018

I want to install MM3 on a virgin host running Debian 9. I want to minimize problems as bugs are fixed and necessary upgrades are published. I will use PostgreSQL, nginx, and Postfix, and am reasonably competent runnng my own remote server (full control, hard iron server, not virtual). The host will only serve mail to the public and nothing else (no websites, no other users). I did run a successful MM2 site (thanks to Mark’s copious and gracious help!) for a couple of years from 2011 to 2013, so I’m no stranger to some of the MM3 jargon. I have been running Apache 2.4+ with 10+ virtual https websites since 2010. I use Letsencrypt certificates for all of them. I have no experience with Docker, Django, or nginx. Should I choose the Docker method or individual compnent installation? I realize this is an open ended and very subjective request, but I would appreciate any advice. Best regards, -Tom

2 2

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

Pre-approved howto
by thor.rustad＠gmail.com July 9, 2018

July 9, 2018

I have tried to understand the concept of pre-approved messages, but I'm spending way too much trying to figure it out. Help! The scenario is as follows: Mailman installation with hundreds of lists. Each list's owner is only supposed to add/remove members, so approving/rejecting messages is not in the "job description". Then we have a small group of superusers who will be the ones sending documents etc to all 800 lists. The superusers should be able to do so without being stopped by size limits etc. How can I achieve this? ---- Thor Atle Rustad ----

3 3

Mailman 3 localization
by Danil Smirnov July 5, 2018

July 5, 2018

Hi! I saw in the docs: Localization > > We have it! We just don’t have proper documentation here yet. > Could you please be more specific - can I switch Mailman 3 installation to Spanish? Regards, Danil Smirnov

7 13

Query on how to change moderator message to non-members
by robert.kydd＠gmail.com July 4, 2018

July 4, 2018

Hi My users are upset that when their mail is waiting moderation release they receive this message: 'Your mail to 'Members' with the subject AW: [Members] Hamburg 2019 Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list' Is their a way to change the text "post by a non-member to a members-only list" as they are registered members of the Joomla site

3 8

Unknown attribute: max_message_size
by Thor Atle Rustad June 27, 2018

June 27, 2018

If I make changes here: https://example.com/postorius/lists/test2.example.com/settings/message_acce…, I get a warning that the Maximum Message Size field at the bottom is mandatory. However, if I put a number in that field and save, I get "Unknown attribute: max_message_size". That makes sense, since Mark states in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… that max_messages_size is not exposed in REST. What to do? I have Maxking mailman-docker but can easily copy files into the image if necessary. Thor

5 8

List admin statistics
by Andrew Hodgson June 26, 2018

June 26, 2018

Hi, On my Mailman3 installation the posting statistic doesn't seem to be getting reset, the digest stat is showing correctly however. Not sure about the volume stat. I imported my list from a Mailman2 pck file and the last posting data is the last message that went via Mailman2. Any ideas? Thanks. Andrew.

2 1

Gmail/Fetchmail in Mailman3?
by Bill Christensen June 24, 2018

June 24, 2018

Hi folks, We're (finally) in the early stages of upgrading from Mailman2 to Mailman3. Our Mailman2 setup uses Fetchmail to retrieve list mail from our accounts on Gmail. Is there a similar setup for Mailman3? I admit that I've only done a light scan of the docs so far, but haven't found anything addressing such a scenario. Thanks in advance! -- Bill Christensen http://SustainableSources.com http://LinkedIn.com/in/billc108 Dance like nobody's watching. Encrypt like everyone is. --Adrián Lamo

2 3

Header / Footer apear as attachements on Outlook / Office365
by Asaf Ohayon June 21, 2018

June 21, 2018

Trying to play with Header / Footer working OK on normal email clients, But on office they apear as attached txt files. Any Idea ? -- Asaf Ohayon SRE | SysBind M: +972 547920828 P: + 972 3 5096219 E: asaf(a)sysbind.co.il Rothschild 60, Bat Yam www.sysbind.co.il

2 1

Avoiding reply to list when User does "Reply To All"
by Asaf Ohayon June 19, 2018

June 19, 2018

hello I've played with explicit reply-to address, and "Reply goes to list" -> "Explicit Reply-to headers set", And it works fine when user does "Reply" in the client (e.g: gmail), But when she presses Reply To All, still it sends also to the list, Is there some way to avoid this ? Thanks -- Asaf Ohayon SRE | SysBind M: +972 547920828 P: + 972 3 5096219 E: asaf(a)sysbind.co.il Rothschild 60, Bat Yam www.sysbind.co.il

2 1

HTML header / footer template
by Asaf Ohayon June 18, 2018

June 18, 2018

Is it possible to put HTML header to allow inserting images ? Thanks -- Asaf Ohayon

2 4

Functionailty of web host domains
by Johannes Winter June 16, 2018

June 16, 2018

Hello everybody, I'd actually like to use mailman3 in a multi-site setup, so that lists are only accessible from corresponding domains. I already asked once oif this would be possible with domain admins, but that is not implemented: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Then i was asking myself whether it could be possible with the "wed host" functionality. For each domain you can specify a "web host". But when I specify a different one than the default for one domain, and make it accessible with specifying `DJANGO_ALLOWED_HOSTS`, all mailinglists from the other web hosts are also shown when I access the second site. So does this 'web host' option have a meaning, or is it just an alias for the first site? Best regards, Johannes Winter

2 1

Migrate from mysql to postgresql
by Bjoern Franke June 14, 2018

June 14, 2018

Hi, is it possible to migrate a mailman3-mysql-database to a postgresql-database? I tried to convert it with pgloader, but some identifiers had to be cut off: _address_id); 2018-03-17T21:33:39.087000+01:00 WARNING PostgreSQL warning: Bezeichner idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e wird auf idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac gekrzt Kind regards Bjoern

2 2

Disable like button
by Marvin Gülker June 13, 2018

June 13, 2018

Hi everyone, is it possible to disable the facebookish like/dislike thumbs buttons on posts in Hyperkitty? I have the impression that this kind of functionality discourages useful, argumentative discussion and instead causes emotional voting without arguments on whatever is at hand (it is one of the features I would really like to disable on GitHub as well). A voting facility on its own is surely fine, but it shouldn't be on each post, but only where one actually wants to cast a vote. Also, one isn't informed of the thumbs up/thumbs down count when only using the email interface and not Hyperkitty. This can lead to confusion for users that only use Hyperkitty and feel their "votes" are being ignored. Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

3 2

Is there a reason not to implement the config_list command ?
by Asaf Ohayon June 11, 2018

June 11, 2018

Hello Is it meant to be implemented ? and if so, how is it recommended to do (for someone new to mailman 3 programming) Thanks

2 1

What is result of planned MM3 integrated installation at Pycon?
by Tom Browder June 10, 2018

June 10, 2018

I may have missed the announcement, but I thought it was hoped to get a major leap toward an integrated MM3 installation at the May Pycon. Did anything exciting happen toward that goal, or should I just press on with the latest release? Thanks. Best regards, -Tom

2 3

Scheduled tasks
by Darren Smith June 8, 2018

June 8, 2018

All, I am looking more through the documentation of the Mailman Suite here: https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf In section 3.2.5 it talks about the scheduled tasks that need to be run to do "specific routine functions" in hyperkitty. I installed through the easy install script found here: https://github.com/iomarmochtar/mailman3_ei/ However, I can't find anything in THAT documentation that talks about these cron jobs, and in fact the Mailman Suite isn't installed through that script. Can someone point me to any other documentation about the tasks that need to be run on a continual basis? Our hyperkitty installation seems to be bogging down more and more, and I am hoping that it will be as simple as just running some jobs that haven't been on our radar. Thoughts? -Darren

2 3

Attachments
by Darren Smith June 6, 2018

June 6, 2018

Guys, Is there a setting to disallow attachments in mailman3? Doing a cursory search I can't find it.

3 2

Re: GDPR - save subscriptions confirmation emails
by contact＠maadix.net June 4, 2018

June 4, 2018

Thanks Selva for you answer. In my Mailman 3 installation there is no /var/log/mailman/subscribe I have logs about confirmations emails in mailman/var/logs/smtp.log the format is the following: Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) handling connection Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'LHLO mails.example.com' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'MAIL FROM:<contact(a)maadix.net>' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) sender: contact(a)example.net Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'RCPT TO:<prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org>' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) recip: prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'DATA' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'QUIT' So, one solution that comes to my mind is to grep this log file. This is not a perfect solution and the full confirmation email is still missing. I am not sure if this would be GDPR compliant. Maddish El 03/06/18 a las 18:17, Selva Nair escribió: > Hi, > > On Sun, Jun 3, 2018 at 10:12 AM, contact(a)maadix.net <contact(a)maadix.net> wrote: >> >> Hi, >> >> I am new in the list. I have been looking for this topic in the archives >> in order to avoid duplicate, but I could not find any thread. >> >> According to the new GDPR rules, lists owners need to have a >> confirmation from subscribers, and this is easy to do with Mailman 3. >> >> What I can't figure out is how to save all the confirmation emails >> received from users. >> >> I only see the confirmations commands emails in the logs, >> >> Is there another place/way to store them? > > We have been doing this with mailman2 since Canadian Anti-Spam Law (CASL) > got enacted (2014) by independently archiving the confirmation messages. > With postfix we use recipient_bcc_maps and a script to do some extra filtering > but its clunky, and does not check that the confirmation succeeded or not. > > A feature within mailman to archive successful confirmations would be > useful. Keeping unsubscribe requests and evidence of subsequent > actions also seems necessary at least as per CASL. > > That said, we also keep the /var/log/mailman/subscribe logs (not sure > what that would be in mailman 3). Although the log has a single line > for each action, it may be enough to show (?) that a double opt-in process > was properly followed or unsub request was acted up on. > > Thanks, > > Selva > -- Maadix *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

3 3