- Mailman-users - lists.mailman3.org

Emailing a list from the list server
by Mark Dadgar June 1, 2020

June 1, 2020

Ok, I admit I am baffled by this one. I cannot email a list from an account on the list server itself (for example, programmatically by script, but also manually) using mail / mailx / mutt / etc from the command line. The emails just disappear into the ether. I can email other arbitrary addresses just fine, including real users hosted on that server. Here’s the postfix main.cf section for mailman3: 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 What obvious thing am I missing? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

2 3

Header Filters
by Peter Adebahr June 1, 2020

June 1, 2020

Hi *, we are trying to dispose of automatic replies like "out of office" etc. For these ends, we have set Header to "subject" (w/o quotes) Pattern to ".*out.of.office.*" Action to "Hold for moderation" However, these mails are passed through to the list. How is this to be set to become effective? Thank you and have a good week Peter

2 1

installing mailman3 core
by Ralf Wiegand May 29, 2020

May 29, 2020

Mark - What is the difference between to two install methods? What are my pros and cons? I have been using this: >>>> |# Note: if we are using a dedicated postgresql database server, all postgresql changes need to be done on the actual postgresql server.| |>>>| |sudo yum install postgresql-server postgresql-contrib| |sudo postgresql-setup initdb| |sudo systemctl start postgresql| |sudo systemctl enable postgresql| |sudo -u postgres psql -c ||"SELECT version();"| |sudo useradd -c ||"Mailman User"| |-s /bin/bash -m mailman| |sudo -u postgres create role mailman;| |sudo -u postgres createdb -O $USER mailman| |sudo -u postgres psql -c ||"grant all privileges on database mailman to mailman;"| |sudo -u postgres psql -c ||"ALTER ROLE mailman WITH PASSWORD 'secret123';"| |sudo -u postgres psql -c ||"ALTER ROLE "||mailman||" WITH LOGIN;"| |sudo echo ||"listen_addresses = '*' "| |>> /var/lib/pgsql/10/data/postgresql.conf| |sudo echo ||"# The user mailman will be able to access all databases from a trusted location (any) without a password"| |>> /var/lib/pgsql/data/pg_hba.conf| |sudo echo ||"host all mailman 0.0.0.0/0 trust"| |>> /var/lib/pgsql/data/pg_hba.conf| |sudo systemctl restart postgresql| |sudo ss -nlt | grep 5432| |<<<| |sudo yum install python36* --skip-broken -y| |# check make sure you have both versions| |sudo python --version| |Python 2.7.5| |sudo python3 --version| |Python 3.6.8| |sudo pip3 install psycopg2-binary| |sudo chown mailman.mailman /opt/mailman| |sudo chmod 755 /opt/mailman| |# NOTE: The first initial mailman3 core setup has to be done manually.| |# This is a important step to ensure the user "mailman" will run the actual mailman3 application and not root.| |# switch to user mailman| |mailman# cd /opt/mailman| |mailman# git clone https:||//gitlab.com/mailman/mailman.git| |mailman# cat <<EOT >> /opt/mailman/mailman/src/mailman/config/mailman.cfg| |[devmode]| |enabled: yes| |recipient: root@localhost| |[webservice]| |hostname: localhost| |port: 8001| |show_tracebacks: yes| |use_https: yes| |[mta]| |incoming: mailman.mta.postfix.LMTP| |outgoing: mailman.mta.deliver.deliver| |lmtp_host: localhost| |lmtp_port: 8024| |smtp_host: localhost| |smtp_port: 25| |[database]| |class||: mailman.database.postgresql.PostgreSQLDatabase| |url: postgres:||//mailman:secret123@<IP-ADDRESS or FQDN>/mailman| |EOT| |mailman# python3.6 -m venv venv-3.6| |>>| |mailman# source venv-3.6/bin/activate| |(venv-3.6) [mailman@empire mailman]$ cd mailman| |(venv-3.6) [mailman@empire mailman]$ python setup.py develop| |(venv-3.6) [mailman@empire mailman]$ mailman info| |<<| | | | | |So I was told I don't have to do this, I can just simple do (rhel7) | |yum install pyhton3| |pip install mailman| | | | |

3 4

Hyperkitty issue(s)
by Bryan Loniewski May 28, 2020

May 28, 2020

Hello -- I'm stuck trying to integrate Hyperkitty. I see the following errors in mailman.log and mailmansuite.log respectively: <snipped> [2020-05-27 16:42:11 -0400] [5140] [ERROR] Error handling request /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 134, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 406, in on_get for archiver in archiver_set.archivers File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 407, in <dictcomp> if archiver.system_archiver.is_enabled} File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/model/mailinglist.py", line 587, in system_archiver raise AssertionError('Archiver not found: {}'.format(self.name)) AssertionError: Archiver not found: hyperkitty and <snipped> Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/postorius/middleware.py", line 42, in __call__ return self.get_response(request) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 36, in inner response = response_for_exception(request, exc) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 90, in response_for_exception response = handle_uncaught_exception(request, get_resolver(get_urlconf()), sys.exc_info()) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 125, in handle_uncaught_exception return debug.technical_500_response(request, *exc_info) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/views/debug.py", line 89, in technical_500_response reporter = ExceptionReporter(request, exc_type, exc_value, tb) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/views/debug.py", line 254, in __init__ self.template_info = getattr(self.exc_value, 'template_debug', None) File "/opt/mailman/mm/venv/lib/python3.6/tempfile.py", line 479, in __getattr__ file = self.__dict__['file'] KeyError: 'file' Note that I've kinda followed the Virtualenv route along with using Mark's helpful webpage re: his experiences. Some relevant? config files... mailman.cfg: <snip> [archiver.prototype] enable: yes [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg <snip> mailman-hyperkitty.cfg: [general] base_url: https://a_real_domain/mm3/hyperkitty api_key: <movealong> I can provide additional conf file setups if warranted? I am curious (and perhaps this is in fact the issue) why when I run mailman conf I don't see the archiver.hyperkittty section even though its in the mailman.cfg file? While at the same time I do see archiver.{mail_archive,mhonarc}? I know it's reading my mailman.cfg based on other sections I've already setup/manipulated. Another data point: $ grep -i hyperkitty requirements.txt HyperKitty==1.3.2 mailman-hyperkitty==1.1.0 Any suggestions? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator

3 7

automation of mailman3 core startup
by Ralf Wiegand May 27, 2020

May 27, 2020

|mailman# source venv-3.6/bin/activate| |(venv-3.6) [mailman@empire mailman]$ cd mailman| |(venv-3.6) [mailman@empire mailman]$ python setup.py develop| |(venv-3.6) [mailman@empire mailman]$ mailman info| | | |Hello Mark -| |Question: The above assumes that the user mailman will run the mailman3 core application. So the user "mailman" has all the correct permissions. The issue I have is to automate this part, so at start up mailman3 will be running, at shutdown, being shutdown properly. | | | |How can I do this?| | | |Ralf |

2 1

Mailman rewrite the Cc header incorrectly
by Alan So May 27, 2020

May 27, 2020

I just notice that if I send an email to a list with a Cc header broken into multiple lines and the pair of double quotes are put in different lines, the email addresses afterwards will be wrongly rewritten. For example, CC: "ABC DEF (XYZ)" <name(a)example.com> It will become the following after going through the mailing list: CC: XYZ <"ABC DEF"@mail.server.name> It seems that Outlook often split the To/Cc header into multiple lines and they often add double quotes to the full name of the users. Is the rewriting of Cc header handled by Mailman's code or another Python class? Thanks. Regards, Alan So

2 21

Emergency Moderation
by Brian Carpenter May 26, 2020

May 26, 2020

Is there an Emergency Moderation function (similar to the one that Mailman 2 had) with Mailman 3 core/Postorius? Thanks, Brian

5 11

Migrating Mailman 3 lists
by Brian Carpenter May 26, 2020

May 26, 2020

Hello Mailman users, I know how to migrate mailman 2 lists to a new mailman 3 server. However I do not know how to migrate a mailman 3 list from one mailman 3 server to another one. Are there any instructions or protocol on how to accomplish this? The Mailman 3 server I want to migrate *from* was setup using Docker. The Mailman 3 server I want to migrate these lists *to* was setup using a python virtual environment via pip. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

9 17

performance report - mailman 3.3.1rc1 / postorius 1.3.1
by sunil soprey May 26, 2020

May 26, 2020

Hi all - I just wanted to share my perf-load results of Mailman3. Hopefully community finds helpful. I realized mailman3 cannot run on AWS t3a* ( 2cpu or 4cpu @ 8 gigs ) Specs: AWS EC2 - m5a.xl and c5.xl Version: mailman 3.3.1rc1 What: Duration load test of 30k emails across 200 lists. Some lists have a depth of 9k users, other lists have 100 emails address. * create 200 lists of random names Results * Postorius kept hanging on vanilla AWS LTS and LTS2 image. I had to tune the kernel settings ( somax, syslimits, tcp wmem) * gunicorn.cfg must be created and workers/threads property must be added. I noticed hanging python and tcp/socket errors * Total run time = 50mins for fresh-load

1 1

Postorius, Hyperkitty new release candidates
by Abhilash Raj May 24, 2020

May 24, 2020

Hi Everyone, I am pleased to announce a couple of more releases: - Postorius: 1.3.3rc1 Changelog: https://docs.mailman3.org/projects/postorius/en/latest/news.html#rc1 Download: https://pypi.org/project/postorius/1.3.3rc1/ - Hyperkitty: 1.3.3rc1 Changelog: https://hyperkitty.readthedocs.io/en/latest/news.html#rc1 Download: https://pypi.org/project/HyperKitty/1.3.3rc1/ - Mailmanclient: 3.3.1rc1 Changelog: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… Download: https://pypi.org/project/mailmanclient/3.3.1rc1/ - Django-mailman3: 1.3.3rc1 Changelog: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Download: https://pypi.org/project/django-mailman3/1.3.3rc1/ Python 3.6+ and Django 2.0+ is supported for all of them. Django 3.0 support for Hyperkitty requires manually upgrading a dependency (django-haystack>=3.0b2, once a stable version of this has been released, it shouldn't require manually upgrading). There are tons of bug-fixes across the board and some new features. Biggest visible change is switch to Bootstrap 4, which has been long pending for us. Bootstrap 4 completely changes the CSS grid model using the new Flexbox. There might be some small changes or breakages when using on mobile. Please report such issues to us via Gitlab! Some other notable changes are in Postorius, which includes many more list settings exposed include content filtering settings, bounce processing (which was added in the previous release of Mailman Core) settings and some other ones. You can now also specify a reason when rejecting held messages. There was also a gnarly bug, which caused the name of some members to be the string "None". For the longest time, I couldn't figure out the reason for it, but it ended up being a simple fix in mailmanclient's json serialization of display_name, which would result in Python's None value being passed as string "None" to Mailman's API for subscription. There is also better support for filtering visible lists based on the current vhost, which I see a few people are already waiting for from mailman-users list. A full changelog has been added to each project in the top. These are still pre-releases and if you are installing via pip, you would need the `--pre` flag, for e.g. $ pip install --pre --upgrade postorius hyperkitty As with all other releases, these have also been running on mail.python.org and lists.mailman3.org for some time now, so it should be relatively safe to upgrade to. Stable releases for this is now scheduled in 1 week, hopefully, next weekend. -- thanks, Abhilash Raj (maxking)

1 1

Updating from Ubuntu-20.04 LTE installation
by Peter Adebahr May 24, 2020

May 24, 2020

Hi Mark, thank you for the fast solution of our subscription problem - which brings me to the next step: Our installation was done by "apt-get install" in Ubuntu 20, thus still running MM 3.2.2 (and python 3.8.2). Do you have any advise, how to upgrade from there to your current version? I know this might be a bit dangerous, but with today's VMs the risk is much less than it used to be: Do you think it would be possible, just to replace the code and library parts, keeping the database and config files as is? If not, what would you do when you have to keep the system running (except for maintenance time, of course)? Thank you again and and have a nice relaxed weekend Peter

3 2

Hyperkitty: remove discussions
by Peter Adebahr May 22, 2020

May 22, 2020

Hi *, is it possible to remove discussions from the archives? As it were tests only, removing the complete archive would be ok, too. For the customer, we would like to start this list with a clean archive :) Thank you Peter

2 1

Subscribing by E-Mail
by Peter Adebahr May 22, 2020

May 22, 2020

Hi *, on MM2 systems, we used to subscribe people via an external application by sending an e-mail to the request address with a subject of "subscribe address=user(a)example.com" This returns a "bad argument" in MM3 - any ideas how to solve this? We cannot set the actual from-address in a foreign application... Thank you Peter

2 1

OpenID Connect support
by Gilles Filippini May 21, 2020

May 21, 2020

Hi, As I understand it the OpenID authentication mode available in Mailman3 refers to the now deprecated version 2.0 of the protocol. Am I correct? Is there any ongoing work to bring support for OpenID Connect? Thanks in advance, _g.

1 2

ValueError: ...:EVP_DigestInit_ex:disabled for fips
by Ralf Wiegand May 20, 2020

May 20, 2020

(venv-3.6) [root@maildev mailman-suite_project]# python manage.py migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, openid, postorius, sessions, sites, socialaccount Running migrations: Applying contenttypes.0001_initial...Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/management/base.py", line 364, in execute output = self.handle(*args, **options) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/management/base.py", line 83, in wrapped res = handle_func(*args, **kwargs) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/management/commands/migrate.py", line 234, in handle fake_initial=fake_initial, File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/migrations/executor.py", line 117, in migrate state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/migrations/executor.py", line 147, in _migrate_all_forwards state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/migrations/executor.py", line 245, in apply_migration state = migration.apply(state, schema_editor) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/migrations/migration.py", line 124, in apply operation.database_forwards(self.app_label, schema_editor, old_state, project_state) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/migrations/operations/models.py", line 530, in database_forwards getattr(new_model._meta, self.option_name, set()), File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/base/schema.py", line 367, in alter_unique_together self.execute(self._create_unique_sql(model, columns)) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/base/schema.py", line 126, in execute sql = str(sql) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/ddl_references.py", line 194, in __str__ return self.template % self.parts File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/ddl_references.py", line 103, in __str__ return self.create_index_name(self.table, self.columns, self.suffix) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/base/schema.py", line 1049, in create_unique_name return self.quote_name(self._create_index_name(*args, **kwargs)) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/base/schema.py", line 884, in _create_index_name hash_suffix_part = '%s%s' % (names_digest(table_name, *column_names, length=8), suffix) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/utils.py", line 221, in names_digest h = hashlib.md5() *ValueError: error:060800A3:digital envelope routines:EVP_DigestInit_ex:disabled for fips* Hello group, I am running into this error. any idea what is going wrong here? Help is greatly appreciated. Ralf

2 3

Link another address
by Brian Carpenter May 19, 2020

May 19, 2020

I am thinking about incorporating the following Postorius/Django account feature into Affinity: Other emails: (no other email) Link another address However I cannot think of a serious real-world need for this. What are the developers' reasoning behind this? Was this feature highly demanded by Mailman 3 users? Just trying to find out what I am missing here. Thanks, Brian

3 2

/hyperkitty/list/ shows "example.com" / mailman3 archives not updated
by patrick-mailinglists＠whonix.org May 18, 2020

May 18, 2020

/hyperkitty/list/ shows "example.com". Not the actual domain name that I configured. How can I fix this? I would not mind too much about hyperkitty showing "example.com". But the more important issue is that mailman3 archives are not updated. Therefore I guess it's a symptom of a more important issue. E-mails to the list are delivered to e-mail subscribers, though. Seems only the web part is broken. Using Debian buster mailman3 packages. In configuration folder /etc/mailman3 I cannot find any textual string saying "example.com". (`grep -r -i example /etc/mailman3`) Therefore I don't know where mailman3 gets "example.com" from. Could be broken linux file/folder access rights? Any way to debug? Kind regards, Patrick

2 2

Mailman Header Behavior
by Samir Faci May 16, 2020

May 16, 2020

I'm trying to use AWS SES as a mail relay for IP Health and other tidbits and it seems like it's very particular on what the headers look like. The FROM field has to be from a verified email meaning the list name has to be in the from field. I'm getting something along these lines for the rejection: May 15 16:28:26 lists postfix/smtp[2938320]: 1EA6C13880A: to=< csgeek(a)esamir.com>, relay=email-smtp.us-west-2.amazonaws.com[52.88.99.145]:587, delay=0.76, delays=0.01/0.02/0.43/0.31, dsn=5.0.0, status=bounced (host email-smtp.us-west-2.amazonaws.com[52.88.99.145] said: 554 Message rejected: Email address is not verified. The following identities failed the check in region US-WEST-2: Samir Faci <samir(a)esamir.com> (in reply to end of DATA command)) If on the other hand I enable the Anonymous list option then everything works, but I obviously have no clue who sent the email or how to respond to the person (if they're not subscribed) Is there a way to force mailman to ensure that the list name shows up in the from field? -- Thank you Samir Faci https://keybase.io/csgeek

5 8

unknown encoding: windows-874
by Mark Dadgar May 15, 2020

May 15, 2020

Anyone seen this before? Just started happening today. Latest ubuntu packages: - Mark ----- mark(a)pdc-racing.net | 408-348-2878 —— Internal Server Error: /mailman3/hyperkitty/api/mailman/archive LookupError at /hyperkitty/api/mailman/archive unknown encoding: windows-874 Request Method: POST Request URL: http://localhost/mailman3/hyperkitty/api/mailman/archive?key=MiloIsTheBestD… <http://localhost/mailman3/hyperkitty/api/mailman/archive?key=MiloIsTheBestD…> Django Version: 2.2.12 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.2 Python Path: ['.', '', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Wed, 13 May 2020 16:42:46 -0700 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', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py" in inner 40. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py" in _decorator 71. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/csrf.py" in wrapped_view 54. return view_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py" in archive 117. add_to_list(mlist_fqdn, msg) File "/usr/lib/python3/dist-packages/hyperkitty/lib/incoming.py" in add_to_list 123. email.content, attachments = scrubber.scrub() File "/usr/lib/python3/dist-packages/django_mailman3/lib/scrub.py" in scrub 77. attachments = self._get_all_attachments() File "/usr/lib/python3/dist-packages/django_mailman3/lib/scrub.py" in _get_all_attachments 98. attachments.append(self._parse_attachment(part, part_num)) File "/usr/lib/python3/dist-packages/django_mailman3/lib/scrub.py" in _parse_attachment 156. payload = part.get_content() File "/usr/lib/python3.8/email/message.py" in get_content 1096. if content_manager is None: File "/usr/lib/python3.8/email/contentmanager.py" in get_content 22. return self.get_handlers[maintype](msg, *args, **kw) File "/usr/lib/python3.8/email/contentmanager.py" in get_text_content 67. return content.decode(charset, errors=errors) Exception Type: LookupError at /hyperkitty/api/mailman/archive Exception Value: unknown encoding: windows-874 Request information: USER: AnonymousUser GET: key = <REDACTED> POST: mlist = <REDACTED> FILES: message = <InMemoryUploadedFile: message.txt ()> COOKIES: No cookie data META: CONTENT_LENGTH = '52215' CONTENT_TYPE = 'multipart/form-data; boundary=c697884a8c5c014c7e388933c444cab3' CONTEXT_DOCUMENT_ROOT = '/var/www/html' CONTEXT_PREFIX = '' DOCUMENT_ROOT = '/var/www/html' GATEWAY_INTERFACE = 'CGI/1.1' HTTP_ACCEPT = '*/*' HTTP_ACCEPT_ENCODING = 'gzip, deflate' HTTP_CONNECTION = 'keep-alive' HTTP_HOST = 'localhost' HTTP_USER_AGENT = 'python-requests/2.22.0' PATH = '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin' PATH_INFO = '/hyperkitty/api/mailman/archive' QUERY_STRING = 'key=MiloIsTheBestDogEver2018%21' REMOTE_ADDR = '127.0.0.1' REMOTE_PORT = '45516' REQUEST_METHOD = 'POST' REQUEST_SCHEME = 'http' REQUEST_URI = '/mailman3/hyperkitty/api/mailman/archive?key=MiloIsTheBestDogEver2018%21' SCRIPT_FILENAME = 'proxy:uwsgi://localhost//hyperkitty/api/mailman/archive' <uwsgi://localhost//hyperkitty/api/mailman/archive'> SCRIPT_NAME = '/mailman3' SERVER_ADDR = '127.0.0.1' SERVER_ADMIN = 'webmaster@localhost' SERVER_NAME = 'localhost' SERVER_PORT = '80' SERVER_PROTOCOL = 'HTTP/1.1' SERVER_SIGNATURE = '<address>Apache/2.4.41 (Ubuntu) Server at localhost Port 80</address>\n' SERVER_SOFTWARE = 'Apache/2.4.41 (Ubuntu)' uwsgi.core = 1 uwsgi.node = b'mail' uwsgi.version = b'2.0.18-debian' wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <uwsgi._Input object at 0x7ff7d81444b0> wsgi.multiprocess = False wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'http' wsgi.version = '(1, 0)' Settings: Using settings module settings ABSOLUTE_URL_OVERRIDES = {} ACCOUNT_AUTHENTICATION_METHOD = 'username_email' ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https' ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = 'mandatory' ACCOUNT_UNIQUE_EMAIL = True ADMINS = "(('Mailman Suite Admin', 'mark(a)pdc-racing.net <mailto:mark@pdc-racing.net>'),)" ALLOWED_HOSTS = ['*'] APPEND_SLASH = True AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')" AUTH_PASSWORD_VALIDATORS = '********************' AUTH_USER_MODEL = 'auth.User' BASE_DIR = '/usr/share/mailman3-web' CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}} CACHE_MIDDLEWARE_ALIAS = 'default' CACHE_MIDDLEWARE_KEY_PREFIX = '********************' CACHE_MIDDLEWARE_SECONDS = 600 COMPRESS_CACHEABLE_PRECOMPILERS = '()' COMPRESS_CACHE_BACKEND = 'default' COMPRESS_CACHE_KEY_FUNCTION = '********************' COMPRESS_CLEAN_CSS_ARGUMENTS = '' COMPRESS_CLEAN_CSS_BINARY = 'cleancss' COMPRESS_CLOSURE_COMPILER_ARGUMENTS = '' COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar' COMPRESS_CSS_COMPRESSOR = 'compressor.css.CssCompressor' COMPRESS_CSS_FILTERS = ['compressor.filters.css_default.CssAbsoluteFilter'] COMPRESS_CSS_HASHING_METHOD = 'mtime' COMPRESS_DATA_URI_MAX_SIZE = 1024 COMPRESS_DEBUG_TOGGLE = None COMPRESS_ENABLED = True COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7ff7db78fb80> COMPRESS_JS_COMPRESSOR = 'compressor.js.JsCompressor' COMPRESS_JS_FILTERS = ['compressor.filters.jsmin.JSMinFilter'] COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = True COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/mailman3/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = 'CACHE' COMPRESS_PARSER = 'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = '()' COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/var/lib/mailman3/web/static' COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage' COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/mailman3/static/'} COMPRESS_URL = '/mailman3/static/' COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/' COMPRESS_VERBOSE = False COMPRESS_YUGLIFY_BINARY = 'yuglify' COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal' COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal' COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar' COMPRESS_YUI_CSS_ARGUMENTS = '' COMPRESS_YUI_JS_ARGUMENTS = '' CSRF_COOKIE_AGE = 31449600 CSRF_COOKIE_DOMAIN = None CSRF_COOKIE_HTTPONLY = False CSRF_COOKIE_NAME = 'csrftoken' CSRF_COOKIE_PATH = '/' CSRF_COOKIE_SAMESITE = 'Lax' CSRF_COOKIE_SECURE = False CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure' CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN' CSRF_TRUSTED_ORIGINS = [] CSRF_USE_SESSIONS = False DATABASES = {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': '/var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db', 'USER': '', 'PASSWORD': '********************', 'HOST': '', 'PORT': '', 'OPTIONS': {}, 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'NAME': None, 'MIRROR': None}}} DATABASE_ROUTERS = [] DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440 DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000 DATETIME_FORMAT = 'N j, Y, P' DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%Y-%m-%d', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%Y', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M', '%m/%d/%y'] DATE_FORMAT = 'N j, Y' DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y'] DEBUG = False DEBUG_PROPAGATE_EXCEPTIONS = False DECIMAL_SEPARATOR = '.' DEFAULT_CHARSET = 'utf-8' DEFAULT_CONTENT_TYPE = 'text/html' DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = 'postorius(a)pdc-racing.net <mailto:postorius@pdc-racing.net>' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAILNAME = 'pdc-racing.net <http://pdc-racing.net/>' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = '' EMAIL_PORT = 25 EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = '********************' EMAIL_SUBJECT_PREFIX = '[Django] ' EMAIL_TIMEOUT = None EMAIL_USE_LOCALTIME = False EMAIL_USE_SSL = False EMAIL_USE_TLS = False FILE_CHARSET = 'utf-8' FILE_UPLOAD_DIRECTORY_PERMISSIONS = None FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler'] FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440 FILE_UPLOAD_PERMISSIONS = None FILE_UPLOAD_TEMP_DIR = None FILTER_VHOST = False FIRST_DAY_OF_WEEK = 0 FIXTURE_DIRS = [] FORCE_SCRIPT_NAME = None FORMAT_MODULE_PATH = None FORM_RENDERER = 'django.forms.renderers.DjangoTemplates' HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'xapian_backend.XapianEngine', 'PATH': '/var/lib/mailman3/web/xapian_index'}} HOSTNAME = 'localhost.local' IGNORABLE_404_URLS = [] INSTALLED_APPS = "('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', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora')" INTERNAL_IPS = [] LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('hy', 'Armenian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('th', 'Thai'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')] LANGUAGES_BIDI = ['he', 'ar', 'fa', 'ur'] LANGUAGE_CODE = 'en-us' LANGUAGE_COOKIE_AGE = None LANGUAGE_COOKIE_DOMAIN = None LANGUAGE_COOKIE_NAME = 'django_language' LANGUAGE_COOKIE_PATH = '/' LOCALE_PATHS = [] LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.RotatingFileHandler', 'filename': '/var/log/mailman3/web/mailman-web.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'INFO', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'postorius': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}} LOGGING_CONFIG = 'logging.config.dictConfig' LOGIN_REDIRECT_URL = 'list_index' LOGIN_URL = 'account_login' LOGOUT_REDIRECT_URL = None LOGOUT_URL = 'account_logout' MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1')" MAILMAN_ARCHIVER_KEY = '********************' MAILMAN_REST_API_PASS = '********************' MAILMAN_REST_API_URL = '********************' MAILMAN_REST_API_USER = '********************' MANAGERS = [] MEDIA_ROOT = '' MEDIA_URL = '' MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage' MESSAGE_TAGS = {40: 'danger'} MIDDLEWARE = "('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')" MIGRATION_MODULES = {} MONTH_DAY_FORMAT = 'F j' NUMBER_GROUPING = 0 PASSWORD_HASHERS = '********************' PASSWORD_RESET_TIMEOUT_DAYS = '********************' POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/ <http://localhost/mailman3/>' PREPEND_WWW = False Q_CLUSTER = {'timeout': 300, 'save_limit': 100, 'orm': 'default', 'poll': 5} ROOT_URLCONF = 'urls' SECRET_KEY = '********************' SECURE_BROWSER_XSS_FILTER = False SECURE_CONTENT_TYPE_NOSNIFF = False SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = None SECURE_REDIRECT_EXEMPT = [] SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = 'root(a)pdc-racing.net <mailto:root@pdc-racing.net>' SESSION_CACHE_ALIAS = 'default' SESSION_COOKIE_AGE = 1209600 SESSION_COOKIE_DOMAIN = None SESSION_COOKIE_HTTPONLY = True SESSION_COOKIE_NAME = 'sessionid' SESSION_COOKIE_PATH = '/' SESSION_COOKIE_SAMESITE = 'Lax' SESSION_COOKIE_SECURE = False SESSION_ENGINE = 'django.contrib.sessions.backends.db' SESSION_EXPIRE_AT_BROWSER_CLOSE = False SESSION_FILE_PATH = None SESSION_SAVE_EVERY_REQUEST = False SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' SETTINGS_MODULE = 'settings' SHORT_DATETIME_FORMAT = 'm/d/Y P' SHORT_DATE_FORMAT = 'm/d/Y' SIGNING_BACKEND = 'django.core.signing.TimestampSigner' SILENCED_SYSTEM_CHECKS = [] SITE_ID = 1 SOCIALACCOUNT_PROVIDERS = {} STATICFILES_DIRS = '()' STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')" STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage' STATIC_ROOT = '/var/lib/mailman3/web/static' STATIC_URL = '/mailman3/static/' TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}] TEST_NON_SERIALIZED_APPS = [] TEST_RUNNER = 'django.test.runner.DiscoverRunner' THOUSAND_SEPARATOR = ',' TIME_FORMAT = 'P' TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M'] TIME_ZONE = 'UTC' USE_I18N = True USE_L10N = True USE_THOUSAND_SEPARATOR = False USE_TZ = True USE_X_FORWARDED_HOST = True USE_X_FORWARDED_PORT = False WSGI_APPLICATION = 'wsgi.application' X_FRAME_OPTIONS = 'SAMEORIGIN' YEAR_MONTH_FORMAT = 'F Y'

3 2

Github auth deprecated API
by Quanah Gibson-Mount May 14, 2020

May 14, 2020

The version of mailman3 I'm running apparently uses a deprecated API for GitHub authentication. Does anyone know if this has been fixed? I couldn't find an issue for it on the postorius issue tracker. Sample email: ==================================================== Hello there! On May 14th, 2020 at 00:38 (UTC) your application used an access token (with the User-Agent python-requests/2.21.0) as part of a query parameter to access an endpoint through the GitHub API. https://api.github.com/user Please use the Authorization HTTP header instead as using the `access_token` query parameter is deprecated. Depending on your API usage, we'll be sending you this email reminder on a monthly basis. Visit https://developer.github.com/changes/2020-02-10-deprecating-auth-through-qu… for more information about suggested workarounds and removal dates. ==================================================== Thanks, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

2 2

Open List
by Samir Faci May 13, 2020

May 13, 2020

So, I found a setting to allow me to create an Open List. I assume this is still doable in MM3 though I can't find the equivalent option. https://mail.python.org/pipermail/mailman-users/2009-March/065479.html 2nd question is how do I create a new List Style. I'd like Open- Archived and Open-NonArchived to be options when creating a new list. -- Thank you Samir Faci https://keybase.io/csgeek

2 2

