- Mailman-users - lists.mailman3.org

performance report - mailman 3.3.1rc1 / postorius 1.3.1
by sunil soprey 26 May '20

26 May '20

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 24 May '20

24 May '20

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 24 May '20

24 May '20

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 22 May '20

22 May '20

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 22 May '20

22 May '20

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 21 May '20

21 May '20

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 20 May '20

20 May '20

(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 19 May '20

19 May '20

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 18 May '20

18 May '20

/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 16 May '20

16 May '20

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