Mailman3 command line issue: NameError: name 'cli' is not defined when executing command=cli
by John W May 13, 2020

May 13, 2020

Hi, I am following the guide here: https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/create.h… and am falling at the first hurdle. command = cli('mailman.commands.cli_lists.create') NameError: name 'cli' is not defined. I am running the command in the mailman shell. Doing a help("mailman.commands") works so Python can see that. I thought it might require pyCLI so I installed that but still no joy.

2 1

Held messages not being deleted
by Andrew Hodgson May 12, 2020

May 12, 2020

Hi, I am finding that held messages although being deleted in the database are still being stored in the ~/var/messages directory structure. Is this by design? Thanks. Andrew.

2 1

Understanding of members, accounts
by Peter Adebahr May 12, 2020

May 12, 2020

Hi *, meanwhile we have subscribed a few addresses by the method of mass subscription. As these have to be private lists, users will have to provide a password to get access to the archives. I haven't found a way to provide, as admin, passwords to users. So I assumed users should go to "login", "lost password" and thus set their own. Alas, their e-mail addresses are not found in any list. Is the solution to "sign up", using one's very e-mail address already in the system? I would like to understand why there is a difference between being (only) a subscribed member and a member having an account - or, what might be the advantage of being a member without an account? Thank you and best regards, Peter

2 1

exim4 + mailman3 lmtp failure
by Thomas Drillich May 10, 2020

May 10, 2020

Hello, I tried to setup exim4 + mailman3 but it seems to stuck at lmtp delivery of mailman3. Could you give me a hint, to detect the reason of failure ? greetings Thomas ---- returned message --- This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: seebruecke(a)listen.td3.eu all hosts for 'listen.td3.eu' have been failing for a long time (and retry time not reached) Reporting-MTA: dns; detroit.drillich.net Action: failed Final-Recipient: rfc822;seebruecke(a)listen.td3.eu Status: 5.0.0 ----------------------------------------------------------- >exim -bv -d+all seebruecke(a)listen.td3.eu ... 19:45:02.715 32200 listen.td3.eu in "+mm_domains"? yes (matched "+mm_domains") 19:45:02.715 32200 checking require_files 19:45:02.715 32200 ┌considering: /var/lib/mailman3//lists/${local_part}.${domain} 19:45:02.715 32200 ├──expanding: /var/lib/mailman3//lists/${local_part}.${domain} 19:45:02.715 32200 └─────result: /var/lib/mailman3//lists/seebruecke.listen.td3.eu 19:45:02.715 32200 file check: /var/lib/mailman3//lists/${local_part}.${domain} 19:45:02.715 32200 expanded file: /var/lib/mailman3//lists/seebruecke.listen.td3.eu 19:45:02.715 32200 stat() yielded 0 19:45:02.715 32200 calling mailman3_router router 19:45:02.715 32200 mailman3_router router called for seebruecke(a)listen.td3.eu 19:45:02.715 32200 domain = listen.td3.eu 19:45:02.715 32200 set transport mailman3_transport 19:45:02.715 32200 queued for mailman3_transport transport: local_part = seebruecke 19:45:02.715 32200 domain = listen.td3.eu 19:45:02.715 32200 errors_to=NULL 19:45:02.715 32200 domain_data=NULL localpart_data=NULL 19:45:02.715 32200 routed by mailman3_router router 19:45:02.715 32200 envelope to: seebruecke(a)listen.td3.eu 19:45:02.715 32200 transport: mailman3_transport seebruecke(a)listen.td3.eu router = mailman3_router, transport = mailman3_transport # /etc/exim4/conf.d/transport/55_mm3_transport mailman3_transport: driver = smtp protocol = lmtp allow_localhost hosts = localhost port = MM3_LMTP_PORT rcpt_include_affixes = true -- mit freundlichem Gruss -- regards Thomas Drillich Heugasse 4 / D-55116 Mainz / Germany fon +49-6131-570-2621 mobil +49-162-469-5875

3 6

Handling of Mail from non-subscribers
by Peter Adebahr May 9, 2020

May 9, 2020

Hi *, I have a fresh setup of MM3 on Ubuntu 20, installed by apt-get. It seems to be running fine so far, except for some (to me) strange behaviour: When posting to the list as a non-subscriber, I see the mail coming in on mailman's smtp.log, then it vanishes. No notice of this mail being hold is sent to the sender, no notice to the moderator, and logging into Postorius as owner of the list, it is not showing up in "Held messages" "Hold for moderation" has been set. Any idea how to debug this will be welcome - thank you :) Best regards, Peter

2 7

PSA: Avoiding spam-scanning outgoing mailman3 mail
by Mark Dadgar May 8, 2020

May 8, 2020

So I integrated SpamAssassin into my mailman3 server the other day, using the ubuntu packages which implement the “standard” SpamAssassin install with a filter on port 25 and re-injection using /usr/sbin/sendmail. From postfix/master.cf: # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== smtp inet n - n - 10 smtpd -o content_filter=spamassassin spamassassin unix - n n - - pipe user=debian-spamd argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender} ${recipient} The problem there, of course, is that mailman3 traffic gets scanned twice: once on the way in from the original sender and once on the way out as mailman3 duplicates it to list recipients. This is because out-of-the-box mailman3 tends to be configured to re-inject list email via port 25, which is scanning for spam on incoming email. This is horribly inefficient, obviously, and gets worse the bigger your mailing list is. Given that it’s written in Perl, SpamAssassin isn’t the most efficient thing in the first place. Anyway, I got literally zero hits on solving this when I googled it, so here’s mine to save future mailman3+SpamAssassin users some grief. The easy fix was to edit the [mta] setting in mailman.cfg to deliver email via the submit port instead, which has no filtering applied to it: smtp_host: localhost # using the submit port bypasses spamassassin filtering on outgoing list email smtp_port: 587 smtp_user: mm3send <— I created this user for this purpose smtp_pass: <password-for-mm3send-user> This works great and can be applied to any email filtering. FYI. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

2 2

Link in the top-left corner of Hyperkitty
by Seth Seeger May 8, 2020

May 8, 2020

Hello, There is a link to the root of Hyperkitty in the top left corner of my Hyperkitty pages. It links to the correct domain, but the text isn’t right - it’s the first domain name I was using at the beginning of my install for testing. I’d like to update it, but can’t find what to change. Thanks, Seth

3 7

Can it work on FreebSD
by Peter Fraser May 8, 2020

May 8, 2020

Hi All I would really be interested in getting this working of FreeBSD. I find the BSD’s to be very stable and easy to maintain. Please could anyone point me to any document or suggestions to get it working on FreeBSD? Much Appreciated. Regards SI Sent from [1]Mail for Windows 10 References 1. https://go.microsoft.com/fwlink/?LinkId=550986

3 2

Post log?
by Mark Dadgar May 6, 2020

May 6, 2020

Is there the equivalent of the post log from mailman 2.x available? I see every logging option but that one listed here: https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.htm… <https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.htm…> That was a handy way to track list traffic statistics and I was hoping to munge up the old mm_stats script to use the mailman3 logging format. I am running the ubuntu 3.2.2-based package. Thanks, as always! - Mark ----- mark(a)pdc-racing.net | 408-348-2878

2 2

How to remove a nonmember from a list
by skenny＠scss.tcd.ie May 5, 2020

May 5, 2020

Hi, I've been banging my head against the proverbial wall for more than a day trying to remove nonmembers from a list (I am a Mailman3 and Python novice so that might account for something, but anyway ...) According to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, it should be possible to do: MailingList.remove_role('nonmember', 'email_address(a)example.com') However I can't get this to work. I think I have manage to track down all the required imports. This is what I see: TypeError: remove_role() missing 1 required positional argument: 'address' More digging in the docs seems to indicate that a third parameter is required - "self". At this point though I am way out of my depth, and would appreciate any guidance. Thanks very much Stephen Kenny

4 26

HyperKitty Question
by Samir Faci May 5, 2020

May 5, 2020

Okay, I have mailman3 working to allow me to send/receive emails. postorius seems to be working fine. My only issue seems to be with hyperkitty saving the archive. postorius seems to be working fine. Hyperkitty on the other hand is failing. I have nginx running with multiple website being serviced from the same server. I updated the config where port 80 gets redirected to SSL. I tried setting mailman3-hyperkitty.conf to both: base_url: http://localhost/hyperkitty/ base_url: https://lists.domain.com/hyperkitty/ But neither seem to be working. Does hyperkitty require traffic to be going over port 80? -- Thank you Samir Faci https://keybase.io/csgeek

2 2

Re: Installation Wooes
by Mark Sapiro May 4, 2020

May 4, 2020

On 5/3/20 8:13 PM, Samir Faci wrote: > > Postfix Failed Logs. > > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 > May 4 03:07:36 lists postfix/smtpd[1968155]: connect from > unknown[198.199.98.177] > May 4 03:07:36 lists postfix/smtpd[1968155]: 745B31473C6: > client=unknown[198.199.98.177] > May 4 03:07:36 lists postfix/cleanup[1968158]: 745B31473C6: > message-id=<158856165549.136760.840427238489827082@lists> > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: > from=<booh-bounces(a)lists.domain.org So mailman and Postfix are on different machines. That may complicate things, but > <mailto:booh-bounces@lists.domain.org>>, size=5474, nrcpt=1 (queue active) > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > May 4 03:07:36 lists postfix/lmtp[1968159]: 745B31473C6: > to=<booh-owner(a)lists.domain.org <mailto:booh-owner@lists.domain.org>>, > relay=lists.domain.org <http://lists.domain.org>[198.199.98.177]:8024, > delay=0.03, delays=0/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) This was a successful delivery. > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: removed > May 4 03:07:38 lists postfix/smtpd[1968155]: connect from > unknown[198.199.98.177] > May 4 03:07:38 lists postfix/smtpd[1968155]: NOQUEUE: reject: RCPT from > unknown[198.199.98.177]: 554 5.7.1 <csgeek(a)domain.com > <mailto:csgeek@domain.com>>: Relay access denied; > from=<booh-bounces+csgeek=domain.com(a)lists.domain.org > <mailto:domain.com@lists.domain.org>> to=<csgeek(a)domain.com > <mailto:csgeek@domain.com>> proto=ESMTP helo=<[127.0.1.1]> You are sending from a remote machine 198.199.98.177 to a presumably remote domain domain.com so relay access is denied as it should be. You need to add 198.199.98.177 to mynetworks in Postfix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 6

Re: Installation Wooes
by Mark Sapiro May 4, 2020

May 4, 2020

On 5/3/20 8:43 PM, Samir Faci wrote: > Inline. > > On Sun, May 3, 2020, 20:32 Mark Sapiro <mark(a)msapiro.net > <mailto:mark@msapiro.net>> wrote: > > You are sending from a remote machine 198.199.98.177 to a presumably > remote domain domain.com <http://domain.com> so relay access is > denied as it should be. > > You need to add 198.199.98.177 to mynetworks in Postfix. > > > I can but domain.com <http://domain.com> is basically my Gmail I just > regex-ed the logs. If that's the fix is have to add every recepients > domain to mynetworks. You absolutely don't want to do that. The log entry is confusing. Between your munging domains and my MUA adding mailto: links to every email address, it's a mess. Let's try again: May 4 03:07:38 lists postfix/smtpd[1968155]: NOQUEUE: reject: RCPT from unknown[198.199.98.177]: 554 5.7.1 <csgeek(a)domain.com>: Relay access denied; from=<booh-bounces+csgeek=domain.com(a)lists.domain.org> to=<csgeek(a)domain.com> proto=ESMTP helo=<[127.0.1.1]>. This says Postfix received a RCPT command from 98.199.98.177. It looks like it comes from Mailman, i.e., the envelope sender loogs like a Mailman VERPed address <booh-bounces+csgeek=domain.com(a)lists.domain.org> for a message to <csgeek(a)domain.com> and that is the envelope recipient and the sender identified itself in EHLO as [127.0.1.1]. So Postfix thinks it is asked to relay from 98.199.98.177 to domain.com. Note that 98.199.98.177 is a Comcast network IP. It has nothing to do with gmail. So is the connect comes from Mailman on the Postfix machine, why does Postfix think it comes from 98.199.98.177. That's the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Error after upgrading mailman3
by Gelpi Andrea May 4, 2020

May 4, 2020

Hi, in my installation the command mailman notify does not exist. Checking the debian packages I noticed the I could upgrade mailman form 3.2.1 to 3.2.2; mailman-web form 20180916-8 to 20180916-10; python3-django-hyperkitty from 1.2.2 to 1.3.2 I did it with apt-get install After that when I try to go to a postorius page the error Mailman REST API not available. Please start Mailman core in mailman log I found: May 4 15:13:08 posta mailman3[10259]: Cannot import runner module: mailman.runners.rest.RESTRunner May 4 15:13:08 posta mailman3[10259]: Traceback (most recent call last): May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/bin/runner.py", line 55, in make_runner May 4 15:13:08 posta mailman3[10259]: runner_class = find_name(class_path) May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 52, in find_name May 4 15:13:08 posta mailman3[10259]: module = import_module(module_path) May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module May 4 15:13:08 posta mailman3[10259]: return _bootstrap._gcd_import(name[level:], package, level) May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 1006, in _gcd_import May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 983, in _find_and_load May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 677, in _load_unlocked May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap_external>", line 728, in exec_module May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/runners/rest.py", line 27, in <module> May 4 15:13:08 posta mailman3[10259]: from mailman.rest.wsgiapp import make_server May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 25, in <module> May 4 15:13:08 posta mailman3[10259]: from falcon.routing import map_http_methods, set_default_responders May 4 15:13:08 posta mailman3[10259]: ImportError: cannot import name 'map_http_methods' from 'falcon.routing' (/usr/lib/python3/dist-packages/falcon/routing/__init__.py) I think there is a dependency error somewhere. Is there a way to solve it? Thank You -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

3 3

Installation Wooes
by Samir Faci May 4, 2020

May 4, 2020

A few questions about an Ubuntu install. I managed to add my domain to hyperkitty, created a new list and now i'm getting this behavior: ``` May 02 07:47:24 2020 (55358) deque: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 331, in _step_send_confirmation self._set_token(TokenOwner.subscriber) File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 157, in _set_token self.token = pendings.add(pendable, timedelta(days=3650)) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line 91, in add token = token_factory.new() File "/usr/lib/python3/dist-packages/mailman/utilities/uid.py", line 79, in new return self._next_unpredictable_id() File "/usr/lib/python3/dist-packages/mailman/utilities/uid.py", line 155, in _next_unpredictable_id x = random.random() + right_now % 1.0 + time.clock() % 1.0 AttributeError: module 'time' has no attribute 'clock' ``` I'm on python 3.8.2 Question #2. I'm setting up mailman 3 on sqlite for simplicity's sake. Do people find the performance of mysql / postgres worth the upgrade? 2B. Is there a migration path if I want to switch to mysql at a later date? -- Thank you Samir Faci https://keybase.io/csgeek

3 6

/bin/sh: sassc: command not found
by Ralf Wiegand May 4, 2020

May 4, 2020

/bin/sh: sassc: command not found - Not sure on what I am missing? FilterError at /hyperkitty/ /bin/sh: sassc: command not found Request Method: GET Request URL: http://192.168.0.27:8000/hyperkitty/ Django Version: 2.2.12 Exception Type: FilterError Exception Value: /bin/sh: sassc: command not found Exception Location: /opt/mailman/venv-3.6/lib64/python3.6/site-packages/django_compressor-2.4-py3.6.egg/compressor/filters/base.py in input, line 206 Python Executable: /opt/mailman/venv-3.6/bin/python Python Version: 3.6.8

3 5

Separating Lists by Domain
by brian＠emwd.com May 1, 2020

May 1, 2020

I have successfully setup a second domain with my Mailman3 setup. I also created a list using the second domain. So I have two domains with one list each. The issue I see at this point is all of the lists are shown via Postorius regardless of the list domain used. Is it possible to have only the lists to show that are part of the domain being used to access? For example: http://domaina.com/postorius/lists/ Only listnames(a)domaina.com show up. http://domainb.com/postorius/lists/ Only listnames(a)domainb.com show up. Right now both domaina AND domainb lists showup regardless of the domain being used to access Postorius. The same goes for Hyperkitty as well. Brian

6 11

Running mailman3 on AWS and dealing with SES email verification
by Mohsen Masoudfar May 1, 2020

May 1, 2020

Hi, This seems to be a very basic question and/or issue, but I could not find a reliable for it: Assume a list member with the email address like (just as an example) joe.student(a)university.edu<mailto:joe.student@university.edu> sends an email to a list, Mailman gets the email, processes it and would try to send that email to all members with a sender field as: 'joe.student(a)university.edu<mailto:joe.student@university.edu>'. plus listname(a)listserver.TLD<mailto:listname@listserver.TLD> AWS allows verified email addresses to send an email from an EC2 to internet, so the listname(a)listserver.TLD<mailto:listname@listserver.TLD> is OK, because listserver.TLD is already verified, BUT Joe's email is not and cannot be, because there are thousands of list users and they can change daily. The result is that Mailman's try to send the email would fail with the following error message: Message rejected: Email address is not verified. The following identities failed the check in region US-EAST-1: joe.student(a)university.edu<mailto:joe.student@university.edu> I changed the list property and made it an anonymous one, and it started sending the emails to the whole list members, but only with listname(a)listserver.TLD<mailto:listname@listserver.TLD> as the sender. So the list recipients cannot know the initiator of the discussion. I found some solution: * Asking the members to add their email to the signature * manipulating the from field and add the name of the sender as a comment, not that easy, needs some Python code * manipulating the from files and replacing the @ with something else, not that easy, needs some Python code * . . . More important: None of these would allow a simple click on the reply bottom to send the email to the original sender. I am thinking of running mailman on-premise and use our email relay, which we have full control on. But really, there is no elegant solution for this? I already opened a ticket with AWS support and they just insisted on their policy of verification. Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087

2 3

Recipient address rejected: User unknown in local recipient table
by Mohsen Masoudfar May 1, 2020

May 1, 2020

Hi, I created a list called list_b@newlistserv.<tld<mailto:list_b@newlistserv.%3ctld>> , and added a user to it and invited the user. The user got a welcome email, when the user replies with help, The email gets rejected with the message: list_b wasn't found at newlistserv.<tld> and I see this entry in the postfix log on the server: postfix/smtpd[6757]: NOQUEUE: reject: RCPT from mail-eopbgr750113.outbound.xxx: 550 5.1.1 <list_b(a)newlistserv.xxx>: Recipient address rejected: User unknown in local recipient table; from=<xxx> to=<list_b(a)newlistserv.xxx> proto=ESMTP helo=<NAM02-BL2-obe.outbound.protection.outlook.com> I am new to mailman3, my understanding was, maybe wrong, that when I create a list, mailman3 adds that to the local list of users. I think , I am missing something . . . Or probably this is related to a postfix setting? Best regards Mohsen

3 6

I have issue where it does not send emails on to people in the list I create.
by john_warland＠hotmail.com April 30, 2020

April 30, 2020

Hello, I am quite new to Mailman3 and have been trying to get a working local test setup on a single VM (Centos07) I have issue where if I send an email to the list. it does not send emails on to the people subscribed to that list. Note the steps below were put together from memory after a few days of repeatably trying different things so there will be some inaccuracies I have mailman running on same local box as postfix, postorius and hyperkitty. I have root as the superuser in Postorius and have tried the following: In unix shell created new user 'developer' In unix shell created new user 'tester' In shell send an email from developer user to tester: echo 'Hello' | mailx -s 'Hello Subject line' tester(a)sandbox.mytest.com Confirmed user tester received email in cat /home/tester/Maildir/new/ folder: Return-Path: <developer(a)cloud7.sandbox.mytest.com> X-Original-To: tester(a)cloud7.sandbox.mytest.com Delivered-To: tester(a)cloud7.sandbox.mytest.com Received: by cloud7.sandbox.mytest.com (Postfix, from userid 1000) In Postorius web frontend: Signed up as root Received confirmation email in /root/Maildir/new/ folder so cut and pasted the Url in the email to activate account. Created new list called testlist(a)sandbox.mytest.com Logged out Signed up as tester Received confirmation email in /home/tester/Maildir/new/ folder so cut and pasted the Url to activate account. Subscribed tester to the testlist. Next in unix shell su as developer and send an email to testlist(a)sandbox.mytest.com The root user gets the following email Content-Transfer-Encoding: 7bit Subject: Your message to testlist(a)cloud7.sandbox.mytest.com awaits moderator approval From: testlist-bounces(a)cloud7.sandbox.mytest.com To: developer(a)cloud7.sandbox.mytest.com Message-ID: <158824480291.3035.17408340520496115243(a)localhost.localdomain> Date: Thu, 30 Apr 2020 11:06:42 +0000 Precedence: bulk X-Mailman-Version: 3.3.0 Your mail to 'testlist(a)cloud7.sandbox.mytest.com' with the subject hello there 2 Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member Either the message will get posted to the list, or you will receive notification of the moderator's decision. Once I have gone back into Postorius as root and approved the message, root user gets a second email: Return-Path: <testlist-bounces(a)cloud7.sandbox.mytest.com> X-Original-To: root(a)cloud7.sandbox.mytest.com Delivered-To: root(a)cloud7.sandbox.mytest.com Received: from localhost.localdomain (localhost [IPv6:::1]) by cloud7.sandbox.mytest.com (Postfix) with ESMTP id E056A84CE4 for <root(a)cloud7.sandbox.mytest.com>; Thu, 30 Apr 2020 11:09:10 +0000 (UTC) Received: by cloud7.sandbox.mytest.com (Postfix, from userid 1000) id 8F1B684CE4; Thu, 30 Apr 2020 11:06:41 +0000 (UTC) Date: Thu, 30 Apr 2020 11:06:41 +0000 To: testlist(a)cloud7.sandbox.mytest.com User-Agent: Heirloom mailx 12.5 7/5/10 MIME-Version: 1.0 Message-Id: <20200430110641.8F1B684CE4(a)sandbox.mytest.com> From: developer(a)cloud7.sandbox.mytest.com X-MailFrom: developer(a)cloud7.sandbox.mytest.com X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation Message-ID-Hash: FAPTJKJRZG2ELSOSBRBIDOBWXP3Y5QAY X-Message-ID-Hash: FAPTJKJRZG2ELSOSBRBIDOBWXP3Y5QAY X-Mailman-Approved-At: Thu, 30 Apr 2020 11:09:10 +0000 X-Mailman-Version: 3.3.0 Precedence: list Subject: [Testlist] hello there 2 List-Id: A test list <testlist.sandbox.mytest.com> List-Help: <mailto:testlist-request@sandbox.mytest.com?subject=help> List-Post: <mailto:testlist@sandbox.mytest.com> List-Subscribe: <mailto:testlist-join@sandbox.mytest.com> List-Unsubscribe: <mailto:testlist-leave@sandbox.mytest.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit A test email 2 _______________________________________________ Testlist mailing list -- testlist(a)sandbox.mytest.com To unsubscribe send an email to testlist-leave(a)sandbox.mytest.com At no point does the email appear in the tester(a)sandbox.mytest.com Maildir Configs as follows.. ================================================================================================== /etc/postfix/main.cf: ================================================================================================== queue_directory = /var/spool/postfix command_directory = /usr/sbin daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix mail_owner = postfix myhostname = cloud7.sandbox.mytest.com mydomain = sandbox.mytest.com myorigin = $mydomain inet_interfaces = all inet_protocols = all mydestination = $myhostname, localhost.$mydomain, localhost, mail.$mydomain, www.$mydomain, ftp.$mydomain, sandbox.mytest.com unknown_local_recipient_reject_code = 550 # Next line Obfuscated mynetworks = 192.***.***.0/24, 127.0.0.0/8 alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases recipient_delimiter = + home_mailbox = Maildir/ debug_peer_level = 2 debug_peer_list = sandbox.mytest.com debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 sendmail_path = /usr/sbin/sendmail.postfix newaliases_path = /usr/bin/newaliases.postfix mailq_path = /usr/bin/mailq.postfix setgid_group = postdrop html_directory = no manpage_directory = /usr/share/man sample_directory = /usr/share/doc/postfix-2.10.1/samples readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES disable_dns_lookups = yes owner_request_special = no transport_maps = hash:/var/lib/mailman/data/postfix_lmtp # Setting to nothing fixes 'Recepient address rejected: User unknown in local recipient table local_recipient_maps = relay_domains = hash:/var/lib/mailman/data/postfix_domains ================================================================================================== /etc/mailman.cfg ================================================================================================== [devmode] enabled: yes recipient: root(a)sandbox.mytest.com [mailman] # local = Recommended as installing mailman from source. Folder structure in /var/tmp/mailman # fhs = /var/bin, /var/log, etc.. layout: fhs [logging.database] level: info [mta] # This config is for when mailman and the MTA (Postfix) are on the same host incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix [webservice] hostname: localhost port: 8001 use_https: no admin_user: restadmin admin_pass: restpass api_version: 3.1 ================================================================================================== /etc/mailman-suite-1.0.0/mailman-suite_project/settings.py ================================================================================================== In this file the main changes were: DEBUG=True SERVER_EMAIL = 'root(a)localhost.local' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' Commented out three lines of code: # if DEBUG == True: # EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' # EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails') Complete file: """ Django Settings for Mailman Suite (hyperkitty + postorius) For more information on this file, see https://docs.djangoproject.com/en/1.8/topics/settings/ For the full list of settings and their values, see https://docs.djangoproject.com/en/1.8/ref/settings/ """ # Build paths inside the project like this: os.path.join(BASE_DIR, ...) import os BASE_DIR = os.path.dirname(os.path.abspath(__file__)) # SECURITY WARNING: keep the secret key used in production secret! SECRET_KEY = 'change-this-on-your-production-server' # SECURITY WARNING: don't run with debug turned on in production! # Have to keep it True atm as the css styles screw up when set to False DEBUG = True ADMINS = ( ('Mailman Suite Admin', 'root@localhost'), ) SITE_ID = 1 # Hosts/domain names that are valid for this site; required if DEBUG is False # See https://docs.djangoproject.com/en/1.8/ref/settings/#allowed-hosts ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. "MAILMAN_SERVER_ADDRESS", <--- I inject IP Address here # Add here all production URLs you may have. ] # Mailman API credentials MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' MAILMAN_ARCHIVER_KEY = 'SecretArchiverAPIKey' MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') # Application definition INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', '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.facebook', 'allauth.socialaccount.providers.twitter', 'allauth.socialaccount.providers.stackexchange', ) MIDDLEWARE = ( 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', ) ROOT_URLCONF = 'urls' TEMPLATES = [ { 'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': { 'context_processors': [ 'django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius', ], }, }, ] WSGI_APPLICATION = 'wsgi.application' # Database # https://docs.djangoproject.com/en/1.8/ref/settings/#databases DATABASES = { 'default': { # Use 'sqlite3', 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'. 'ENGINE': 'django.db.backends.sqlite3', # DB name or path to database file if using sqlite3. 'NAME': os.path.join(BASE_DIR, 'mailmansuite.db'), # The following settings are not used with sqlite3: 'USER': 'mailmansuite', 'PASSWORD': 'mmpass', # HOST: empty for localhost through domain sockets or '127.0.0.1' for # localhost through TCP. 'HOST': '', # PORT: set to empty string for default. 'PORT': '', } # Example for PostgreSQL (recommanded for production): #'default': { # 'ENGINE': 'django.db.backends.postgresql_psycopg2', # 'NAME': 'database_name', # 'USER': 'database_user', # 'PASSWORD': 'database_password', # 'HOST': 'localhost', #} } # If you're behind a proxy, use the X-Forwarded-Host header # See https://docs.djangoproject.com/en/1.8/ref/settings/#use-x-forwarded-host # USE_X_FORWARDED_HOST = True # And if your proxy does your SSL encoding for you, set SECURE_PROXY_SSL_HEADER # https://docs.djangoproject.com/en/1.8/ref/settings/#secure-proxy-ssl-header # SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') # SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_SCHEME', 'https') # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' # Password validation # https://docs.djangoproject.com/en/1.9/ref/settings/#auth-password-validators AUTH_PASSWORD_VALIDATORS = [ { 'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator', }, { 'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator', }, { 'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator', }, { 'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator', }, ] # Internationalization # https://docs.djangoproject.com/en/1.8/topics/i18n/ LANGUAGE_CODE = 'en-us' TIME_ZONE = 'UTC' USE_I18N = True USE_L10N = True USE_TZ = True # Static files (CSS, JavaScript, Images) # https://docs.djangoproject.com/en/1.8/howto/static-files/ # Absolute path to the directory static files should be collected to. # Don't put anything in this directory yourself; store your static files # in apps' "static/" subdirectories and in STATICFILES_DIRS. # Example: "/var/www/example.com/static/" STATIC_ROOT = os.path.join(BASE_DIR, 'static') # URL prefix for static files. # Example: "http://example.com/static/", "http://static.example.com/" STATIC_URL = '/static/' # Additional locations of static files STATICFILES_DIRS = ( # Put strings here, like "/home/html/static" or "C:/www/django/static". # Always use forward slashes, even on Windows. # Don't forget to use absolute paths, not relative paths. # BASE_DIR + '/static/', ) # List of finder classes that know how to find static files in # various locations. STATICFILES_FINDERS = ( 'django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', # 'django.contrib.staticfiles.finders.DefaultStorageFinder', 'compressor.finders.CompressorFinder', ) # Django 1.6+ defaults to a JSON serializer, but it won't work with # django-openid, see # https://bugs.launchpad.net/django-openid-auth/+bug/1252826 SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' LOGIN_URL = 'account_login' LOGIN_REDIRECT_URL = 'list_index' LOGOUT_URL = 'account_logout' # If you enable internal authentication, this is the address that the emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-email # DEFAULT_FROM_EMAIL = "mailing-lists(a)you-domain.org" DEFAULT_FROM_EMAIL = 'postorius(a)localhost.local' # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root(a)localhost.local' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' # Compatibility with Bootstrap 3 from django.contrib.messages import constants as messages # flake8: noqa MESSAGE_TAGS = { messages.ERROR: 'danger' } # # Social auth # AUTHENTICATION_BACKENDS = ( 'django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend', ) # Django Allauth ACCOUNT_AUTHENTICATION_METHOD = "username_email" ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = "mandatory" # You probably want https in production, but this is a dev setup file ACCOUNT_DEFAULT_HTTP_PROTOCOL = "http" ACCOUNT_UNIQUE_EMAIL = True SOCIALACCOUNT_PROVIDERS = { 'openid': { 'SERVERS': [ dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com'), ], }, 'google': { 'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}, }, 'facebook': { 'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': [ 'email', 'name', 'first_name', 'last_name', 'locale', 'timezone', ], 'VERSION': 'v2.4', }, } # # Gravatar # https://github.com/twaddington/django-gravatar # # Gravatar base url. # GRAVATAR_URL = 'http://cdn.libravatar.org/' # Gravatar base secure https url. # GRAVATAR_SECURE_URL = 'https://seccdn.libravatar.org/' # Gravatar size in pixels. # GRAVATAR_DEFAULT_SIZE = '80' # An image url or one of the following: 'mm', 'identicon', 'monsterid', # 'wavatar', 'retro'. # GRAVATAR_DEFAULT_IMAGE = 'mm' # One of the following: 'g', 'pg', 'r', 'x'. # GRAVATAR_DEFAULT_RATING = 'g' # True to use https by default, False for plain http. # GRAVATAR_DEFAULT_SECURE = True # # django-compressor # https://pypi.python.org/pypi/django_compressor # COMPRESS_PRECOMPILERS = ( ('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sass -t compressed {infile} {outfile}'), ('text/x-sass', 'sass -t compressed {infile} {outfile}'), ) # On a production setup, setting COMPRESS_OFFLINE to True will bring a # significant performance improvement, as CSS files will not need to be # recompiled on each requests. It means running an additional "compress" # management command after each code upgrade. # http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression # COMPRESS_OFFLINE = True # Needed for debug mode # INTERNAL_IPS = ('127.0.0.1',) # # Full-text search engine # HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), # You can also use the Xapian engine, it's faster and more accurate, # but requires another library. # http://django-haystack.readthedocs.io/en/v2.4.1/installing_search_engines.h… # Example configuration for Xapian: #'ENGINE': 'xapian_backend.XapianEngine' }, } # # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } # A sample logging configuration. The only tangible logging # performed by this configuration is to send an email to # the site admins on every HTTP 500 error when DEBUG=False. # See http://docs.djangoproject.com/en/dev/topics/logging for # more details on how to customize your logging configuration. LOGGING = { 'version': 1, 'disable_existing_loggers': False, 'filters': { 'require_debug_false': { '()': 'django.utils.log.RequireDebugFalse' } }, 'handlers': { 'mail_admins': { #'level': 'ERROR', 'level': 'INFO', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler' }, 'file':{ #'level': 'ERROR', 'level': 'INFO', #'class': 'logging.handlers.RotatingFileHandler', 'class': 'logging.handlers.WatchedFileHandler', 'filename': os.path.join(BASE_DIR, 'logs', 'mailmansuite.log'), 'formatter': 'verbose', }, 'console': { 'class': 'logging.StreamHandler', 'formatter': 'simple', }, }, 'loggers': { 'django.request': { 'handlers': ['mail_admins', 'file'], #'level': 'ERROR', 'level': 'INFO', 'propagate': True, }, 'django': { 'handlers': ['file'], #'level': 'ERROR', 'level': 'INFO', 'propagate': True, }, 'hyperkitty': { 'handlers': ['file'], #'level': 'DEBUG', 'level': 'INFO', 'propagate': True, }, 'postorius': { 'handlers': ['console', 'file'], #'level': 'ERROR', 'level': 'INFO', }, }, 'formatters': { 'verbose': { 'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s' }, 'simple': { 'format': '%(levelname)s %(message)s' }, }, 'root': { 'handlers': ['file'], #'level': 'ERROR', 'level': 'INFO', }, } # Using the cache infrastructure can significantly improve performance on a # production setup. This is an example with a local Memcached server. #CACHES = { # 'default': { # 'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache', # 'LOCATION': '127.0.0.1:11211', # } #} # When DEBUG is True, don't actually send emails to the SMTP server, just store # them in a directory. This way you won't accidentally spam your mailing-lists # while you're fiddling with the code. # Kept DEBUG=True as it breaks css styling when set to False so commented out this code as temp fix. #if DEBUG == True: # EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' # EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails') # # HyperKitty-specific # # Only display mailing-lists from the same virtual host as the webserver FILTER_VHOST = False POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' try: from settings_local import * except ImportError: pass

2 5

Importing Mailman 2 Lists apart from Django
by Brian Carpenter April 30, 2020

April 30, 2020

Hello Mailman Users, Are there instructions on importing a Mailman 2 list into a Mailman 3 core installation only? Does the import21 script not need Django/Postorius/Hyperkitty? It seems Django is required to import archives I guess because of the use of Hyperkitty. How about importing archives without having a Django installation? Is that what the prototype archiver for? We are getting ready to start working on a custom forum application for Mailman 3 (called Empathy) and I am would like to import some mailman 2 archives into the development server to work with. Thanks. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

3 3

MM3 on debian - redirect problem
by Gelpi Andrea April 30, 2020

April 30, 2020

Hi, on a debian10 I have mm3 installed via apt-get apt-get install mailman3-full dpkg-reconfigure mailman3 dpkg-reconfigure mailman3-web I have this minor issue https://webserver/mailman3 redirects to http://webserver/mailman/postorius/lists/ that doesn't exist. The same problem form django admin page to return to lists https://website/mailman3/admin/sites/site In the upper right corner I have a link to https://webserver/mailman3 that redirects to https://mailman/postorius/lists/ I searched for a redirect but without success. Thank You -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

3 3

mailman3 vs postfix
by Ralf Wiegand April 29, 2020

April 29, 2020

Hello, I need some help to get the postfix part to work right. Because this is a test setup I don't really send any emails out. How can I create a admin login account without email verification? Thank you, best regards Ralf Wiegand

2 9

Fwd: [GNC-dev] Passwords are Confidential
by flywire April 29, 2020

April 29, 2020

Looking forward to Mailman 3. How can I get an indication of when Mailman 3 code is likely to run on Fedora 29? On Sun, Apr 26, 2020 at 1:42 AM Mark Sapiro wrote: > On 4/25/20 2:08 AM, flywire wrote: > > MailMan version 2.1.29 > > > > On Sat, Apr 25, 2020 at 6:08 PM Adrien Monteleone wrote: > > > > You can turn off the reminder in your mailman settings. > > > > As this is part of the mailman code, perhaps a bug report to them > > would be in order concerning the storage issue. > > > > Regards, > > Adrien > > > > > On Apr 24, 2020 w17d115, at 11:29 PM, flywire > > > > > > My password is confidential so please don't email it to me in > > plain text. > > > Don't even store it, instead encrypt what I entered and store that > > so you > > > can verify an encrypted version of the password I enter in the > future. > > > This is a well known, long standing issue which will not be fixed in > Mailman 2.1. See <https://bugs.launchpad.net/mailman/+bug/265179> > > It is fixed in Mailman 3. > > -- > Mark Sapiro > Derek Atkins 2020-04-25 18:32:15 EDT Code runs Fedora 29. Mailman 3 isn't available on F29. When code gets upgraded, mailman will be upgraded. As for turning off the reminder; you can turn it off yourself. Thank you.

2 1

having issues with EMAIL_HOST =
by Ralf Wiegand April 28, 2020

April 28, 2020

python manage.py runserver 0.0.0.0:8000 Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/management/__init__.py", line 325, in execute settings.INSTALLED_APPS File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/conf/__init__.py", line 79, in __getattr__ self._setup(name) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/conf/__init__.py", line 66, in _setup self._wrapped = Settings(settings_module) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/conf/__init__.py", line 157, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 994, in _gcd_import File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 665, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 674, in exec_module File "<frozen importlib._bootstrap_external>", line 781, in get_code File "<frozen importlib._bootstrap_external>", line 741, in source_to_code File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/opt/mailman/mailman-suite/mailman-suite_project/settings.py", line 286 EMAIL_HOST = ‘mail.somedomain.org’ ^ SyntaxError: invalid character in identifier Mark - I don't want to complain all the time, but it is a nightmare to install and setup mailman3. Any idea why I am getting the above message? Thank You, Ralf Wiegand

2 1

hyperkitty web site
by Gelpi Andrea April 28, 2020

April 28, 2020

Hi, after importing old mm2 messages into mm3 archive I found that hyperkitty dos not show the lists index in home page if FILTER_VHOST = True https://website/mailman3/hyperkitty/ show an empty lists. If I add list/list@domain1 I can see the archive. I think the problem is the domain name example.com that I saw in the upper left corner. If in django administration I rename that site it works. But having more than one domain this is not a solution. what i need is to separate different domains https:/website1/mailman3/hyperkitty shows some lists https:/website2/mailman3/hyperkitty shows other lists Where am I wrong? What have I to change in hyperkitty to have the correct domain shown? Is there a documentation to configure that? Hyperkitty version is 1.2.2 Thank you. -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

3 4

How to access my mailman 3 REST API over https and from another machine?
by Shashikanth Komandoor April 28, 2020

April 28, 2020

Hi, I have setup Mailman 3.3 version and would like to use the REST API by another application. But that application is on another machine and so I need to allow accessibility from another machine also. Along with that as I am trying to access from another machine I need to access the REST API of mailman 3 over https only. Could any one guide me to enable mailman 3 REST API over https and access from another machine other than localhost only ? -- Thanks & Regards, Shashi Kanth.K 9052671936

3 2

MM2 to MM3 on debian 10
by Gelpi Andrea April 28, 2020

April 28, 2020

Hi, on a debian 10 with MM3 I'm trying to migrate form some old MM2 mailing lists. I know that not all can work. In my old lists I have email and regular expressions in reject_these_nonmembers and discard_these_nonmembers After importing the list all these email are in non member list. All these email have Delivery status enabled. Does this mean that all of them will receive any message sent to the list? The moderation rule is correct, but if I understood correct Delivery status should be disabled. For migration I followed this link https://docs.mailman3.org/en/latest/migration.html To migrate archives it states to run python manage.py hyperkitty ... I cant' find a manage.py on debian 10 A search shows the only /usr/share/mailman3-web/manage.py exists. Is there any documentation specific for debian? Thank You -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

2 3

Re: [Mailman-Developers] How to know the URLs for CURL while getting or modifying the data of mailman 3
by Stephen J. Turnbull April 25, 2020

April 25, 2020

Shashi, This whole thread is off-topic for the developers list. This list is for development of Mailman, not for teaching people to use it. Read the whole recommended documentation before you ask busy developers to tutor you in very basic things. There's a mailman-users(a)mailman3.org list for users to help each other. All of the Mailman developers who might be willing to answer your questions are there as well, but there are also many experienced users, some of whom have experimented with the REST API who will also help. Please reply there for further help. (Reply-To is set.) That said, there are plenty of URLs in the API documentation. Here's a hint: search for "dump_json". That function takes an URL. You may want https: instead of http: in your URLs, and you may need to change the port from 9001, depending on the configuration of your REST server. Try it with simple GET requests for information first, such as for domains or lists. You can also do these requests with an ordinary web browser, though I don't know what it will do with the JSON-formatted reply. If you don't have domains and lists configured, I suppose the informational requests will come back as empty JSON objects. It should be safe to make them. You can either use Postorius to bootstrap a few example domains, lists, and users, or (the hard way) figure out how to POST appropriate requests. I don't recommend trying to update the backend DBMS by hand; the schema is quite complicated. I don't know how to use curl to update Mailman's databases. That requires a POST request which I have never done with curl. The POST request needs to be valid JSON. The more I think about this, the less I think your idea of using curl is worthwhile, because formatting JSON requests by hand is going to be a real annoyance and a great way to mess up your database with spurious information. You're really going to want programmatic support for this. But that's already all available in Python in the Mailman system. It's up to you, but I feel a responsibility to warn you that using curl is not going to be simpler than learning enough Python to do these things. Regards,

2 1

Bounce processing
by Andrew Hodgson April 23, 2020

April 23, 2020

Hi, Just upgraded to Mailman 3.3.1 at the beginning of the week and its very refreshing to have bounce processing working after all this time, stops the continued delivery to dud email addresses causing problems with junk email scoring. Anyway after a few days of using this I have noted the following feedback: When users are set to disabled after their bounce score reaches a certain threshold, I seem to recall on Mailman 2 they were sent an email with a link to reactivate their subscription. On Mailman 3 they are told to contact the list admin, I have had messages from a few subscribers regarding this asking how they can re-enable delivery. I am also getting bounces that look like they are coming from Qmail (Yahoo addresses) which are being forwarded to the list owner as unrecognised bounces. Should the type of bounces that Mailman 2 was handling be handled in Mailman 3 or is the way that the addresses are extracted different? I have disabled the relevant users but do have the bounces to hand. Thanks. Andrew.

2 1

Changing web access
by Ralf Wiegand April 22, 2020

April 22, 2020

Hello Members, I am testing mailman3 in a test environment. python manage.py runserver Performing system checks... System check identified no issues (0 silenced). April 22, 2020 - 14:13:57 Django version 2.2.12, using settings 'settings' Starting development server at http://127.0.0.1:8000/ Quit the server with CONTROL-C. tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 6497/python tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 6404/python How can I change this to have access from any host on my local network. The server running mailman3+hyperkitty+postorius is a rhel7 server without a GUI interface. I also need to give access to our developer on the same subnet. Thank You, Best regards, Ralf Wiegand

3 5

Can't open PID file after start.
by Torge Riedel April 22, 2020

April 22, 2020

Hi, today there were some package upgrades on my server for python3. Just to be safe I did a "systemctl restart mailman" afterwards. Calling "systemctl status mailman" gave me the following output: mailman.service - GNU Mailing List Manager Loaded: loaded (/opt/mailman/core/mailman.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-04-22 07:01:30 CEST; 6s ago Process: 24178 ExecStop=/opt/mailman/core/bin/mailman.sh stop (code=exited, status=0/SUCCESS) Process: 24180 ExecStart=/opt/mailman/core/bin/mailman.sh start (code=exited, status=0/SUCCESS) Main PID: 24182 (python3) Tasks: 13 (limit: 2335) CGroup: /system.slice/mailman.service ├─24182 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/master -C /opt/mailman/core/mailman.cfg ├─24185 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=archive:0:1 ├─24186 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=bounces:0:1 ├─24187 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=command:0:1 ├─24188 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=in:0:1 ├─24189 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=lmtp:0:1 ├─24190 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=nntp:0:1 ├─24191 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=out:0:1 ├─24192 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=pipeline:0:1 ├─24193 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 ├─24194 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=retry:0:1 ├─24195 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=virgin:0:1 └─24196 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=digest:0:1 Apr 22 07:01:28 basis2 systemd[1]: Starting GNU Mailing List Manager... Apr 22 07:01:29 basis2 mailman.sh[24180]: Starting Mailman's master runner Apr 22 07:01:29 basis2 systemd[1]: mailman.service: Can't open PID file /opt/mailman/var/master.pid (yet?) after start: No such file or directory Apr 22 07:01:30 basis2 systemd[1]: Started GNU Mailing List Manager. Should I treat the PID message as an info or is it an error and something is now broken? The file is there (content is 24182) and timestamp is from the time where I restarted mailman. Best Torge

2 2

Different Mail Domain Cause Key Error
by Brian Carpenter April 22, 2020

April 22, 2020

I have a client that requires his list address to be list(a)domain.com. But since he is using domain.com for an external website, he has to access his list via Postorius using list.domain.com. So here is what I did: Django Admin Add Site: list.domain.com Add Mail Domain: domain.com (Site selected is list.domain.com) Postorius Add Domain: Mailhost is domain.com. Web Host is list.domain.com (list.domain.com) I have list.domain.com listed in the allowed hosts in settings_local.py. I even added domain.com there as well. When I try to access Postorius using list.domain.com I get a "An error occurred while processing your request." message and the logs shows the dreaded: ``` 'Internal Server Error: /mailman3/lists/ KeyError at /mailman3/lists/ 'file' ``` Did I miss a step here? Thanks, Brian

3 6

MM3 gateway errors and frequent reboot needs
by hansen＠rc.org April 22, 2020

April 22, 2020

We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? Please advise. PS: My old MM2 installation could (and did) run without any help. Not so with MM3.

4 3

Mailman Core 3.3.1 release
by Abhilash Raj April 19, 2020

April 19, 2020

Hey Everyone, I am pleased to announce Mailman Core 3.3.1 is now out. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1/ To install this release via pip, you can run: $ pip install --upgrade mailman -- thanks, Abhilash Raj (maxking)

1 0

Extract posts into mbox file
by Andrew Bernard April 18, 2020

April 18, 2020

Where are the posts stored in the database? What tables? How would on go about exporting them into mbox format for the complete set?

3 2

Recommended way to backup a mailman3 instance
by Gilles Filippini April 18, 2020

April 18, 2020

Hi, I'd like to schedule periodic backup for our mailman3 instance. Are there recommended ways for doing this without down times? Thanks in advance, _g.

4 12

Is a directory: '…/mailman/templates'
by Stefan Tatschner April 14, 2020

April 14, 2020

hey folks, I am struggling with my mailman server for quite some time now. I am on 3.3 and the out runner cannot sent emails any more. According to this issue [1] I found out--by logging the exception as well--, that mailman has this problem: Mar 31 09:34:51 2020 (71057) ACCEPT: <c1e4aa1be5b61c289c69a66a6d55565333d5a35b.camel(a)rumpelsepp.org> Mar 31 09:34:52 2020 (71079) Cannot connect to SMTP server 127.0.0.1 on port 25: [Errno 21] Is a directory: '/usr/lib/python3.8/site-packages/mailman/templates' What the hell is going on here? ☹︎ any ideas what's wrong? The runner doesn't try to connect to postfix, since it fails with a strange template error. Stefan [1]: https://gitlab.com/mailman/mailman/-/issues/514

5 6

Mailman Core 3.3.1rc1 release
by Abhilash Raj April 10, 2020

April 10, 2020

Hey Everyone, I have just released Mailman Core 3.3.1rc1. The final release is scheduled for next week, 17th April. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#rc1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1rc1/ To install this release via pip, you can run: $ pip install --upgrade --pre mailman Note the `--pre` flag because this is a pre-release. If you can, I encourage you to try this out with your environment and report any major breakage to us. We have been running this code on the server hosting this list, so it has already seen some testing, but it is always nice to have some more. If there aren't any major breaking changes reported, the final release will be identical to this one. -- thanks, Abhilash Raj (maxking)

2 1

SMTPAuthenticationError at /accounts/login/
by mmasoudf＠aaas.org April 9, 2020

April 9, 2020

I have setup the stack according to: Mailman Suite Documentation. Release 3.3 PDF file. I configured EMAIL_HOST_USER and EMAIL_HOST_PASSWORD in Django settings.py. I could not find the place that I might configure it for Postfix and , sort of logically, I get the following error: SMTPAuthenticationError at /accounts/login/ I can see that it tries the user name and password I configured in settings.py (EMAIL_HOST_USER , EMAIL_HOST_PASSWORD). When I try to access the site through the web. I can login as admin, but not as any other user. I am running the site on AWS and to be able to use AWS mail-servers I have to define following parameter for AWS: smtp_sasl_password_maps which points to a hash for AWS 'ACCESS KEY ID' and 'SECRET ACCESS KEY' Any idea is highly appreciated.

3 2

Loads of postgres requests: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" ...
by Gilles Filippini April 9, 2020

April 9, 2020

Hello, I run a small mailman3 server (6 lists, less than 100 users), and I can't access anymore to the administration web page for one of these lists: > Something went wrong > Mailman REST API not available. Please start Mailman core. The other lists seems OK. Looking at the postregsql logs I see a full load of these requests (4 to 5 per second!): LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2020-04-09T07:57:37.828200+00:00'::timestamptz) LIMIT 1 Any clue appreciated. Many thanks in advance, _g.

2 2

Re: Uncaught runner exception
by Wolfgang Bock April 9, 2020

April 9, 2020

Hello Mark, thanks for your hint. Postfix is runnig as mta on my machine. I tested port 25 with swaks ->mail to user on server: localhost port 25 -> everything fine Mailman is configured with localhost for incoming and outgoing mails. After stopping mailman3, deleting all files in the queue directories, restart mailman3 I sent a test-mail /var/log/mailman3/mailman.log Apr 07 12:08:23 2020 (28198) Master started Apr 07 12:08:24 2020 (28206) out runner started. Apr 07 12:08:24 2020 (28202) command runner started. Apr 07 12:08:24 2020 (28203) in runner started. Apr 07 12:08:24 2020 (28200) archive runner started. Apr 07 12:08:24 2020 (28201) bounces runner started. Apr 07 12:08:24 2020 (28210) retry runner started. Apr 07 12:08:25 2020 (28208) rest runner started. Apr 07 12:08:25 2020 (28212) digest runner started. Apr 07 12:08:25 2020 (28205) nntp runner started. Apr 07 12:08:26 2020 (28211) virgin runner started. Apr 07 12:08:26 2020 (28207) pipeline runner started. Apr 07 12:08:26 2020 (28204) lmtp runner started. Apr 07 12:09:19 2020 (28203) ACCEPT: <000f01d60cc4$96c9a8d0$c45cfa70$@[domain]> Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server localhost on port 25 I have no idea what to do for solving my problems. Regards from Hamburg Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Montag, 6. April 2020 23:50 An: Wolfgang Bock <mailinglisten(a)wbock.de> Betreff: Re: [MM3-users] Re: Uncaught runner exception On 4/6/20 2:44 PM, Wolfgang Bock via Mailman-users wrote: > Thank you Steven for your reply! > > I Set smtp_server to port 25 and got a "Cannot connect ro SMTP Server > on port 25", the former error message didn't show again. > > As I see port 25 is reseved for postfix. So I have to fiddle out how > mailman3 could also use this port for sending mails out. .... You need an MTA for Mailman to deliver its mail to. Normally this will be Postfix, sendmail, Exim, etc running on localhost and listening on port 25. Do you have such an MTA running on localhost? Note, Mailman does not directly send mail to end recipients. It only delivers mail to an outgoing MTA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 8

Outgoing STMP services? IP reputations?
by Seth Seeger April 7, 2020

April 7, 2020

Hello everyone, Forgive me if this is the wrong list. I’m curious to hear what users are doing for MM3 hosting and what you are using for outgoing services. I am hosting a Mailman3 installation for a community that I am part of, and we have 6 lists which generated 136,000 outgoing emails last month. I’m currently hosting this on a 2-core 4GB RAM EC2 (t3a.medium) instance at Amazon. I went with Amazon because their outgoing email relay (SES) is free for the first 62,000 emails/month. (I didn’t do my homework - I thought that would be plenty!) I’d much rather be hosting on Linode, since their setup is waaaaay simpler and easier to understand. I went with an SMTP service so that I wouldn’t have to deal with managing an IP address reputation…. (Any other SMTP relay service besides the Amazon SES/hosting would cost >$80/month.) Do you use an SMTP relay service? Do you just send directly from your VM’s IP address? Do you have trouble with getting black listed? What have you done about your IP address reputation? Is DKIM and SPF enough to get past an IP address without an established reputation? Thank you! Seth

3 2

Uncaught runner exception
by Wolfgang Bock April 7, 2020

April 7, 2020

Hello, I need your help. I got a "Uncaught runner exception: invalid literal for int() with base 10:" Referring to a discussion in Sept. 2019 with Manos Pitsidianakis "Cannot connect to SMTP server localhost on port 25" I did following: stop both postfix and mailman 3 services. Deleted all files in the /var/lib/mailman3/queue directories. Restarted both services. With following configurations: (extracts): /etc/mailman3/mailman.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: Tried with 127.0.0.1/localhost/server ip or FQDN=servername smtp_port: (got a "cannot connect to SMTP Server on port 25") so I let this item empty ... smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 configuration: python:mailman.config.postfix /var/log/postfix/mail.info Apr 6 00:02:22 ... postfix/postfix-script[31407]: starting the Postfix mail system Apr 6 00:02:22 ... postfix/master[31409]: daemon started -- version 3.4.8, configuration /etc/postfix Apr 6 00:03:09 ... postfix/smtpd[31462]: connect from mout-p-103.mailbox.org[80.241.56.161] Apr 6 00:03:09 ... policyd-spf[31468]: prepend Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=80.241.56.161; helo=mout-p-103.mailbox.org; envelope-from=[mail address]; receiver=<UNKNOWN> Apr 6 00:03:09 ... postfix/smtpd[31462]: D29FE138023E: client=mout-p-103.mailbox.org[80.241.56.161] Apr 6 00:03:09 ... postfix/cleanup[31471]: D29FE138023E: message-id=<6a504834-123a-60f6-3a0e-494623b74523(a)mailbox.org> Apr 6 00:03:25 ... postfix/qmgr[31411]: D29FE138023E: from=<[mail address]>, size=2811, nrcpt=1 (queue active) Apr 6 00:03:25 ... postfix/smtpd[31462]: disconnect from mout-p-103.mailbox.org[80.241.56.161] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Apr 6 00:03:25 ... postfix/lmtp[31481]: D29FE138023E: to=<[list address]>, relay=127.0.0.1[127.0.0.1]:8024, delay=16, delays=16/0.01/0/0.1, dsn=2.0.0, status=sent (250 Ok) Apr 6 00:03:25 ... postfix/qmgr[31411]: D29FE138023E: removed /var/log/mailman3/mailman.log Apr 06 00:02:12 2020 (31148) Master started Apr 06 00:02:13 2020 (31158) rest runner started. Apr 06 00:02:13 2020 (31150) archive runner started. Apr 06 00:02:13 2020 (31159) retry runner started. Apr 06 00:02:14 2020 (31161) virgin runner started. Apr 06 00:02:14 2020 (31154) lmtp runner started. Apr 06 00:02:14 2020 (31155) nntp runner started. Apr 06 00:02:14 2020 (31153) in runner started. Apr 06 00:02:14 2020 (31151) bounces runner started. Apr 06 00:02:15 2020 (31157) pipeline runner started. Apr 06 00:02:15 2020 (31152) command runner started. Apr 06 00:02:15 2020 (31162) digest runner started. Apr 06 00:02:16 2020 (31156) out runner started. Apr 06 00:03:26 2020 (31153) ACCEPT: <6a504834-123a-60f6-3a0e-494623b74523(a)mailbox.org> Apr 06 00:03:26 2020 (31156) Uncaught runner exception: invalid literal for int() with base 10: '' Apr 06 00:03:26 2020 (31156) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 77, in deliver agent = BulkDelivery(int(config.mta.max_recipients)) File "/usr/lib/python3/dist-packages/mailman/mta/bulk.py", line 50, in __init__ super().__init__() File "/usr/lib/python3/dist-packages/mailman/mta/base.py", line 45, in __init__ config.mta.smtp_host, int(config.mta.smtp_port), Any hints how to solve the problem?? Regards Wolfgang

2 4

Protocol version
by David Krantz April 5, 2020

April 5, 2020

Hi. I have the following displayed when I look at the "System Information" in Postorius: Mailman Core Version GNU Mailman 3.3.0 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.7.6 (default, Dec 19 2019, 23:49:42) [GCC 5.4.0 20160609] What surprises me is the protocol version. I have tried to set the protocol version to 3.1 in mailman core (which should be the latest according to the documentation) and restarting both core and web but that gives no effect. Normally I have not had any protocol version defined. Everything seems to work just fine but something is strange, either the documentation, my setup or mailman/postorius. // David

1 1

Postorius confirmation mails shown in uwsgi-error.log but not sent
by Ralph Seichter April 4, 2020

April 4, 2020

I have struggled for hours but cannot seem to figure it out. After registering new user accounts in Postorius, the "confirm your address" emails don't get sent via SMTP (my MTA does not even log connection attempts), but their content is displayed in uwsgi-error.log. I think I disabled developer mode in Core and Postorius: $ mailman conf | grep devmode [devmode] enabled: no [devmode] recipient: [devmode] testing: no [devmode] wait: 60s $ grep ^DEBUG settings.py DEBUG = False Users can subscribe via list-join(a)domain.tld, including confirmations. Account registration using the WebUI works as well, it's just the emails that don't get sent. What am I missing, I wonder? -Ralph

3 10

Finding a mailman3 installation description that works
by ralf.wiegand＠tena-sda.org April 1, 2020

April 1, 2020

WE are currently using mailman2. I have the task to setup and install a maiman3 server. Postfix is installed and working. Can anybody point me to a link where the actual installation is described using RHEL 7 or RHEL 8. This will be a hardened DISA compliant server, so I am trying to avoid installing compilers and tools that are not part of the standard RHEL 7 repos. Thank You, Best regards, Ralf Wiegand

3 4

Mailman3 moving to new server, not able to establish SMTP connection
by Andrew Hodgson March 28, 2020

March 28, 2020

Hi, Whilst we are all stuck in doors I have started a project to move Mailman3 from a Docker installation to a new server using a Python venv. Old server was Debian Jessie and the new one is Buster. Using Exim with stock config. Everything seems to be going ok but mail isn't delivering (cannot connect to SMTP server). I have /opt/mailman which I did chown -R list:list mailman.cfg has following MTA settings: [mta] incoming: mailman.mta.exim4.LMTP configuration: python:mailman.config.exim4 I wrote a Systemd unit which starts Mailman from the venv and started up Mailman once I got Postgres sorted so it would create the necessary files in the var directory structure. One thing I noticed and had to fix is that it doesn't creat the directories for existing lists, and the Exim config examples out there check for the existance of those directories to identify whether the address exists. I created those anyway and set ownership perms as before. Once I fixed that I sent a test message to the owner address and that routed correctly and the headers indicated the message was sent back to localhost by Mailman. However I can't get it to route a list message, here is a log showing the start of the Mailman master processes and me sending a test message from Outlook (so incoming mail is routing ok): Mar 28 16:03:20 2020 (21877) Master started Mar 28 16:03:32 2020 (21889) lmtp runner started. Mar 28 16:03:32 2020 (21896) virgin runner started. Mar 28 16:03:32 2020 (21887) command runner started. Mar 28 16:03:32 2020 (21890) nntp runner started. Mar 28 16:03:32 2020 (21886) bounces runner started. Mar 28 16:03:33 2020 (21892) pipeline runner started. Mar 28 16:03:33 2020 (21888) in runner started. Mar 28 16:03:33 2020 (21895) retry runner started. Mar 28 16:03:34 2020 (21894) rest runner started. [2020-03-28 16:03:34 +0000] [21894] [INFO] Starting gunicorn 20.0.4 [2020-03-28 16:03:34 +0000] [21894] [INFO] Listening at: http://127.0.0.1:8001 (21894) [2020-03-28 16:03:34 +0000] [21894] [INFO] Using worker: sync [2020-03-28 16:03:34 +0000] [21963] [INFO] Booting worker with pid: 21963 Mar 28 16:03:34 2020 (21885) archive runner started. [2020-03-28 16:03:34 +0000] [21965] [INFO] Booting worker with pid: 21965 Mar 28 16:03:34 2020 (21897) digest runner started. Mar 28 16:03:36 2020 (21891) out runner started. Mar 28 16:04:25 2020 (21888) ACCEPT: <AM0PR08MB39085771D0E2D9114FDE8E83AFCD0(a)AM0PR08MB3908.eurprd08.prod.outlook.com> Mar 28 16:04:26 2020 (21885) HyperKitty archived message <AM0PR08MB39085771D0E2D9114FDE8E83AFCD0(a)AM0PR08MB3908.eurprd08.prod.outlook.com> to https://lists.hodgsonfamily.org/hyperkitty/list/blind-sysadmins@lists.hodgs… [28/Mar/2020:16:04:26 +0000] "GET /3.0/lists/blind-sysadmins(a)lists.hodgsonfamily.org HTTP/1.1" 200 445 "-" "GNU Mailman REST client v3.3.0" Mar 28 16:04:27 2020 (21891) Cannot connect to SMTP server localhost on port 25 [28/Mar/2020:16:04:27 +0000] "GET /3.0/lists/blind-sysadmins(a)lists.hodgsonfamily.org/config HTTP/1.1" 200 2595 "-" "GNU Mailman REST client v3.3.0" [28/Mar/2020:16:04:27 +0000] "GET /3.0/users/andrew(a)hodgson.io HTTP/1.1" 200 439 "-" "GNU Mailman REST client v3.3.0" Now in the out queue I have this: root@elrond:/opt/mailman# ls -la /opt/mailman/var/queue/out total 32 drwxrwx--- 2 list list 4096 Mar 28 16:34 . drwxr-xr-x 14 list list 4096 Mar 28 13:25 .. -rw-rw---- 1 list list 11152 Mar 28 16:34 1585413255.2412584+390ab148e589108ed9e849445e5e90410f69def3.bak -rw-rw---- 1 list list 11152 Mar 28 16:34 1585413255.4891446+75bde47331619263b05f582c28ceb85a13bb5265.pck.tmp There is no connection attempt in the Exim log from Mailman and I can connect to localhost:25. This is a dualstack machine and I was wondering whether we had any IPV6 issues (I had an issue with Gunicorn and Nginx routing traffic due to this earlier that I had to sort), but as owner addresses are working I don't know what is different on that. Any suggestions? Thanks. Andrew.

1 1

421 - Too many sessions from source IP
by hansen＠rc.org March 27, 2020

March 27, 2020

My new MM3 server is receiving these errors from cox.net: "(delivery temporarily suspended: host cxr.mx.a.cloudfilter.net[34.212.80.54] refused to talk to me: 421 cxr-ibgw-6004a.stratus.cloudmark.com cmsmtp too many sessions from 213.125.4.246. Refer to Error Codes section at https://www.cox.com/residential/support/email-error-codes.html for more information. AUP#CXCNCT) " The link gives just this: 421 - [too many sessions from <source IP>] The sending IP address has exceeded the five maximum concurrent connection limit. Configure your sending server to establish no more than five concurrent connections. 1. Is that a legitimate excuse to refuse passing on emails or is cox.net too stingy? 2. Is that a setting we need to change in Mailman somewhere? Or should this be handled in some Postfix setting? Yours, Allan

4 3

Archives with encoding characters
by Seth Seeger March 25, 2020

March 25, 2020

Hello everyone, I have a few (but not all) members complaining that their digests are full of coded characters. Two examples below were forwarded to me: > What I ended up doing was creating 2 "practice lines" in the centre of=20 > our big teaching circle (I always teach new figures in a big circle) -=20 > which each had 3 people set up in a line with generous space between,=20 > and first=C2=A0 I walked through one of those lines myself starting first= > =20 and > Robins pass Right=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Larks Loop L= > eft What is the cause? Is there anything I can do about it? Thanks, Seth

3 7

Things I miss about mailman2
by Quanah Gibson-Mount March 24, 2020

March 24, 2020

Now that we are on mailman3, I'm finding things that were really useful in mailman2 are completely missing in mailman3, which seems odd, since they in particular affect the ability of list moderators to do their job well. a) When a post was made to a moderated list in mailman2, I would get an email that included a LINK to the held email. Now I just get a canned email saying I need to go to the dashboard, blah blah. Why was this link removed? It was extremely useful and now I have to jump through extra hoops. b) When a post is made to a moderated list in mailman2, when I went to the page to approve/deny/discard, there was additionally an option to remove the moderated flag from the user for all future emails. This option no longer exists. This was EXTREMELY useful, as we force all new members of the list to be moderated for a time while we evaluate the quality of their postings. Now I have to go manually track down the user and their settings. Unnecessary extra hoops to jump through c) When a post is made to a moderated list, one of the options when selecting REJECT was it allowed me to set a custom message when rejecting the email. This was extremely useful. For example today, someone emailed our bug tracking list directly instead of filing a bug. In the past, I would have added a note to them about what they should do (in this case, I would have told them to send their email to our community technical discussion list). Now I can no longer do that, I can only reject it or discard it. Why was this removed? --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

6 9

Xapian alternatives
by Andrew Bernard March 24, 2020

March 24, 2020

Are there alternative search engines to Xapian that can be used for Mailman 3? I have come to understand that Xapian development stalled in the v2.0 attempt.

4 6

Thread matching query does not exist
by andrew.bernard＠gmail.com March 19, 2020

March 19, 2020

Now I am seeing this in the log every few seconds: 12:12:29 [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] 12:12:29 [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. : Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_q-1.0.1-py3.7.egg/django_q/cluster.py", line 377, in worker res = f(*task['args'], **task['kwargs']) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.2.3-py3.7.egg/hyperkitty/tasks.py", line 189, in _rebuild_thread_cache_votes thread = Thread.objects.get(id=thread_id) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-2.1.9-py3.7.egg/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-2.1.9-py3.7.egg/django/db/models/query.py", line 399, in get self.model._meta.object_name hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. Any help? How do I identify the thread in question? I imported an archive from a Listserv list, processed into something resembling mbox format (which I now understand not to be a standard at all) and have about 100,000 messages there. I am having a lot of trouble with these sort of errors, as you will see from my flurry of posts recently. Yes, I am running all the jobs. Andrew

3 3

IsADirectoryError: [Errno 21] Is a directory: '/usr/local/lib/python3.7/site-packages/mailman/templates'
by sunil soprey March 19, 2020

March 19, 2020

Has anyone encountered this error? I pulled the latest mailman suite (versions below), and facing this error in two places * mass subscription add of users -> Click on mass-subscription for list, enter email Django 2.2.11 django-allauth 0.41.0 django-appconf 1.0.3 django-ca 1.15.0 django-compressor 2.4 django-extensions 2.2.8 django-gravatar2 1.4.4 django-gunicorn 0.1.1 django-haystack 2.8.1 django-health-check 3.12.1 django-mailman3 1.3.2 django-object-actions 2.0.0 django-picklefield 2.1.1 django-prometheus 2.0.0 django-q 1.2.1 django-redis 4.11.0 django-redis-cache 2.1.0 django-rest-auth 0.9.5 django-saml2-auth 2.2.1 djangorestframework 3.11.0 djangorestframework-jwt 1.11.0 python3 -V Python 3.7.6 django-mailman3 1.3.2 HyperKitty 1.3.2 mailman 3.3.0 mailman-hyperkitty 1.1.0 mailmanclient 3.3.0 postorius 1.3.2 sADirectoryError: [Errno 21] Is a directory: '/usr/local/lib/python3.7/site-packages/mailman/templates' [2020-03-17 03:56:54 +0000] [4220] [ERROR] Socket error processing request. Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 134, in handle self.handle_request(listener, req, client, addr) File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 190, in andle_request util.reraise(*sys.exc_info()) File "/usr/local/lib/python3.7/site-packages/gunicorn/util.py", line 625, in reraise raise value File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 175, in andle_request respiter = self.wsgi(environ, resp.start_response) File "/usr/local/lib/python3.7/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/local/lib/python3.7/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/usr/local/lib/python3.7/site-packages/mailman/rest/members.py", line 266, in on_post pre_approved=pre_approved) File "/usr/local/lib/python3.7/site-packages/mailman/app/subscriptions.py", line 523, in register list(workflow) File "/usr/local/lib/python3.7/site-packages/mailman/app/workflow.py", line 69, in __next__ return step()

2 3

Finding a user to delete them
by Quanah Gibson-Mount March 17, 2020

March 17, 2020

Due to a bug in mailman3, I have an incorrect user that's been created via github auth that has no confirmed email address yet. I've been poking around the user manager documentation (why is there no UI for user management???), and after adding in bits that are missing from the official documentation (<https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/usermanager…> is missing "from mailman.testing.documentation import dump_list" despite using dump_list repeatedly in its examples) I can't find the user. I have the confirmation email mailman3 sent out, that tells me the username mailman3 created for the incorrect account is "quanah98", but the user manager documentation doesn't detail how to find a user by their username, only their email. And apparently if the email hasn't been confirmed (and I *do not* want it confirmed), you can't find them by email. Suggestions on how to track down this user so I can delete them would be much appreciated. Thanks, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 13

Add old email address
by Quanah Gibson-Mount March 14, 2020

March 14, 2020

We've recently migrated our project's email lists from mailman2 to mailman3. Given the project has been around for a few decades, many people have used different email addresesses over the years, some of which they no longer have access to. However, it would be useful to still be able to associate those emails with a given account. Is there a way that I can do this as an administrator of the mailman3 system? Thanks, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

2 4

Using REST api to subscribe member
by Brian Carpenter March 11, 2020

March 11, 2020

I have a development server that only has Mailman core installed on it. I used a virtual environment to do the installation but I did not install Postorius or Hyperkitty as I am currently working on developing a custom u.i. for Mailman 3. My programmer said the following: "I have a problem with mailman on development server ... I was trying to add member to a list using REST api, but to no avail. After I tried all possible and impossible things, I finally looked at the logs. Error I found in log file is: IsADirectoryError: [Errno 21] Is a directory: '/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/templates' I guess mailman was looking for a template for welcome mail, and failed for some reason. I also guess this has something to do with locale or language settings I tried googling, but couldn't find anything" The log that gave the error was /opt/mailman/mm/logs/mailman.log My programmer tried it on another server that has both Postorius and Hyperkitty working and the api call worked, i.e. added the member to the list and sent out a welcome email. So what else do I need to install to be able to use the api to add members to a list using a non-postorius interface? Any assistance would be appreciated. Thanks, Brian

1 0

How to configure a mailing list?
by Patrick Ben Koetter March 10, 2020

March 10, 2020

Greetings, I do have mailman 3 installed via virtualenv and it is up an running. Now I'd like to create a mailing list, but I can't find any instructions how I should do this. Is there a resource online I missed? If not, can anyone on this list tell me how to do it preferrably using a command line tool? TIA p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

2 1

Scrub non digest
by Eduardo Costa March 9, 2020

March 9, 2020

Hi, on mailman2 used to scrub attachments in non digest, each member received the attachment link, how can I do it on mailman3? Best Regards, -- ...................................... Eduardo Costa Centro de Comunicações - Instituto Politécnico de Bragança raposo at ipb.pt http://www.ipb.pt/~raposo/ ......................................

2 1

Was Mailman3.org down this morning?
by Brian Carpenter March 9, 2020

March 9, 2020

I was unable to get to the lists or mailman3.org documentation at all this morning. Brian

5 5

Help on removing moderators
by sean_sullivan＠rhoworld.com March 4, 2020

March 4, 2020

Hello Mailman-users. I was hoping someone more experienced than myself would be able to help me with an issue I am currently experiencing. I have created a function to add moderators which works great, but I have also been trying to remove moderators as another function, but I am running into some issues. When I use the mailman shell based upon the documentation, it works great: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… everything works as expected. However, if I try and bring that in as a function that can be used with mailman withlist, I am consistently getting errors, and being that I am not very experienced in python, it has me scratching my head to say the least. from mailmanclient import Client from mailman.interfaces.member import MemberRole, AlreadySubscribedError from mailman.testing.helpers import subscribe addresses = ['test1(a)example.com', 'test2(a)example.com', 'test3(a)example.com'] client = Client('http://localhost:8001/3.1', 'restadmin', 'restpass') def set_owners(mlist): for email_addr in addresses: try: member = subscribe(mlist, '', email=email_addr, role=MemberRole.owner ) print (member) except AlreadySubscribedError as err: print (err) def remove(mlist): my_list = client.get_list(mlist) # print(my_list.fqdn_listname) # for email_addr in addresses: # my_list.remove_owner(email_addr) The errors I am getting are: ./bin/mailman withlist -r set_owners.remove -l it-test-b(a)lists.rhoworld.com Traceback (most recent call last): File "./bin/mailman", line 8, in <module> sys.exit(main()) File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/opt/mailman3/lib/python3.6/site-packages/mailman/bin/mailman.py", line 68, in invoke return super().invoke(ctx) File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 1137, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/opt/mailman3/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func return f(get_current_context(), *args, **kwargs) File "/opt/mailman3/lib/python3.6/site-packages/mailman/commands/cli_withlist.py", line 293, in shell r = call_name(dotted_name, m, *run_args) File "/opt/mailman3/lib/python3.6/site-packages/mailman/utilities/modules.py", line 70, in call_name return named_callable(*args, **kws) File "/opt/mailman3/bin/set_owners.py", line 24, in remove my_list = client.get_list(mlist) File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/client.py", line 347, in get_list 'lists/{0}'.format(fqdn_listname)) File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 404: 404 Not Found So, I am wondering, is it possible to do something like this or am I completely misunderstanding the documentation, and why do I get a 404 here, when in the shell everything works as expected. I know I must be missing something, but cannot for the life of me figure out what that is. Any help would be greatly appreciated. Thanks, Sean

2 3

Remove PDF attachents
by Eduardo Costa March 4, 2020

March 4, 2020

Hello, How do I configure the list to remove attachments of type pdf and others. Best Regards. -- ...................................... Eduardo Costa Centro de Comunicações - Instituto Politécnico de Bragança raposo at ipb.pt http://www.ipb.pt/~raposo/ ......................................

2 1

Mailman web Stopped working after upgrade
by David Krantz March 3, 2020

March 3, 2020

Hi. I have a VERY strange behaviour. I upgraded mailman3 and mailman web this weekend. It works fine (apart from ARC which don't work correctly in my setup but that is ok). But tonight the web user interface stopped working and I have not been logged in since it worked last time so something very strange is going on. I get the dreadful error message about psycopg2._psycopg is missing although it is installed both in ubuntu and in pip in the venv I run mailman. Mailman core still works fine, it is just Django being flaky. I think that this might be due to some kind of python misfeature where compiled code behaves slightly differently to interpreted code, that might explain the delay in it working initially before breaking. I have no idea of how to solve this. I have tried to uninstall and reinstlall psycopg2 in different versions without any luck. Any ideas? Logs below. I get the following in the web server error log (removing the web things that frankly are not interesting): mod_wsgi (pid=4488): Target WSGI script 'MAILMANROOT/bin/mailman-web20200229.wsgi' cannot be loaded as Python module. mod_wsgi (pid=4488): Exception occurred processing WSGI script 'MAILMANROOT/bin/mailman-web20200229.wsgi'. Traceback (most recent call last): File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/backends/postgresql/base.py", line 20, in <module> import psycopg2 as Database File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/psycopg2/__init__.py", line 50, in <module> from psycopg2._psycopg import BINARY, NUMBER, STRING, DATETIME, ROWID ImportError: No module named 'psycopg2._psycopg' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "MAILMANROOT/bin/mailman-web20200229.wsgi", line 47, in <module> application = get_wsgi_application() File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/core/wsgi.py", line 12, in get_wsgi_application django.setup(set_prefix=False) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/apps/registry.py", line 114, in populate app_config.import_models() File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/apps/config.py", line 211, in import_models self.models_module = import_module(models_module_name) File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 986, in _gcd_import File "<frozen importlib._bootstrap>", line 969, in _find_and_load File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 673, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 665, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/postorius-1.3.2-py3.7.egg/postorius/models.py", line 27, in <module> from django.contrib.auth.models import User File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/contrib/auth/models.py", line 2, in <module> from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/contrib/auth/base_user.py", line 47, in <module> class AbstractBaseUser(models.Model): File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/models/base.py", line 117, in __new__ new_class.add_to_class('_meta', Options(meta, app_label)) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/models/base.py", line 321, in add_to_class value.contribute_to_class(cls, name) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/models/options.py", line 204, in contribute_to_class self.db_table = truncate_name(self.db_table, connection.ops.max_name_length()) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/__init__.py", line 28, in __getattr__ return getattr(connections[DEFAULT_DB_ALIAS], item) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/utils.py", line 201, in __getitem__ backend = load_backend(db['ENGINE']) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/utils.py", line 110, in load_backend return import_module('%s.base' % backend_name) File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "MAILMANROOT/venv-3.7_2020/lib/python3.7/site-packages/Django-2.2.10-py3.7.egg/django/db/backends/postgresql/base.py", line 24, in <module> raise ImproperlyConfigured("Error loading psycopg2 module: %s" % e) django.core.exceptions.ImproperlyConfigured: Error loading psycopg2 module: No module named 'psycopg2._psycopg' Regards // David

2 5

Running customized version of Mailman 3
by Alan Kelm March 3, 2020

March 3, 2020

Since 2005, our organization has been running a customized version of Mailman 2 with extensions that meet our particular needs. The main novelty is support for /fixed subscription lists/, in which the list members are predetermined (corresponding to a "committee"). Fixed list subscribers are not offered the opportunity to unsubscribe, nor can others add themselves to the list. A further enhancement is /hybrid lists/ which, for example, have both a fixed and opt-in part. (This is implemented as a fixed list residing within an opt-in one in a way which is transparent to users). Our customizations consist of code adjustments (patches) to 23 files. We are considering moving to Mailman 3 and would like to do this in a way which makes it possible to periodically upgrade our installation to the newest Mailman version, without clobbering our customizations. Thus, I do not think that installing via "pip" is the right approach for us. While I'm relatively new to git and GitLab, they seem to be ideally suited to this situation. If I understand the developer documentation correctly, I start out by creating a "fork" and can later "fetch" changes from the master branch and "rebase" to bring them into our branch. I would welcome comments on what we are doing. I also wonder whether others might be interested in support for "fixed lists", if they are done in a way which can be "contributed" back into Mailman. I extend our "thank you" to the developers of Mailman who have provided the robust system which has served us well for 15 years and provides the possibility to extend this into the future. -Alan -- Alan Kelm Manager, Electronic Services Canadian Mathematical Society Tel: +1 (613) 733-2662 ext. 799 Please consider the environment. [cms web link] <https://cms.math.ca/> Alan Kelm Chef, services électroniques Société mathématique du Canada Tél : +1 (613) 733-2662 poste 799 Considérez svp l'environnement.

3 5

Question about members
by Dieter Leupold March 3, 2020

March 3, 2020

Hi together, short question: is it possible to display the time stamp when members have completed their subscriptions? Thanks a lot for your information! -- Dieter

2 1

ARC issues
by David Krantz March 2, 2020

March 2, 2020

Hi! I have now tested ARC signing of messages a bit more and have found (I think) all settings so that it works in that it generates the signed headers that ARC is. But the signature is not accepted; gmail says "body hash mismatch" and hotmail says "arc=fail (47)". I have set the following settings under the [ARC] section. I have tried both with the sig_headers set as displayed below and with it commented to lean against the defaults. I use the same key and selector as for DKIM-signing with the server's domain. The DKIM-signature is accepted. Is there any known issues with ARC that I should be aware of? I run the latest release of mailman (3.3.0 of core) on Python 3.7.6 and I use postfix as MTA. enabled: yes privkey: <my key path> selector: <my selector> domain: <my server's domain> dmarc: yes dkim: yes authserv_id: <my server's domain> trusted_authserv_ids: <my hosted domains> #sig_headers: From, Sender, Reply-To, Subject, Date, Message-ID, To, Cc, MIME-Version, Content-Type, Content-Transfer-Encoding, Content-ID, Content-Description, Resent-Date, Resent-From, Resent-Sender, Resent-To, Resent-Cc, Resent-Message-ID, In-Reply-To, References, List-Id, List-Help, List-Unsubscribe, List-Subscribe, List-Post, List-Owner, List-Archive I hope that this is something simple that I have forgot. Cheers // David

3 4

How to run 'manage.py update_index_one_list' command.
by Frank van den Heuvel Feb. 26, 2020

Feb. 26, 2020

I am importing old archives mbox files from Mailman2. I have fixed the archive mail address to reflect the address of the destination import. These are the steps: 1. sed 's|oldlist@oldexample\.org|testlist@example\.org|g' mbox > mbox.testlist 2. /opt/mailman/mm/bin/django-admin hyperkitty_import --since 01/01/1990 -l testlist(a)example.org mbox.testlist The output of the last command is: Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. \ To update the index for this list, run the 'manage.py update_index_one_list testlist(a)example.org' command. The result is that the e-mail's are imported but not indexed. To finalize this process I am seeking manage.py that will execute the update index command. I am on a Debian 10 with Mailman3 in /opt. locate manage.py returns: /opt/mailman/mm/venv/lib/python3.7/site-packages/django/conf/project_template/manage.py-tpl /opt/mailman/mm/venv/lib/python3.7/site-packages/example_project/manage.py /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py None of these python files can execute the needed command. What can I do to get the newly imported posts indexed? Regards, Frank

3 6

Mass unverified subscriptions end up as pending user confirmation instead.
by hansen＠rc.org Feb. 26, 2020

Feb. 26, 2020

After mass subscribing with these settings: Pre confirm: Yes, Pre approved: Yes, Pre Verified (sic): No the addresses appeared in the list's 'Pending user confirmation' list. They were pre-confirmed. The addresses did not appear in the Django Admin's non-verified addresses list. They were not verified. Also why does Postorius lists just 'Pending Approval' and 'Pending Confirmation' but not 'Pending Verification'? Yours, Allan

2 1

Tags in Hyperkitty
by Gila Halpern Feb. 21, 2020

Feb. 21, 2020

Are tags still under development? They don't appear to do anything at the moment, they are not searchable, and clicking on existing tags does nothing.

2 1

leaving Sympa for MM3
by rance.hall＠esu10.org Feb. 21, 2020

Feb. 21, 2020

Our shop is an educational shop and left mailman many years ago for Sympa because of features in Sympa not in mailman. Currently Sympa is showing its age, and is relying on perl modules that have been EOL's and the Sympa community has not discussed (within in ear-shot of me at least) what to do about it. We found that we are not using the extra features Sympa provides anymore and with MM3 already dockerized it seems that MM3 is a much better fit for our organization for the foreseeable future. So I got a dockerized setup up and running in a test environment and am pleased with the results except for now I have to start thinking about migration from Sympa to MM3. The API is useful in this effort as there are python wrappers already done and I didn't have any trouble scripting list creation with the API tools to migrate list owners, moderators and users. Now for the question/hard part. Migrating list archives. In Sympa the list archive is just a maildir format directory structure reflecting month/year. In MM3 the Archive is stored in the db with attributes that are likely only available as the message is processed. I'd really rather not loose the archive data if I can help it. Does anyone have any thoughts on how I could perhaps import this?

2 1

Advice on migrating to Mailman 3
by Christoph Groth Feb. 20, 2020

Feb. 20, 2020

Dear Mailman 3 users, Currently we are hosting the website [1] and mailing list [2] of our free software project with a shared hosting plan of a webhosting company. As such there is no dedicated server, but we do have SSH access (as a regular user) to the shared server. The mailing list software (Mailman 2) is administrated separately by our hoster on a dedicated machine. We are rather happy with this setup: we pay about 10 USD per month and have only little administration work to do. The only problem is that our list runs on Mailman 2. We would like to move to Mailman 3, but this does not seem to be that simple. Perhaps someone here would be so kind to give us advice? The number of (shared) hosters who offer Mailman 3 seems to be very limited [3]. Would it be a good idea to book a virtual private server (VPS) somewhere, that runs, say, Debian, and simply install Mailman 3 through the distribution’s package system? I’m already running a small personal box with nginx on it, and this is very little work, but running Mailman would require sending out up to a few thousand email messages per day (our list has a few hundred subscribers). Is this something that one is commonly allowed to do on a VPS system? Most VPS offers that I see are silent about mail. If we setup such a system, can we assume that it will silently operate without causing much administration work most of the time (like my nginx server)? Or is maintaining a Mailman 3 server a significant burden ([2] seems to imply that)? If yes, are you aware of organizations that propose Mailman 3 hosting for open source projects? Python.org seems to host some lists for third party projects, but otherwise I haven’t seen much. Thanks Christoph [1] https://kwant-project.org/ [2] https://mailman-mail5.webfaction.com/listinfo/kwant-discuss [3] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…

6 6

Email verification
by Allan Hansen Feb. 19, 2020

Feb. 19, 2020

Some members cannot get past the email verification when they create their accounts. They insist that they have looked in their spam folders. Their email addresses they entered are correct - the are able to log into their accounts with the right email address. But they get the message saying that a confirmation message was sent and if they don’s see it to contact us. 1. Who is ‘us’? My members are asking... 2. How do I help them? I tried subscribing them to a bogus list with pre-verified email, but that did not work, so both they and I are stuck. Tried finding help in archive, but did not see anything. Yours, Allan Hansen hansen(a)rc.org

4 9

Installing MM3 via pip fails…
by Patrick Ben Koetter Feb. 18, 2020

Feb. 18, 2020

Has anyone managed to install MM3 recently using pip on Ubuntu 18? I followed the instructions at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. As soon as I get to the Django part things get hairy. It seems Django requires something that was removed from it. Any ideas or experience how I can get around that? p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

2 4

No module named 'hyperkitty.urls' after upgrading python3
by jean-christophe manciot Feb. 18, 2020

Feb. 18, 2020

Ubuntu 20.04 python3 3.8.0-3 python3-django-hyperkitty: 1.3.2 ``` Traceback (most recent call last): File "/usr/share/mailman3-web/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 361, in execute self.check() File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 387, in check all_issues = self._run_checks( File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 377, in _run_checks return checks.run_checks(**kwargs) File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line 72, in run_checks new_errors = check(app_configs=app_configs) File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 13, in check_url_config return check_resolver(resolver) File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 23, in check_resolver return check_method() File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 399, in check for pattern in self.url_patterns: File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 584, in url_patterns patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module) File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 577, in urlconf_module return import_module(self.urlconf_name) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 671, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 783, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/etc/mailman3/django/urls.py", line 30, in <module> url(r'^hyperkitty/', include('hyperkitty.urls')), File "/usr/lib/python3/dist-packages/django/urls/conf.py", line 34, in include urlconf_module = import_module(urlconf_module) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked ModuleNotFoundError: No module named 'hyperkitty.urls' ``` ``` # dpkg --contents python3-django-hyperkitty_1.3.2+b1-20.04_amd64.deb|grep urls -rw-r--r-- root/staff 1356 2020-01-14 12:22 ./usr/local/lib/python3.7/dist-packages/HyperKitty-1.3.2-py3.7.egg/example_project/urls.py -rw-r--r-- root/staff 1043 2020-01-14 12:22 ./usr/local/lib/python3.7/dist-packages/HyperKitty-1.3.2-py3.7.egg/hyperkitty/tests/urls_test.py -rw-r--r-- root/staff 7783 2020-01-14 12:22 ./usr/local/lib/python3.7/dist-packages/HyperKitty-1.3.2-py3.7.egg/hyperkitty/urls.py -rw-r--r-- root/root 1356 2019-09-01 02:56 ./usr/share/doc/python3-django-hyperkitty/examples/urls.py ``` No such issue with python3 3.7.5-3. Any suggestion?

3 6

Random characters in "The results of your email commands" e-mail
by Jeffrey D Feb. 18, 2020

Feb. 18, 2020

Hi, Today I sending an e-mail to "mylist-request(a)domain.tld" with the subject "help" and I received the expected e-mail with the following content; confirm - Confirm a subscription request. echo - Echo back your arguments. end - Stop processing commands. help - Get help about available email commands. join - Join this mailing list. leave - Leave this mailing list. stop - An alias for 'end'. subscribe - An alias for 'join'. unsubscribe - An alias for 'leave'. No such command: -- No such command: vriendelijke Only I think my mail signature broke something in Mailman (see the No such command). Because every e-mail with a subject like "help", "stop" or "join", gives a reply with random characters. The Mailman logs doesn't show any error, so I'm not sure what is wrong. Deleting the mailinglist and create a new one won't fix the issue, also restarting Mailman doesn't help. An example of the random characters: Nzzf&ju[zZ0:v,jzkb^}nJyazZCj}{m5t5Cx<{iysG5o[w}jgn+g[lrwf*mzrLk)rjwliazZZnjyW(fvrh{aXXWj+&j)b b-'jX+zwl&v{rx &~y6.r(fu4:' Is this a bug in Mailman? Or something in my Mailman config...

2 2

Listing/Exporting member list error: Mailman REST API not available. Please start Mailman core.
by Thomas Lehker Feb. 17, 2020

Feb. 17, 2020

Our MailMan3 server is extremely slow and when trying to list or export members for a larger list it is throwing 'Mailman REST API not available. Please start Mailman core'. In Mailman core logs I am seeing [27] [CRITICAL] WORKER TIMEOUT (pid:40) [43] [INFO] Booting worker with pid: 43 Has anyone seen this issue? Is there any way to increase 'timeouts'? Thanks for any help! Tom Mailman Novice 16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com/roster/owner HTTP/1.1" 200 634 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/list.somelist.com/roster/moderator HTTP/1.1" 200 638 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/somelist(a)somelist.com/config HTTP/1.1" 200 2257 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:05 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:10 +0000] "GET /3.1/lists/list.somelist.com/member/somelist@somelist HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:16 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:19 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:26 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0" [2020-01-16 16:56:58 +0000] [27] [CRITICAL] WORKER TIMEOUT (pid:40) [2020-01-16 16:57:00 +0000] [43] [INFO] Booting worker with pid: 43 DISCLAIMER: The information contained in this message is privileged and confidential. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the message and delete/destroy any copy of this message. Information in this message that does not relate to the official business of the firm shall be understood as neither given nor endorsed by it.

4 4

Mailman stopping message distribution because of SMTP errors
by Victoriano Giralt Feb. 12, 2020

Feb. 12, 2020

Hi list, I have recently migrated some lists from Mailman 2 to Mailman 3. Users have been added using the mailman client as pre-verified addresses so the migration happened "silently". Thus, there was a dozen "bad" addresses (domains that did not exist anymore). Unfortunately, Mailman got some of the "bad" addresses in the first message batch for sending out, so, Postfix closed the connection because of "too many errors" and this stopped the process completely, i.e. Mailman did not continue sending messages to the rest of the list over 600 addresses. There was no more information in the logs than the Postfix error messages in smtp.log. Once the "bad" addresses were removed, the list started working as expected. I consider this a bug. The bouncing addresses should have been marked as "non deliverable" and the subscriptions "paused" and the rest should have been delivered. Or, the list owner should have been notified that there was a problem with message distribution. None of these happened. Thanks! -- Victoriano Giralt CIO University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

2 2

How to get rid of footer (Mailman3)
by tarmokumar＠gmail.com Feb. 12, 2020

Feb. 12, 2020

Hi, I have read multiple posts in this forum that you should be able to get rid of the footer completely but I am unable to. I have tried: - adding the footer template to a list and not adding any "Data" to it. Result was a attachment with some "dfgdfgdfgdfg" text in it. - adding/creating a blank "list:member:generic:footer" document to /var/templates/site/en, var/templates/lists/LIST.ID/en/ and var/templates/domains/DOMAIN/en/. Result is that the sent e-mail still has the original unsubscribe text in the footer (as an attachment) - removing all the files from /mailman/src/mailman/templates/en, still no change We are running Mailman within Docker on these versions: maxking/mailman-core:0.3.2 maxking/mailman-web:0.3.2 When searching the docker for example "list:member:generic:footer" file, there isnt one (except the one I created) and when I search the file for text "unsubscribe", then it is only included in the postfix_lmtp file, but this doesnt seem to be it since it is overwritten every time.

2 1

Sync Members of a MM3 Mailing List
by brian＠emwd.com Feb. 12, 2020

Feb. 12, 2020

Does Mailman 3 have a feature/script/function that corresponds with the sync_members script that Mailman 2 has? I have a Mailman 3 client that wants to automate the process of keeping a MM3 list synchronized with a file on the server. Thanks, Brian

4 4

task runjobs minutely uses 100% cpu
by Lars Schimmer Feb. 12, 2020

Feb. 12, 2020

Hi! Since we do run roughly 40 mailinglists on mailman3, the schedules/cronjob task python3 /usr/share/mailman3-web/manage.py runjobs minutely uses 1 CPU core 100% all the time. Any idea howto see why? debian mailma3n-full package 3.2.1-1 Mailman Core Version GNU Mailman 3.2.1 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC 8.3.0] MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 6

Your Dashboard
by Torge Riedel Feb. 12, 2020

Feb. 12, 2020

Hi, everytime I receive a mail for moderation it says: At your convenience, visit your dashboard to approve or deny the request. So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. If it is already there, where do I find it? If not, do others also find such a dashboard helpful? Best regards Torge

5 6

minutely cronjobs: ModuleNotFoundError: No module named 'settings
by Bjoern Franke Feb. 10, 2020

Feb. 10, 2020

Hi, on a system running Debian 10 the minutely cronjobs fail since it was rebooted. The following is the output of django-admin >/dev/null && django-admin runjobs minutely --pythonpath /usr/share/mailman3-suite --settings settings Traceback (most recent call last): File "/usr/bin/django-admin", line 21, in <module> management.execute_from_command_line() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 308, in execute settings.INSTALLED_APPS File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 56, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 41, in _setup self._wrapped = Settings(settings_module) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 110, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 965, in _find_and_load_unlocked ModuleNotFoundError: No module named 'settings' I'm wondering why this module is missing and reinstalled several django packages, but none of them has explicitly a settings module. Kind regards Bjoern

2 2

Cannot setup announce-only mailing list
by Alberto Granzotto Feb. 8, 2020

Feb. 8, 2020

Dear all, I don't understand how to set up an "announce only" mailing list using Postorius Version 1.2.4. What I do is the following: - Click on "Create New List" - From "List Style", select "Announce only mailing list style." - Fill all other fields in the form - Click "Create list" At this point people can subscribe to the newly created announce mailing list. If they add themselves they end up in "List Members", and if they email the announce mailing list, their email is relayed to all other members, just like a normal mailing list :/ Moreover, subscribers get this message, inviting them to post to the announce only mailing list: > Welcome to the "Test-announce" mailing list! > > To post to this list, send your email to: > > test-announce(a)lists.dist0rtion.com Of course, I want to keep this mailing list "read only" for members, and I want only selected people to post to that mailing list. Any idea on how to achieve that? Best, Alberto

4 4

Attachement processings questions
by Lars Schimmer Feb. 7, 2020

Feb. 7, 2020

Hello, I got some questions about attachements in MM3 mailinglists and HyperKitty. Hard to find any real documentation about this in the huge load of links out there. Short: Debian Stretch system with MailMan 3.2.1-1 packages (Postorius 1.2.4, HyperKitty 1.2.2). In a mailinglist it seems some mails are not forwarded to a member, but is listed in archive in hyperkitty. That mail did include a PDF attachement, but HyperKitty does not list any attachement. All I found was "convert HTML to plaintext", but does this setting remove attachements? Is there any generel documentation about attachement processing in MM3? I would like this mailinglist to accept mails with attachements, send it to the members and archvie the attachments in HyperKitty, to. Any idea where to look? Thank you so far. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

2 6

where to configure max_days_to_hold on MM3 GUI interface?
by Shashikanth Komandoor Feb. 6, 2020

Feb. 6, 2020

Hi Sir, I came to know that the held messages can be restricted to be processed after a specific no of days or can be discard after some days using the parameter *max_days_to_hold*. But I could see that parameter value configurable on MM2 GUI interface in General Options but I don't see the same on the MM3 GUI interface. Could you please help me if I am missing something? -- Thanks & Regards, Shashi Kanth.K 9052671936

3 6

Disable response to the list request address
by Dieter Leupold Feb. 6, 2020

Feb. 6, 2020

Hi all, a short question (MM3.1.1): is it possible to avoid responses when someone sends emails to the request-address (xxx-request(a)lists.xxxx.com) of a mailinglist? Thanks for your information! Dieter Leupold

2 1

Re: Mailman3 on Debian 10
by Mark Sapiro Jan. 31, 2020

Jan. 31, 2020

On 1/30/20 8:24 AM, Bala Mutyam wrote: > Hi Mark, > > Thanks for the update and I managed to resolve the errors on the UI. > > I have 2 more questions about the mailman3. > > 1) how to create Mailing Lists? You can create lists with the `mailman create` command lint tool or via Postorius as a superuser. > 2) super user login is not working even with correct login credentials and giving me - The username and/or password you specified are not correct. How did you create the super user? You should do it with the django admin createsuperuser command. > 3) Password Reset Email urls and email confirmation web pages giving me - This site can't be reached error. If this is an error from your browser, there is something wrong with the host portion of the URL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: Mailman3 on Debian 10
by Mark Sapiro Jan. 31, 2020

Jan. 31, 2020

On 1/30/20 9:22 AM, Bala Mutyam wrote: > Sorry one more issue, > > Mailman settings page giving me below error. > > Server error > An error occurred while processing your request. > > Error logs: > > ERROR 2020-01-30 17:20:11,331 16285 django.request Internal Server Error: /postorius/accounts/subscriptions/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 41, in inner > response = get_response(request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3/dist-packages/postorius/views/user.py", line 306, in user_subscriptions > mm_user = MailmanUser.objects.get_or_create_from_django(request.user) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 164, in get_or_create_from_django > return self.get(address=user.email) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 86, in get > return method(*args, **kwargs) > File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 322, in get_user > return User(self._connection, content['self_link'], content) > KeyError: 'self_link' Just prior to this is a call to the REST API to GET /users/user(a)example.com (or whatever the user's address is). It appears that that user doesn't exist in core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Deliverability and Spam Filtering
by tom＠gather.coop Jan. 30, 2020

Jan. 30, 2020

Hi folks! First time poster, long time Mailman user. I am setting up a new Mailman 3 instance, and am super excited about the REST API. I plan to use it to enable tight integration with a separate web app that I maintain. As I am setting up the mail server, I am wondering about two related things: deliverability (for outgoing mail) and spam filtering (for incoming mail). What solutions have folks used for these? I know it is generally common now to outsource this critical task to a cloud provider like Mailgun or etc. Have folks needed this or is running ones own incoming and outgoing mail not a big deal? So many horror stories out there... As far as Mailgun goes, I think it should be straightforward to configure it for outgoing mail, but I'm not sure how I'd use it for incoming. Mailgun can forward mail via HTTP or to another email address. Neither I think would work out of the box. It would be great if there were a REST API endpoint for incoming mail, but I don't think such a thing exists, right? Perhaps I could add one? Another thought I had was that I could write a simple HTTP server that receives mail from Mailgun and forwards it to Mailman via LMTP. But it seems simpler to go right to Mailman's core API given that one exist already. Or am I thinking about this all wrong? Are there other more suitable services out there? I looked for cloud MTA providers but didn't turn up much except for in the large enterprise space, which I'm sure I can't afford. Thanks for any thoughts!

4 3

SUBSCRIBE_FORM_SECRET in MM3?
by Gila Halpern Jan. 30, 2020

Jan. 30, 2020

I've been looking into ways to prevent spam on my company's list, and one thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configuration, which embeds a CSRF token into the form, and prevents it from being submitted until five seconds after it renders, to keep bots from subscribing. Unfortunately, the information I found pertained to Mailman 2. Does this option exist in MM3 as well, or is there a similar option?

3 2

Mass subscribe gives HTTP Error 500 when using custom template
by Jeffrey D Jan. 30, 2020

Jan. 30, 2020

Hi, I have some issues with the Mass Subscribe option on Mailman 3.2.1. When using a custom "The notice sent to a member when they are subscribed to the mailing list." template, Postorius will throw an exception after pushing the "Subscribe Users" button on Mass Subscribe. In the web interface you will see a red notification bar with the text: "HTTP Error 500: b'A server error occurred. Please contact the administrator.'". And in the Mailman.log you will see the following error message: Traceback (most recent call last): File "/usr/lib/python3.7/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 216, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ File "falcon/api.py", line 189, in falcon.api.API.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/members.py", line 266, in on_post pre_approved=pre_approved) File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 520, in register list(workflow) File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 326, in _step_do_subscription self.member = self.mlist.subscribe(self.subscriber) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 494, in subscribe notify(SubscriptionEvent(self, member)) File "/usr/lib/python3/dist-packages/zope/event/__init__.py", line 31, in notify subscriber(event) File "/usr/lib/python3/dist-packages/mailman/app/membership.py", line 169, in handle_SubscriptionEvent send_welcome_message(mlist, member, member.preferred_language) File "/usr/lib/python3/dist-packages/mailman/app/notifications.py", line 52, in send_welcome_message 'list:user:notice:welcome', mlist, language=language.code)) File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 188, in get name, lookup_context, **substitutions) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 109, in get contents = protocols.get(actual_uri, **auth) File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 38, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3/dist-packages/requests/api.py", line 75, in get return request('get', url, params=params, **kwargs) File "/usr/lib/python3/dist-packages/requests/api.py", line 60, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 516, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /postorius/api/templates/list/<MAILINGLIST>/list:user:notice:welcome (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0b5ce8d8d0>: Failed to establish a new connection: [Errno 111] Connection refused')) Postorius/Mailman is running on port 8001, only Postorius still connecting on port 8000. Anyone seen something similar? Thanks in advance! Jeffrey

2 2

DMARC Munging
by Allan Hansen Jan. 30, 2020

Jan. 30, 2020

All, The munged From: header in MM3 still says 'name' via ‘listname’ <‘listaddress’> This caused me and my subscribers a lot of grief in MM2: Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around. Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this: 'name' via ‘listname’ <‘whoopsieaddress’> Which will return an automated reply explaining the issue. I like this option. How can I get that in? Yours, Allan Hansen allan_hansen(a)icloud.com PS: I always use sender in Reply-To.

2 3

Re: Mailman3 on Debian 10
by Abhilash Raj Jan. 29, 2020

Jan. 29, 2020

Please use mailman-users(a)mailman3.org for questions related to Mailman 3. On Wed, Jan 29, 2020, at 9:22 AM, Bala Mutyam wrote: > Hi there, > > I’m trying to install Mailman3 on Debian 10 as follows . > 1) Installed MariaDB, created databases, users for mailman3 and mailman3-web > 2) Then installed mailman3-full', 'dbconfig-mysql', 'python-pymysql', 'python3-pymysql', 'python3-mysqldb', 'nginx using Anisble script. > 3) I have removed Apache2 as it was installed with mailman3-full. > 4) Created a symbolic link for /etc/mailman3/nginx.conf and updated config files for mailman.cfg, mailman-hyperkitty.cfg, 25_mm3_macros, 455_mm3_router and 55_mm3_transport > > but the mailman service is not able to start it’s giving below error. Could you help me how to resolve it please? And also instructions for to install Mailman3 using Debian packages mailman3-full. I would like to use MySQl as backend and Exim4 as mail server. I couldn’t find new mailing list using the command line utility (/usr/sbin/newlist? > > Please see the attached Traceback. > > On webUI I’m seeing > Server error > An error occurred while processing your request. > > > *Attachments:* > * Mailman3 Errors.txt -- thanks, Abhilash Raj (maxking)

2 1

Cron of Mailman notify is not working
by Shashikanth Komandoor Jan. 29, 2020

Jan. 29, 2020

Hello, With your help, I was able to setup mailman 3.3 on my RHEL 7.5 machine and running well and good. For daily notification I have added the below line in the crontab: 00 08 * * * /var/lib/mailman/venv3/bin/mailman notify But this cron job is not working while I was able to run the same command manually at my CLI. Please help if there is any issue with mailman 3.3 or cronjob. -- Thanks & Regards, Shashi Kanth.K 9052671936

2 3

DMARC Mitigation Wrap
by Allan Hansen Jan. 27, 2020

Jan. 27, 2020

All, After a reinstall I’m back to thinking about the MM3 DMARC mitigation issue. Until munging can be improved, I will be using the option to wrap: MM3 has the option to wrap the main message with a wrap_message. It appears, however, that MM3 is oblivious to all my attempts to include whitespace, in this case a <cr>. When the enclosed message is automatically unwrapped by the receiving client, this causes the wrap and enclosed message's From: header to butt up against each other, which is rather ugly. I tried many tricks, but none worked, such as, <cr>, SPACE+, TAB+, <BLANKLINE>, SHIFT-RETURN, two RETURNS, \r\n and UTF-8 codes. They all either got ignored or copied as entered to the output message. Here’s an example. I just want to put a divider after the wrap_message main text. The From address of this message has been replaced with the list address, while the From name has 'via list' appended. Please be careful when using 'via list' addresses later for new emails, as they will be sent to the whole list.\r\n -------------------------- ----------------------------------------------------------------------\r\n From: Allan Hansen <allan_hansen(a)icloud.com <mailto:allan_hansen@icloud.com>> Subject: [Testlist] wrap with divider and BLANKLINE Which coding option am I missing? I have searched for one online. Yours, Allan Hansen allan_hansen(a)icloud.com

2 1

Header and footer templates in MM3
by Gila Halpern Jan. 26, 2020

Jan. 26, 2020

I read the earlier message from Peter Mueller about message decoration, and where the templates are in the file system. However, when I edit the header and footer templates in Postorius, those templates do not appear in the location specified. Should I be looking somewhere else? (I intend to write a program to rotate though several headers/footers, so I need to know where to have it write to.) Gila Halpern

3 3

Can I install Mailman 3.3 on RHEL 8 ?
by Shashikanth Komandoor Jan. 25, 2020

Jan. 25, 2020

Hi Team/Sir, Can Mailman 3.3 be installed on RHEL 8? I got this query because while I was trying to install the prerequisites for Mailman 3.3 as per the website http://docs.mailman3.org/en/latest/devsetup.html I found nodejs-less is also to be installed. But I don't find the nodejs-less as part of BaseOS packages or the AppStream modules. Please suggest how to go ahead. -- Thanks & Regards, Shashi Kanth.K 9052671936

1 0

Cannot see the cron jobs for Mailman 3 Installed
by Shashikanth Komandoor Jan. 24, 2020

Jan. 24, 2020

Hi, I have setup the Mailman 3 on my RHEL 7.5 box and found it was working fine. But I found that I am not getting daily summary notifications for which I learnt after browsing through different websites, there should be an entry of *checkdb* in the cron job list. But I did not find any such nor I don't find any cron job updated after the installation of mailman 3. So, please guide how to get those cron jobs of mailman 3 installed again without disturbing the already installed setup. Thanks in advance. -- Thanks & Regards, Shashi Kanth.K 9052671936

2 3

Cannot locate manage.py
by Frank van den Heuvel Jan. 22, 2020

Jan. 22, 2020

Hello, While following https://docs.mailman3.org/en/latest/migration.html, I want to execute: python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox Of course edited with values for my list. But I already get stuck in not being able to locate "manage.py". When I run "locate manage.py", I get: /opt/mailman/mm/venv/lib/python3.7/site-packages/django/conf/project_template/manage.py-tpl /opt/mailman/mm/venv/lib/python3.7/site-packages/example_project/manage.py /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py Which one is the right one? With kind regards and thanks for your work! Frank van den Heuvel BTW: This is a debian 10.2 with Mailman3: Django Version: 2.2.9 Python Executable: /opt/mailman/mm/venv/bin/python Python Version: 3.7.3 Python Path: ['/opt/mailman/mm', '/opt/mailman/mm/', '/opt/mailman/mm/bin', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/opt/mailman/mm/venv/lib/python3.7/site-packages'] Server time: Tue, 21 Jan 2020 08:34:45 -0800 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', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')

2 1

start_chain not present in migrated lists
by Paul Honig Jan. 21, 2020

Jan. 21, 2020

Hi, Please let me know where I can post my question if this list is not the right place. I'm configuring a mailing list server, migrating from Mailman 2.1 to 3.2.2, and I can't get the migrated mailing lists to work. When I create new mailing lists there is no problem. Here are the versions of Mailman I run : mailman 3.2.2 mailman-hyperkitty (1.1.0) django-mailman3 (1.2.0) postorius (1.3.2) mailmanclient (3.2.2) HyperKitty (1.2.2) The command line I use the migrate the mailing list: /opt/mailman_venv/bin/mailman -C /opt/mailman_venv/var/etc/mailman.cfg import21 mltest(a)test.domain /var/vmail/mig/data/lists/mltest/config.pck When I send an email to a migrated list, of which I made myself a member, no mail is sent, and I get the following stack trace in the log: ==> /var/log/mailman/mailman.log <== Jan 21 15:02:37 2020 (15948) Uncaught runner exception: None Jan 21 15:02:37 2020 (15948) Traceback (most recent call last): File "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/core/chains.py", line 40, in process chain = config.chains[start_chain] KeyError: None Jan 21 15:02:37 2020 (15948) SHUNTING: 1579615357.5331464+c5918e305ec281d47ef0caaed070c8c4bde26ee3 It seems like the start_chain has value 'None' and that prevents the mail from processed, but I can't find where to correctly set the start_chain. Please let me know how I can remedy this issue. Kind regards, Paul Honig This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo(a)esa.int)

2 1

Handling of SPAM mails in mailman3 - Check for X-Spam Header
by Torge Riedel Jan. 19, 2020

Jan. 19, 2020

Hi, we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, this is the second question: Such SPAM mails are currently hold for moderation with reason "not from a list member". Is there no check for the "X-Spam: Yes" header or is this check done later? I would prefer that a check for such a header is done first and is reported as the reason. Which is IMHO a very important information. Or maybe show "This is detected as SPAM" in big bold red letters in a new column in the list of mails to moderate for such a mail. Maybe there is more eye-candy solution for it. Sometimes mail accounts of allowed users are hacked and we do not want spread SPAM accidently. On my setup all mails are checked by rspamd before local delivery and I see that the "X-Spam" header is set for such mails. So even mails from allowed members with header "X-Spam: Yes" should be hold for moderation. Maybe this is already the case, did not gave it a try yet. Best regards Torge

2 5

Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail
by Torge Riedel Jan. 19, 2020

Jan. 19, 2020

Hi, we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, here is the first, second comes in a separate post: The list moderator currently receives a copy of the original mail in the info mail he gets for moderation. This is bad in case it was a SPAM mail, cause we have seen that such an info mail is detected also as SPAM. That might rise problems cause other mail servers might block the info mail as SPAM and if this happens too often blocking the whole server. I fear. At least I see that my rspamd starts learning the info mail as SPAM. I don't want that to happen. I searched mailman web interface for a setting to disable adding a copy to the info mail. But have not found it. Is it missing or where do I have to look? Best regards Torge

3 4

Mailman runners missing - nothing in logs
by Torge Riedel Jan. 19, 2020

Jan. 19, 2020

Hi, since migration from mailman2 to mailman3 I had twice the following, last time today: When sending a mail to a list I get the following reply from postfix after a while: connect to 127.0.0.1[127.0.0.1]:8024: Connection refused Searched on that and found some posts, where the following shell command is named to check what is running: ps -fwwu mailman And I get this as output: UID PID PPID C STIME TTY TIME CMD mailman 1166 1 0 Jan07 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/master -C /opt/mailman/core/mailman.cfg mailman 1180 1166 0 Jan07 ? 00:03:09 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 mailman 1212 1180 0 Jan07 ? 00:01:10 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 mailman 11039 11036 0 06:25 ? 00:00:03 /usr/bin/uwsgi-core --ini mailman3.ini mailman 11064 11039 0 06:25 ? 00:00:00 /usr/bin/uwsgi-core --ini mailman3.ini mailman 11065 11039 0 06:25 ? 00:00:01 /usr/bin/uwsgi-core --ini mailman3.ini mailman 17257 1180 0 Jan12 ? 00:00:37 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 Lots of expected runners are missing. After restarting the service the output of the same command is: UID PID PPID C STIME TTY TIME CMD mailman 11039 11036 0 06:25 ? 00:00:03 /usr/bin/uwsgi-core --ini mailman3.ini mailman 11064 11039 0 06:25 ? 00:00:00 /usr/bin/uwsgi-core --ini mailman3.ini mailman 11065 11039 0 06:25 ? 00:00:01 /usr/bin/uwsgi-core --ini mailman3.ini mailman 14430 1 13 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/master -C /opt/mailman/core/mailman.cfg mailman 14434 14430 18 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=archive:0:1 mailman 14435 14430 20 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=bounces:0:1 mailman 14436 14430 18 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=command:0:1 mailman 14437 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=in:0:1 mailman 14438 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=lmtp:0:1 mailman 14439 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=nntp:0:1 mailman 14440 14430 19 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=out:0:1 mailman 14441 14430 20 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=pipeline:0:1 mailman 14442 14430 20 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 mailman 14443 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=retry:0:1 mailman 14444 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=virgin:0:1 mailman 14445 14430 18 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=digest:0:1 So now back to good. I checked all the logs prior to restarting the service in directory /opt/mailman/var/log, but I do not see any errors. And the master was still running, I would expect that the master will start / restart a runner in case it died? Fun fact: First time of this problem was two weeks from now, which was two weeks after migration to mailman3. I'm excited if it will happen in two weeks again. Installed packages for core: mailman (3.3.0) mailman-hyperkitty (1.1.0) Any suggestions where I should have a deeper look and maybe find the root cause of this problem? Thanks in advance Torge

2 2

Another set of new releases
by Abhilash Raj Jan. 19, 2020

Jan. 19, 2020

Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.2 - Django-mailman3 1.3.2 - Hyperkitty 1.3.2 This release was required as it turned out 1.3.1 releases did not includes translations in the tarballs that I created and uploaded to PyPI. They do include a couple of bugfixes and more translations. - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) All three of these releases also officially drop support for Django 1.11. Although, there hasn't been any code change that breaks compatibility with 1.11. It has just been dropped form our CI machinery since our dependencies no longer support 1.11. All the releases are available on PyPI, as usual! -- Thanks Abhilash Raj

2 3

Settings for https support
by Dieter Leupold Jan. 16, 2020

Jan. 16, 2020

Hi, I configured Postorius (via Apache2) to use https, which looks fine. But the connection to hyperkitty failed with "code 400, message Bad request syntax". I tried serveral settings....without success. Could you give me an example, which settings are to configure? Thanks for your help! -- Dieter

2 1

Mailman shell tutorial
by andrew.bernard＠gmail.com Jan. 15, 2020

Jan. 15, 2020

is there a tutorial or some examples for using the mailman shell? Is there detailed documentation on it? Anything I try to do such as the following fails: $ mailman shell Welcome to the GNU Mailman shell >>> command('mailman shell --details') Traceback (most recent call last): File "<console>", line 1, in <module> NameError: name 'command' is not defined >>> I execute the shell as user mailman and from within the same venv that all the programs run under.

4 5

Adding a domsin
by Allan Hansen Jan. 13, 2020

Jan. 13, 2020

Hi all, I’m still working on setting up my lists in a domain that was added after MM3 installation. It’s mostly working but the Postorius page and the ‘noreply’ emails still sport the old domain name. I hav looked at all the py and cfg files where the old name appeared, and they no longer hold the old name. My coadmin now tells me that the database has a table with the old name. Any suggestion as to whether that can cause the issue and if it’s safe to change the table. Yours, Allan Hansen P.O. Box 2423 Cypress, CA 90630

3 3

Cannot setup HTTPS support for mailman3-web
by jean-christophe manciot Jan. 11, 2020

Jan. 11, 2020

Ubuntu 20.04 mailman3 3.2.2-1 mailman3-web 0+20180916-10 python3-django 2:2.2.9-2ubuntu1 In ```/etc/mailman3/uwsgi.ini``` (example.org is defined in the local /etc/hosts as 10.0.0.1): ``` [uwsgi] # Port on which uwsgi will be listening. ### suwsgi: uwsgi protocol over TLS uwsgi-socket = example.org:8430 # https://uwsgi-docs.readthedocs.io/en/latest/HTTPS.html?highlight=ssl https = /etc/ssl/example.org.crt,/etc/ssl/example.org_rsakey.pem.decrypted,HIGH ... # Drop privileges and don't run as root. uid = www-data gid = www-data ... ``` I suppose that uwsgi reads the certificate & its private key before dropping root privileges. Right now, uwsgi cannot access them as ```www-data```. In ```/etc/mailman3/mailman-web.py``` (symlinked to django settings.py) : ``` ... SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_SCHEME', 'https') # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' ... POSTORIUS_TEMPLATE_BASE_URL = 'https://example.org:8430' ``` In ```/etc/nginx/sites-enabled/example.org.conf``` ``` ... location / { include /etc/nginx/uwsgi_params; # upstream app server uwsgi_pass suwsgi://example.org:8430; } ``` uwsgi is listening on the right address/port: ``` # networks-list-connections.sh | grep :8430 tcp 0 0 10.0.0.1:8430 0.0.0.0:* LISTEN 33 54336045 1768187/uwsgi ``` Despite those settings and all the relevant systemd services restarted, I get ```502 Bad Gateway``` while browsing to ```https://example.org/postorius/lists/?all-lists``` (or any other page) with the following error nginx message: ``` *1 peer closed connection in SSL handshake while SSL handshaking to upstream, client: 10.0.0.1, server: example.org, request: "GET /postorius/lists/?all-lists HTTP/2.0", upstream: "suwsgi://10.0.0.1:8430", host: "example.org", referrer: "https://example.org/postorius/lists/" ``` Of course, without those specific https/suwsgi settings, everything works fine. What am I missing/doing incorrectly? Does uwsgi need access to the certificate/private key while running as non-root for instance?

3 3

Default values for new lists
by Sten Aus Jan. 11, 2020

Jan. 11, 2020

Hi I haven't found out where I could choose or edit default list values (when creating new list). For example I would like that all new lists would be with *private archive* (and change this when it is needed). This is great that I can choose not to advertise list in Index (which I can choose from list creation interface) but I would like to choose other options too. Right now only solution is to create list and then choose Archiving and then select "private archives". Another thing is that I would like to choose default subscription policy to "Moderate". If anyone has encountered this problem, let me know! All the best Sten

4 5

bounce processing on this list
by Mark Sapiro Jan. 9, 2020

Jan. 9, 2020

I have just installed the latest Mailman core for this list. This version now actually processes bounces. As a result of the huge backlog of unprocessed, queued bounces, some members may receive one or more bounce probe messages. As long as the probes don't bounce, your subscription will be unaffected and you can ignore the probe message. Sorry for the noise. Hopefully it's just a one time catch-up. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

FILTER_VHOST for 3.2.1 not working after install
by Élodie BOSSIER Jan. 8, 2020

Jan. 8, 2020

Hello, I'm using Mailman 2.1.29 since several years and all was perfect except the virtual_host which was "faked" : it was possible to have several mailing list by domain linked to their own domain and url but not same mailing list name for multiple domains. Example (with lighttpd) : - at http://ml.bossier.fr/listinfo we can see ONLY mailing list "test2@", "Test3@" and "Test4@" for @ml.bossier.fr - and at http://ml.franceserv.fr/listinfo we can see ONLY mailing list "bar@", "newsletter@" and "test@" for @ml.franceserv.fr Each url_host have their "own" mailing list. It's the main reason I would like migrate and use Mailman 3 and be able to have "test(a)ml.bossier.fr" and "test(a)ml.franceserv.fr". So I installed Mailman 3.2.1 and I have set "FILTER_VHOST = True" into /etc/mailman3/mailman-web.py then : mailman create --language fr --owner admin(a)franceserv.fr --domain test(a)ml.franceserv.fr mailman create --language fr --owner admin(a)franceserv.fr --domain test2(a)ml.bossier.fr And I have this result (with nginx as front) : - at http://ml.franceserv.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" - and at http://ml.bossier.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" (same result) And it's my problem, I would like be able to see the linked mailing list to their own url. I would like with Mailman 3.2.1 see into : - "example1.com/postorius/lists/" only the mailing list related to example1, - and into "example2.com/postorius/lists/" only the mailing list related to example2 as Mailman 2.1.x do it. I don't understand what I missed, could you help me please ? Best regards, Élodie PS. Sorry for my english language I'm french.

2 1

Migration from 2.1 to 3
by brunol＠agro.uba.ar Jan. 8, 2020

Jan. 8, 2020

Hi, I am in the process to migrate an old 2.1 installation to 3.2.1 (Debian 10.1) Following the 2.1 to 3 docs: - Create a new list - Use the import21 command The command runs successfully (at least no errors in stdout). There is a problem when sending an email to the newly imported list, the message never get send to the members. I do get moderation emails, and if i do a mass subscribe, the welcome email is received by the new members. In a fresh 3 new list (not imported from 2.1) this does not happen. I already tried looking for clues in the logs [logging.smtp] path: debug.log level: debug [logging.smtp-failure] path: debug.log level: debug [logging.error] path: debug.log level: debug But i haven't seen anything useful yet. Any hints on this?

4 14

Hyperkitty - not sending from GUI & reply-thread
by sunil soprey Jan. 8, 2020

Jan. 8, 2020

With latest release (HK 1.3.1), does anyone have an issue with no emails from reply-thread? I able to send/receive emails to/from mailman. I see MTA delivered emails, just no emails from HK GUI. No errors logs (py exception) nor mailman. ideaS? Versions: mailman-hyperkitty (1.1.0) - Mailman archiver plugin for HyperKitty INSTALLED: 1.1.0 (latest) HyperKitty (1.3.1) - A web interface to access GNU Mailman v3 archives INSTALLED: 1.3.1 (latest) mailman (3.3.0) - Mailman -- the GNU mailing list manager INSTALLED: 3.3.0 (latest) postorius (1.3.1) - A web user interface for GNU Mailman INSTALLED: 1.3.1 (latest) django-mailman3 (1.3.1) - Django library to help interaction with Mailman INSTALLED: 1.3.1 (latest) mailmanclient (3.3.0) - mailmanclient -- Python bindings for Mailman REST API INSTALLED: 3.3.0 (latest) f

2 1

Re: [Mailman-Users] MM3 startup issues
by Mark Sapiro Jan. 7, 2020

Jan. 7, 2020

Restoring original Subject:, and doesn't this thread belong on mailman-users(a)msailman3.org - CCing there. On 1/5/20 11:51 PM, Allan Hansen wrote: > > Thanks again, Mark! > My responses below. > >> On 1/4/20 5:47 PM, Allan Hansen wrote: >>> >>> a. The server was set up with the wrong domain name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ in >>> the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? >> >> >> What are the setytings in Postorius -> Settings -> Archiving? > > Archive policy: Private archives > Archive archivers: hyperkitty, prototype Are the messages in Mailman's var/archives/prototype/LIST@DOMAIN/new directory? Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? What's the setting for base_url in mailman-hyperkitty.cfg? Are there any errors in var/logs/mailman.log? >>> b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That’s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. >> >> >> Set >> >> FILTER_VHOST = True >> >> in settings_local.py >> > > Yes, Brian told me to do the same. This is the what I wrote back: > > hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py > > Edited the setting to: > # Only display mailing-lists from the same virtual host as the webserver > FILTER_VHOST = True You shouldn't edit settings.py. You should override the setting by putting it in settings_local.py. > Then Brian told me to restart qcluster: > hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster qcluster is not what you need to restart. You need to restart whatever is supporting the wsgi interface to Django. This may be uwsgi or gunicorn or ??. Whatever it is, that's what needs to be restarted. > I then logged in, but the same lists are showing. It either takes the system a long time to reset or it has ignored the > setting. > Just tried it again, and the lists are all showing. Do I need to manually recompile the file? > >> >>> c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: >>> >>> Something went wrong >>> Mailman REST API not available. Please start Mailman core. >> >> >> Postorius is unable to access core's REST API. Is Mailman running? > > Well, I was able to post to the lists, so I assume it is. Listing at processes, I see a bunch of postgres, python3, nginx, django-adminp but > nothing explicitly with a ‘mailman’ string. If you do `ps ax|grep runner=`, what do you see? If you don't see at least three processes with `--runner=rest:0:1`, stop Mailman and start Mailman. >> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as `filename` in the `file` handler in the LOGGING >> definition in settings(_local).py. > > hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 45, in _get_site_by_request > SITE_CACHE[domain] = self.get(domain__iexact=domain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. This is because of the domain change. In settings(_local).py you have a setting for SITE_ID. Possibly, setting that in settings_local.py to a value one greater that the current setting will do. To be certain of the correct value, you need to look at the django_site table in mailman's database. That table has 3 columns, id, domain and name. The id for the row of your domain is what needs to be set as SITE_ID. > [ABH] At this point I click to accept a subsription request: > > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen > chunked=chunked, > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > response.begin() > File "/usr/lib/python3.7/http/client.py", line 296, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response > > So yes, the REST API is not there. How can I get it going? Stop Mailman and then start it. > Before we added the new domain, I was able to accept subscription requests to the previous domain’s lists. No more. > > Yours, > > Allan -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 3

MM3 shunting mails
by Anders Nilsson Jan. 3, 2020

Jan. 3, 2020

I'm running a Mailman 3.1.0 installation on a CentOS 7 machine. Using RPMs from https://repos.fedorapeople.org/repos/abompard/hyperkitty/el-7/x86_64/ I do have problems with some lists occasionally going into some kind of shunt mode, where alla mails sent to them gets shunted. In the Mailman log I get entries for each shunted email: Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) Traceback (most recent call last): File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 171, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3.4/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 121, in process process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 70, in process archiver_set = IListArchiverSet(mlist) File "/usr/lib/python3.4/site-packages/zope/component/hookable.py", line 33, in __call__ return self.__implementation(*args, **kw) File "/usr/lib/python3.4/site-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib64/python3.4/site-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3.4/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none() File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", line 2733, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) SHUNTING: 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 And so far my Google-fu hasn't been good enough to give me any useful answers to why this happens. If I dump one of the pickles using qfile I cannot see any complaints. Most of the times, if I remove and recreate a failing list and run unshunt the shunted emails get processed and sent. Anyone seen something similar? Regards, Anders Nilsson -- Anders Nilsson, Ph.D. <andersn(a)control.lth.se> Dep. of Automatic Control, Lund University Phone: +46 (0)46 222 87 94, Fax: +46 (0)46 13 81 18 Mob: +46 (0)703 22 57 67

4 4

Mark a list to prevent it being shown as inactive on HyperKitty
by Steven Maddox Jan. 3, 2020

Jan. 3, 2020

Lo Folks, Subject says it all really, is there anyway to mark a list as one which should never be shown as inactive on the HyperKitty web interface? We've got a list which we consider to be "active", it's just that there might be the odd month here or there which it won't show activity. Failing having such a setting (as described above)... maybe there is a way of changing what it considers to be 'inactive' (I'm assuming that it is 30 days?). At the moment (in order to counteract commit 156f4cda) I've dropped this into templates/hyperkitty/bottom.html to uncheck the "Hide Inactive" checkbox... but that doesn't actually stop HyperKitty from considering it inactive - just shows it in dark grey. <script> document.querySelector("input[type='checkbox'][value='inactive']").checked = false; </script> -- Steven Maddox Lantizia

2 1

Weekend releases
by Abhilash Raj Dec. 26, 2019

Dec. 26, 2019

Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.1 - Django-mailman3 1.3.1 - Hyperkitty 1.3.1 These are all bugfix releases and include several fixes each. The full changelogs are available at: - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) Most notable fixes include a fix for PostgeSQL support in Hyperkitty, ability to delete a MailingList in Hyperkitty and list settings changes are immediately reflected in Hyperkitty (like making a List private). It also includes support for Python 3.8 and Django 3.0 in Postorius and Django-maialman3. Hyperkitty doesn't yet support either of them due to some dependencies not yet supporting Django 3.0 and a bug in Python 3.8.0 causing a test case failure[1]. I hope that we are able to support the latest and greatest as soon as possible, I am excited to be able to play with Django's aync capabilities. Finally, since our i18n workflow has been setup, we have lots of new translations coming in. This release also includes more parts of Postorius being translatable, including section headers. I am really happy to see Mailman 3 move closer to Mailman 2 in terms of i18n. If you want to help us improve the coverage, head on to Weblate[2]. All the releases are available on PyPI, as usual! [1] Fun Fact: The bug was due to a code that I contributed ;-). It is now fixed and will be soon out with Python 3.8.1 sometime this month. [2] https://hosted.weblate.org/projects/gnu-mailman/ -- thanks, Abhilash Raj (maxking)

3 4

postfix virtual domain and mailman 3
by work＠andrefincato.info Dec. 25, 2019

Dec. 25, 2019

hi everyone! i start by saying that i browsed through the archives in here for the past three days, and re-read the mailman 3 docs several times, as well the postfix docs. the thread closest to my problem is this one https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ; i was not sure if it was good to re-open though. i have a postfix + dovecot setup using the "separate domains and non-unix accounts". problem: ``` postfix/smtpd[26356]: NOQUEUE: reject: RCPT from wout1-smtp.messagingengine.com[64.147.123.24]: 550 5.1.1 <list-name(a)domain.com>: Recipient address rejected: User unknown; from=<some(a)email.com> to=<list-name(a)domain.com> proto=ESMTP helo=<wout1-smtp.messagingengine.com> ``` postfix main.cf relevant portion for virtual users ``` # deliver mail for virtual users to Dovecot's LMTP socket virtual_transport = lmtp:unix:private/dovecot-lmtp # setup virtual domains and non-unix accounts virtual_mailbox_domains = /etc/postfix/vhosts virtual_mailbox_base = /var/spool/vmail virtual_mailbox_maps = hash:/etc/postfix/vmaps virtual_uid_maps = static:1001 virtual_gid_maps = static:1001 virtual_alias_maps = hash:/etc/postfix/valias ``` postfix `main.cf` mailman settings ``` transport_maps = regexp:/opt/mailman/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/var/data/postfix_domains ``` question: i tried to add the `alias_domain` to mailman using Mailman Core REST APIs because I read about https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-… ; entering the mailman console and doing `dump_json('http://localhost:9001/3.0/domains/example.com/lists')` was giving me error that `dump_json` is not an available module. is that the way to go? should I add a an `alias_domain` to Mailman in order for it to output a `postfix_vmap` when doing `mailman aliases`? and then add it to postfix `main.cf` like so ``` virtual_alias_maps = hash:/etc/postfix/valias, regexp:/opt/mailman/var/data//postfix_vmap ``` or do you suggest as a simple viable solution to create a new unix account and setup postfix to use local domains? thanks and hopefully my confusion arose from reading all these threads will dissipate soon!

2 1

content filtering in version 3.1
by Dieter Leupold Dec. 20, 2019

Dec. 20, 2019

Hi, I'm new to MM3. I installed version 3.1.1 on Ubuntu 18.04. All looks fine. But i miss the setting "pass_mime_types" at content filtering. Also i don't find the settings for bounce processing. Are these features no longer supported at version 3.1.1? Thanks for your information! -- Dieter Leupold

2 4

Please update your Mailman installations: CVE-2019-19844
by Abhilash Raj Dec. 19, 2019

Dec. 19, 2019

Hey Mailman Users, A new Django vulnerability was disclosed yesterday[1] which can lead to account hijacks via password reset emails. The fix has been released as a part of Django 3.0.1, 2.2.9, and 1.11.27. We do not support Django 3.0.1, so, please upgrade to 2.2.9 or 1.11.27, depending on which version of Mailman components you are using. If you are using a virtualenv based installation, you can install the new versions using `pip` (venv) $ pip install -U django==2.2.9 or similar for 1.11.27. You can also upgrade django-allauth to 0.41.0, which also fixes this issue[2]. I hope distro packages will soon have updated packages with the fixes. I have also published new versions of Container Images, 0.3.2 (or, 0.3) both have been updated. See more details about updating the containers here[3]. [1]: https://www.djangoproject.com/weblog/2019/dec/18/security-releases/ [2]: https://github.com/pennersr/django-allauth/blob/master/ChangeLog.rst#0410-2… -- thanks, Abhilash Raj (maxking)

1 0

No Message-ID and Postfix
by Seth Seeger Dec. 18, 2019

Dec. 18, 2019

Hello everyone, I have two mailing list members who use an old Android tablet or a Windows 10 mail program, and when they reply to an email, their submission gets rejected: 550 No Message-ID header provided (in reply to end of DATA command) I found this note on how to solve it with Exim: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… https://gitlab.com/mailman/mailman/issues/448 https://gitlab.com/mailman/mailman/merge_requests/540/diffs?commit_id=fa811… Has anyone solved this for Postfix? Thanks, Seth

2 1

"Must issue a STARTTLS command first" issue during social login 'send_email_confirmation'
by jean-christophe manciot Dec. 18, 2019

Dec. 18, 2019

Ubuntu 20.04 mailman3 3.2.2-1 postfix 3.4.7-2 ```/etc/mailman3/mailman.cfg``` ``` [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: user smtp_pass: 'password' smtp_secure_mode: SecureMode.STARTTLS lmtp_host: 127.0.0.1 lmtp_port: 9024 configuration: python:mailman.config.postfix ``` The ```smtp_secure_mode``` value is based on https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht…. I am able to send emails using a mail client located on a remote device with the same user/password credentials. Yet, trying to perform a social login leads to: ``` ERROR 2019-12-17 11:44:00,414 211904 django.request Internal Server Error: /accounts/github/login/callback/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/oauth2/views.py", line 73, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/oauth2/views.py", line 143, in dispatch return complete_social_login(request, login) File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 152, in complete_social_login return _complete_social_login(request, sociallogin) File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 167, in _complete_social_login ret = _login_social_account(request, sociallogin) File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 55, in _login_social_account signal_kwargs={"sociallogin": sociallogin}) File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 144, in perform_login send_email_confirmation(request, user, signup=signup) File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 312, in send_email_confirmation signup=signup) File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 60, in send_confirmation confirmation.send(request, signup=signup) File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 166, in send get_adapter(request).send_confirmation_mail(request, self, signup) File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 450, in send_confirmation_mail ctx) File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 137, in send_mail msg.send() File "/usr/lib/python3/dist-packages/django/core/mail/message.py", line 291, in send return self.get_connection(fail_silently).send_messages([self]) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 110, in send_messages sent = self._send(message) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 126, in _send self.connection.sendmail(from_email, recipients, message.as_bytes(linesep='\r\n')) File "/usr/lib/python3.7/smtplib.py", line 867, in sendmail raise SMTPSenderRefused(code, resp, from_addr) smtplib.SMTPSenderRefused: (530, b'5.7.0 Must issue a STARTTLS command first', 'user@mysite') ``` Any suggestion?

3 3

Mass subscribe question
by Brian Carpenter Dec. 17, 2019

Dec. 17, 2019

Does mass subscribing bypass a list's subscription policy? I had a list owner mass subscribe a large number of invalid mailboxes which resulted in us terminating their service since Mailman 3 has no bounce processing that helps to clean a list up nor a mass invite function that a user can use instead of mass subscribing. If mass subscribing does bypass the subscription policy then I beg you to make mass inviting and bounce processing a HIGH priority. I am really disappointed that Mailman 3 did not come out with a bounce process feature right out of the gates. But the fact it still doesn't have one on Mailman 3.3 seems scandalous. Brian

1 0

UnicodeEncodeError: 'ascii' codec can't encode character
by Marvin Gülker Dec. 16, 2019

Dec. 16, 2019

Hi, I've accidentally sent from an unregisted address to one of my lists. Mailman correctly held the message back for moderation, but when I go to the page for held messages in postorios, I receive a 500 error. I've included an except from the log below. To me, it looks as if it errors on processing my last name (which has a non-ascii character in it). This is Postorius 1.1.2 on Ubuntu 18.04 LTS from the repos. I've searched on the tracker for the problem and found one ticket[1], but it has something with logging so I suppose this is a different problem. Ideas? And how do I discard the message without access to the held messages page? Python version is 3.6.8. Log excerpt: Dec 09 13:21:04 2019 (3090) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get resource = self._make_collection(request) File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource resource['msg'] = msg.as_string() File "/usr/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode character '\ufffd' in position 269: ordinal not in range(128) Dec 09 13:21:04 2019 (3090) 127.0.0.1 - - "GET /3.0/lists/tsc-devel(a)lists.secretchronicles.org/held?count=10&page=1 HTTP/1.1" 500 59 -- Blog: https://mg.guelker.eu

3 15

admin/login/ cannot be accessed
by jean-christophe manciot Dec. 14, 2019

Dec. 14, 2019

Ubuntu 20.04 python3-django 2:2.2.6-1ubuntu1 python3-django-hyperkitty 1.3.1 (built from sources) mailman3-full 3.2.2-1 Nginx server configuration: ``` ... ######## # Static ######## location /favicon.ico { alias <mysite_dir>/static/hyperkitty/img/favicon.ico; } location /static/favicon.ico { alias <mysite_dir>/static/postorius/img/favicon.ico; } location /static/ { alias <mysite_dir>/static/; } ####################### # Upstream uwsgi server ####################### location / { include /etc/nginx/uwsgi_params; uwsgi_pass 127.0.0.1:<uwsgi_server_port>; } ... ``` where: - <mysite_dir> is a symlink to <django_dir>/static - <uwsgi_server_port> matches the one defined in ```/etc/mailman3/uwsgi.ini```: ``` [uwsgi] # Port on which uwsgi will be listening. uwsgi-socket = 127.0.0.1:<uwsgi_server_port> ``` All 3 systemd services run fine: - mailman3 - mailman3-web - qcluster I'm trying to login to the django administration pages. I get the django administration login page at: https://mysite/admin/login/ Logging in with the admin credentials leads to: ``` This site can’t be reached The webpage at https://mysite/admin/login/ might be temporarily down or it may have moved permanently to a new web address. ERR_HTTP2_PROTOCOL_ERROR ``` This is very strange because it is the URL which I used to get the login page in the first place. If I launch a test web server at another port with: ``` <django_dir># python3 manage.py runserver <mysite_ip_address>:8080 Performing system checks... System check identified no issues (0 silenced). December 11, 2019 - 17:50:48 Django version 2.2.6, using settings 'settings' Starting development server at http://<mysite_ip_address>:8080/ Quit the server with CONTROL-C. ``` and access it at ```http://<mysite_ip_address>:8080/admin/login/``` to login with the same credentials as before, I get through and all the django administration lines appear, although in a degraded layout: ``` Site administration Accounts Email addresses Add Change Authentication and Authorization Groups Add Change Users Add Change Django Mailman 3 Mail domains Add Change Profiles Add Change ... ``` Any idea what could be happening here?

2 6

bounces with empty message-id
by Peter Münster Dec. 12, 2019

Dec. 12, 2019

Hi, It seems, that mailman bounces the bounces, so that the list-owner never sees them: --8<---------------cut here---------------start------------->8--- postfix/smtpd[12002]: connect from out04.smtpout.orange.fr[193.252.22.213] postfix/smtpd[12002]: 879D6F12E8: client=out04.smtpout.orange.fr[193.252.22.213] postfix/cleanup[11841]: 879D6F12E8: message-id=<> postfix/qmgr[10092]: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active) postfix/smtpd[12002]: disconnect from out04.smtpout.orange.fr[193.252.22.213] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) postfix/qmgr[10092]: 879D6F12E8: removed --8<---------------cut here---------------end--------------->8--- What could I do please, to get the bounces? I would like to use VERP to identify wrong addresses... TIA for any hints, -- Peter

3 8

Hyperkitty Error
by Brian Carpenter Dec. 11, 2019

Dec. 11, 2019

I am seeing the following error being repeated every 2 seconds in the uwsgi-error.log: 01:22:05 [Q] INFO Process-1:19112 processing [compute_thread_positions] 01:22:05 [Q] ERROR Failed [compute_thread_positions] - 'DiGraph' object has no attribute 'node' : Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/django_q/cluster.py", line 381, in worker res = f(*task['args'], **task['kwargs']) File "/usr/lib/python3.6/site-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors obj = graph.node[msgid]["obj"] AttributeError: 'DiGraph' object has no attribute 'node' I am running the docker version of Mailman, version 1.3.0. Any suggestions? Thanks, Brian

3 4

Default moderation for new members
by Seth Seeger Dec. 11, 2019

Dec. 11, 2019

Hello everyone, I’m loving Mailman3 so far! Great work on it. I’d like to have new members who join my lists have their posting ability set to moderated. (After their first legitimate post, they would set to be unmoderated.) I haven’t been able to find this, though I’m suspecting the language has changed. Thanks, Seth

2 3

HyperKitty async tasks runner: systemd qcluster service fails eventually
by actionmystique＠gmail.com Dec. 9, 2019

Dec. 9, 2019

Ubuntu 20.04 mailman3 3.2.2-1 python3-django-hyperkitty 1.3.0-1ubuntu1 According to [Hyperkitty Asynchronous tasks paragraph](https://hyperkitty.readthedocs.io/en/latest/install.html#asynchronous-tasks), we can start a qcluster systemd service file: ``` [Unit] Description=HyperKitty async tasks runner After=network.target remote-fs.target [Service] ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings User=<user> Group=<group> Restart=always [Install] WantedBy=multi-user.target ``` Starting it works fine: ``` # systemctl restart qcluster # systemctl status qcluster ● qcluster.service - HyperKitty async tasks runner Loaded: loaded (/etc/systemd/system/qcluster.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2019-12-04 15:09:46 CET; 2ms ago Main PID: 1055959 ((go-admin)) Tasks: 0 (limit: 9284) Memory: 0B CGroup: /system.slice/qcluster.service └─1055959 (go-admin) Dec 04 15:09:46 samsung4-ubuntu systemd[1]: Started HyperKitty async tasks runner. ``` However, the service fails after a few seconds: ``` # systemctl status qcluster ● qcluster.service - HyperKitty async tasks runner Loaded: loaded (/etc/systemd/system/qcluster.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2019-12-04 15:09:48 CET; 1min 1s ago Process: 1055961 ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings (code=exited, status=1/FAILURE) Main PID: 1055961 (code=exited, status=1/FAILURE) Dec 04 15:09:48 samsung4-ubuntu systemd[1]: qcluster.service: Service RestartSec=100ms expired, scheduling restart. Dec 04 15:09:48 samsung4-ubuntu systemd[1]: qcluster.service: Scheduled restart job, restart counter is at 5. Dec 04 15:09:48 samsung4-ubuntu systemd[1]: Stopped HyperKitty async tasks runner. Dec 04 15:09:48 samsung4-ubuntu systemd[1]: qcluster.service: Start request repeated too quickly. Dec 04 15:09:48 samsung4-ubuntu systemd[1]: qcluster.service: Failed with result 'exit-code'. Dec 04 15:09:48 samsung4-ubuntu systemd[1]: Failed to start HyperKitty async tasks runner. ``` The corresponding log file is empty and I cannot find any issue in the other logs. Any suggestion? Also, another doc paragraph [Running the task queue (required)](http://docs.mailman3.org/en/latest/config-web.html#running-the-t…) talks about another required command "python manage.py qcluster"; so which one is it?

3 9

Source Installation Assistance
by Brian Carpenter Dec. 6, 2019

Dec. 6, 2019

I am trying to install Mailman 3 from source using: https://docs.mailman3.org/en/latest/index.html My first question is where is the best place to get assistance or ask questions regarding the installation process? I am not sure if mailman-users is that place anymore. Thanks, Brian

4 6

Cannot start lmtp runner due to error while attempting to bind on address ('127.0.0.1', 8024): address already in use
by actionmystique＠gmail.com Dec. 4, 2019

Dec. 4, 2019

Ubuntu focal 20.04 mailman3 3.2.2-1 In ```/etc/mailman3/mailman.cfg```: ``` # Where the LMTP server listens for connections. Use 127.0.0.1 instead of # localhost for Postfix integration, because Postfix only consults DNS # (e.g. not /etc/hosts). # Configuration is for a system where Mailman and the MTA are on the same host lmtp_host: 127.0.0.1 lmtp_port: 8024 ``` Stopping mailman3 and checking that no lmtp runner is active: ``` # systemctl stop mailman3 # ps -aux |grep mailman|grep -Pv "(postgres|grep)" www-data 855395 0.0 0.4 82856 37904 ? Ss 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 855411 0.0 0.3 156588 25724 ? Sl 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 858518 0.0 0.2 82856 22532 ? Ss 13:52 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini ``` Starting mailman3 and checking all active mailman3 runners: ``` # ps -aux |grep mailman|grep -Pv "(postgres|grep)" www-data 855395 0.0 0.4 82856 37904 ? Ss 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 855411 0.0 0.3 156588 25724 ? Sl 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 858612 0.0 0.2 82856 22532 ? Ss 13:54 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini list 858626 17.8 0.9 103248 74680 ? Ss 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/master --force -C /etc/mailman3/mailman.cfg list 858628 27.2 0.7 87176 62244 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 list 858629 28.6 0.8 89116 64044 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 list 858630 29.2 0.8 90184 64972 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 list 858631 27.0 0.7 87560 62420 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 list 858632 28.8 0.8 89620 64508 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1 list 858633 26.6 0.7 84464 60800 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 list 858634 26.2 0.7 81964 58580 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 list 858635 28.4 0.7 88692 63648 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 list 858636 26.4 0.7 83308 59820 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 list 858637 26.8 0.7 84076 60828 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 list 858638 29.2 0.8 90176 64964 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 list 858639 27.4 0.7 87564 62528 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 ``` We clearly see that lmtp runner is active; then it exits after a few seconds: ``` # ps -aux |grep mailman|grep -Pv "(postgres|grep)" www-data 855395 0.0 0.4 82856 37904 ? Ss 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 855411 0.0 0.3 156588 25724 ? Sl 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 858612 0.0 0.2 82856 22532 ? Ss 13:54 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini list 858626 2.7 0.9 103248 74680 ? Ss 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/master --force -C /etc/mailman3/mailman.cfg list 858628 4.3 0.9 103260 74704 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 list 858629 4.3 0.9 103256 74964 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 list 858630 4.3 0.9 103256 74920 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 list 858631 4.3 0.9 103256 74804 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 list 858633 4.4 0.9 103924 75444 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 list 858634 4.3 0.9 103256 74392 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 list 858635 4.3 0.9 103260 74876 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 list 858636 4.4 0.9 182412 79472 ? Sl 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 list 858637 4.4 0.9 103256 74964 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 list 858638 4.5 0.9 103256 74808 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 list 858639 4.4 0.9 103256 74776 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 ``` The systemd service status gives a clue: ``` # systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-12-02 13:54:45 CET; 2min 51s ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 858617 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=0/SUCCESS) Main PID: 858626 (python3) Tasks: 14 (limit: 9284) Memory: 688.5M CGroup: /system.slice/mailman3.service ├─858626 /usr/bin/python3 /usr/lib/mailman3/bin/master --force -C /etc/mailman3/mailman.cfg ├─858628 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 ├─858629 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 ├─858630 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 ├─858631 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 ├─858633 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 ├─858634 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 ├─858635 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 ├─858636 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 ├─858637 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 ├─858638 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 └─858639 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: self.lmtp.start() Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: File "/usr/lib/python3/dist-packages/aiosmtpd/controller.py", line 60, in start Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: raise self._thread_exception Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: File "/usr/lib/python3/dist-packages/aiosmtpd/controller.py", line 40, in _run Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: ssl=self.ssl_context)) Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: File "/usr/lib/python3.7/asyncio/base_events.py", line 579, in run_until_complete Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: return future.result() Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: File "/usr/lib/python3.7/asyncio/base_events.py", line 1374, in create_server Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: % (sa, err.strerror.lower())) from None Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: OSError: [Errno 98] error while attempting to bind on address ('127.0.0.1', 8024): address already in use ``` Of course the port is already in use: it is used by dovecot. ``` tcp6 0 0 ::1:8024 :::* LISTEN 0 1317360 129620/dovecot tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 0 1316324 129620/dovecot ``` I must be missing something.

3 5

Changelog and/or Release Notes
by Brian Carpenter Nov. 28, 2019

Nov. 28, 2019

Now that I am using Mailman 3.3, where can I find the release notes and/or changelog for core, postorius and hyperkitty under Mailman 3.3? Thanks! Brian

2 2

Re: [Mailman-Users] Mailman 3 Ready?
by Stephen J. Turnbull Nov. 27, 2019

Nov. 27, 2019

Allan Hansen writes: > What is the best, easiest, guaranteed-to-work way to get this > Mailman 3 up and running (OS, add-ons, options, etc.). When I tried > myself, I saw a lot of options that I really did not really care to > have because I did not know the consequences of each. I’m an > application programmer, not a systems programmer. It's email, there are no guarantees. I hate to say that, but that's the way it is. In particular, I'm concerned about the "iRedMail" integration, which may be a complete wildcard from my point of view. With respect to the relevant iRedMail components, I can say that Mailman 3 is perfectly happy with Postfix as MTA (it's the recommended configuration, although I use Exim4 for historical reasons), and I've been satisfied with a small-scale set of lists (about 10 active ones, with at most 20 subscribers total) using Apache+mod_swgi to host Postorius and HyperKitty. The problem would be if your friend (is that the Frank in the CC? hi, Frank!) really really wants to manage Mailman 3 through iRedAdmin -- that will get messy I suspect, and pragmatically speaking, we can't support it, we don't have the cycles. So he'd be on his own, especially since the iRedMail folks have their own bespoke mailing list manager. I would recommend avoiding iRedAdmin integration, and just using Postorius since the subscribers and non-site-admin moderators (if any) will need to use Postorius anyway. Ignoring the iRedAdmin issue, the absolute simplest is 1. Install any Linux distribution with a Docker package. 2. Install the distribution's Docker package. 3. Download and install Mailman Project's Mailman 3 container. 4. Upgrade the container manually (ie, download and reinstall) as appropriate. For reference, what I would recommend to my friends, who would give me hands-on access in emergencies: 1. Install the Debian distribution. (What I use.) 2. Pin the Mailman 3 packages to "experimental". The idea would be to get Mailman 3 upgrades as fast as possible, even at the risk of packaging issues. (My experience with default-to-experimental system for several years was that this happened at most once a year, and the three or four cases all got fixed within days.) 3. Install the Mailman 3 packages. 4. Adjust any dependencies that need non-"stable" versions. 5. Upgrade via apt or whatever occasionally. 6. When Mailman 3 is working well, downgrade the pins to a more stable level. Since you do have such a friend, there's probably a similar process that works for his distribution-of-choice. > The problem is that my MacOS users are getting tripped up by the > mangling, as it is hidden by the mail clients. I have instructed > them to remove previous recipients regularly from the list of such, > if they contain the ‘via list’ string. But they don’t read my > emails, and we see many embarrassing email ssent to the lists that > are meant for one-on-one communication. I guess we could provide a setting where reply-to goes *only* to author, instead of to author *and* list as we currently recommend. But that is going to make you (or list owners) the focus of user ire because their intended replies to list go only to author. What do you think? tl;dr The rest is me blowing off steam. :-) > The fact that the mangling will continue is a disappointment. It's a disappointment to the sane people at the IETF, too, including the rep from Yahoo!, who's a very smart lady (I may be biased, she gave me a kitten once. ;-) Yahoo! is violating the original concept (DMARC "p=reject" was supposed to be used *only* for "transactional" mail, i.e., direct private communication between a business and its clients), but I see her point: when you've had a hundred million or so address books hacked and sold to spammers, and the spammers are sending literally millions of "recommendation from a friend" spams per hour for days on end, you use the tools to hand. > I’m inclined to tell all my AOL and Yahoo users and others in the same > boat to find another email service. I know the feeling. I'm lucky in that respect: the Ministry of Education prohibits use of yahoo mailboxes at Japanese universities. (Which is a WTF of a different kind: yahoo.co.jp is a franchise, not controlled by yahoo.com, and doesn't use p=reject at least at the time MoE issued that policy.) Mail is just hard. It was designed for a "friendly network of users", not for today's rather hostile open Internet, and even if they had envisioned this in the 70s when the message format and SMTP mail transmission protocol were designed, the fundamental problem is that pretty much everyone has a genuine need, even if only occasional, to receive messages from untrusted and even unknown senders.

1 0

Setting up From: field as list address
by Steven Maddox Nov. 25, 2019

Nov. 25, 2019

Hi folks, I'm trying to configure our mailman3 lists (via postorious) in a way that'll mean they'll behave in the way way that I've witnessed on another 3rd party list (one running mailman2). This is where (when receiving a message from the list) the From: is the list itself, and the person who actually sent it bizarrely appears as a CC:, for example... From: Steven Madox via Shropshire LUG <shropshire(a)mailman.lug.org.uk> Subject: [Shropshire LUG] Whatever To: shropshire(a)mailman.lug.org.uk CC: s.maddox(a)lantizia.me.uk At the moment our settings are the default/recommended... I *was* just going to set munging to 'Reply goes to list' which would just set a 'Reply-To' header... until I realised that... a) that won't help Thunderbird users as it just ignores Reply-To if it came from a list b) doesn't fix the issue with people having their own SPF/DKIM set on their mail domains So ultimately I'm starting to see why this 3rd party mailing list (another linux user group, a neighbouring one just south of us) does it this way... if anyone knows the mailman3 equivalent setting? p.s. I've read both the mailman2 and 3 notes related to why munging is not recommended, but I'd still like to know how this is done - to keep our options open more than anything. -- Steven Maddox Lantizia

2 3

[Mailman-Users] Mailman 3 Ready?
by Stephen J. Turnbull Nov. 25, 2019

Nov. 25, 2019

Reply-To set to mailman-users(a)mailman3.org. Allan Hansen writes: > I need to upgrade from Mailman 2.1 - my hardware needs upgrading > (badly) and the address mangling is having my subscribers rip their > hair out. That's not going to go away. We have ARC support in Mailman 3, but (a) like most envelope manipulation, that should be done in boundary MTAs, not in Mailman, and (b) ARC implementation is not universal. *Very likely* some of your subscribers are going to lose mail if you depend on ARC, rather than munge from. > I need to get this done before they start on my already thinning > hair! I sympathize. I tell the little kids I meet that my hair grows out of the bottom of my face, not the top (it's very alliterative in Japanese[1], the kids frequently don't get it but the accompanying adults usually laugh). > I’m ready and eager to move on to MM3 on a Linux box. The obvious "turn-key" installation is to use the Docker containers, which Abhilash keeps fairly up-to-date. But see comment below about universal working solutions. Which distro do you have? Are you using the distro's packages of Mailman 3 (not yet a good idea, unfortunately), or installing from source? > I have looked into it a few times now and I keep running into the > same blocks. I don't see much moving either. I was hoping someone > (Mailman developing community) would come up with a better working > solution. It's email. There are no universal working solutions. > [Some third party wrote:] My concern is that the Mailman3 is not > ready. There are too many dead ends and undocumented stuff. Who is this guy and has he consulted us? I'd like to do an archive search if he's done so to see what the issues are. > For Mailman2 I have a working integration with iRedMail, that does > not seem to work with 3. What's iRedMail? How does it fit into the community your lists serve? > So, is MM3 ready for the big screen? Works for us, for values of us including python.org. > If so, is there some way/how/where/when that my friend can get help > helping me with the installation other than the published > installation docs, which did not work for us? mailman-users(a)mailman3.org is the Mailman 3 version of this list. If your friend is the type to get his hands dirty with code, and has the time for development activity, mailman-developers(a)python.org would also be useful. You might be better off getting bids from consultants. There's a page listing them on wiki.list.org. > I have looked for both free and commercial alternatives to MM, There are sites that support MM commercially. I think the prices are reasonable, of course YMMV on that. Again, there's a page for those services on wiki.list.org. Footnotes: [1] "hage dakara hige o" -- the vowels are pronounced as Spanish or Italian, the consonants as in English.

1 0

Create new list styles via Postorius
by Torge Riedel Nov. 23, 2019

Nov. 23, 2019

Dear all, I have found this documentation on list styles: https://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html Is there any way to create and configure list styles via Postorius web interface? Thanks in advance Torge

2 1

Advice
by jk＠ascii.com Nov. 20, 2019

Nov. 20, 2019

We are seeking a consultant to help migrate us from Mailman 2.1.9 to 3 > Mailing list (Core + Postorius) + web-forum (Hyperkitty). Any recommendations is appreciated - Jerry

3 2

Adding / manipulating users
by Seth Seeger Nov. 19, 2019

Nov. 19, 2019

Hello, Thank you for your help with the moderation status. My next question - I have two lists from Yahoo to import. I’ve migrated them through groups.io and have a convenient export. I now have all the data in formats I can handle. (json file for members, mbox for archives.) What’s the best way to import hundreds of users, setting their mail delivery status and moderation status at the same time? (There doesn’t seem to be a command line option for adding members anymore where you can also set their delivery status.) I’ve looked at the documentation, but couldn’t figure out what to do. Thanks, Seth

2 3

postorius ssl-certificates for virtual hosts
by Wolfgang Bock Nov. 18, 2019

Nov. 18, 2019

Hello, On my server are several virtual hosts running with different lists per host. The appropriate webaddress is in general: https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. My domains: [domain-1] starts with a b* [domain-2] starts with a s* [domain-3] starts with a t* If I use the webadress https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… and I do a click on the https-symbol in the address line of my browser I get the secury-information " every thing is ok" and the certificate-information is about the wildcard-certificate I just created for the right domain. Different result is for the webadress https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. In this case I get an information like "you are using a wrong certificate" clicking on the https-symbol references tot he certificate of [domain-1] I set in my apache2 configuration a symbolic link to apache.conf in the /etc/mailman3/directory and made this active. What did I wrong?? If I set use_https to yes in mailman.cfg I get on the website for all lists: postorius: Something went wrong Mailman REST API not available. Please start Mailman core. In the logs I found … mailman.log Nov 14 23:04:25 2019 (28584) command runner started. Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=0&page=1 HTTP/1.1" 200 90 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=10&page=1 HTTP/1.1" 200 606 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.1/domains HTTP/1.1" 200 1438 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - code 400, message Bad HTTP/0.9 request type ('\x16\x03\x01\x02\x00\x01\x00\x01ü\x03\x03\x00³m\x98¶\x02¨\\Å^\x11£ì{\x94«§*\x 9cÅýÎk\x9f¡ã\x89s/õë') Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "........ü...³m.¶.¨\Å^.£ì{.«§*.ÅýÎk.¡ã.s/õë .Ô$M...b¥øDR.Ï...G¹PpÖ.'W°û-Óìü¶.>......À,À0..Ì©Ì¨ÌªÀ+À/..À$À(.kÀ#À'.gÀ" 400 mailman-web.log ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API not available Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call response, content = Http().request(url, method, data_str, headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in _conn_request conn.connect() File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, in connect self.sock = self._context.wrap_socket(sock, server_hostname=self.host) File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket session=session File "/usr/lib/python3.7/ssl.py", line 853, in _create self.do_handshake() File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake self._sslobj.do_handshake() ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1056) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 706, in list_index choosable_domains = _get_choosable_domains(request) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 560, in _get_choosable_domains return [(d.mail_host, d.mail_host) for d in domains] File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 560, in <listcomp> return [(d.mail_host, d.mail_host) for d in domains] File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 121, in __getattr__ return self._get(name) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 87, in _get return self.rest_data.get(key) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 76, in rest_data response, content = self._connection.call(self._url) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call raise MailmanConnectionError('Could not connect to Mailman API') mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API [pid: 1405|app: 0|req: 963/963] 2a02:8108:483f:b9c0:94f1:d2bb:9642:b6d0 () {62 vars in 1310 bytes} 22:20:41 2019] GET /mailman3/postorius/lists/ => generated 3901 bytes in 89 msecs (HTTP/1.1 503) 5 headers in 180 bytes (1 switches on core 0)

2 6

[Django] ERROR (EXTERNAL IP): Internal Server Error:
by Wolfgang Bock Nov. 18, 2019

Nov. 18, 2019

Hello, I got an errormessage via mail to root@[domain-01]. The complete text is attached in a utf-8-text-file. In the lines ...6, 8, 12, 119, 138, 141, 149, 150, 151, 155, 161, 162, 165, 166, 169, 187, 247, 251, 321 ....you can find links to different domains anonymised as [domain-01], [domain-02], [domain-03], [domain-04]. I don't know how to solve this problem. Regards Wolfgang

2 2

Mailing lists sometimes do not honor moderation_action of non-members
by Alan So Nov. 14, 2019

Nov. 14, 2019

We notice that sometimes mailing lists do not honor moderation_action of non-members. Instead, it follows the default action of the lists. It looks like we can sometimes fix the issue by adding/removing the non-members or adding/removing them as owner in certain order but we are not sure about exactly what we have to do. So, it looks like that it is not caused by the list configuration. We have already verified from the web UI, mailman client and the DB table member that moderation_action of the corresponding non-members are set correctly. Any clues for us to provide further information to troubleshoot the issue and any recommended workaround to get around the issue? Thanks a lot.

3 14

Python error, debian package, again
by Lars Schimmer Nov. 6, 2019

Nov. 6, 2019

Hi! I did filed #248 in https://gitlab.com/mailman/hyperkitty/issues and tried to resolve this issue. Furst converted the database as noted in the ticket, no solution. Second search all unicode subject lines in DB for the specific mailinglist, and delete them all via hyperkitty web interface, no success, error still appears. As the error happens 10-12 time on strange times (6am 2:20 pm, 4:20pm), it does not look like a fixed cron job. Abhilash Raj (maxking) mentionend, it maybe a issue with mailman core trying to deliver the message to hyperkitty. But how can I remove those broken messages, or twitch hyperkitty to accept and discard them? Those 30-60 error messsages/day are really annoying and on the other side do not look fine for mailman3 to break at such a easy task. (could have discarded those messages, also). So, please, howto fix this? thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

2 3

When mass subscribing using format John Doe <john.doe@example.com>, "Members" show some with real name, others without.
by Henrik Rasmussen Oct. 30, 2019

Oct. 30, 2019

GNU Mailman 3.2.0 (La Villa Strangiato): A list administrator asked me why some people is subscribed with full name and some are not, when he is mass subscribing people using the format John Doe john.doe(a)example.com. He had experienced this a lot of times. I tested this several times on my test lists, and one member, who already had his name registrered in Account (Postorius top right), and thus also in Django, kept being subscribed without real name, while the others was subscribed with full name in Members -> Subscribers. It seems (I’m not certain about this) that the one’s without real name is the one’s already having an account and thus registred in Django (admin/auth/user/), while the ones subscribed with full name associated is the ones not having an account already. However, as soon as the member (the one with the account) went to Account and changed his real name, the name was immediately associated with the subscription in Members -> Subscribers. I expect this to be by design, but why isn’t the name associated with the subscription when mass subscribing in the first place, taken from the account? Henrik Rasmussen

2 1

High Server Load problem
by Brian Carpenter Oct. 30, 2019

Oct. 30, 2019

For about a week now, I am seeing very high server loads and it seems to have something to do with the following process hanging: uwsgi --ini /opt/mailman-web/uwsgi.ini I am using the docker version of Mailman. When this process hangs, the server load just goes sky high and both Postorius and Hyperkitty no longer responds. I don't have very many sites on this server and I am running about 30 lists. I really need some assistance here as this needs to be fixed. I am seeing nothing in the logs that is explaining why this process is hanging and why the server load goes through the roof. Running docker-compose restart mailman-web kills the hanged process and the server load goes down. Postorius and Hyperkitty starts responding again. This seems to happen once a day. Brian

2 4

Rendering HTML for moderation
by Gila Halpern Oct. 30, 2019

Oct. 30, 2019

Hi, new member here doing some research for my boss. Does Mailman 3 allow HTML rendering in the moderation queue, or only plain text? I'm asking because our list mod doesn't have time to check each image in a submission individually, so we currently don't allow images, but the boss wants to allow them.

2 1

Mangled digests on Mailman3
by Mark Dadgar Oct. 29, 2019

Oct. 29, 2019

So since I upgraded to Mailman3 recently, I’m getting reports of mangled digests even with with plaintext digests turned on. Running 3.2.1 from the ubuntu packages. This list was imported from mailman 2.1.x. Example below. Any thoughts on how to fix this? - Mark ----- mark(a)pdc-racing.net | 408-348-2878 From: tr*****-request(a)pdc-racing.net <mailto:trackjunkies-request@pdc-racing.net> Subject: tr***** Digest, Vol 267, Issue 464 Date: October 19, 2019 at 5:49:46 PM PDT To: tr*****(a)pdc-racing.net <mailto:trackjunkies@pdc-racing.net> Reply-To: tr*****(a)pdc-racing.net <mailto:trackjunkies@pdc-racing.net> Send tr***** mailing list submissions to tr*****(a)pdc-racing.net <mailto:trackjunkies@pdc-racing.net> To subscribe or unsubscribe via email, send a message with subject or body 'help' to tr*****-request(a)pdc-racing.net <mailto:trackjunkies-request@pdc-racing.net> You can reach the person managing the list at tr*****-owner(a)pdc-racing.net <mailto:trackjunkies-owner@pdc-racing.net> When replying, please edit your Subject line so it is more specific than "Re: Contents of tr***** digest..." Today's Topics: 1. Re: PGE phasing out EV-A (XXXXX) ---------------------------------------------------------------------- Date: Sun, 20 Oct 2019 00:49:38 +0000 From: XXXXX Subject: [PDC] Re: PGE phasing out EV-A To: tr***** - The Single Biggest Drag On US GDP <tr*****(a)pdc-racing.net <mailto:trackjunkies@pdc-racing.net>> Message-ID: <0bca2bfb8e294ea5b910d7ae6d2a698c(a)Progent.com <mailto:0bca2bfb8e294ea5b910d7ae6d2a698c@Progent.com>> Content-Type: multipart/related; boundary="_005_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_"; type="multipart/alternative" --_005_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_ Content-Type: multipart/alternative; boundary="_000_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_" --_000_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGVyZSBhcmUgdGhlIFNNVUQgcmF0ZXMuIFNvY2lhbGlzbSB3b3JrcyENCg0KVGltZS1vZi1EYXkg KDUtOCBwLm0uKSBSYXRlIGRldGFpbHMNCiBOb24tc3VtbWVyDQpPY3RvYmVyIDEgLSBNYXkgMzEN Ck9mZi1wZWFrDQpNaWRuaWdodCDigJMgNSBwLm0uDQokMC4wOTY5IGtXaA0KQWxsIGRheSB3ZWVr ZW5kcyBhbmQgaG9saWRheXMNClBlYWsNCjUgcC5tLiDigJMgOCBwLm0uDQokMC4xMzM4IGtXaA0K T2ZmLXBlYWsNCjggcC5tLiAtIG1pZG5pZ2h0DQokMC4wOTY5IGtXaA0KIFN1bW1lcg0KSnVuZSAx IC0gU2VwdGVtYmVyIDMwDQpPZmYtcGVhaw0KTWlkbmlnaHQg4oCTIG5vb24NCiQwLjExNjYga1do Etc.

2 1

Chinese characters in list name shows question mark (?)
by Franklin Weng Oct. 26, 2019

Oct. 26, 2019

Hi list, I set up a mailman3 server and built a few lists to test. When I set the list name using Chinese characters, the web site shows correctly. However in the subscribing welcome mail the list name was shown in question marks. Screenshot is here: https://nextcloud.slat.org/index.php/s/CxPjpYMbQzQ6444 The LANGUAGE_CODE settings.py (in Debian /etc/mailman3/mailman-web.py) is set to zh-tw , and USE_I18N and USE_L10N are all set to True. Is there any other setting I should look at? Thanks, Franklin

2 7

Search problem in 3.2.1?
by Mark Dadgar Oct. 23, 2019

Oct. 23, 2019

Anyone seen this before? This is the result of any search query I run. I installed ElasticSearch as the search engine yesterday and this is the result. It is still indexing (large archives). Mailman 3.2.1 from the debian packages in Ubuntu 19.10. - Mark ----- mark(a)pdc-racing.net | 408-348-2878 Begin forwarded message: From: root(a)pdc-racing.net Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/search Date: October 22, 2019 at 7:44:49 AM PDT To: mark(a)pdc-racing.net Internal Server Error: /mailman3/hyperkitty/search UnboundLocalError at /hyperkitty/search local variable 'search_exception' referenced before assignment Request Method: GET Request URL: https://mail.pdc-racing.net/mailman3/hyperkitty/search?q=Ken Django Version: 1.11.22 Python Executable: /usr/bin/uwsgi-core Python Version: 3.7.5 Python Path: ['.', '', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Tue, 22 Oct 2019 14:44:49 +0000 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', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/paginator.py" in count 79. return self.object_list.count() File "/usr/lib/python3/dist-packages/haystack/query.py" in count 522. return len(self) File "/usr/lib/python3/dist-packages/haystack/query.py" in __len__ 86. self._result_count = self.query.get_count() File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in get_count 619. self.run() File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in run 951. results = self.backend.search(final_query, **search_kwargs) File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in wrapper 33. return func(obj, query_string, *args, **kwargs) File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in search 524. _source=True) File "/usr/local/lib/python3.7/dist-packages/elasticsearch/client/utils.py" in _wrapped 84. return func(*args, params=params, **kwargs) During handling of the above exception (search() got an unexpected keyword argument 'doc_type'), another exception occurred: File "/usr/lib/python3/dist-packages/hyperkitty/views/search.py" in search 90. request.GET.get('count'), File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py" in paginate 72. objects = paginator.page(page_num) File "/usr/lib/python3/dist-packages/django/core/paginator.py" in page 57. number = self.validate_number(number) File "/usr/lib/python3/dist-packages/django/core/paginator.py" in validate_number 46. if number > self.num_pages: File "/usr/lib/python3/dist-packages/django/utils/functional.py" in __get__ 35. res = instance.__dict__[self.name] = self.func(instance) File "/usr/lib/python3/dist-packages/django/core/paginator.py" in num_pages 91. if self.count == 0 and not self.allow_empty_first_page: File "/usr/lib/python3/dist-packages/django/utils/functional.py" in __get__ 35. res = instance.__dict__[self.name] = self.func(instance) File "/usr/lib/python3/dist-packages/django/core/paginator.py" in count 84. return len(self.object_list) File "/usr/lib/python3/dist-packages/haystack/query.py" in __len__ 86. self._result_count = self.query.get_count() File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in get_count 619. self.run() File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in run 951. results = self.backend.search(final_query, **search_kwargs) File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in wrapper 33. return func(obj, query_string, *args, **kwargs) File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in search 524. _source=True) File "/usr/local/lib/python3.7/dist-packages/elasticsearch/client/utils.py" in _wrapped 84. return func(*args, params=params, **kwargs) During handling of the above exception (search() got an unexpected keyword argument 'doc_type'), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/search.py" in search 100. if not isinstance(e, search_exception): Exception Type: UnboundLocalError at /hyperkitty/search Exception Value: local variable 'search_exception' referenced before assignment Request information: USER: admin GET: q = 'Ken' POST: No POST data FILES: No FILES data

2 6

Domain Issue with MM3
by Liebeskind Uri (luri) Oct. 23, 2019

Oct. 23, 2019

Hi all, our University has various departments and research projects and teams. Each of them might want more than one mailing list. It would be straight forward to create mailing lists such as: <list-name>@lists.mydomain.ch Example: In this case "digital" is an entity / Project / Department marketing.digital(a)lists.zhaw.ch<mailto:marketing.digital@lists.zhaw.ch> newsletter.digital(a)lists.zhaw.ch<mailto:newsletter.digital@lists.zhaw.ch> research.digital(a)lists.zhaw.ch<mailto:research.digital@lists.zhaw.ch> Other Examples might be: help.health(a)lists.zhaw.ch newsletter.health(a)lists.zhaw.ch research.health(a)lists.zhaw.ch<mailto:research.health@lists.zhaw.ch> If entities have more than one mailing list, it is required to build a stronger "mailing list identity", it is required to let the "entity" be part of the domain name: marketing(a)digital.lists.zhaw.ch newsletter@digital@lists.zhaw.ch career(a)health.lists.zhaw.ch newsletter(a)health.lists.zhaw.ch career(a)ict.lists.zhaw.ch support(a)ict.lists.zhaw.ch The University of Zurich (uzh.ch) does this as well and it looks very reasonable and useful to me: https://lists.uzh.ch/sympa/ca/domains https://business.lists.uzh.ch/sympa https://dqbm.lists.uzh.ch/sympa https://chess.lists.uzh.ch/sympa I have setup this mailing list test(a)digital.lists.zhaw.ch<mailto:test@digital.lists.zhaw.ch> but subscribing failed. * Subscribing via the Mass Import Form failed with a Server Error message in the browser. * Subscribing via e-mail test-join(a)digital.lists.zhaw.ch<mailto:test-join@digital.lists.zhaw.ch> because no response came from MM3. The mail to join has been delivered properly to MM3 but MM3 has swallowed the mail w/o response or error message. There also has not been any pending subscription. 2019-10-23T19:51:33.678705+02:00 svma-s-01321 postfix/smtpd[98348]: connect from srv-mail-013.zhaw.ch[160.85.104.123] 2019-10-23T19:51:33.692258+02:00 svma-s-01321 postfix/smtpd[98348]: A8EFC3FA6A: client=srv-mail-013.zhaw.ch[160.85.104.123] 2019-10-23T19:51:33.693192+02:00 svma-s-01321 postfix/cleanup[98351]: A8EFC3FA6A: message-id=<eb90deb6-58af-a873-3382-c27ce6d05031(a)anydomain.org> 2019-10-23T19:51:33.704102+02:00 svma-s-01321 postfix/qmgr[90603]: A8EFC3FA6A: from=<name(a)anydomain.org>, size=5329, nrcpt=1 (queue active) 2019-10-23T19:51:33.704864+02:00 svma-s-01321 postfix/smtpd[98348]: disconnect from srv-mail-013.zhaw.ch[160.85.104.123] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 2019-10-23T19:51:33.763670+02:00 svma-s-01321 postfix/lmtp[98352]: A8EFC3FA6A: to=<test-join(a)digital.lists.zhaw.ch>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.08, delays=0.02/0.01/0/0.05, dsn=2.0.0, status=sent (250 Ok) 2019-10-23T19:51:33.764485+02:00 svma-s-01321 postfix/qmgr[90603]: A8EFC3FA6A: removed 2019-10-23T19:52:29.278529+02:00 svma-s-01321 postfix/smtpd[98348]: table hash:/var/lib/mailman3/data/postfix_lmtp(0,lock|fold_fix|utf8_request) has changed -- restarting 2019-10-23T19:52:29.286154+02:00 svma-s-01321 postfix/smtpd[98558]: connect from localhost[127.0.0.1] 2019-10-23T19:52:29.288612+02:00 svma-s-01321 postfix/cleanup[98351]: table hash:/var/lib/mailman3/data/postfix_domains(0,lock|utf8_request) has changed -- restarting 2019-10-23T19:52:29.292655+02:00 svma-s-01321 postfix/smtpd[98558]: 476AD3FA6A: client=localhost[127.0.0.1] 2019-10-23T19:52:29.293671+02:00 svma-s-01321 postfix/cleanup[98559]: 476AD3FA6A: message-id=<157185314763.94537.10517326910475727036(a)svma-s-01321.zhaw.ch> 2019-10-23T19:52:29.296393+02:00 svma-s-01321 postfix/qmgr[90603]: table hash:/var/lib/mailman3/data/postfix_domains(0,lock|utf8_request) has changed -- restarting 2019-10-23T19:52:29.298231+02:00 svma-s-01321 postfix/smtpd[98558]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 commands=4 I'd be grateful for a useful hint what is going wrong here? Kind regards, Uri Liebeskind -- ------------------------------------ Zurich University of Applied Sciences Information and Communication Technology Uri Liebeskind System Administrator Gertrudstrasse 15 Postfach 805 CH-8401 Winterthur Tel. +41 58 934 72 63 Fax. +41 58 935 72 63 http://www.zhaw.ch/en/ -------------------------------------

2 1

Issues installing postorius and hyperkitty
by thushantha.lakmal＠arm.com Oct. 23, 2019

Oct. 23, 2019

Hi All. Im trying to install the mailmain suite with the postorius and hyperkitty . Mailman installation completed successfully but for postorius and hyperkitty Im getting the following errors .. Please can someone help me .. For postorius (Using pip3 install postorius ) ERROR: django-mailman3 1.3.0 has requirement Django<2.2,>=1.11, but you'll have django 2.2.6 which is incompatible. For hyperkitty (Using pip3 install hyperkitty ) de41118f448bcb3b8df405c5228e1 Stored in directory: /root/.cache/pip/wheels/79/50/a5/9410f4b2e62e35c285de46ffa88c2562403cb576e1e7859d68 Building wheel for rcssmin (setup.py) ... error ERROR: Command errored out with exit status 1: command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-491rzr5s --python-tag cp36 cwd: /tmp/pip-install-563o314q/rcssmin/ Complete output (12 lines): running bdist_wheel running build running build_py creating build creating build/lib.linux-x86_64-3.6 copying ./rcssmin.py -> build/lib.linux-x86_64-3.6 running build_ext building '_rcssmin' extension creating build/temp.linux-x86_64-3.6 gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.6m -c rcssmin.c -o build/temp.linux-x86_64-3.6/rcssmin.o unable to execute 'gcc': No such file or directory error: command 'gcc' failed with exit status 1 ---------------------------------------- ERROR: Failed building wheel for rcssmin Running setup.py clean for rcssmin Successfully built robot-detection django-haystack Failed to build rcssmin Installing collected packages: rjsmin, django-appconf, rcssmin, django-compressor, robot-detection, django-haystack, djangorestframework, decorator, networkx, django-extensions, wcwidth, blessed, arrow, django-picklefield, django-q, hyperkitty Running setup.py install for rcssmin ... error ERROR: Command errored out with exit status 1: command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-6g8g9aoj/install-record.txt --single-version-externally-managed --compile cwd: /tmp/pip-install-563o314q/rcssmin/ Complete output (12 lines): running install running build running build_py creating build creating build/lib.linux-x86_64-3.6 copying ./rcssmin.py -> build/lib.linux-x86_64-3.6 running build_ext building '_rcssmin' extension creating build/temp.linux-x86_64-3.6 gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.6m -c rcssmin.c -o build/temp.linux-x86_64-3.6/rcssmin.o unable to execute 'gcc': No such file or directory error: command 'gcc' failed with exit status 1 ---------------------------------------- ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-6g8g9aoj/install-record.txt --single-version-externally-managed --compile Check the logs for full command output.

2 1

bouncing mail commands
by Liebeskind Uri (luri) Oct. 23, 2019

Oct. 23, 2019

Hi all, when a subscribtion confirmation is sent to MM it replies a bounce mail about unknown commands in the mail. This is very confusing for the users / subscribers and I'd like to disable this function. Actually our users do not need to send commands in the subject and in the body. So responding to words that are unknown commands is not helpful. Currently I have Postfix header and body checks in place that discard this messages from MM to avoid bothering our users. But how can MM3 be configured not to respond to unknown commands or not to parse the mail for commands at all? Thank you for your help and kind regards, Uri Liebeskind -- ------------------------------------ Zurich University of Applied Sciences Information and Communication Technology Uri Liebeskind System Administrator Gertrudstrasse 15 Postfach 805 CH-8401 Winterthur Tel. +41 58 934 72 63 Fax. +41 58 935 72 63 http://www.zhaw.ch/en/ -------------------------------------

2 1

why owner mails rerouted to list
by Tamas HOLCZER Oct. 23, 2019

Oct. 23, 2019

Hi All, we have moved to Mailman3 from Mailman2 recently, and have a quite strange problem: Every message sent to owners is forwarded to the lists instead of the owner's mail address. So for example if a non-member sends a message to MYLIST(a)MYDOMAIN.COM, then a notification appears on MYLIST (and all members receive it, the message also appears in the archive) instead of sending it to the private address of the owner set on the web interface. I found no obvious error either in mailman.log, smtp.log or the MTA's logs. This problem can cause a storm of mails as per default the owner is not allowed to send a message to a member-only list so each notifications generates a new notification. This storm is mitigated temporarily by accepting everything from the owner in a non-member setting, but it is only a workaround. I want mails sent to MYLIST-owner(a)MYDOMAIN.COM to be forwarded to the real owner instead of the list. The same is true for MYLIST-admin(a)MYDOMAIN.COM, and probably for the other administrative addresses. We are using GNU Mailman 3.2.1 (La Villa Strangiato) from the Debian Buster repo. As MTA we use exim4 (running on the same machine as Mailman), and have Amavisd on a separate machine for spam filtering. How can I test what happens to mails sent to the owner inside Mailman? Any help or tips on debugging this issue would be highly appreciated. Best regards, Tamas Here is an anonymized header for such a message: From MYLIST-bounces(a)MYDOMAIN.COM Mon Oct 21 21:13:59 2019 Return-path: <MYLIST-bounces(a)MYDOMAIN.COM> Envelope-to: MYADDRESS(a)MYDOMAIN.COM Delivery-date: Mon, 21 Oct 2019 21:13:59 +0200 Received: from [SPAMFILTER] (helo=localhost) by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) id 1iMd7u-0007pv-VR; Mon, 21 Oct 2019 21:13:59 +0200 X-Virus-Scanned: by amavis-dc Received: from MAILSERVER.MYDOMAIN.COM ([MAILSERVER-LOCAL-IP]) by localhost (spamfilter.MYDOMAIN.COM [SPAMFILTER]) (amavisd-new, port 10023) with ESMTP id Pe6CPG7d_0VR; Mon, 21 Oct 2019 21:13:57 +0200 (CEST) Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) id 1iMd7t-0007pn-Mu; Mon, 21 Oct 2019 21:13:57 +0200 Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) id 1iMd7r-0007pR-JZ for MYLIST-owner(a)MYDOMAIN.COM; Mon, 21 Oct 2019 21:13:55 +0200 From: MYLIST-owner(a)MYDOMAIN.COM To: MYLIST-owner(a)MYDOMAIN.COM MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1338746665924884909==" Message-ID: <157168523467.30989.13607822853875106726(a)MAILSERVER.MYDOMAIN.COM> Date: Mon, 21 Oct 2019 21:13:54 +0200 Precedence: bulk X-Mailman-Version: 3.2.1 Message-ID-Hash: UWYSMZDJO3ZXNBKY6GE6AS6FBLCZL6BG X-Message-ID-Hash: UWYSMZDJO3ZXNBKY6GE6AS6FBLCZL6BG X-MailFrom: MYLIST-bounces(a)MYDOMAIN.COM X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation Subject: [MYLIST] MYLIST(a)MYDOMAIN.COM post from ... requires approval List-Id: Name of the List <MYLIST.MYDOMAIN.COM> Archived-At: <https://MYDOMAIN.COM/hyperkitty/list/MYLIST@MYDOMAIN.COM/message/UWYSMZDJO3…> List-Archive: <https://MYDOMAIN.COM/hyperkitty/list/MYLIST@MYDOMAIN.COM/> List-Help: <mailto:MYLIST-request@MYDOMAIN.COM?subject=help> List-Post: <mailto:MYLIST@MYDOMAIN.COM> List-Subscribe: <mailto:MYLIST-join@MYDOMAIN.COM> List-Unsubscribe: <mailto:MYLIST-leave@MYDOMAIN.COM> --===============1338746665924884909== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit As list administrator, your authorization is requested for the following mailing list posting: List: MYLIST(a)MYDOMAIN.COM From: ... Subject: ... The message is being held because: The message is not from a list member At your convenience, visit your dashboard to approve or deny the request. ...

2 1

To what extent can mailman 3 handle images and html?
by Paul Arenson Oct. 23, 2019

Oct. 23, 2019

Hi The other day I attempted to send a message from my mail client (Apple computer, Mail program, html--well, what they call Rich Text). While a user was able to send a message previously that contained an image, I was unsuccessful. As well, links were weird. LINKS ===== Because My wordpress often has a Japanese URL and they can become very long, I tried both the URL as is and embedded (made a clickable html link). URL === So while I typed https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis.... It came out double as https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... (The full link was truncated with ... at the end, and the link appeared twice with the second instance preceded by "">") The embedded one did not come out embedded buy showed the text like this: Alternate link: 多摩川河川敷に男性の遺体、増水した川に流されたか <https://www.tokyoprogressive.org/%e5%a4%9a%e6%91%a9%e5%b7%9d%e6%b2%b3%e5%... QUESTION 1: Is there a preferred way to write links, or will there always be problems with the mail clients? (Even the web archive shows this problem though): https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… See the top item Homeless man drowns in river during Typhoon and what I mean. IMAGE No image appears though one was added inline. And, as I said, a user was previously able to add one. I do not know how she did it. I also posted it to my web site instead of the newsletter for unrelated reasons. But there was an image (Originally got a warning the message was held because the attachment or something). So are there guidelines one whether/how to attach an image so that it makes it? Thanks

4 7

Re: To what extent can mailman 3 handle images and html?
by tokyoprogressive＠mailbox.org Oct. 23, 2019

Oct. 23, 2019

Thank you, Mark. Yes. All solved and your explanation on how THIS list handles attachments also understood. Appreciate as always. Sent from my iPhone

1 0

LMTP on unix socket
by Hristo Venev Oct. 21, 2019

Oct. 21, 2019

How do I configure mailman to use a unix socket for lmtp connections? Setting [mta] incoming: mailman.mta.null.NullMTA lmtp_host: /path/to/socket does not work. Mailman still tries to create a TCP socket.

3 3

Receiving 8bit-clean mail
by Alyssa Ross Oct. 20, 2019

Oct. 20, 2019

A subscriber to a mailing list I administer has been sending 8bit UTF-8 encoded mail, with no further quoted-printable / base64 / etc. encoding. This is handled fine by my MTA and MUA, but Mailman seems to have trouble with it. When mail is sent out from Mailman, the « character is replaced by ??. Is this a bug, or is there just a configuration option or something I need to set? I couldn't find anything in the documentation.

3 3

Ubuntu package?
by Mark Dadgar Oct. 18, 2019

Oct. 18, 2019

Are the Ubuntu package maintainers on this list? Can you ping me directly if you are? Thanks. - Mark ----- mark(a)pdc-racing.net <mailto:mark@pdc-racing.net> | 408-348-2878

1 0

Re: [Mailman-i18n] Mailman 3 Internationalization setup
by Abhilash Raj Oct. 17, 2019

Oct. 17, 2019

On Thu, Oct 17, 2019, at 6:55 AM, Rémi Oudin wrote: > Hi! > > It seems that the projects are not public anymore. > Should we ask you to give us access for the translations? It should be, I haven't changed anything in past few days. What makes you think they aren't public? Are you not able to visit their page? Just as side note, the URL for Postorius is now changed to https://hosted.weblate.org/projects/gnu-mailman/postorius/ Everything else is same. > > Cheers, > -- > Guinness > > Attachments: > * signature.asc -- thanks, Abhilash Raj (maxking)

1 0

Converting discussion list to read-only list (settings)
by Paul Arenson Oct. 17, 2019

Oct. 17, 2019

I have found that my users in the discussion list are creating their own topics rather than using the existing ones, so decided to make it a read-only list and use WordPress moderated comments. Since I do not have the original settings for READ ONLY (this is a hosted version), I want to make sure that these are correct. Can someone comment. Thanks MOST IMPORTANT—> What setting makes it a discussion list as opposed to read only? ALTER MESSAGES ----------------------- Filter content Now YES Collapse Alternatives Now yes Convert html to plain text Now NO Anonymous NOW YES Include RFC2369 headers Now Yes Include the list post header Now Yes Reply Goes to List Now No munging Pipeline Default DMARC MITIFGATIONS ----------------------- Replace From with list address DMARC mitigate unconditionally Now NO MESSAGE ACCEPTANCE ----------------------- Require Explicit Destination Yes Administrivia YES Default action to take when a member posts to the list Hold for moderation Default action to take when a member posts to the list Hold for moderation OTHER? ------------- Thanks Paul Arenson

2 14

max_delivery_threads
by Sven Buesing Oct. 16, 2019

Oct. 16, 2019

Hi, we are currently running mailman version 3.3.0. We want to enable max_delivery_threads - we want to send personalized mails (To: ), and we hope that threading would speed things up - but it seems this option has no functionality despite being documented in the schema.cfg. Threading is compiled into python: >>> import sysconfig >>> print(sysconfig.get_config_vars('WITH_THREAD')) [1] Am I doing anything wrong or is the documentation simply wrong? This ist the mta-section of the mailman.cfg. [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver max_delivery_threads: 20 max_recipients: 500 lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: 127.0.0.1 smtp_port: 25 configuration: python:mailman.config.postfix Regards, Sven

2 2

Tune Mail Delivery
by Brian Carpenter Oct. 14, 2019

Oct. 14, 2019

Some ISPs require outgoing delivery to not exceed a certain threshold. With Mailman 2, we used the following: SMTP_MAX_RCPTS SMTP_MAX_SESSIONS_PER_CONNECTION Does Mailman 3 have an equivalent to the above 2 settings? Thank, Brian

2 1

Help with fresh debian install
by Mark Dadgar Oct. 11, 2019

Oct. 11, 2019

Mailman3-Users, First-time poster, long-time Mailman user (since August of 2002!). I brought up a fresh install of Mailman3 via the current Debian package alongside my current 2.1 setup (installed and updated from source since 2002) on Ubuntu 18.04 LTS. Importing lists from 2.1 has been a real problem. I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: — mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck Traceback (most recent call last): File "/usr/bin/mailman", line 11, in <module> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main initialize(config_path) File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 189, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 152, in initialize_2 mailman.core.logging.initialize(propagate_logs) File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 157, in initialize _init_logger(propagate, sub_name, log, logger_config) File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 110, in _init_logger handler = ReopenableFileHandler(sub_name, path_abs) File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 50, in __init__ self._stream = self._open() File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 53, in _open return codecs.open(self.filename, 'a', 'utf-8') File "/usr/lib/python3.6/codecs.py", line 897, in open file = builtins.open(filename, mode, buffering) PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' Error in atexit._run_exitfuncs: Traceback (most recent call last): File "/usr/lib/python3.6/logging/__init__.py", line 1945, in shutdown h.flush() File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 56, in flush if self._stream: AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' — If I run it as root, it runs for a long time but spews a HUGE stream of these errors to /var/log/mailman3/mailman.log: — Oct 03 17:08:48 2019 (19118) Skipping and preserving unparseable message: 1570147727.3029191+80f1cc4d18f54868ad6162e8e41e52567185e983 Oct 03 17:08:49 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' Oct 03 17:08:49 2019 (19118) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' Oct 03 17:08:49 2019 (19118) Skipping and preserving unparseable message: 1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c Oct 03 17:08:50 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147729.8732843+1cd24522f62dbd73c759a0f9a749a2ed63c91668.pck' Oct 03 17:08:50 2019 (19118) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147729.8732843+1cd24522f62dbd73c759a0f9a749a2ed63c91668.pck' Oct 03 17:08:50 2019 (19118) Skipping and preserving unparseable message: 1570147729.8732843+1cd24522f62dbd73c759a0f9a749a2ed63c91668 Oct 03 17:08:51 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147731.1456919+4354e647280c69f4dbfbd5a158b682fe3ed6cbcf.pck' Oct 03 17:08:51 2019 (19118) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147731.1456919+4354e647280c69f4dbfbd5a158b682fe3ed6cbcf.pck' Oct 03 17:08:51 2019 (19118) Skipping and preserving unparseable message: 1570147731.1456919+4354e647280c69f4dbfbd5a158b682fe3ed6cbcf Oct 03 17:08:53 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147732.4526153+f423b0ba2693b41ffc3f829da2290639634c349d.pck' Oct 03 17:08:53 2019 (19118) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147732.4526153+f423b0ba2693b41ffc3f829da2290639634c349d.pck' Oct 03 17:08:53 2019 (19118) Skipping and preserving unparseable message: 1570147732.4526153+f423b0ba2693b41ffc3f829da2290639634c349d — It also dumps some mail footer templates into the template directory that are owned by root, which seems … incorrect? Any thoughts on what’s going wrong here? Many thanks in advance! Really looking forward to having modern archives! - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 9

Show diplay_name in a list
by ruben＠bkonrad.de Oct. 10, 2019

Oct. 10, 2019

Hello, I'm trying to figure out how to show the display_name of a member in postorius in Members > Subscriber. I was trying to add {{ member.diplay_name }} in the template ${postorius}/templates/postorius/lists/members.html Here an abstract of where I inserted the code: [...] {% for member in members %} <tr> {% if role == 'subscriber' %} <td> <label class="checkbox-inline"> <input type="checkbox" class="member-checkbox" name="choices" id="id_choices_{{ forloop.counter0 }}" value="{{ member.email }}" /> {{ member.display_name }} <{{ member.email }}> </label> [...] I could not figure out why it wouldn't work. I'm running mailman3 Version 3.1.1-9 on an Ubuntu 18.04. Any idea what I was missing there? Thanks in advance for any help. - Ruben

4 4

Personalization issue when no To header?
by Alan So Oct. 8, 2019

Oct. 8, 2019

We have ported a number of lists from mailman 2 to mailman 3 earlier. We cannot find any personalization setting in the mailman 3 web UI or using the mailman client. It is fine as it is not essential. However, recently we notice an issue. As the lists in the mailman 2 probably have personalization turned on, it looks like that the setting are also migrated by using "mailman import21". Recently, some users start sending mail simply with Bcc without any addresses in the To header. We notice the following error: Oct 08 11:26:03 2019 (1832) Uncaught runner exception: 'to' Oct 08 11:26:03 2019 (1832) Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver refused = agent.deliver(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 163, in deliver callback(mlist, message_copy, msgdata_copy) File "/usr/local/lib/python3.6/site-packages/mailman/mta/personalized.py", line 58, in personalize_to msg.replace_header('To', formataddr((name, recipient))) File "/usr/lib64/python3.6/email/message.py", line 558, in replace_header raise KeyError(_name) KeyError: 'to' After tracing the source codes above, we suspect that the issue was caused by no To header due to personalization is turned on. Any quick suggestion of workarounds such as how to turn off personalization for all lists? We do not have much experiences with mailman shell. Thanks a lot.

1 0

Mailman 3 Internationalization setup
by Abhilash Raj Oct. 7, 2019

Oct. 7, 2019

Hi All, Mailman 3 is now setup for continuous internationalization. We are using Hosted Weblate[1], which is the hosted service for the Weblate project[2]. It is actually quite nice and I've been learning how to properly document a Django project from it's documentation. Which brings me to it's documentation. Weblate has great documentation for translators[2]. The UI pretty simple and should be easy to navigate around. We have setup the workflow in a way that each commit in Gitlab generates a webhook and updates Weblate. Weblate is then able to pull all the changes in real time. To pull translations back into Gitlab, I have a custom script running every night that pulls translations (as commits) and generates pull requests against the upstream repos. Weblate has the ability to automatically push the translations back, but for security reasons, I didn't want to give a 3rd party service direct push access to our repos. I've been working on a Patch to Weblate[3], which would allow it to send translations as Merge Requests (as compared to direct-push). After it is merged and deployed at hosted.weblate.org, I hope I can retire my custom script. We have setup the following projects: - Mailman Core (https://hosted.weblate.org/projects/gnu-mailman/mailman/) - Postorius* (https://hosted.weblate.org/projects/gnu-mailman/translations/) - Hyperkitty (https://hosted.weblate.org/projects/gnu-mailman/hyperkitty/) - Django-mailman3 (https://hosted.weblate.org/projects/gnu-mailman/django-mailman3/) There should be empty .po files generated for most languages supported by Django and Mailman Core. If there are any questions or bugs related to source strings, please send out an email to mailman-developers(a)python.org. The current translation %age is pretty low, hopefully we'll be ale to get it close to Mailman 2 sometime soon :) [1]: https://hosted.weblate.org/projects/gnu-mailman/ [2]: https://docs.weblate.org/en/latest/user/translating.html [3]: https://github.com/WeblateOrg/weblate/pull/3024 [*] Yeah, the URL for Postorius is a bit weird, because it was called "translations" before. At the time, I didn't know the difference between a project and a translation component in Weblate terminologies. And they don't give out permissions to change the URL, so we're maybe stuck with it. -- thanks, Abhilash Raj (maxking)

1 0

Mailman 3 installation documentation
by Abhilash Raj Oct. 7, 2019

Oct. 7, 2019

Hi All, I have been trying to work on revamping the documentation site we have at https://docs.mailman3.org. It is on https:// but I am not sure why the http->https redirect doesn't work in Readthedocs. I have set it to "serve always from https". Anyway, it might not look too different right now, but there are some small re-organizations. I have been learning some new ReST and Sphinx tricks and been trying to cross-reference and link various sections and settings. The docs site shows up Mailman's logo now (I didn't even know we could do that ;-). There is a place[1] for all supported Django settings that Postorius and Hyperkitty have. I am also planning to add some common Django settings that often people have to lookup and is not fun for people from non-python backgrounds. Hopefully, it will make lives easier for administrators. I have reverted my own stupid decision to use "sudo pip3 install" in the docs to instead use virtualenv. The installation docs are going to grow to be more comprehensive. I am also working on mailman-web project[3], which should simply installation process for all the web components using a single project and provide better guidance on Django's settings file management and howto run manage.py commands. I have added a `mailman-web` command, which, for those of you familiar with internal details of Django, is going to be our custom manage.py script. It sets up settings correctly and would hopefully reduce the pain of using `django-admin` and/or finding out the right path for `manage.py` script. It is still not ready for prime time, but it is usable. Early adopters can play with it if they like! I would really appreciate if people who have tried to manually install Mailman 3 in the past would share their experiences about what they think could be documented better. You can reply here or open an issue[2]. The user documentation are going to follow, hopefully soon :) [1]: https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… [2]: https://gitlab.com/mailman/mailman-suite-doc/issues [3]: https://gitlab.com/mailman/mailman-web -- thanks, Abhilash Raj (maxking)

2 1

confirm mail rejected
by Marc Sluiter Sept. 29, 2019

Sept. 29, 2019

Hi, im trying to setup mailman and have an issue: first my environment: - I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/ - I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/ I got almost everything working (with some configuration modifications, see other mail). The only thing which doesn’t work is conformation mails, they are rejected: In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp. Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps? For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/ Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)? Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?) Thanks and greetings, Marc

4 4

Cannot show archives
by Qiuhong.Su �K秋�t Sept. 27, 2019

Sept. 27, 2019

Hi all, After I setup mailman3 and run mailman-suite, I can do: 1. Register user 2. Login 3. Create new Domain 4. Create new List 5. Subscribe to the list When I try to send email to the list by run command: echo ��test email�� | mail �Cs ��test email�� test(a)example.com<mailto:test@example.com> User test can receive this email, but I cannot find it on Archives, and other members cannot receive this email too. Can anyone help me? Thank you! Regards, Qiuhong ************************************************************************* This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. [Delta Electronics, INC. China] *************************************************************************

4 4

Linking to a forum thread from a (news) website.
by Paul Arenson Sept. 25, 2019

Sept. 25, 2019

I have been struggling to get this right and I think I have finally done it. I have a website with many opinion and news articles. I have linked from the article to a pre-written thread, such as from here: EXAMPLE WEBSITE ARTICLE https://www.tokyoprogressive.org/remembering-the-tsushima-maru-disaster-75-… to EXAMPLE THREAD ON LIST Title: Remembering the Tsushima Maru Disaster 75 Years Later https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… PROBLEM The problem is that this does not show the subsequent comment that was added. And SHOW REPLIES BY DATE does not do it either. SOLUTION I figured out that all replies are listed under Re:, so if the first comment does not have the Re:, then it gets cut off. So if I click https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… you will see all the subsequent posts. Since I want to post a link BEFORE anyone starts replying, I have to make my first post in the thread titled Re: EXAMPLE OF NEW POSTING STYLE Make sure the thread has a Re: in it. (Actually I made a mistake and wrote Re; and it still worked.) https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… Or: https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… ----------------- QUESTION Am I correct that if I want to create a thread and link to it, but make sure the first note is included, I need to make the thread title: Re: Something? -----------------

2 2

Manual setup - permissions
by Tobias Hachmer Sept. 25, 2019

Sept. 25, 2019

Hello, I'm new to mailman3 and started to setup an instance from scratch per hand, but I'm struggeling running the peaces with the correct user/permissions. I can't find anything regarding running this and that with that user in the docs, so I have the following: virtualenv_dir: /opt/venvs/mailman3 Installed packages in venv: - "Django>=1.11" - "django-haystack" - "libsass" - "mailman==3.3.0" - "mailmanclient" - "mailman-hyperkitty==1.1.0" - "postorius==1.3.0" - "hyperkitty==1.3.0" - "whoosh" - "uwsgi" I have installed the core stuff in /opt/mailman3/core, all is owned by user+group "mailman3": root@host:/opt/mailman3# tree . ├── core │ ├── etc │ │ ├── hyperkitty.cfg │ │ ├── mailman.cfg │ │ └── uwsgi.ini │ ├── log │ │ ├── bounce.log │ │ ├── debug.log │ │ ├── mailman.log │ │ ├── plugins.log │ │ └── smtp.log │ └── var │ ├── archives │ │ └── hyperkitty │ │ └── spool │ │ ├── ... │ ├── cache │ ├── data │ │ ├── mailman.db │ │ ├── postfix_domains │ │ ├── postfix_domains.db │ │ ├── postfix_lmtp │ │ └── postfix_lmtp.db │ ├── lists │ │ └── admin.lists.... │ ├── locks │ ├── master.lck │ ├── master.lck|...|...|... │ ├── master.pid │ ├── message" │ │ ├── ... │ ├── queue │ │ ├── archive │ │ ├── bad │ │ ├── bounces │ │ ├── command │ │ ├── digest │ │ ├── in │ │ ├── nntp │ │ ├── out │ │ ├── pipeline │ │ ├── retry │ │ ├── shunt │ │ └── virgin │ └── templates The django project is installed in /opt/mailman3/web, all is owned by user+group "nginx": └── web └── project ├── db │ └── mailmansuite.db ├── emails ├── fulltext_index │ └── _MAIN_0.toc ├── logs │ ├── mailmansuite.log │ ├── uwsgi-error.log │ └── uwsgi.log ├── manage.py ├── __pycache__ │ ├── settings.cpython-35.pyc │ └── urls.cpython-35.pyc ├── run │ └── uwsgi.sock ├── settings.py ├── static ├── urls.py └── wsgi.py The mailman3 core ist running with user+group "mailman3". And the uwsgi service is running as root with drops privileges to user+group "nginx". Now, running the scheduled tasks (which run from user+group "nginx") for django I ran into permission problems, because the nginx user can't access/write to the needed files in /opt/mailman3/core/... If anyone of you is able to read ansible tasks, this is how I set this up via ansible: https://github.com/freifunk-mwu/ansible-ffmwu/blob/mail/roles/service-bundl… I would appreciate any hints how to run the different peaces of mailman3 with the correct user/groups/permissions. Thanks in advance, Tobias

4 4

Re: Issues with migrating from Mailman2 to Mailman 3
by Mark Sapiro Sept. 24, 2019

Sept. 24, 2019

On 9/23/19 12:03 AM, Paul Arenson wrote: > Thank you Mark. > > I found my solution. Simplifies things. People do not have to even > think about subscribing….. <snip> > How does that sound? OK -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Issues with migrating from Mailman2 to Mailman 3
by Uwe Grasshoff Sept. 23, 2019

Sept. 23, 2019

Hello all, I'm currently trying to convert a Debian based mailman2 installation to a docker based mailman3 installation. I successfully running the mailman-web and mailman-core containers together with the database container but I'm struggling with the import of the old mailing lists. In the core container I'm running this two commands for every mailing list: mailman create mailman(a)example.com mailman import21 mailman(a)example.com /oldmailman/lists/mailman/config.pck Then I'm switching over to the mailman-web container and running this two commands: python3.6 manage.py hyperkitty_import -l mailman(a)example.com /oldmailman/archives/private/mailman.mbox/mailman.mbox python3.6 manage.py update_index_one_list mailman(a)example.com I'm getting no errors or something else which could indicate a problem. After that I'm looking into the web interface http://example.com/postorius/lists/ There I can only see the public mailing list and the private ones are not shown there (as expected). When I then try to login with the List Manager credentials of the lists (from mailman2) I can't login in. So I thought maybe I have to "register" myself again to than get access to the list management. So I tried that but when I filled out the form and click "Register" I'm presented with an error page which titles "Serverfehler" (Server error in german) and the message "An error occurred while processing your request." When I then go back a step and try to register again I got the error message that the username is already taken. When I then try to login I can't login I always get the "An error occurred while processing your request." page. Does anyone have an idea what point I'm missing? -- With best Regards Uwe Grasshoff

2 2

Weird response to postings after subscriptions and accounts
by Paul Arenson Sept. 23, 2019

Sept. 23, 2019

I accidentally posted to a test account I had not actually used. Am reposting to my correct account. Sorry to the moderators. In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself? 1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… 2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below" 3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org 4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER? 5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows: "Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account. To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com" 6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by sending a message to....... I then get a notice: "Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member" 7) While if they send FROM THE interface it goes through. 8) What I am confused about. Signing up for an account should make them a member, right? Subscribing should make them a non member, no? But here it seems that both make them a non member. And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post. Before I can move my actual members over from another mailing list provider, I want to make sure what works and what doesn't. Thanks. PS I am running out of test accounts to use to test my own setup. Thanks. paul!!!Subscribe to this list still shows up at the bottom.

4 9

"Cannot connect to SMTP server localhost on port 25"
by Manos Pitsidianakis Sept. 22, 2019

Sept. 22, 2019

Hello, I've been getting "Cannot connect to SMTP server localhost on port 25" from runner "out" in mailman.log over some mails stuck in shunt queue, postfix logs show nothing when this happens, tcpdump on lo interface port 25 shows nothing. The log shows up when I start mailman, and then it seems not to show up again. This is my mailman.cfg's relevant parts: [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix I can do 'telnet localhost 25' just fine, including as mailman user. I can send and receive mail on my mail server. I tried making a test list and sent/received messages fine. smtp debug logs show "Using agent: <mailman.mta.deliver.Deliver object at 0x7fdd9793c940>" and "IndividualDelivery to: <email(a)address.tld>" on repeat, where the email address is one of the addresses of the shunted mails. version 3.2.2

2 12

User integration with Django application
by Victoriano Giralt Sept. 21, 2019

Sept. 21, 2019

Hi! Is there a way to integrate Mailman3 user database with an already existing Django application? And then, generate the list roster with a subset of those users. I've been scavenging the archives and failing to find an answer. Thanks! -- Victoriano Giralt CIO University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

2 1

Huge performance issue: Mailman doesn't (seem to) receive any mails.
by Henrik Rasmussen Sept. 20, 2019

Sept. 20, 2019

I am running maxking/mailman-*:0.2 (GNU Mailman 3.2.0 (La Villa Strangiato)). It looks like Mailman is not receiving (enough) mails, but are keps in the Postfix queue and I can't figure out why. I get a lot of "mail for [172.19.199.2]:8024 is using up 7841 of 7841 active queue entries" in the postfix container log (more postfix log at the buttom. I have restarted all Mailman containers this morning, but this didn't help anything. Last entries in Mailman's smtp.log were when we restarted the containers: Sep 18 08:30:02 2019 (36) Peer: ('172.19.199.1', 35454) Sep 18 08:30:02 2019 (36) ('172.19.199.1', 35454) handling connection Sep 18 08:30:13 2019 (36) ('172.19.199.1', 35454) EOF received Sep 18 08:30:13 2019 (36) Connection lost during _handle_client() Sep 18 08:30:13 2019 (36) ('172.19.199.1', 35454) connection lost Sep 18 08:30:18 2019 (36) Peer: ('172.19.199.1', 37164) Sep 18 08:30:18 2019 (36) ('172.19.199.1', 37164) handling connection Sep 18 08:30:20 2019 (36) ('172.19.199.1', 37164) EOF received Sep 18 08:30:20 2019 (36) Connection lost during _handle_client() Sep 18 08:30:20 2019 (36) ('172.19.199.1', 37164) connection lost The runners last ran at Sep 18 08:42:21 2019 The mailman.log updates constantly, but with "Sep 18 09:45:16 2019 (39) 172.19.199.3 - - "GET /3.0/users/" something something only or other http gets. A lot of them is 404 errors, but also a lot of "GET /3.0/lists/LISTNAME HTTP 200 responces, which should not be related. In "uwsgi-error.log" I get some tracebacks, but since I don't think should be related to incoming mails, I'll leave the traceback for now. Sep 18 10:07:47 postfix postfix/smtpd[5426]: connect from gateway[172.19.199.1] Sep 18 10:07:47 postfix postfix/smtpd[5426]: 45DAA7E97BE94: client=gateway[172.19.199.1] Sep 18 10:07:47 postfix postfix/cleanup[5429]: 45DAA7E97BE94: message-id=<A29DAD01610ED744A9D6F14880665668011C8A2C@P 1KITMBX01WC01.unicph.domain> Sep 18 10:07:47 postfix opendkim[19]: 45DAA7E97BE94: DKIM-Signature field added (s=default, d=listsgw.ku.dk) Sep 18 10:07:47 postfix postfix/smtpd[5426]: disconnect from gateway[172.19.199.1] Sep 18 10:07:47 postfix postfix/qmgr[98]: 45DAA7E97BE94: from=<sender(a)example.com>, size=7988, nrcpt=1 (queue active) Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: mail for [172.19.199.2]:8024 is using up 7844 of 7844 active queue entries Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: you may need to reduce lmtp connect and helo timeouts Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: so that Postfix quickly skips unavailable hosts Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: you may need to increase the main.cf minimal_backoff_time and maximal_backoff_time Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: so that Postfix wastes less time on undeliverable mail Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: you may need to increase the master.cf lmtp process limit Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: please avoid flushing the whole queue when you have Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: lots of deferred mail, that is bad for performance Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: to turn off these warnings specify: qmgr_clog_warn_time = 0 [SLIP] Sep 18 10:26:34 postfix postfix/qmgr[98]: B34C07E980CA3: from=<LISTNAME(a)lists.example.com>, size=1219, nrcpt=1 (queue active) Sep 18 10:26:34 postfix postfix/smtp[6559]: connect to sst-dk.mx1-dk.mailanyone.net[130.226.237.91]:25: Connection refused Sep 18 10:26:34 postfix postfix/smtp[6559]: connect to sst-dk.mx1-dk.mailanyone.net[::ffff:130.226.237.91]:25: Connection refused Sep 18 10:26:34 postfix postfix/smtp[6559]: connect to sst-dk.mx2-dk.mailanyone.net[::ffff:130.226.237.91]:25: Connection refused Sep 18 10:26:34 postfix postfix/smtp[6559]: connect to sst-dk.mx2-dk.mailanyone.net[130.226.237.91]:25: Connection refused Sep 18 10:26:34 postfix postfix/smtp[6559]: connect to sst-dk.mx3-dk.mailanyone.net[130.226.237.91]:25: Connection refused Sep 18 10:26:34 postfix postfix/smtp[6559]: B34C07E980CA3: to=<RECIPIENT(a)foo.bar>, relay=none, delay=420673, delays=420673/0.05/0.2/0, dsn=4.4.1, status=deferred (connect to sst-dk.mx3-dk.mailanyone.net[130.226.237.91]:25: Connection refused) / Henrik Rasmussen

3 10

My list has been switched from public to private archives, but they are still visible
by Paul Arenson Sept. 20, 2019

Sept. 20, 2019

Can anyone help with this? I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… Am I misunderstanding what a private archive is? Is something wrong with my setup (which is hosted)? Thank you.

4 8

Mailing List Description that can't be modified by list owners
by chilfer＠unr.edu Sept. 20, 2019

Sept. 20, 2019

Is there a way to create an additional mailing list field or lock down the current Description or Information fields so they are not modifiable by a list owner? The goal is to have a field that identifies the department or area a list belongs to so that it's easier to find if an owner leaves the organization and the owner needs to be updated on multiple lists.

2 1

Re: hosted signup is producing unexpected results
by tokyoprogressive＠mailbox.org Sept. 17, 2019

Sept. 17, 2019

I mistakenly posted twice. Please see: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Sent from my iPhone

1 0