- Mailman-users - lists.mailman3.org

Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)
by Wikinaut 02 Oct '23

02 Oct '23

After having changed and re-changed "only" the line in /etc/mailman3/mailman-web.py (which looks to be only a "blinder" and the real problem could be a different one) POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' the web access via Postorius is not working any more and throws "Error 500" My logfile /var/log/mailman3/web/mailman-web.log shows now File "/usr/share/mailman3-web/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.9/dist-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.9/dist-packages/django/core/management/__init__.py", line 420, in execute django.setup() File "/usr/local/lib/python3.9/dist-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/usr/local/lib/python3.9/dist-packages/django/apps/registry.py", line 116, in populate app_config.import_models() File "/usr/local/lib/python3.9/dist-packages/django/apps/config.py", line 269, in import_models self.models_module = import_module(models_module_name) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 680, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 790, in exec_module File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/django_q/models.py", line 12, in <module> from django_q.signing import SignedPackage File "/usr/lib/python3/dist-packages/django_q/signing.py", line 7, in <module> from django_q import core_signing as signing File "/usr/lib/python3/dist-packages/django_q/core_signing.py", line 9, in <module> from django.utils.encoding import force_bytes, force_str, force_text ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py) I already run pip install -U postorius to update that (looks okay to me): Requirement already satisfied: postorius in /usr/local/lib/python3.9/dist-packages (1.3.8) Collecting postorius Using cached postorius-1.3.8-py3-none-any.whl Downloading postorius-1.3.7.tar.gz (3.2 MB) Requirement already satisfied: django-mailman3>=1.3.8 in /usr/local/lib/python3.9/dist-packages (from postorius) (1.3.9) Requirement already satisfied: readme-renderer[md] in /usr/lib/python3/dist-packages (from postorius) (24.0) Requirement already satisfied: django<4.2,>=3.2 in /usr/local/lib/python3.9/dist-packages (from postorius) (4.1.9) Requirement already satisfied: mailmanclient>=3.3.3 in /usr/local/lib/python3.9/dist-packages (from postorius) (3.3.5) Requirement already satisfied: sqlparse>=0.2.2 in /usr/lib/python3/dist-packages (from django<4.2,>=3.2->postorius) (0.4.1) Requirement already satisfied: asgiref<4,>=3.5.2 in /usr/local/lib/python3.9/dist-packages (from django<4.2,>=3.2->postorius) (3.7.2) Requirement already satisfied: typing-extensions>=4 in /usr/local/lib/python3.9/dist-packages (from asgiref<4,>=3.5.2->django<4.2,>=3.2->postorius) (4.6.3) Requirement already satisfied: django-allauth in /usr/lib/python3/dist-packages (from django-mailman3>=1.3.8->postorius) (0.44.0) Requirement already satisfied: pytz in /usr/lib/python3/dist-packages (from django-mailman3>=1.3.8->postorius) (2021.1) Requirement already satisfied: django-gravatar2>=1.0.6 in /usr/lib/python3/dist-packages (from django-mailman3>=1.3.8->postorius) (1.4.4) Requirement already satisfied: requests in /usr/lib/python3/dist-packages (from mailmanclient>=3.3.3->postorius) (2.25.1) Requirement already satisfied: cmarkgfm>=0.2.0 in /usr/lib/python3/dist-packages (from readme-renderer[md]->postorius) (0.4.2) dpkg -l | grep django ii python3-django 2:2.2.28-1~deb11u2 all High-level Python web development framework ii python3-django-allauth 0.44.0+ds-1+deb11u1 all Django app for local and social authentication (Python 3 version) ii python3-django-appconf 1.0.3-1 all helper class handling configuration defaults of apps - Python 3.x ii python3-django-compressor 2.4-2 all Compresses linked, inline JS or CSS into single cached files - Python 3.x ii python3-django-extensions 3.0.3-3 all Useful extensions for Django projects (Python 3 version) ii python3-django-filters 2.4.0-1 all filter Django QuerySets based on user selections ii python3-django-gravatar2 1.4.4-2 all Python3 library that provides essential Gravatar support ii python3-django-guardian 2.0.0-2 all per object permissions of django for Python3 ii python3-django-haystack 3.0-1 all modular search for Django (Python version) ii python3-django-hyperkitty 1.3.4-4 all Web user interface to access GNU Mailman3 archives ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-django-picklefield 3.0.1-1 all Pickled object field for Django (Python3 version) ii python3-django-postorius 1.3.4-2+deb11u1 all Web user interface to access GNU Mailman3 ii python3-django-q 1.2.1-1 all Django multiprocessing distributed task queue (Python 3 version) ii python3-djangorestframework 3.12.1-1 all Web APIs for Django, made easy for Python3 debian 11 (bullseye) Looks to be a problem between django 4 and /usr/local/lib/python3.9/dist-packages/django/utils/encoding.py ? Please can anybody help?

4 8

Templates via Webinterface are i) not set, and ii) set templates (files) are not shown in the Webinterface
by Wikinaut 30 Sep '23

30 Sep '23

I use mailman3 since a while, for some of my lists I have been using - list:member:digest:footer.txt - list:member:regular:footer.txt When I go to "Vorlagen" (LC: DE) (templates) in the web interface, I do _not_ see these two templates! When I got o my newest mailing list and when I setup templates via the Webinterfaces, these are shown there, but are neither working nor seen as files. What's wrong here? Is that a problem of the localisation language (DE)? Bug, feature or misunderstanding of myself?

2 2

Is there a way of recording bounce messages?
by Andrew Hodgson 28 Sep '23

28 Sep '23

Hi. I recently had an incident of all gmail.com members being bounced off one email list (around 180 subscribers). The messages recording the bounce don't include the original DSN. Is there a way of getting the DSN recorded? I'm sure it will give me some nonsense Gmail refusal message but I would like to identify if messages are bouncing for specific users, or if I am harming my reputation by sending to disabled accounts etc. Thanks. Andrew.

5 17

Mailing list name with capital letters?
by mrl＠psfc.mit.edu 26 Sep '23

26 Sep '23

How can I create a mailing list with capital letters? Right now, only the first letter can be capitalized. Some of my mailing list names in mailman 2 had capital letters. When I migrated them to mailman 3, the capital letters remained. So it should be possible to create new ones? Thanks. - Mark

3 3

Mailman 3 - Header Filter
by Thomas Lehker 25 Sep '23

25 Sep '23

I am a Mailman neophyte and need help with filtering posts based on the subject field. We have a few list owners that want 'Out of Office' replies discarded. When using the below syntax in Postorius/Header filter the post is not discarded but ends up in 'Held Messages'. Is there any syntax I am missing or a setting in the lists that needs to be disabled/enabled to get these posts dropped? Any help is much appreciated. Header: ^subject: subject: subject Pattern: Automatic Reply 'Automatic Reply' "Automatic Reply" Action: Discard 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

Issues with @gmail.com addresses
by Mohsen Masoudfar 25 Sep '23

25 Sep '23

Hi, since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. I checked the logs and I see that the emails are going out: to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) But it seems the users are getting email delivered to them. I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. Is there any way to help this list members? Thanks

8 21

Strange password problem
by Eggert Ehmke 25 Sep '23

25 Sep '23

This happened several times recently with Postorius Version 1.3.8: -I try to log in as admin -rejected because of wrong password (password is stored in browser) -used forgotten password function -reset password to the stored value from browser -login works now. Works also when logged out/in again -however, the next day this behaviour repeats. Any hints?

6 22

how to administrate mailman3 in CLI ?
by testeur 23 Sep '23

23 Sep '23

Hello, I have installed mailman3 and i want to administrate it with rest api, i ve read https://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usi… and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… i tryied with mailman command, but it don't do some actions (eg. delete held messages...). i tryied mailman shell... i tryied with curl to manage it, i can see if there is a pending message with : curl --user restadmin:restpass http://localhost:8001/3.1/lists/ml@domain.tld/held/count|| python3 -m json.tool| but how to delete all held messages ? is it possible in one time ? And how to select a specific message to discard /accept / defer ? do i have to use a POST ? Regards, PatG

3 4

Message getting held due to max number of recipients and maximum message size
by Wong, Wesley 22 Sep '23

22 Sep '23

Hi all, I am running into an issue with messages getting held for a list with the following reasons: The message is being held because: Message has more than 10 recipients The message is larger than the 40 KB maximum size Either the message will get posted to the list, or you will receive notification of the moderator's decision. Currently, the settings are set to 0 for both settings on the list so I am not sure where mailman is getting the default settings. Is this default hard coded somewhere in the Mailman core? The version of Mailman running is 3.3.6. Any help for this issue is greatly appreciate. wesley Wesley Wong Senior Systems Engineer Anderson Computing & Information Services | ACIS 310-206-2571 [ucla-logo---new_smaller] ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image001.png Replaced multipart/alternative part with first alternative.

2 3

Hyperkitty
by Massimiliano Paragnani 21 Sep '23

21 Sep '23

I set up the mailman3 services and lists, and we can send mail to the list successfully. However in the Archive section I couldn't see anything. My configuration: ubuntu, milman core 3.2.2, postresql, postorius 1.2.4, hyperkitty 1.3.2 This is my mailman conf result: [antispam] header_checks: [antispam] jump_chain: hold [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive [archiver.mail_archive] clobber_date: maybe [archiver.mail_archive] clobber_skew: 1d [archiver.mail_archive] configuration: python:mailman.config.mail_archive [archiver.mail_archive] enable: no [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc [archiver.mhonarc] clobber_date: maybe [archiver.mhonarc] clobber_skew: 1d [archiver.mhonarc] configuration: python:mailman.config.mhonarc [archiver.mhonarc] enable: no [archiver.prototype] class: mailman.archiving.prototype.Prototype [archiver.prototype] clobber_date: maybe [archiver.prototype] clobber_skew: 1d [archiver.prototype] configuration: changeme [archiver.prototype] enable: no [bounces] register_bounces_every: 15m [database] class: mailman.database.postgresql.PostgreSQLDatabase [database] debug: no [database] url: postgres://mailman3:--------------@localhost/mailman3 [devmode] enabled: no [devmode] recipient: [devmode] testing: no [devmode] wait: 60s [digests] mime_digest_keep_headers: Date From To Cc Subject Message-ID Keywords In-Reply-To References Content-Type MIME-Version Content-Transfer-Encoding Precedence Reply-To Message List-Post [digests] plain_digest_keep_headers: Message Date From Subject To Cc Message-ID Keywords Content-Type [dmarc] cache_lifetime: 7d [dmarc] org_domain_data_url: https://publicsuffix.org/list/public_suffix_list.dat [dmarc] resolver_lifetime: 5s [dmarc] resolver_timeout: 3s [language.ar] charset: utf-8 [language.ar] description: Arabic [language.ar] enabled: yes [language.ast] charset: iso-8859-1 [language.ast] description: Asturian [language.ast] enabled: yes [language.ca] charset: utf-8 [language.ca] description: Catalan [language.ca] enabled: yes [language.cs] charset: iso-8859-2 [language.cs] description: Czech [language.cs] enabled: yes [language.da] charset: iso-8859-1 [language.da] description: Danish [language.da] enabled: yes [language.de] charset: utf-8 [language.de] description: German [language.de] enabled: yes [language.el] charset: iso-8859-7 [language.el] description: Greek [language.el] enabled: yes [language.es] charset: iso-8859-1 [language.es] description: Spanish [language.es] enabled: yes [language.et] charset: iso-8859-15 [language.et] description: Estonian [language.et] enabled: yes [language.eu] charset: iso-8859-15 [language.eu] description: Euskara [language.eu] enabled: yes [language.fi] charset: iso-8859-1 [language.fi] description: Finnish [language.fi] enabled: yes [language.fr] charset: iso-8859-1 [language.fr] description: French [language.fr] enabled: yes [language.gl] charset: utf-8 [language.gl] description: Galician [language.gl] enabled: yes [language.he] charset: utf-8 [language.he] description: Hebrew [language.he] enabled: yes [language.hr] charset: iso-8859-2 [language.hr] description: Croatian [language.hr] enabled: yes [language.hu] charset: iso-8859-2 [language.hu] description: Hungarian [language.hu] enabled: yes [language.ia] charset: iso-8859-15 [language.ia] description: Interlingua [language.ia] enabled: yes [language.it] charset: iso-8859-1 [language.it] description: Italian [language.it] enabled: yes [language.ja] charset: euc-jp [language.ja] description: Japanese [language.ja] enabled: yes [language.ko] charset: euc-kr [language.ko] description: Korean [language.ko] enabled: yes [language.lt] charset: iso-8859-13 [language.lt] description: Lithuanian [language.lt] enabled: yes [language.nl] charset: iso-8859-1 [language.nl] description: Dutch [language.nl] enabled: yes [language.no] charset: iso-8859-1 [language.no] description: Norwegian [language.no] enabled: yes [language.pl] charset: iso-8859-2 [language.pl] description: Polish [language.pl] enabled: yes [language.pt] charset: iso-8859-1 [language.pt] description: Protuguese [language.pt] enabled: yes [language.pt_BR] charset: iso-8859-1 [language.pt_BR] description: Protuguese (Brazil) [language.pt_BR] enabled: yes [language.ro] charset: iso-8859-2 [language.ro] description: Romanian [language.ro] enabled: yes [language.ru] charset: koi8-r [language.ru] description: Russian [language.ru] enabled: yes [language.sk] charset: utf-8 [language.sk] description: Slovak [language.sk] enabled: yes [language.sl] charset: iso-8859-2 [language.sl] description: Slovenian [language.sl] enabled: yes [language.sr] charset: utf-8 [language.sr] description: Serbian [language.sr] enabled: yes [language.sv] charset: iso-8859-1 [language.sv] description: Swedish [language.sv] enabled: yes [language.tr] charset: iso-8859-9 [language.tr] description: Turkish [language.tr] enabled: yes [language.uk] charset: utf-8 [language.uk] description: Ukrainian [language.uk] enabled: yes [language.vi] charset: utf-8 [language.vi] description: Vietnamese [language.vi] enabled: yes [language.zh_CN] charset: utf-8 [language.zh_CN] description: Chinese [language.zh_CN] enabled: yes [language.zh_TW] charset: utf-8 [language.zh_TW] description: Chinese (Taiwan) [language.zh_TW] enabled: yes [logging.archiver] datefmt: %b %d %H:%M:%S %Y [logging.archiver] format: %(asctime)s (%(process)d) %(message)s [logging.archiver] level: info [logging.archiver] path: mailman.log [logging.archiver] propagate: no [logging.bounce] datefmt: %b %d %H:%M:%S %Y [logging.bounce] format: %(asctime)s (%(process)d) %(message)s [logging.bounce] level: info [logging.bounce] path: bounce.log [logging.bounce] propagate: no [logging.config] datefmt: %b %d %H:%M:%S %Y [logging.config] format: %(asctime)s (%(process)d) %(message)s [logging.config] level: info [logging.config] path: mailman.log [logging.config] propagate: no [logging.database] datefmt: %b %d %H:%M:%S %Y [logging.database] format: %(asctime)s (%(process)d) %(message)s [logging.database] level: warn [logging.database] path: mailman.log [logging.database] propagate: no [logging.debug] datefmt: %b %d %H:%M:%S %Y [logging.debug] format: %(asctime)s (%(process)d) %(message)s [logging.debug] level: info [logging.debug] path: debug.log [logging.debug] propagate: no [logging.error] datefmt: %b %d %H:%M:%S %Y [logging.error] format: %(asctime)s (%(process)d) %(message)s [logging.error] level: info [logging.error] path: mailman.log [logging.error] propagate: no [logging.fromusenet] datefmt: %b %d %H:%M:%S %Y [logging.fromusenet] format: %(asctime)s (%(process)d) %(message)s [logging.fromusenet] level: info [logging.fromusenet] path: mailman.log [logging.fromusenet] propagate: no [logging.http] datefmt: %b %d %H:%M:%S %Y [logging.http] format: %(asctime)s (%(process)d) %(message)s [logging.http] level: info [logging.http] path: mailman.log [logging.http] propagate: no [logging.locks] datefmt: %b %d %H:%M:%S %Y [logging.locks] format: %(asctime)s (%(process)d) %(message)s [logging.locks] level: info [logging.locks] path: mailman.log [logging.locks] propagate: no [logging.mischief] datefmt: %b %d %H:%M:%S %Y [logging.mischief] format: %(asctime)s (%(process)d) %(message)s [logging.mischief] level: info [logging.mischief] path: mailman.log [logging.mischief] propagate: no [logging.plugins] datefmt: %b %d %H:%M:%S %Y [logging.plugins] format: %(asctime)s (%(process)d) %(message)s [logging.plugins] level: info [logging.plugins] path: plugins.log [logging.plugins] propagate: no [logging.root] datefmt: %b %d %H:%M:%S %Y [logging.root] format: %(asctime)s (%(process)d) %(message)s [logging.root] level: info [logging.root] path: mailman.log [logging.root] propagate: no [logging.runner] datefmt: %b %d %H:%M:%S %Y [logging.runner] format: %(asctime)s (%(process)d) %(message)s [logging.runner] level: info [logging.runner] path: mailman.log [logging.runner] propagate: no [logging.smtp] datefmt: %b %d %H:%M:%S %Y [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg [logging.smtp] format: %(asctime)s (%(process)d) %(message)s [logging.smtp] level: info [logging.smtp] path: smtp.log [logging.smtp] propagate: no [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures [logging.smtp] success: $msgid post to $listname from $sender, $size bytes [logging.subscribe] datefmt: %b %d %H:%M:%S %Y [logging.subscribe] format: %(asctime)s (%(process)d) %(message)s [logging.subscribe] level: info [logging.subscribe] path: mailman.log [logging.subscribe] propagate: no [logging.vette] datefmt: %b %d %H:%M:%S %Y [logging.vette] format: %(asctime)s (%(process)d) %(message)s [logging.vette] level: info [logging.vette] path: mailman.log [logging.vette] propagate: no [mailman] cache_life: 7d [mailman] default_language: en [mailman] email_commands_max_lines: 10 [mailman] filtered_messages_are_preservable: no [mailman] html_to_plain_text_command: /usr/bin/lynx -dump $filename [mailman] layout: debian [mailman] listname_chars: [-_.0-9a-z] [mailman] noreply_address: noreply [mailman] pending_request_life: 3d [mailman] post_hook: [mailman] pre_hook: [mailman] sender_headers: from from_ reply-to sender [mailman] site_owner: max.paragnani(a)gmail.com [mta] configuration: python:mailman.config.postfix [mta] delivery_retry_period: 5d [mta] incoming: mailman.mta.postfix.LMTP [mta] lmtp_host: 127.0.0.1 [mta] lmtp_port: 8024 [mta] max_autoresponses_per_day: 10 [mta] max_delivery_threads: 0 [mta] max_recipients: 500 [mta] max_sessions_per_connection: 0 [mta] outgoing: mailman.mta.deliver.deliver [mta] remove_dkim_headers: no [mta] smtp_host: localhost [mta] smtp_pass: [mta] smtp_port: 25 [mta] smtp_user: [mta] verp_confirm_format: $address+$cookie [mta] verp_confirm_regexp: ^(.*<)?(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$ [mta] verp_confirmations: no [mta] verp_delimiter: + [mta] verp_delivery_interval: 0 [mta] verp_format: ${bounces}+${local}=${domain} [mta] verp_personalized_deliveries: no [mta] verp_probe_format: $bounces+$token@$domain [mta] verp_probe_regexp: ^(?P<bounces>[^+]+?)\+(?P<token>[^@]+)@.*$ [mta] verp_probes: no [mta] verp_regexp: ^(?P<bounces>[^+]+?)\+(?P<local>[^=]+)=(?P<domain>[^@]+)@.*$ [nntp] host: [nntp] password: [nntp] port: [nntp] remove_headers: nntp-posting-host nntp-posting-date x-trace x-complaints-to xref date-received posted posting-version relay-version received [nntp] rewrite_duplicate_headers: To X-Original-To CC X-Original-CC Content-Transfer-Encoding X-Original-Content-Transfer-Encoding MIME-Version X-MIME-Version [nntp] user: [passwords] configuration: python:mailman.config.passlib [passwords] password_length: 8 [plugin.master] class: [plugin.master] component_package: [plugin.master] configuration: [plugin.master] enabled: no [shell] banner: Welcome to the GNU Mailman shell [shell] history_file: [shell] prompt: >>> [shell] use_ipython: no [styles] default: legacy-default [webservice] admin_pass: --------------------------------- [webservice] admin_user: restadmin [webservice] api_version: 3.1 [webservice] hostname: localhost [webservice] port: 8001 [webservice] show_tracebacks: yes [webservice] use_https: no

7 20

Re: Importing mbox files into archive defect with lines with From
by Alex Schuilenburg 21 Sep '23

21 Sep '23

Hi Stephen On 19/09/2023 19:59, Stephen J. Turnbull wrote: > Did you intend to send this to me only? Nope, apologies. I'm happy to add the list back in - I thought I hit reply-to-list. > Alex Schuilenburg writes: > > > Yes, I retested with from the git head as well. Same result. It > > sees the line > > > > From 1st April 2019, our turnover has exceeded the threshold for > > > > as the start of a new message and reports no anomolies although > > there is clearly one. > > If there is an empty line preceding that one, and the "F" is in the > first column (no marginal whitespace), that is considered correct > behavior for processing an mbox file. As an email separator agreed, provided the body has all "First " (preceded by a blank line and nothing preceding on the same line) suitably escaped. > If you don't like it, don't use the mbox format. The maildir > message-per-file format is widely supported, and if you want a > folder-per-file rather than message-per-file format, MMDF is fairly > widely supported, and does not suffer from the ambiguities of mbox. > All three (with variations) are supported by recent Python 3. Understood. My issue is the lists were imported from MM2.1 in 2020 into MM3.2.1 onto hyperkitty+mariadb/mysql. So the current installation has no mbox files - archives are stored in a mysql database. > > The old MM3 installation I am migrating away from is obviously > > broken in that its mbox archive when downloaded is not escaped, > > That's interesting. I presume that's because HyperKitty saves > messages in a database rather than as mbox files, and the old mbox > exporter just flattened and concatenated the messages. Or perhaps > that also uses mailbox.mbox and old enough versions of that didn't > From-stuff. Spot on. I have to move the lists onto a new Debian 12 server using the native mailman 3.3.8 & mailman-web 0+20200530-2 packages. I tried dropping in the old mailman3 database under the new software but that did not work. Instead I manually imported the old mailman3 data directly into the new mailman3 database as, after inspections, there were no new tables and only a couple of additional fields which have suitable defaults. So dumped the mailman3 data with mysqldump --no-create-info --no-create-db --disable-keys --complete-insert --ignore-table=mailman3.alembic_version mailman3 and simply imported the dump into the new schema. OK so far. The lists showed up in postorius, obviously without archives in hyperkitty. > The normal way to upgrade a HyperKitty archive is to do nothing, just > upgrade the software. I guess you moved to a new host and deleted the > database? The preferred way is to dump the database to SQL, and then > load it in to the new database directly rather than downloading the > mbox files and importing. No ambiguity and much faster. Thats what I thought initially, but that failed as per https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…. As my old installation appears to have the django_migrations table inconsistent with the state of the database, and Debian have been unresponsive so far. Unfortunately the same mailman3-style manual import of mailman3web from old mailman3web db into the new db was not possible. There were additional tables and fields that needed values rather than defaults. Instead I opted to download the mbox exports from the old installation via the web interface and import them into the new installation for expediency.This is where I was when I posted the message. However, the old installation's mbox archive export (from the database) was problematic (e.g. 5min timeout) but after getting around those issues I ended up with some broken mbox files (e.g. the "From 1st April ..." line within a message, resulting in hyperkitty_import failures). > > although I tested downloading this thread archive and it is clearly > > escaped. Unfortunately I cannot tell if hyperkitty_import works > > using the git head since I am restricted to using the version > > provided with Debian 12. > > In July it worked for me on a site with 5300 archived lists. I assume > some of them had From-stuffed lines. Can't be sure, most of the posts > are machine-generated, but lines beginning with "From " are pretty > common in natural English. I'd be surprised if there were not any. I have 2003 lists and several occurrences. > > > There are indeed two versions though of mailbox.py on the VM: > > > > /usr/lib/python3/dist-packages/mailman/utilities/mailbox.py: from > > mailman3 (3.3.8-2~deb12u1) > > /usr/lib/python3.11/mailbox.py from libpython3.11-stdlib (3.11.2-6) > > The first applies one small change to the second (a so-called > "monkey-patch") for use by Mailman core. It should only be visible > to Python by the name "mailman.utilities.mailbox". The HyperKitty > utilities import the name "mailbox". If overwriting the first with > the second changes HyperKitty's behavior, something is wrong with > sys.path. Then I guess that is the case in Debian 12. > > > the latter of which appears far more substantial , so I dropped > > that module over the former and reran hyperkitty_import over the > > '>' escaped mbox, and while it did import without error, it did > > leave the escape in place (i.e. the 'From ...' was quoted when > > viewed). > > This is considered correct behavior. It is not possible to determine > whether the escape was in the original, or added by a receiving MTA. > Better to leave it. I thought that ">From " would be escaped to ">>From ", and so on, so the escape could easily be reversed when imported. I tested exports from the mailman-users lists and lines beginning "From " (preceded by a blank line) are escaped to ">From ", so incorrectly figured this would be unescaped by hyperkitty_import. After all, I would expect that an export of the archive to mbox, followed by a delete of the archive, followed by a hyperkitty_import of the archive, should leave you at the same place. Not with ">From " escapes in the new archives. In fact I also had a number of messages with "Message-ID: <>" and worse: all messages with attachments had the text/plain content empty. So mbox exports from MM 3.2.1 on Debian 10 (using hyperkitty+mysql) are broken. > > > The unescaped mbox import died in the same way. > > As expected. > > > Anyhow, thanks for your suggestion. For now I can stick with a > > manual repair and spaced escape of From_. > > If the old database is still available, I recommend dumping that and > loading it into a fresh version of the DBMS. > ... Thanks for the pointer. As I had already done the same with mailman3, so repeated the excercise. The following dump and import worked. oldhost> mysqldump --no-create-info --no-create-db --disable-keys --complete-insert mailman3web > mailman3web.sql newhost> mysql MariaDB [(none]> use mailman3web MariaDB [mailman3web]> source mailman3web.sql Thanks again -- Alex

2 3

Can't send emails to list users
by Rob Passalacqua 19 Sep '23

19 Sep '23

I've looked on the forums and haven't found someone with the exact same issue as me. It appears that my mailman 3 server is either only sending to the first3 recipients on the list or only sending out mail to users that are members in Django because only 3 recipients are getting the emails. Here is my /var/log/mailman3/smtp.log: Sep 01 08:00:04 2023 (1405) <169357680279.2857929.16011221517221650936(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.028921127319335938 seconds Sep 01 08:00:04 2023 (1405) <169357680279.2857929.16011221517221650936(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1107 bytes Sep 01 08:00:04 2023 (1405) <169357680284.2857929.17642987556878027498(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.00876307487487793 seconds Sep 01 08:00:04 2023 (1405) <169357680284.2857929.17642987556878027498(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1384 bytes Sep 01 08:02:03 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.08111977577209473 seconds Sep 01 08:02:03 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> post to graduates(a)lists.mydomain.com from itroost(a)mydomain.com, 22320 bytes Sep 01 08:08:21 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.08126330375671387 seconds Sep 01 08:08:21 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from itroost(a)mydomain.com, 22320 bytes Sep 01 08:08:33 2023 (1405) <SJ0PR04MB7469F9DA4C471D4CF0AA8329C8E5A(a)SJ0PR04MB7469.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.19033193588256836 seconds Sep 01 08:08:33 2023 (1405) <SJ0PR04MB7469F9DA4C471D4CF0AA8329C8E5A(a)SJ0PR04MB7469.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from marcomm(a)mydomain.com, 627057 bytes Sep 08 13:16:05 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 08 13:16:05 2023 (1402) Peer: ('127.0.0.1', 39988) Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) handling connection Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'LHLO lists.mydomain.com' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'MAIL FROM:<radiga(a)mydomain.com>' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) sender: radiga(a)mydomain.com Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) recip: undergraduates(a)lists.mydomain.com Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'DATA' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'QUIT' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) connection lost Sep 08 13:16:05 2023 (1402) Connection lost during _handle_client() Sep 08 13:16:07 2023 (1405) <169420056594.1401.9589247638462690499(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005960226058959961 seconds Sep 08 13:16:07 2023 (1405) <169420056594.1401.9589247638462690499(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1151 bytes Sep 08 14:26:48 2023 (1405) <CYYPR04MB90325509F556F72D6E562F1CA2EDA(a)CYYPR04MB9032.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.11815094947814941 seconds Sep 08 14:26:48 2023 (1405) <CYYPR04MB90325509F556F72D6E562F1CA2EDA(a)CYYPR04MB9032.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from radiga(a)mydomain.com, 19719 bytes Sep 11 16:28:09 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 11 16:28:09 2023 (1402) Peer: ('127.0.0.1', 54070) Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) handling connection Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'LHLO lists.mydomain.com' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'MAIL FROM:<mbutterworth(a)mydomain.com>' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) sender: mbutterworth(a)mydomain.com Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'RCPT TO:<graduates(a)lists.mydomain.com>' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) recip: graduates(a)lists.mydomain.com Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) recip: undergraduates(a)lists.mydomain.com Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'DATA' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'QUIT' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) connection lost Sep 11 16:28:09 2023 (1402) Connection lost during _handle_client() Sep 11 16:28:12 2023 (1405) <169447129087.1401.7570255973486097010(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 1 recips, completed in 0.0067327022552490234 seconds Sep 11 16:28:12 2023 (1405) <169447129087.1401.7570255973486097010(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from graduates-bounces(a)lists.mydomain.com, 1125 bytes Sep 11 16:28:12 2023 (1405) <169447129099.1401.13948217098256502621(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005612611770629883 seconds Sep 11 16:28:12 2023 (1405) <169447129099.1401.13948217098256502621(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1225 bytes Sep 12 08:00:04 2023 (1405) <169452720292.3537648.2620214486815282831(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.027950286865234375 seconds Sep 12 08:00:04 2023 (1405) <169452720292.3537648.2620214486815282831(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1054 bytes Sep 12 08:00:04 2023 (1405) <169452720295.3537648.16444246393071130094(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.0057718753814697266 seconds Sep 12 08:00:04 2023 (1405) <169452720295.3537648.16444246393071130094(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1151 bytes Sep 12 08:33:17 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.08274292945861816 seconds Sep 12 08:33:17 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> post to graduates(a)lists.mydomain.com from mbutterworth(a)mydomain.com, 53024 bytes Sep 12 08:33:26 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.061426639556884766 seconds Sep 12 08:33:26 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from mbutterworth(a)mydomain.com, 53024 bytes Sep 12 13:19:19 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 12 13:19:19 2023 (1402) Peer: ('127.0.0.1', 54328) Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) handling connection Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'LHLO lists.mydomain.com' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'MAIL FROM:<oanderson(a)mydomain.com>' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) sender: oanderson(a)mydomain.com Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'RCPT TO:<graduates(a)lists.mydomain.com>' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) recip: graduates(a)lists.mydomain.com Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) recip: undergraduates(a)lists.mydomain.com Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'DATA' Sep 12 13:19:20 2023 (1402) ('127.0.0.1', 54328) Data: b'QUIT' Sep 12 13:19:20 2023 (1402) ('127.0.0.1', 54328) connection lost Sep 12 13:19:20 2023 (1402) Connection lost during _handle_client() Sep 12 13:19:22 2023 (1405) <169454636036.1401.8937840345817588576(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 1 recips, completed in 0.0059452056884765625 seconds Sep 12 13:19:22 2023 (1405) <169454636036.1401.8937840345817588576(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from graduates-bounces(a)lists.mydomain.com, 1152 bytes Sep 12 13:19:22 2023 (1405) <169454636048.1401.2318933518942482920(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005008220672607422 seconds Sep 12 13:19:22 2023 (1405) <169454636048.1401.2318933518942482920(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1251 bytes Sep 12 15:25:29 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 12 15:25:29 2023 (1402) Peer: ('127.0.0.1', 44946) Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) handling connection Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'LHLO lists.mydomain.com' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'MAIL FROM:<oanderson(a)mydomain.com>' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) sender: oanderson(a)mydomain.com Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) recip: undergraduates(a)lists.mydomain.com Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'DATA' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'QUIT' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) connection lost Sep 12 15:25:29 2023 (1402) Connection lost during _handle_client() Sep 12 15:25:30 2023 (1405) <169455392982.1401.10957221749647131956(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.006732940673828125 seconds Sep 12 15:25:30 2023 (1405) <169455392982.1401.10957221749647131956(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1237 bytes Sep 13 08:00:04 2023 (1405) <169461360294.3599633.12410089636004689205(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.027216196060180664 seconds Sep 13 08:00:04 2023 (1405) <169461360294.3599633.12410089636004689205(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1079 bytes Sep 13 08:00:04 2023 (1405) <169461360298.3599633.9616667478508973418(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.00615382194519043 seconds Sep 13 08:00:04 2023 (1405) <169461360298.3599633.9616667478508973418(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1377 bytes Sep 13 08:37:09 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.438995361328125 seconds Sep 13 08:37:09 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> post to graduates(a)lists.mydomain.com from oanderson(a)mydomain.com, 1787833 bytes Sep 13 08:37:37 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.41765809059143066 seconds Sep 13 08:37:37 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from oanderson(a)mydomain.com, 1787833 bytes Sep 13 08:37:37 2023 (1405) <BYAPR04MB581366BC29E904B4A7E7EFCCDBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.05196428298950195 seconds Sep 13 08:37:37 2023 (1405) <BYAPR04MB581366BC29E904B4A7E7EFCCDBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from oanderson(a)mydomain.com, 22280 bytes Sep 14 11:13:14 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 11:13:14 2023 (1402) Peer: ('127.0.0.1', 46146) Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) handling connection Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'LHLO lists.mydomain.com' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'MAIL FROM:<informationservices(a)mydomain.com>' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) sender: informationservices(a)mydomain.com Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) recip: undergraduates(a)lists.mydomain.com Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'DATA' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'QUIT' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) connection lost Sep 14 11:13:14 2023 (1402) Connection lost during _handle_client() Sep 14 11:13:16 2023 (1405) <169471159483.1401.16856017446433914677(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005692005157470703 seconds Sep 14 11:13:16 2023 (1405) <169471159483.1401.16856017446433914677(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1210 bytes Sep 14 11:15:53 2023 (1405) <SJ0PR04MB85671FB097F25CF9F4874740BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.08924412727355957 seconds Sep 14 11:15:53 2023 (1405) <SJ0PR04MB85671FB097F25CF9F4874740BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from informationservices(a)mydomain.com, 22049 bytes Sep 14 14:34:11 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 14:34:11 2023 (1402) Peer: ('127.0.0.1', 60848) Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) handling connection Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'LHLO lists.mydomain.com' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'MAIL FROM:<informationservices(a)mydomain.com>' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) sender: informationservices(a)mydomain.com Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'RCPT TO:<ug(a)lists.mydomain.com>' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) recip: ug(a)lists.mydomain.com Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'DATA' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'QUIT' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) connection lost Sep 14 14:34:11 2023 (1402) Connection lost during _handle_client() Sep 14 14:34:14 2023 (1405) <169472365226.1401.465743651937418379(a)lists.mydomain.com> smtp to ug(a)lists.mydomain.com for 1 recips, completed in 0.00711822509765625 seconds Sep 14 14:34:14 2023 (1405) <169472365226.1401.465743651937418379(a)lists.mydomain.com> post to ug(a)lists.mydomain.com from ug-bounces(a)lists.mydomain.com, 1153 bytes Sep 14 14:34:33 2023 (1405) <SJ0PR04MB856797E91A59977ABCF9BAB7BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> smtp to ug(a)lists.mydomain.com for 4 recips, completed in 0.054645538330078125 seconds Sep 14 14:34:33 2023 (1405) <SJ0PR04MB856797E91A59977ABCF9BAB7BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> post to ug(a)lists.mydomain.com from informationservices(a)mydomain.com, 21976 bytes Sep 14 16:36:56 2023 (1305) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 16:36:56 2023 (1305) Peer: ('127.0.0.1', 54478) Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) handling connection Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'LHLO lists.mydomain.com' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) sender: rpassalacqua(a)mydomain.com Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) recip: test(a)lists.mydomain.com Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'DATA' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'QUIT' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) connection lost Sep 14 16:36:56 2023 (1305) Connection lost during _handle_client() Sep 14 16:36:58 2023 (1307) <169473101747.1304.15129450588472089900(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.0060198307037353516 seconds Sep 14 16:36:58 2023 (1307) <169473101747.1304.15129450588472089900(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1067 bytes Sep 14 16:38:48 2023 (1307) <BY5PR04MB71216AD8880847E842960CB6B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.05848550796508789 seconds Sep 14 16:38:48 2023 (1307) <BY5PR04MB71216AD8880847E842960CB6B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8680 bytes Sep 14 17:39:38 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 17:39:38 2023 (4281) Peer: ('127.0.0.1', 38814) Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) handling connection Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'LHLO lists.mydomain.com' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) sender: rpassalacqua(a)mydomain.com Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) recip: test(a)lists.mydomain.com Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'DATA' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'QUIT' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) connection lost Sep 14 17:39:38 2023 (4281) Connection lost during _handle_client() Sep 14 17:39:40 2023 (4283) <169473477870.4280.4174702240504737654(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005831241607666016 seconds Sep 14 17:39:40 2023 (4283) <169473477870.4280.4174702240504737654(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1085 bytes Sep 14 17:42:59 2023 (4283) <BY5PR04MB71215FF54B65F1D74C4567C0B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.06569862365722656 seconds Sep 14 17:42:59 2023 (4283) <BY5PR04MB71215FF54B65F1D74C4567C0B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 32685 bytes Sep 14 18:03:41 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 18:03:41 2023 (4281) Peer: ('127.0.0.1', 42054) Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) handling connection Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'LHLO lists.mydomain.com' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) sender: rpassalacqua(a)mydomain.com Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) recip: test(a)lists.mydomain.com Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'DATA' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'QUIT' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) connection lost Sep 14 18:03:41 2023 (4281) Connection lost during _handle_client() Sep 14 18:03:42 2023 (4283) <169473622130.4280.7069249432915457814(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.006022214889526367 seconds Sep 14 18:03:42 2023 (4283) <169473622130.4280.7069249432915457814(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1065 bytes Sep 14 18:07:57 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 18:07:57 2023 (4281) Peer: ('127.0.0.1', 50610) Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) handling connection Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'LHLO lists.mydomain.com' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) sender: rpassalacqua(a)mydomain.com Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) recip: test(a)lists.mydomain.com Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'DATA' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'QUIT' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) connection lost Sep 14 18:07:57 2023 (4281) Connection lost during _handle_client() Sep 14 18:07:58 2023 (4283) <169473647867.4280.14938940229014329856(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.0055654048919677734 seconds Sep 14 18:07:58 2023 (4283) <169473647867.4280.14938940229014329856(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1098 bytes Sep 14 18:10:17 2023 (4283) <BY5PR04MB71217ABD906F6FE7AFD2B4B9B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.06551766395568848 seconds Sep 14 18:10:17 2023 (4283) <BY5PR04MB71217ABD906F6FE7AFD2B4B9B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8688 bytes Sep 14 18:10:20 2023 (4283) <BY5PR04MB7121FAB23617A4597304E327B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.03918266296386719 seconds Sep 14 18:10:20 2023 (4283) <BY5PR04MB7121FAB23617A4597304E327B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8880 bytes Sep 15 09:16:03 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 15 09:16:03 2023 (4281) Peer: ('127.0.0.1', 38006) Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) handling connection Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'LHLO lists.mydomain.com' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) sender: rpassalacqua(a)mydomain.com Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) recip: test(a)lists.mydomain.com Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'DATA' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'QUIT' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) connection lost Sep 15 09:16:03 2023 (4281) Connection lost during _handle_client() Sep 15 09:16:05 2023 (4283) <169479096385.4280.8198285364938859931(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005726337432861328 seconds Sep 15 09:16:05 2023 (4283) <169479096385.4280.8198285364938859931(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1069 bytes Sep 15 09:16:54 2023 (4283) <BY5PR04MB71219485E3D6DBF7FFEF45E5B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.04341244697570801 seconds Sep 15 09:16:54 2023 (4283) <BY5PR04MB71219485E3D6DBF7FFEF45E5B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 9719 bytes Sep 15 11:12:26 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 15 11:12:26 2023 (4281) Peer: ('127.0.0.1', 59844) Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) handling connection Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'LHLO lists.mydomain.com' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) sender: rpassalacqua(a)mydomain.com Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) recip: test(a)lists.mydomain.com Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'DATA' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'QUIT' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) connection lost Sep 15 11:12:26 2023 (4281) Connection lost during _handle_client() Sep 15 11:12:28 2023 (4283) <169479794718.4280.8209850830279553803(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005163669586181641 seconds Sep 15 11:12:28 2023 (4283) <169479794718.4280.8209850830279553803(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1098 bytes Sep 15 11:12:49 2023 (4283) <BY5PR04MB71214E309721B3CC9F3072F9B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.0408024787902832 seconds Sep 15 11:12:49 2023 (4283) <BY5PR04MB71214E309721B3CC9F3072F9B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8817 bytes Sep 18 16:51:02 2023 (1286) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 18 16:51:02 2023 (1286) Peer: ('127.0.0.1', 56034) Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) handling connection Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'LHLO lists.mydomain.com' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) sender: rpassalacqua(a)mydomain.com Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) recip: test(a)lists.mydomain.com Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'DATA' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'QUIT' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) connection lost Sep 18 16:51:02 2023 (1286) Connection lost during _handle_client() Sep 18 16:51:03 2023 (1288) <169507746274.1285.2209553928985210953(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005767107009887695 seconds Sep 18 16:51:03 2023 (1288) <169507746274.1285.2209553928985210953(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1075 bytes Sep 18 16:58:09 2023 (1288) <BY5PR04MB7121D7152C07846F0FCFB100B3FBA(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.07815432548522949 seconds Sep 18 16:58:09 2023 (1288) <BY5PR04MB7121D7152C07846F0FCFB100B3FBA(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8756 bytes Sep 19 08:49:33 2023 (1286) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 19 08:49:33 2023 (1286) Peer: ('127.0.0.1', 59616) Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) handling connection Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'LHLO lists.mydomain.com' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) sender: rpassalacqua(a)mydomain.com Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) recip: test(a)lists.mydomain.com Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'DATA' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'QUIT' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) connection lost Sep 19 08:49:33 2023 (1286) Connection lost during _handle_client() Sep 19 08:49:36 2023 (1288) <169513497462.1285.8696625500767060363(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.007772684097290039 seconds Sep 19 08:49:36 2023 (1288) <169513497462.1285.8696625500767060363(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1076 bytes Sep 19 08:50:23 2023 (1288) <BY5PR04MB7121991E697D92F88D586AFFB3FAA(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.04478025436401367 seconds Sep 19 08:50:23 2023 (1288) <BY5PR04MB7121991E697D92F88D586AFFB3FAA(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8828 bytes

3 4

Importing mbox files into archive defect with lines with From
by andrew.bernard＠gmail.com 19 Sep '23

19 Sep '23

A curious problem, but seems to be well defined. I am importing mbox format files with 25 years worth of archives in 250 files from a Listserv list into hyperkitty. All is going swimmingly, except I get lots of partial emails with sender of None put into the current month, with text that has clearly been truncated. As I look at each one, I see that the line in the imported text is immediately after a line starting with 'From'. Clearly, 'From:' is an RCS-82 header, but 'From ' is not, and yet there is much evidence here that this is messing up the import. Is this a known bug? If not, how do I report it?

8 15

Modify approval email
by pau.baiges＠csuc.cat 19 Sep '23

19 Sep '23

Good morning, Is there a way to modify the email that is sent by default to list owners when a non-list member sends email to the list? Basically the default email that is sent is this: ________________________________________________________ As list administrator, your authorization is requested for the following mailing list posting: List: lis1(a)llistes.csuc.cat From: jim(a)csuc.cat Subject: test The message is being held because: El missatge no és d'un membre de la llista At your convenience, visit your dashboard to approve or deny the request. _____________________________________________________________________ We would like to add the link to the page to accept the email from the list itself. I think I remember that in the old mailman it could be done Thanks!

4 4

I'm seeing a lot of database locked errors
by bryan.kartzman＠yu.edu 19 Sep '23

19 Sep '23

We switched the mailman database from sqlite to postgresql a while back to minimize any database locking but I'm seeing a lot of errors for the django sqlite database. Is it possible to move that to postgres as well? 16:18:39 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: database is locked The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:39 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: database is locked The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:39 [Q] INFO Process-1:4 processing [compute_thread_positions] 16:18:39 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: database is locked The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:39 [Q] INFO Processed [compute_thread_positions] 16:18:44 [Q] INFO Process-1:2 processing [compute_thread_positions] 16:18:44 [Q] INFO Processed [compute_thread_positions] 16:18:44 [Q] INFO Process-1:1 processing [compute_thread_positions] 16:18:44 [Q] INFO Processed [compute_thread_positions] 16:18:44 [Q] INFO Process-1:3 processing [compute_thread_positions] 16:18:44 [Q] INFO Process-1:4 processing [compute_thread_positions] 16:18:44 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: database is locked The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:44 [Q] INFO Processed [compute_thread_positions] 16:18:49 [Q] INFO Process-1:2 processing [compute_thread_positions] 16:18:49 [Q] INFO Process-1:1 processing [compute_thread_positions] 16:18:49 [Q] INFO Process-1:3 processing [compute_thread_positions] 16:18:49 [Q] INFO Process-1:4 processing [compute_thread_positions] 16:18:49 [Q] INFO Process-1:2 processing [compute_thread_positions] 16:18:49 [Q] INFO Process-1:1 processing [compute_thread_positions] 16:18:49 [Q] INFO Processed [compute_thread_positions] 16:18:49 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: database is locked The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:49 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: database is locked The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:49 [Q] INFO Processed [compute_thread_positions] 16:18:49 [Q] INFO Processed [compute_thread_positions] 16:18:49 [Q] INFO Processed [compute_thread_positions] 16:19:39 [Q] INFO Process-1:4 processing [compute_thread_positions] 16:19:39 [Q] INFO Process-1:3 processing [compute_thread_positions] 16:19:39 [Q] INFO Process-1:1 processing [compute_thread_positions] 16:19:39 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: database is locked The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked

2 14

LDAP user email verification
by Tony Deshields 15 Sep '23

15 Sep '23

I'm running the docker-mailman setup with LDAP integrated. My users that authenticate against LDAP are still required to verify their email address however, I do not want this functionality. I was looking for guidance on possibly configuring it so my LDAP users do not have to verify their email address.

3 3

Restore/export existing Mailman lists + hyperkitty archives on a new server
by Kimmo L 14 Sep '23

14 Sep '23

Hello! My plan is to install fresh Mailman3 host, which means that i need to migrate/transfer my existing mailman mailing lists + hyperkitty archives to new host. Unfortunately i didnt find any good documentation about this. I tried myself to export and import mailmanweb/mailman databases (from old PostgreSQL to new PostgreSQL) and recreate indexes(mailman-web update_index). Now i can see and search hyperkitty archives, but if try to open one of the mailing list, i get error - HTTP Error 500: {"title": "500 Internal Server Error"} So im pretty sure, that I'm gonna have to transport some more stuff over, which I have no idea. Maybe existing users and user rights. If its not a big trouble, can someone kindly share, what exactly should i need to export/import and what would be the right steps/commands/moves. Br, Kimmo

4 52

Strange issue with bounce processing
by Brian Carpenter 13 Sep '23

13 Sep '23

Dear List, First of all Merry Christmas to those of you that are observing it. I have an issue on one of my Mailman 3 servers. The bounce runner is not running, even after restarting mailman core. All the other runners are working fine. Here is the problem, after restarting it, a number of messages show up in queue/bounces from a single list. However the bounce runner is still not running. So I remove these messages from queue/bounces folder and restart mailman core. The same messages show up from the same single list again in queue/bounces. In the var/logs/bounce.log file, addresses from this list are being logged as being removed after starting mailman core. They correlate with the messages showing up in queue/bounces. I assume these "cached" bounces are what is interfering with the running of the bounce runner. I don't see anything in the mailman or mailmansuite log that would explain this behavior. How can I fix this? Thank you for any assistance. -- Brian Carpenter Harmonylists.com Emwd.com

3 6

Question about "envelope-from" header
by Stephen Daniel 13 Sep '23

13 Sep '23

Mailman Gurus -- I run a small mailman3 implementation in a VM inside Google's cloud. The same VM runs both mailman3 and postfix. Because outbound SMTP is blocked by Google, my postfix relays outbound mail through smtp-relay.gmail.com, using credentials from my google workspace account. Works pretty well. For reasons unrelated to my mailing lists, I'd like to have the same VM provide a couple of mail aliases. Mail that comes in to " alias1(a)mydomain.com" should be relayed to "random1(a)somedomain.com". I am trying to do this by setting up virtual aliases in postfix, as per http://www.postfix.org/virtual.5.html. This works except that smtp-relay.gmail.com rejects the forwarded message because of "invalid credentials". I believe that email going out through smtp-relay.gmail.com can only come from a small set of previously authorized domains, and a random person who sends to "alias1(a)mydomain.com" is unlikely to be on that list. I think I could fix this by having postfix edit the "envelope-from" header as it relays the mail, so that the "envelope-from" header contains something like "admin(a)mydomain.com". Not sure, but I think so. My question is this: If I edit the envelope-from header in my outbound emails to say "admin(a)mydomain.com" am I going to break my email lists? Will bounce processing still work? Will replies to the list still work? Thanks! -- Stephen Daniel

3 2

Mailman messages are getting a TAG in some email clients.....how????
by bob B 13 Sep '23

13 Sep '23

So I know about the setting "Anonymous list" but regardless of that setting some email clients put the list name in [] when it displays messages in your inbox. Does anyone know how email clients are doing this? I have users who email clients do not do this, and was wondering if it is a setting in their client or just not possible. Here is a link to an image showing the tag for a list called TEST6 https://imgur.com/a/7VyJtsD

3 3

How to let mailman log every single email that it sends out?
by Mohsen Masoudfar 10 Sep '23

10 Sep '23

I'm curious about the configuration required to have Mailman record logs for every individual email it sends. I see that it sends to the entire list, but I'm interested in obtaining log entries for each email sent to every individual subscriber on the list. How can I access this information? Is it a postfix setting, or a Mailman3 setting? I have checked /var/log/mail.log and all the logs under /var/log/Mailman3/* Mailman is running on Ubuntu 18.3 Thank you! Mohsen

4 5

Issue with Docker Postfix and Mailman3 Configuration
by recida8902＠picvw.com 09 Sep '23

09 Sep '23

Dear Support Team, I am writing to seek assistance with an issue I am facing while configuring Docker Postfix with Docker Mailman3. I have successfully set up the configuration, and I can send emails without any problems. However, I am encountering an issue where incoming emails are not being received by the Mailman application. When I send an email from my configured email address, it is successfully delivered to the intended recipients. However, when someone else sends an email to the same address, it does not reach the Mailman application, and no error messages are generated. I have already tried the following troubleshooting steps: 1. Checked the Mailman container logs: I reviewed the logs using the docker logs command, but I did not find any error messages or warnings related to the incoming email issue. 2. Verified the Mailman installation: I ensured that Mailman is correctly installed and configured according to the provided documentation. All dependencies are met, and the outgoing email functionality is working as expected. 3. Checked the Mailman configuration: I reviewed the configuration files of Mailman and ensured that all necessary settings are properly configured. However, I couldn't identify any specific variables or options related to incoming email handling. Despite these efforts, I am still unable to receive incoming emails in the Mailman application. I would greatly appreciate any guidance or assistance you can provide to help resolve this issue. Please let me know if there is any additional information or logs that would be helpful for troubleshooting. Thank you in advance for your time and support.

2 1

social login added, but can't connect new login to existing users
by Jörg Schulz 06 Sep '23

06 Sep '23

after lots of research in this list, we managed to add a keycloak login to mailman3. MAILMAN_WEB_SOCIAL_AUTH = ["allauth.socialaccount.providers.keycloak"] # OIDC_CREATE_USER = False SOCIALACCOUNT_PROVIDERS = { 'keycloak': { 'KEYCLOAK_URL': 'https://keycloak.my.domain', 'KEYCLOAK_REALM': 'nct' # 'SCOPE': ['profile', 'email', 'preferred_username'], } } and some entries in https://mailman.my.domain/admin/socialaccount/socialapp This works perfectly for non-existing users/emails. They are created and they are able to subscribe to lists. But, when a user already exists, this does not work; the user gets a password reset email like "...an account using that email address already exists. In case you have forgotten about this, please use the password forgotten procedure to recover your account:..." Which kind of setting/tweak is needed to associate social login accounts to existing mail addresses?

4 4

Postorius no connection to REST API
by rrosner5＠gmail.com 05 Sep '23

05 Sep '23

Hello, I've seen some similar problems, but have not yet found anything that would work for me. I just installed Mailman3-full from debian stable repository (Mailman 3.2.1 to be precise). Mailman itself is working, also are all mailing lists imported from Mailman 2.1. But I just can not get the web interface of Postorius to work. I did manage to get it running through apache2 after I figured out what I had to remove from the old site config and replace it with the stuff in the automatically created config. Upon loading the site, I was able to log in and verify the mail address, but it kept showing that it wasn't able to connect to the REST API. I double and triple checked, that mailman-web.py and mailman-hyperkitty.cfg contain the same API key (api_key in hyperkitty and SECRET_KEY and MAILMAN_ARCHIVER_KEY in mailman web), but that didn't help. I also saw a recommendation, that it can cause problems, when the API key uses symbols like / so I switched it to _ in all three places, but that didn't help. The configuration for mailman, mailman-web and hyperkitty all are set to using https, switching them to http doesn't solve any of the problems. Meanwhile, the site only shows "Internal Server Error" even though I did not change anything. But probably not that relevant while it can't be used either way. What I can provide on logs: /usr/share/mailman3-web/manage.py mmclient Python 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> client.system 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 1049, in connect raise socket_err File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1010, in connect sock.connect((self.host, self.port)) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<console>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 74, in system return self._connection.call('system/versions')[1] 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 From /var/log/mailman3/mailman.log of the last restart: Aug 08 15:28:56 2021 (5322) in runner caught SIGTERM. Stopping. Aug 08 15:28:56 2021 (5322) in runner exiting. Aug 08 15:28:57 2021 (5322) in runner caught SIGTERM. Stopping. Aug 08 15:28:57 2021 (5321) command runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5321) command runner exiting. Aug 08 15:28:57 2021 (5320) bounces runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5320) bounces runner exiting. Aug 08 15:28:57 2021 (5319) archive runner caught SIGTERM. Stopping. Aug 08 15:28:57 2021 (5323) lmtp runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5323) lmtp runner exiting. Aug 08 15:28:58 2021 (5319) archive runner exiting. Aug 08 15:28:57 2021 (5329) virgin runner caught SIGTERM. Stopping. Aug 08 15:28:57 2021 (5330) digest runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5330) digest runner exiting. Aug 08 15:28:58 2021 (5329) virgin runner exiting. Aug 08 15:28:58 2021 (5324) nntp runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5318) Master watcher caught SIGTERM. Exiting. Aug 08 15:28:59 2021 (5318) Master watcher caught SIGTERM. Exiting. Aug 08 15:28:59 2021 (5323) lmtp runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5324) nntp runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5320) bounces runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5329) virgin runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5324) nntp runner exiting. Aug 08 15:28:59 2021 (5326) pipeline runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5319) archive runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5330) digest runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5325) out runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5328) retry runner caught SIGTERM. Stopping. Aug 08 15:29:00 2021 (5327) rest runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5327) rest runner caught SIGTERM. Stopping. Aug 08 15:29:01 2021 (5327) rest runner caught SIGTERM. Stopping. Aug 08 15:29:01 2021 (5325) out runner exiting. Aug 08 15:29:03 2021 (5326) pipeline runner exiting. Aug 08 15:29:03 2021 (5327) rest runner exiting. Aug 08 15:29:11 2021 (5328) retry runner exiting. Aug 08 15:29:48 2021 (5318) Master stopped Aug 08 15:30:30 2021 (5545) Master started Aug 08 15:30:34 2021 (5546) archive runner started. Aug 08 15:30:34 2021 (5549) in runner started. Aug 08 15:30:34 2021 (5550) lmtp runner started. Aug 08 15:30:34 2021 (5554) rest runner started. Aug 08 15:30:35 2021 (5553) pipeline runner started. Aug 08 15:30:35 2021 (5552) out runner started. Aug 08 15:30:36 2021 (5551) nntp runner started. Aug 08 15:30:36 2021 (5547) bounces runner started. Aug 08 15:30:36 2021 (5556) virgin runner started. So everything seems to be starting smoothly. An excerpt from /var/log/mailman3/web/mailman-web.log: Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) 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 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 728, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/usr/share/mailman3-web/settings.py", line 486, in <module> from settings_local import * File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 724, in exec_module File "<frozen importlib._bootstrap_external>", line 859, in get_code File "<frozen importlib._bootstrap_external>", line 916, in get_data PermissionError: [Errno 13] Permission denied: '/usr/share/mailman3-web/settings_local.py' [uwsgi-daemons] throttling "python3 manage.py qcluster" for 25 seconds not sure where the Permission denied comes from/what permissions should be. /usr/share/mailman3-web/settings_local.py is a symlink owned by root to /etc/mailman3/mailman-web.py owned by list:list with 640 permission. The apache2 error log contains nothing from the last restart of mailman3 and mailman3-web and trying to load the web page, the only interesting lines to the end of the log are [Sun Aug 08 14:40:33.642119 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed [Sun Aug 08 14:40:33.644627 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11893] AH10101: failed to make connection to backend: httpd-UDS:0 [Sun Aug 08 14:54:22.555229 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed [Sun Aug 08 14:54:22.555293 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11913] AH10101: failed to make connection to backend: httpd-UDS:0 [Sun Aug 08 14:58:24.376278 2021] [mpm_event:notice] [pid 2247:tid 140583610946688] AH00492: caught SIGWINCH, shutting down gracefully [Sun Aug 08 14:58:34.534966 2021] [mpm_event:notice] [pid 3696:tid 140070763447424] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 Python/3.7 configured -- resuming normal operations [Sun Aug 08 14:58:34.535159 2021] [core:notice] [pid 3696:tid 140070763447424] AH00094: Command line: '/usr/sbin/apache2'

7 31

Postfix-Fehler mit mailman-web
by Jens Günther 04 Sep '23

04 Sep '23

Hello, I installed mailman with Docker already a while ago, now running v0.4.5 with: Mailman Core-Version 3.3.8 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.10.9 Postorius Version 1.3.8 Already a while I get this type of error: 2023-08-26T08:21:59.517986+02:00 postfix/smtpd[2843414]: connect from unknown[192.168.176.6] 2023-08-26T08:21:59.522238+02:00 postfix/smtpd[2843414]: NOQUEUE: reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host rejected: cannot find your hostname, [192.168.176.6]; from=<$admin(a)mydomain.de> to=<$recipient> proto=ESMTP helo=<mailman-web> 2023-08-26T08:21:59.575145+02:00 postfix/smtpd[2843422]: connect from unknown[192.168.176.6] 2023-08-26T08:21:59.581227+02:00 postfix/smtpd[2843422]: NOQUEUE: reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host rejected: cannot find your hostname, [192.168.176.6]; from=<root(a)$mailman.mydomain.de> to=<root@localhost> proto=ESMTP helo=<mailman-web> 2023-08-26T08:21:59.581548+02:00 postfix/smtpd[2843422]: disconnect from unknown[192.168.176.6] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 Where - $admin(a)mydomain.de is set in MAILMAN_ADMIN_EMAIL (mm-web) and as site_owner in mailman-extra.cfg (mm-core) and as DEFAULT_FROM_EMAIL in settings_local.py (mm-web) - $mailman.mydomain.de is set in SERVE_FROM_DOMAIN (mm-web) For me it seems, that mm-web-container is trying to send mail, but don't know why and which ... I can't reproduce it. Does anybody have a clue on wehere I can have a look what happens ... and how to change it? Thank you, Jens.

3 8

Mailman REST API not available. Please start Mailman core.
by joseverde＠gmail.com 04 Sep '23

04 Sep '23

Okay, so I got the webservice of Mailman3 up and running, but when I go to mailman3/postorius/lists/, I get the following error: Something went wrong Mailman REST API not available. Please start Mailman core. When I logged in to the admin user, it threw a server 500 error, but I could refresh and see myself logged in. If I try to go to lists or mailman settings, however, I get the error above.

4 15

How to debug DMARC check?
by Gilles Filippini 03 Sep '23

03 Sep '23

Hi, I've been running a dockerized mailman3 server for several years with DMARC mitigation set to conditional. I use the 0.4 version of the mailman3 docker images. Recently I had to update my network configuration to prevent spammers using IPv6 to circumvent the no-relay configuration of my exim4 server. Previously, I had both exim4 and mailman3 on the same docker bridge 172.19.0.0/16 and exim4 was configured to relay email from this network only. There was no problem regarding DMARC mitigation : most of the emails didn't need to be altered. Now I have added an internal docker network 172.29.0.0/16 and configured exim4 to relay from this internal network only. Since this network is not accessible from the host, IPv6 spammers are blocked (*). But since this modification mailman alters every emails with DMARC mitigation. Any hint how to debug this issue? Thanks in advance, _g. (*) With IPv6 incoming connexions mailman docker replaces the client address with the IPv4 address of the host one the bridge network: 172.19.0.1.

2 4

Add date stamps to django (I think) logfiles?
by kjohnson＠eclypse.org 01 Sep '23

01 Sep '23

The webserver and archive part of mailman writes some logfiles on my system with entries like: 17:19:05 [Q] INFO Process-1 guarding cluster twenty-pluto-arizona-pasta 17:19:05 [Q] INFO Process-1:4 pushing tasks at 2831 17:19:05 [Q] INFO Q Cluster twenty-pluto-arizona-pasta running. These seem to match this format in settings.py: 'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s' except that I would expect asctime to have a date attached. A pointer to relevant documentation would be very much appreciated. Thanks. Ken

3 2

Installing Mailman3 on Debian Bullseye
by Franklin Weng 30 Aug '23

30 Aug '23

Hi, After several times attempts I finally successfully build a (reliable enough) mailman3 instance on Debian. I had a blog article describing how I did it. Maybe there were something you find it ridiculous, but they are all what I found important and may not be shown in the current documents. https://blogs.slat.org/node/1012 Hope this helps. Franklin

6 9

log rotation in maxking-docker-version
by Jens Günther 27 Aug '23

27 Aug '23

Hey there, while checking some logs I was realising that there is no log rotation and some of them piled up to 5GB over the past year(s). Does anybody know how to activate it (if it's possible) or ... Ok, I found a clue and it's still open :-) https://github.com/maxking/docker-mailman/issues/535 -> does anybody have a different approach? Regards, Jens.

2 3

Can't start mailman after reboot.
by mrl＠psfc.mit.edu 24 Aug '23

24 Aug '23

I have successful rebooted my computer server several times, and mailman has always started without a problem Now mailman won't start. See below. I tried to see if it was a problem with mysql. But I can successfully connect to the sql server using the mailman username and password, from the command line. What else can I try??? Thanks. - Mark Aug 24 12:52:17 psfcmail2 systemd[1]: Starting GNU Mailing List Manager... Aug 24 12:52:18 psfcmail2 mailman[28151]: Traceback (most recent call last): Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/bin/mailman", line 8, in <module> Aug 24 12:52:18 psfcmail2 mailman[28151]: sys.exit(main()) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1130, in __call__ Aug 24 12:52:18 psfcmail2 mailman[28151]: return self.main(*args, **kwargs) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1055, in main Aug 24 12:52:18 psfcmail2 mailman[28151]: rv = self.invoke(ctx) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/bin/mailman.py", line 69, in invoke Aug 24 12:52:18 psfcmail2 mailman[28151]: return super().invoke(ctx) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1657, in invoke Aug 24 12:52:18 psfcmail2 mailman[28151]: return _process_result(sub_ctx.command.invoke(sub_ctx)) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1404, in invoke Aug 24 12:52:18 psfcmail2 mailman[28151]: return ctx.invoke(self.callback, **ctx.params) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/core.py", line 760, in invoke Aug 24 12:52:18 psfcmail2 mailman[28151]: return __callback(*args, **kwargs) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func Aug 24 12:52:18 psfcmail2 mailman[28151]: return f(get_current_context(), *args, **kwargs) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/commands/cli_control.py", line 91, in start Aug 24 12:52:18 psfcmail2 mailman[28151]: status, lock = master_state() Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/bin/master.py", line 104, in master_state Aug 24 12:52:18 psfcmail2 mailman[28151]: os.kill(pid, 0) Aug 24 12:52:18 psfcmail2 mailman[28151]: PermissionError: [Errno 1] Operation not permitted Aug 24 12:52:19 psfcmail2 mariadbd[22160]: 2023-08-24 12:52:19 3191 [Warning] Aborted connection 3191 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets)

2 3

Only allow users to subscribe from certain domains
by bob B 23 Aug '23

23 Aug '23

Does Mailman have anyway to just allow users to subscribe themselves to a list from certain domains... ie any user from test.com or test2.com I do not believe this exists, but have a list manger who is asking. I feel they will have to either, approve all requests, or have a web frontend built that could filter that out and then send the subscribe commands in the backend. Thanks

2 2

applying patch 1130
by David Newman 22 Aug '23

22 Aug '23

Please forgive a dumb question from a non-programmer: How to apply the !1130.diff patch to a venv installation? https://gitlab.com/mailman/mailman/-/merge_requests/1130 I am looking to upgrade Debian 11 to 12. The latter uses python3.11, which no longer has a dependency on importlib_resources. As a result, MM3 won't start unless all references to importlib_resources instead call importlib.resources, now part of stdlib. I tried patching all importlib.resource references by hand, and MM3 starts – but that can't be the "right" way to do this. Also, the diff references a src directory that doesn't exist under /opt/mailman. Thanks in advance for patching clues. dn

3 5

importlib_resources issue?
by Dave McGuire 21 Aug '23

21 Aug '23

Hi folks, I'm trying to test a fresh venv-based install from this procedure: https://docs.mailman3.org/en/latest/install/virtualenv.html Platform is SmartOS (Solaris 11) with Python 3.10. The installation goes fine, but initial startup bombs with: ImportError: cannot import name 'path' from 'importlib_resources' (/opt/mailman/venv/lib/python3.10/site-packages/importlib_resources/__init__.py) I assume this is related to importlib_resources moving into stdlib at some point. Is there a reasonable way around this? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 2

Internal Server Error: /mailman3/hyperkitty/api/mailman/archive
by Mail Person 21 Aug '23

21 Aug '23

Hello everyone. I am trying to sort out an error happening when messages are sent to the mailman server. The emails are being sent to the list but I get this error each time: Internal Server Error: /mailman3/hyperkitty/api/mailman/archive OperationalError at /hyperkitty/api/mailman/archive (1366, "Incorrect string value: '\\xF0\\x9F\\x90\\xBA\\x0A\\x0A...' for column 'content' at row 1") Request Method: POST Request URL: http://localhost/mailman3/hyperkitty/api/mailman/archive?key=7OF5IogiQItSUK… Django Version: 2.2.12 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.10 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: Thu, 17 Aug 2023 17:13:09 +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/db/backends/utils.py" in _execute 84. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py" in execute 71. return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 209. res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _query 315. db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in query 226. _mysql.connection.query(self, query) The above exception ((1366, "Incorrect string value: '\\xF0\\x9F\\x90\\xBA\\x0A\\x0A...' for column 'content' at row 1")) was the direct cause of the following exception: 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 153. email.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py" in save 740. self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py" in save_base 777. updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py" in _save_table 870. result = self._do_insert(cls._base_manager, using, fields, update_pk, raw) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in _do_insert 907. return manager._insert([self], fields=fields, return_id=update_pk, File "/usr/lib/python3/dist-packages/django/db/models/manager.py" in manager_method 82. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py" in _insert 1186. return query.get_compiler(using=using).execute_sql(return_id) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py" in execute_sql 1375. cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in execute 67. return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in _execute_with_wrappers 76. return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in _execute 84. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py" in __exit__ 89. raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in _execute 84. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py" in execute 71. return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 209. res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _query 315. db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in query 226. _mysql.connection.query(self, query) Exception Type: OperationalError at /hyperkitty/api/mailman/archive Exception Value: (1366, "Incorrect string value: '\\xF0\\x9F\\x90\\xBA\\x0A\\x0A...' for column 'content' at row 1") Request information: USER: AnonymousUser

2 2

Ansible role to install Mailman3
by samuel.d.darwin＠gmail.com 04 Aug '23

04 Aug '23

Hi, Before installing the Mailman Suite, I searched on https://galaxy.ansible.com/ for Ansible roles that might automate the whole process. https://github.com/galaxyproject/ansible-mailman3 turned out to be quite good. However, it was slightly out-of-date. I cloned it, made a few bug fixes, and corrected linting errors. Then, going further, added optional basic installations of Nginx, Postfix, PostgreSQL into the role. If anyone is installing Mailman they are welcome to try it out. https://github.com/cppalliance/ansible-mailman3 Now, I see there was a discussion on this very list about https://github.com/rivimey/ansible-mailman3 which was also a fork of natefoo's repo. What are the differences? As Stephen Turnbull wrote: "her (rivimey's) setup may be more complicated than most folks need (IIRC, she has a multi-homed setup with Mailman core, Postorius, and HyperKitty on three separate IPs on a separate subnet in the DMZ, while Mailman was really designed for three Mailman applications running on the same host, along with the database server and MTA)." My version of the role didn't follow the tactic of "three separate IPs on a separate subnet in the DMZ". Mainly, it adds postfix and postgres. Fixes small errors. Also, in a git branch of the repository named mailman3-core, I removed all the web code, so there is a version of the role that only installs core. We will use that while bundling the web components into another Django app, already deployed with docker. There is an open question about maintenance. Among the three roles mentioned here, which is being actively kept up-to-date? Perhaps there are no guarantees from any of them. At this instant in time, https://github.com/cppalliance/ansible-mailman3 is the most recent. Would it make sense to mention these roles in the official documentation? Not sure. Installing mailman3 is complicated and because of that, is a good fit for Ansible.

3 2

Mailman3 core didn't start after reboot, because mysql wasn't running yet.
by Mark London 29 Jul '23

29 Jul '23

Hi - We had a power outage, and after my Ubuntu server rebooted , mailman 3 tried to start before mysql was running. I guess because it wasn't a clean reboot, the mysql server took much longer than normal to start, while checking databases. So mailman3 couldn't start. Normal reboots never had this problem. Should it have kept trying? In any event, mailman3 core didn't start, but mailman3-web did start. But it wasn't very happy, of course. And any time someone tried to access the mailing list website, it would send me an error message. I had hundreds of such emails in the morning., that started with the one below. Is there a way to configure my system to make sure this doesn't happen again? Thanks. - Mark Service Unavailable: /mailman3/ Report at /mailman3/ Service Unavailable: /mailman3/ Request Method: GET Request URL:https://lists.psfc.mit.edu/mailman3/ Django Version: 4.1.8 Python Executable: /opt/mailman/venv/bin/uwsgi Python Version: 3.10.6 Python Path: ['.', '', '/riusMiddleware')

4 6

Something wrong in Django admin interfaces
by Franklin Weng 21 Jul '23

21 Jul '23

Hi, Since both Mark and Danil kindly told me that my wish to disable web anonymous account registering requires new version of mailman and django-mailman, I found that newest Debian bookwarm (12) has * mailman 3.3.8-1 (including mailman3-full and mailman3-web 20200530-2.1) * python3-django-mailman3 : 1.3.9-1 * python3-mailman-hyperkitty : 1.2.1 So I re-installed mailman3 (and took notes so that I could write a blog). After installing that, I found that it has problems in django admin page. When I clicked any features like users, Mail domains, Failed tasks... anyone, no matter New or Change, the web page was covered by the first page. All the configuration fields/labels are covered by the first page. Please see the screenshot: https://nextcloud.slat.org/index.php/s/e5KKEEbqDK6DpiN https://nextcloud.slat.org/index.php/s/nLgMRQ9ACyxCwoc It was not able to do the administration tasks. I looked at django-mailman issues https://gitlab.com/mailman/django-mailman3/-/issues but didn't find anything useful. Does anyone have similar issues? What can I do to solve this? Thanks, Franklin

2 1

Any possible way to reduce robot spam accounts?
by Franklin Weng 21 Jul '23

21 Jul '23

Hi, I just installed a mailman3 instance, even haven't announced to anyone yet, there are a lot of spam robot accounts registering into my system. (See https://nextcloud.slat.org/index.php/s/WWHo7F3igYxn8LY for screenshot) I really have no idea how the robots find my system since I haven't told anyone the ip or URL of my mailman instance. And, they're registering on the system, not the mailing list since I have only one list for testing now and it wasn't assaulted by spam yet. No matter what, what I want to ask is that, is there a way to either * just let users join from email (lists-join(a)lists.url) instead of registering on the mailman instance? or * use a scheme like CAPTCHA to reduce the successful opportunity of robot registering? Any help is appreciated! Franklin

4 7

List mails blocked from GMX - web.de > Spamfolder
by itservice＠knut-krueger.de 19 Jul '23

19 Jul '23

How can I configure Mailman3 so that Mails from the list will not be blocked by gmx.net I tried to send with the same user (mailman.cf) at my mail server, which will not be blocked by gmx. unfortunately, I get no bounce back message. They do just not appear in the mail folder of gmx. At web.de they go to the SPAM folder.

4 4

Import old mails into list
by franklin＠slat.org 19 Jul '23

19 Jul '23

Hi, I just built a new mailman3 instance. I installed directly on Debian using mailman3-full and follow /usr/share/doc/mailman3/README.Debian to set up database/web. Then I'd like to import some old mail (in a mbox file) into this list. I searched for any documentation but all I got is Import list data (from 2.1): https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/comma… How do I import an archive into a new mailing list: https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%2… The first is import list data, not list contents (mails). The second is very old, written in 2007, and now I even can't find bin/arch commands. Also, this post in this mailing list: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Which nobody replied yet. And when I tried `django-admin hyperkitty_import` it even told me "Unknown command: 'hyperkitty_import'". Could anyone please tell me how to import old mails from mbox file into a new mailing list? Thanks, Franklin

2 1

Configure administrative users via command line?
by kjohnson＠eclypse.org 18 Jul '23

18 Jul '23

I recently migrated a mailing list from Mailman 2.x to Mailman 3.x. Sending messages to and receiving messages from the list seems to work well. The web interface archives seem to be working well. Xapian is configured as the search engine. With only 60K some messages, archive search seems very fast. How can I configure administrative users via command line? I need to process a moderation request. I have root access on the server. A pointer to the appropriate documentation would be more than welcome. Thank you to anyone who can provide help. Ken

2 3

where do I find the text of a bounce email ?
by Per Jessen 01 Jul '23

01 Jul '23

All, I am trying to figure why a particular outbound message was bounced, so I'm looking for the text of the NDR that was sent - where do I find that ? Fyi, the outbound message was accepted by the first relay, and then presumably later bounced by the actual recipient server (Office365). Any and all hints much appreciated. -- Per Jessen, Zürich (4.6°C) Member, openSUSE Heroes

3 5

Viewing/editing bounce score/status in Postorius
by Tom Smyth 01 Jul '23

01 Jul '23

Is this possible? As of 1.3.2 I can't find it. Perhaps it's in a newer version? I'm working on upgrading. Thanks! -- Tom Smyth (he/him)

2 1

Hyperkitty list overview error: thread matching query does not exist
by Darren Hart 29 Jun '23

29 Jun '23

When attempting to visit the hyperkitty archives list overview for one of my two lists: Https://lists.mydomain.com/hyperkitty/list/mylist@mydomain.com/ The area where the threads should appear shows the loading spinner (but the activity summary bar chart and most active posters post counts do eventually load). The following appears in /var/log/mailman3/web/mailman-web.log: ERROR 2022-05-23 17:50:50,201 1694 django.request Internal Server Error: /hyperkitty/list/mylist(a)mydomain.com/posted-to 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/hyperkitty/lib/view_helpers.py", line 135, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 251, in overview_posted_to for thread in mlist.recent_threads: File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 142, in recent_threads return self.cached_values["recent_threads"]() File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py", line 59, in __call__ return self.get_or_set(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 281, in get_or_set return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 281, in <listcomp> return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get raise self.model.DoesNotExist( hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. Viewing “All Threads” or Threads by month (any month) work as expected, displaying the appropriate threads. The archives for this list worked previously. There was an incident that resulted in DNS not working and the archiver failing for a few days. The mail that came in during that time does show up in the other views. The hyper kitty archives for a second list on this Mailman3 instance is working correctly. How can I fix this view of the archives? Or how can I get more information on what might be failing? Thanks, Darren

3 6

archives html user interface menu selection retention after refresh
by Ken Alker 29 Jun '23

29 Jun '23

I have just started studying the archives feature and I've noticed that if I select "Most Active" in the top menu and then I refresh my browser, the refreshed screen jumps back to Recent after the refresh. In fact, if ANY of the five menu items across the top are selected and then a browser refresh is performed, the result is that one is always taken back to the Recent menu item. It was not apparent to me for a couple of days that this was happening and I'd convinced myself there was some bug in the Recent vs. Most Active lists because the Most Active list changed entirely after I did a refresh, when, in fact, I was then viewing the Recent list again. Confusing. Is there some way that whatever menu item was being viewed before a refresh could be retained so that the same menu item is shown after a refresh? Thinking this through even further, I suppose a side-affect of this request could be that visiting the same page much later (ie. not immediately after a refresh) may result in the page NOT defaulting to the Recent menu item any longer (unless once could clear the "last menu item" memory when the viewer moves AWAY from or closes the page). I don't have enough familiarly with the interface to suggest if this would be a bad side-effect, or good, but would this, indeed become a side-affect that would have to be thought through?

2 1

Re: How do I specify the TCP port number for Postgresql?
by kjohnson＠eclypse.org 28 Jun '23

28 Jun '23

Thank you for this helpful and prompt reply! Ken

1 0

How do I specify the TCP port number for Postgresql?
by kjohnson＠eclypse.org 28 Jun '23

28 Jun '23

The mailman.cfg file on the system I am working on includes this line: url: postgres://mailman3:mailman3:@localhost/mailman3 This works fine as long as the postgresql server is at the default port number of 5432. How do I specify a different TCP port number? My guess is that a change to this line is needed, but unfortunately, it is not obvious to me how to make that change, and I have been unable to find this information in the mailman3 documentation or in a previous mailing list post. Feel free to point me at the documentation or post that I have overlooked. Thanks, Ken

2 1

Archive date/time vs elapsed time
by Mark 28 Jun '23

28 Jun '23

Hi In the archive's "Recent", "Most active" etc displays, the date and time of each post is shown. However, when viewing by "Thread" listing, each post shows the elapsed time since it was posted ie. the number of days, hours since it was posted (eg. 1 day, 2 hours). Is it possible to set Hyperkitty to display the "Thread" listing with the date/time in place of that elapsed time? Thanks Mark

2 4

Postorius claims 2 messages held when there are none - out of sync
by Ken Alker 27 Jun '23

27 Jun '23

When I view a list via Postorius the "Held Messages" menu item has an inverse-red-"2" next to it, as if there are two held messages. There are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the held messages should be in "pipeline" subdirectory). When I click on "Held Messages" I get "Something went wrong" followed by "HTTP Error 500: {"title": "500 Internal Server Error"}". How do I fix this?

3 8

Message is received but is not sent out. Another, similar message, is processed fine.
by Allan Hansen 27 Jun '23

27 Jun '23

Hi all, One of my subscribers is trying to send a message to a list, but it is not being posted. The smtp.log shows that her first message was posted, but a second message (with 2 retries) was not: mailman@list:~/logs$ grep herName smtp.log Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=40109' Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) sender: herName(a)hotmail.com Jun 18 11:25:01 2023 (1243318) <CH3PR12MB82593510B90D8F05177C606BBE5EA(a)CH3PR12MB8259.namprd12.prod.outlook.com> post to theList(a)domain.tlc from herName(a)hotmail.com, 40061 bytes Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=18343' Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) sender: herName(a)hotmail.com Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=19123' Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) sender: herName(a)hotmail.com Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=18930' Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) sender: herName(a)hotmail.com At the second retry she copied me and I saw nothing untowards in her message. She's not getting any error return messages and her subscription is OK. Both messages were multipart/alternative and both contained Hebrew text. I told her I'd look at this, but I'm at a loss. Yours, Allan

3 6

Problems after upgrading from bullseye to bookworm
by Eggert Ehmke 27 Jun '23

27 Jun '23

I upgrade my server to bookworm. In the process python was upgraded from 3.7 to 3.9 . I reinstalled the virtualenv and the mailman packages. When I now start mailman-web, I get this in web/logs/uwsgi-error.log: pkg_resources.DistributionNotFound: The 'flufl.lock>=4.0' distribution was not found and is required by hyperkitty What did I miss? ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

5 5

attachment.html
by Sam Darwin 27 Jun '23

27 Jun '23

Hi, Using a typical modern email client such as Gmail, the messages are usually html formatted. Then, Hyperkitty displays attachment.html on every message. Can that be removed? I was searching for the topic "attachment.html" in the archives and there wasn't much information. What finally cracked the code was Mark's comment: If in Postorius on the list's Settings -> Alter Messages page, Filter Content and Convert html to plaintext are both Yes, the HTML should be converted to plain text and that should appear in HyperKitty. It turns out "Filter content" affects many settings. It's easy to skip over that. I wonder if the UI might call attention somehow, with a graphic element, or with text: "Settings on this page will not take effect. Because 'Filter content' has not been enabled". It is right that "Filter content" must be set in order to remove attachment.html ? And now, a search will have more results. :-)

2 3

clicking on a username when viewing a thread results in "Page not found"
by Ken Alker 27 Jun '23

27 Jun '23

If I click on a username when viewing a thread, it returns "Page not found" then "This page either doesn't exist, or it moved somewhere else.". Any idea why this may be happening? Also, why is it that some usernames are not clickable (ie. black text with no hyperlink)? Thanks! Ken

3 4

old usernames appearing in mailman.log
by Ken Alker 27 Jun '23

27 Jun '23

I have just migrated from a mailman 3.2.2 Debian package installation to a mailman 3.3.8 source install (in a Python virtual environment as mailman user) on an Ubuntu 20.04.6 LTS system. Several months ago, the system had been upgraded from mailman V2 to mailman V3.2.2. The server has been active for over 20 years. I've just taken on the project so I'm new to all of this, and one thing I noticed that caught my eye, and has left me curious, is that for the first a couple of seconds starting just after midnight every night (just after log rotation) mailman.log would have many (dozens, or hundreds) of lines entered in it just like this one: Jun 19 00:00:04 2023 (2266) 127.0.0.1 - - "GET /3.0/users/old-user(a)domain.tld HTTP/1.1" 404 58 where "old-user(a)domain.tld" is the email address of a user who either had unsubscribed or changed their email address (I don't know which, I just know they are no longer a member/subscriber to the list). Each successive entry in the log would have a different "old username" in it. I don't understand why these entries would be in the log and what they mean. Can someone shed some light on this for me? This is merely a question of curiosity, and not one of import. (Since migrating from 3.2.2 to 3.3.8 this behavior has stopped, be that GOOD or BAD.) Ken

2 8

Global ban using regex
by Henrik Rasmussen 27 Jun '23

27 Jun '23

Using some regex testers and generators like https://regex101.com and https://www.site24x7.com/tools/regex-parser.html, the regex (.*)(a)inker\.azerbaijan\.su seems to match EVERYTHING(a)inker.azerbaijan.su (EVERYTHING is constantly changing in current spam mails). However, entering the regex to the Global Ban Add ban /postorius/bans/ result in: `An error occurred: Invalid Parameter "email": Expected a valid email address or regular expression, got (.*)(a)inker\.azerbaijan\.su.'` Same result when using [Ban list] in postorius/lists/[LISTNAME]/bans/. Entering a none regex addresses like eknejfj(a)inker.azerbaijan.su works fine. Does Mailman use a different regex syntax I am using GNU Mailman 3.3.4 (Tom Sawyer) and Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] (maxking/mailman-core:0.3 and maxking/mailman-web:0.3)

2 1

starting gunicorn per mailman.log yet gunicorn not installed
by Ken Alker 27 Jun '23

27 Jun '23

I see the below in my mailman.log, yet I installed uwsgi and NOT gunicorn. My mainmanweb.service file includes "ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" and not the gunicorn equivalent. Does this log entry make sense in my case? [2023-06-22 12:44:36 -0700] [411132] [INFO] Starting gunicorn 20.1.0

4 7

messages stuck in the bad queue
by Ken Alker 26 Jun '23

26 Jun '23

I am working on a mail server that was migrated from mailman V2 to mailman V3 in February. I just noticed that there are over 1000 messages in the bad queue. All of the messages in the bad queue are dated 2/2/23 and all have a timestamp within a one-hour window of each other. I used mailman qfile to inspect five random emails in the bad queue and so far they are all "successfully subscribed" emails, but I presume there are no guarantees there aren't others mixed in there that might be legitimate emails (ie. I just unshunted 140 emails in the shunt queue and they were all good emails and all got processed). I figure that the easiest way to inspect these 1000 emails is just to have them re-delivered. I tried moving one from the bad queue to the shunt queue and I ran "mailman unshunt" but nothing happened. Is there a way to reprocess the bad queue? Also, what exactly is the bad queue? Thank you, Ken KA6KEN (happy field day weekend)

2 4

re-injecting emails that were not archived
by Ken Alker 25 Jun '23

25 Jun '23

I have just migrated from a mailman 3.2.2 Debian package installation to a mailman 3.3.8 source install (in a Python virtual environment as mailman user) on an Ubuntu 20.04.6 LTS system. Several months ago, the system had been upgraded from mailman V2 to mailman V3.2.2. I noticed when I came onto the project last week that there were 140 messages stuck in the "shunt" queue for the two lists hosted by this server (I have no idea why and the old logs were not available and I don't recall the results of "mailman qfile", assuming that had shed some light on the reason why they were shunted). In any event, I unshunted these messages and they flowed out to the subscriber's email addresses successfully. What I was not expecting is that the system did not inject any of these emails into the archive. AFAICT, the messages are no longer anywhere on the system (but I could be mistaken). Here are my questions: 1) Why would these emails not have been injected into the archive? 2) Is there some way for me to re-inject these messages into the two lists? The only place I (THINK I) have them is in my own personal IMAP box since I'm a subscriber to the lists. 3) Can this be done without the emails being re-delivered to subscribers? Thank you, Ken

2 1

Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question
by Ken Alker 25 Jun '23

25 Jun '23

As an aside, for anyone else who is trying to do the same (and to give some background into my procedures so far), I have been following these references: <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> <https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-virtualenv> My goal is to create the least change to file locations and configuration files as possible (I may move things into more "source-installed centric" locations once I have things working again), thus, many files are still in the original Debian package-allocated directories. That said, I was forced to move mailman3web.db to /opt/mailman/web as sqlite (and, hence, mailman-web) simply could not open the database as user mailman from my virtual environment (even with mailman3web.db file permissions set to 777 and owner.group set to mailman.mailman). So far I've gotten mailman running properly and handling the mailing lists, however, I have not gotten the web interface working again.

2 6

Importing MBOX from custom listserv to MM3?
by Thomas Ward 25 Jun '23

25 Jun '23

We are looking at moving from a home grown listserv system at a client to potentially MailMan3 for the lists platform instead. We have historic thread data from the homegrown systems in mbox form. Is there a way to import that into MM3 for indexing in the archiver there so we dont need to keep the (literally massive) MBOX file? Sent from my Galaxy

2 2

Importing mbox file into MM3
by Mark 23 Jun '23

23 Jun '23

Hi All I'm trying to import a large mbox file from a MM2 list into a new list on MM3. The new MM3 list has 3 test emails in its archive. # cd /usr/share/mailman3-web/ # python3 manage.py hyperkitty_import -l LISTNAME@DOMAIN /home/mark/tmp/LISTNAME.mbox Importing from mbox file /home/mark/tmp/LISTNAME.mbox to LISTNAME@DOMAIN 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 Django admin command with arguments 'update_index_one_list LISTNAME@DOMAIN'. That all seems pretty good. Then I attempt to rebuild the archive. # python3 manage.py update_index_one_list LISTNAME@DOMAIN Indexing 3 emails The import or rebuild has failed as it's just rebuilding the existing archive of the 3 test messages. What am I doing wrong? Thanks Mark

2 2

Where in database are subject prefix sequences stored?
by Thomas Ward 22 Jun '23

22 Jun '23

I am using numeric prefixes for a list, such that it's `[ListName-000012]`. Where would that sequence indicator be stored in the database? Postorious' database? Hyperkitty's database? I ask because I'm rebuilding a home-grown listserv solution using Mailman3 and the main requirement is the thread IDs being *properly sequential* with the current implementation, so I have to set the "next ID in sequence" to a start value. I don't see this clearly in the DB where the sequence value would be stored, so if anyone knows that'd be great to know so I can get this working. Thomas

2 2

Help needed to create filters that were working in Mailman 2.
by mrl＠psfc.mit.edu 22 Jun '23

22 Jun '23

How do I make a filter that if it matches, it accepts the message and doesn't check the remaining filters? I could do this using the anti-spam filters in mailman 2, as there was a Accept option. But there is no Accept option in Mailman 3 (that I can find). I tried using "Default antispam action", but that didn't stop the rest of the filters from being applied. Thanks for any suggestions. - Mark

3 4

toward improving correctness when running on single core system ...
by Nelson Strother 21 Jun '23

21 Jun '23

I recognize that most real computer systems now are equipped with multiple CPUs, usually with each CPU having multiple cores or hardware threads. But when one obtains a computer system from a service provider with a small expected load, it is likely that a virtual computer system will provide only a single core. Yes, one can obtain a multi-core virtual system, maybe for only twice the cost; but it would seem wasteful to make that choice solely to support starting and stopping the Mailman3 program when the system load at all other times is satisfied by a single core system. From my observations, mailman 3.3.8 is unreliable when running on a single core system. When `mailman start` is issued, there is a moderately high probability that one or more of the thirteen runner processes will not survive this startup phase. Depending upon the current usage of the mailman installation, one may or may not notice this fact. In either case, `mailman status` provides the same information, with no hint of missing or damaged capabilities when one or more of the runner processes are stillborn. [1] One potential improvement would be to increase the lifetime of the locks used by each of the runner processes during `mailman start`. [2] Based on a small sample of runs of `mailman start`, this change may provide correctness (i.e. I have yet to see a runner process go MIA). But it still seems unsatisfactory for availability / performance, as the elapsed wall clock time for the system to settle down and be functional and responsive is approximately 13 minutes. While this is an improvement from the 20 minute or greater delays observed before making this change, it still differs greatly from the nearly instantaneous startup time experienced on multicore / multiprocessor systems. The best "performance" I have yet obtained on this single core system is WITHOUT the change in [2] below, but by crossing abstraction boundaries and reducing the amount of time this single CPU spends futilely busy waiting for itself when it has not provided an opportunity for another process (maybe even the process currently holding the desired lock) to make any progress. [3] With this change, "only" 9 minutes elapsed wall clock time is wasted (with maybe only the middle 4 minutes at 100% CPU utilization) before the system settles down and is functional and responsive. However, ample room for improvement remains. [4] Please suggest better ideas or corrections. Nelson [1] For a few examples of these failures, see: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] Here is a diff from the original mailman/database/factory.py (or .../mailman/.local/lib/python3.9/site-packages/mailman/database/factory.py if you wish to apply this to an installed system): > 25a26 > > from datetime import timedelta > 53c54,55 > < with Lock(os.path.join(config.LOCK_DIR, 'dbcreate.lck')): > --- > > with Lock(os.path.join(config.LOCK_DIR, 'dbcreate.lck'), > > timedelta(seconds=30)): which increases the delay from the default of 15 seconds to 30 seconds before another process will be empowered to break the lock being held by one of mailman's runner processes, which leads to the death of a process. [3] Here is a diff from the original .../mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py : > 7a8 > > import subprocess > 338a340,344 > > if sys.platform.startswith('linux') and \ > > (len(subprocess.check_output(["lscpu", "-p"]).splitlines()) == 5): > > # there is only one processor [four lines of comments, and only one line for one CPU] > > # let another process run before joining the traffic jam for this lock > > os.system('sleep 20s') For possible similar benefits on other platforms, one should also include variations on this theme using something like e.g.: > > if sys.platform.startswith('win32') and \ > > subprocess.check_output('wmic path win32_Processor get NumberOfLogicalProcessors').strip().endswith(b'1'): I seriously doubt all (or even any?) other users of the flufl.lock package would benefit from this exact change ... but many may benefit from sleeping for e.g. a half-second when on a single core? In the case of Mailman3, sleeping for a fixed duration shorter than 20 seconds retains the original problem of broken locks and runner process death, while sleeping for a fixed duration longer than 20 seconds leads to an increase in both the wall clock delay time as well as the CPU time consumed during `mailman start`. I have not experimented with random or staggered delays, which may further reduce the number of simultaneously blocked waiters for this lock. [4] I have seen `mailman start`complete in less than 1 second wall clock time on a multicore / multiprocessor system. All of these observations made with mailman 3.3.8 as installed via pip.

5 8

How to tell who moderated a post?
by bryan.kartzman＠yu.edu 21 Jun '23

21 Jun '23

Is there any way to tell which moderator of a list approved a particular post to that list?

2 3

Re: mailman3 auto-disabling of subscriptions
by Mark Sapiro 19 Jun '23

19 Jun '23

On 6/17/23 17:02, Mike Wertheim wrote: > I set `remove_dkim_headers: yes` in the [mta] section of mailman.cfg. > > I'm seeing a bunch of these errors in the logs: > 2023-06-17 18:57:11 1qAbMA-005Y7W-HP ** mike.wertheim(a)gmail.com > <mailto:mike.wertheim@gmail.com> R=dnslookup_single_domain > T=remote_smtp_single_domain H=alt2.gmail-smtp-in.l.google.com > <http://alt2.gmail-smtp-in.l.google.com> [172.253.62.26]: SMTP error > from remote mail server after end of data: 550-5.7.26 Unauthenticated > email from gmail.com <http://gmail.com> is not accepted due to > domain's\n550-5.7.26 DMARC policy. Please contact the administrator of > gmail.com <http://gmail.com> domain\n550-5.7.26 if this was a legitimate > mail. Please visit\n550-5.7.26 > https://support.google.com/mail/answer/2451690 > <https://support.google.com/mail/answer/2451690> to learn about the\n550 > 5.7.26 DMARC initiative. > w13-20020a05622a190d00b003fde5babbf5si1170418qtc.14 - gsmtp Your issue is mail From: the gmail.com domain to the list and sent to gmail users is being bounced because it fails DMARC. I.e. Gmail applies a DMARC policy of p=reject to mail From: gmail.com even though it's published DMARC policy is p=none. You need to apply DMARC mitigations to this mail. Unfortunately, this requires setting DMARC Mitigate unconditionally to Yes. Mailman 2.1 has a feature to apply DMARC mitigation to messages From: specific domains regardless of any domain specific DMARC Policy. Unfortunately this hasn't been implemented in Mailman 3 yet. I just filed https://gitlab.com/mailman/mailman/-/issues/1084 for that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Where does sender postorius@ come from?
by Jens Günther 19 Jun '23

19 Jun '23

I just realized, that mails for registering an account and/or resetting ones password are obviously sent from postorius@SERVE_FROM_DOMAIN. Why are they not sent from MAILMAN_ADMIN_EMAIL? The problem is: - an account is trying to register with a mailaddress from a HostEurope-server - HostEurope-Servers are doing Sender-Callouts (bad practise :-D) to verify that a mailaccount exists - mail is then bouncing, b/c those are not answered (shoud I?): status=bounced (host [80.237.138.5] said: 550-Sender verification is required but failed. - bounce then can't be processed, since mailaccount does not exist :-D status=bounced (mail for SERVE_FROM_DOMAIN loops back to myself) Am I missing something are shouldn't it be better to send those mails from MAILMAN_ADMIN_EMAIL? (I don't want to mess with these sender callouts or change anything, HostEurope has been a little bit of a pain in the ... with mailinglists and not much help at all). Thanks in advance, Jens.

3 8

Proxy error.
by Mark London 18 Jun '23

18 Jun '23

My server has several aliases. And Chrome's cookies sometimes get messed up because of it. Several users get a proxy error when trying to connect to the mailman website. One person just fixed it by clearling cookies, although this is not a great solution. Error log says "You may need to add 'psfcmail2.psfc.mit.edu' to ALLOWED_HOSTS". But it is already there in /etc/mailman/settings.py Or should it go elsewhere? Thanks. - Mark Chrome: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request Reason: Error reading from remote server Apache/2.4.52 (Ubuntu) Server at lists.psfc.mit.edu Port 443Error log: ERROR 2023-06-18 19:11:11,568 2114 django.security.DisallowedHost Invalid HTTP_HOST header: 'psfcmail2.psfc.mit.edu'. You may need to add 'psfcmail2.psfc.mit.edu' to ALLOWED_HOSTS. Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 56, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.10/site-packages/django/utils/deprecation.py", line 135, in __call__ response = self.process_request(request) File "/opt/mailman/venv/lib/python3.10/site-packages/django/middleware/common.py", line 48, in process_request host = request.get_host() File "/opt/mailman/venv/lib/python3.10/site-packages/django/http/request.py", line 152, in get_host raise DisallowedHost(msg) django.core.exceptions.DisallowedHost: Invalid HTTP_HOST header: 'psfcmail2.psfc.mit.edu'. You may need to add 'psfcmail2.psfc.mit.edu' to ALLOWED_HOSTS

1 1

mailman3 auto-disabling of subscriptions
by Mike Wertheim 17 Jun '23

17 Jun '23

I'm running an email list on mailman3. My users are getting inundated by messages saying that their subscriptions have been disabled due to their bounce score exceeding the mailing list's bounce_score_threshold. But there is nothing wrong with these users' email accounts. They are all perfectly fine. Apparently the issue is somehow related to spam. Whenever I (as admin) get these emails, I just unsubscribe the user and then re-subscribe them. But also, the user gets confused and emails me about it, which unnecessarily takes up their time and mine. The relevant list settings are currently... bounce score threshold: 5 bounce info stale after: 7d bounce disabled warning interval: 7d bounce disable warnings: 5 What's the best way to fix this? I'm considering reducing "bounce info stale after" to "2d" and/or increasing "bounce disabled warning interval" to "90d".

3 5

Postorius -owner messages
by ssehi＠nebraska.edu 16 Jun '23

16 Jun '23

I manage a number of lists for non-technical users that are considered owners of their own lists. Some of them have expressed that they would like to emulate some other mailing list services' "Quiet" owners for people that need to be able to access the list settings for administrative reconciliation as well as a fallback, but want to leave subscription requests or approval of messages to others that are more involved in the day-to-day management. They'd like to disable owner delivery for themselves, and I'd like to not make the change for them using the shell every time I get one of their requests. We have a Postorius front end set up and working, but it doesn't appear that disabling delivery using the List-based preferences in the Postorius interface stops those Owner communications. Is there a way to allow users to disable that natively in Postorius? Thanks, Sam

2 2

Apache proxy error messages.
by Mark London 15 Jun '23

15 Jun '23

I have two users who are getting a proxy error message when they try to connect her our mailman server: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request Reason: Error reading from remote server Apache/2.4.52 (Ubuntu) Server at lists.psfc.mit.edu Has anybody else in an errorlike this before? One person manage to get around this by going in incognito mode on the browser. Does that make any sense?

2 1

unrequested unsubscription
by Mike Wertheim 15 Jun '23

15 Jun '23

I have a Mailman 3 email list, running on Mailman 3.3.3 on Debian 11. A few of the list members are reporting that they received Email Address Unsubscription Confirmation emails, but claim that they never requested to be unsubscribed. (All are Gmail users. but they might be coincidental, since most list members are Gmail users.) Has anyone seen this behavior before? Any ideas on what might be happening?

3 3

SSO
by bryan.kartzman＠yu.edu 15 Jun '23

15 Jun '23

Is it possible to set up SSO so that once users (owners,moderators) set up an account in Postorius on the mailman3 server we have created , they can authenticate against Azure to login instead of the password for the local account Postorius created?

2 1

How to remove a message with an invalid Message-Id?
by McGuire, Tommy M. (MSFC-IS61)[EAST2] 14 Jun '23

14 Jun '23

I have a fun problem: apparently a message sent to a mailing list has an invalid Message-Id (I think), which is causing the message parse to fail while attempting to archive the message. Unfortunately, the message seems to be trapped somewhere and resulting in error logging every few minutes. Is there any way to find and remove the message? Literally, the only thing I've been able to find out about it is that the Message-Id contains the text "[83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com]>". The actual errors in the mailmanweb.log are: ERROR 2023-06-14 21:49:40,692 3165793 django.request Internal Server Error: /archives/api/mailman/archive Traceback (most recent call last): File "/usr/local/lib/python3.8/email/_header_value_parser.py", line 2069, in get_msg_id token, value = get_dot_atom_text(value) File "/usr/local/lib/python3.8/email/_header_value_parser.py", line 1334, in get_dot_atom_text raise errors.HeaderParseError("expected atom at a start of " email.errors.HeaderParseError: expected atom at a start of dot-atom-text but found '[83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com]>' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/app/mailman/venv/lib/python3.8/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/app/mailman/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/app/mailman/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/app/mailman/venv/lib/python3.8/site-packages/django/views/decorators/http.py", line 40, in inner return func(request, *args, **kwargs) File "/app/mailman/venv/lib/python3.8/site-packages/hyperkitty/views/mailman.py", line 118, in _decorator return func(request, *args, **kwargs) File "/app/mailman/venv/lib/python3.8/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view return view_func(*args, **kwargs) File "/app/mailman/venv/lib/python3.8/site-packages/hyperkitty/views/mailman.py", line 164, in archive add_to_list(mlist_fqdn, msg) File "/app/mailman/venv/lib/python3.8/site-packages/hyperkitty/lib/incoming.py", line 65, in add_to_list msg_id = get_message_id(message) File "/app/mailman/venv/lib/python3.8/site-packages/hyperkitty/lib/utils.py", line 60, in get_message_id msg_id = email.utils.unquote(re.sub(r'\s', '', message['Message-Id'])) File "/usr/local/lib/python3.8/email/message.py", line 391, in __getitem__ return self.get(name) File "/usr/local/lib/python3.8/email/message.py", line 471, in get return self.policy.header_fetch_parse(k, v) File "/usr/local/lib/python3.8/email/policy.py", line 163, in header_fetch_parse return self.header_factory(name, value) File "/usr/local/lib/python3.8/email/headerregistry.py", line 607, in __call__ return self[name](name, value) File "/usr/local/lib/python3.8/email/headerregistry.py", line 202, in __new__ cls.parse(value, kwds) File "/usr/local/lib/python3.8/email/headerregistry.py", line 535, in parse kwds['parse_tree'] = parse_tree = cls.value_parser(value) File "/usr/local/lib/python3.8/email/_header_value_parser.py", line 2126, in parse_message_id token, value = get_msg_id(value) File "/usr/local/lib/python3.8/email/_header_value_parser.py", line 2073, in get_msg_id token, value = get_obs_local_part(value) File "/usr/local/lib/python3.8/email/_header_value_parser.py", line 1516, in get_obs_local_part if (obs_local_part[0].token_type == 'dot' or IndexError: list index out of range The errors in the mailman.log are even less useful; they're basically copies of the HTML error page. Jun 14 17:05:02 2023 (3165816) HyperKitty failure on https://lists.nasa.gov/archives/api/mailman/archive: ... <div class="alert alert-danger">An error occurred while processing your request.</div> ... Jun 14 17:05:02 2023 (3165816) Exception in the HyperKitty archiver: ... Jun 14 17:05:02 2023 (3165816) Traceback (most recent call last): File "/app/mailman/venv/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 151, in _archive_message url = self._send_message(mlist, msg) File "/app/mailman/venv/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 207, in _send_message raise ValueError(result.text) ValueError: ... <div class="alert alert-danger">An error occurred while processing your request.</div> ... Any help would be appreciated! Tommy M. McGuire Tommy.M.McGuire(a)nasa.gov

2 1

Is there a simple way to remove the footer without having to add a customized template?
by Mark London 14 Jun '23

14 Jun '23

I simply want to have no footer for a mailing list. Can I do that without having to create a customized template? Thanks.

3 2

Re: Why is a mailing list not sending the moderator subscribe or post notifications?
by Mark London 14 Jun '23

14 Jun '23

Argh, that is it! Thanks!!!! Admin immed notify YesNo Should the list moderators get immediate notice of new requests, as well as daily notices about collected ones? List moderators (and list administrators) are sent daily reminders of requests pending approval, like subscriptions to a moderated list, or postings that are being held for one reason or another. Setting this option causes notices to be sent immediately on the arrival of new requests as well. On 6/14/2023 4:36 AM, Odhiambo Washington wrote: > *action to take when _a post is held for moderation_*

1 0

Why is a mailing list not sending the moderator subscribe or post notifications?
by Mark London 14 Jun '23

14 Jun '23

Hi - I migrated from mailman 2 to mailman 3. All but one list is working correctly. That list is not sending the moderator any emails. It appears to configured exactly like the other lists. I.e. subscription requests and moderated users posts don't generate any emails to the moderator (me). I tried changing moderator email addresses, and everything else I could think of, but nothing worked. What can I do to debug this problem? This list is much larger than any of my other lists. And has a huge archive. I doubt that is a factor, but I’ll mention it anyway. Also, how do I run the command to remind me of awaiting moderation requests, so that I can run it hourly? In case this can’t be fixed quickly. As an aside, I had some mailman 2 lists that had no moderators. I could swear that for them, that the owners would get moderated requests. Am I hallucinating? I can't check the old server any longer. Thanks. – Mark

2 1

Setting moderation_action when approving a message from a non-member fails
by Tom Smyth 13 Jun '23

13 Jun '23

Hello! When a message is held due to it being from a non-member, I notice that Mailman creates a non-member record for the sender automatically. This is great! But if I try to set their moderation action while approving the message in Postorius, I get: Failed to set moderation action: xxx(a)gmail.com is not a member address of xxx(a)xxx.org Is this expected? I would like to be able to set the moderation action for the non-member that has already been created. I am on Postorius v1.3.2. Thanks! -- Tom Smyth (he/him)

3 2

Read-Mostly list?
by Stephen Daniel 10 Jun '23

10 Jun '23

I wish to have a list that anyone can read. A few designated people can post without moderation, and all other users are moderated. Is this possible? I don't see a way in the list settings to create users who are not moderated when the default action is to moderate. Thanks! -- Steve

2 2

Mailman sends Welcome emails, but does not send [List] postings emails
by justfixit＠marilynstrother.com 10 Jun '23

10 Jun '23

Having recently installed this same version of mailman (GNU Mailman 3.3.8 (Tom Sawyer)) a few times successfully, I have a puzzle with a current new installation. Via the command line I can create lists and add members, and the new members receive their Welcome message from mailman. But when a member sends an email to post to a list (e.g. hc(a)cs.org as shown here), the mailserver delivers it to mailman: May 29 16:36:58 localhost postfix/lmtp[44386]: E762E427CB: to=<hc(a)cs.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.84, delays=0.8/0/0.01/0.03, dsn=2.0.0, status=sent (250 Ok) but no copy is sent to the members / subscribers. After the posts are received by mailman (as recorded in /var/tmp/mailman/logs/smtp.log), nothing more is added in any of the log files in /var/tmp/mailman/logs/... An attempt to imitate a technique seen elsewhere for [logging.smtp] for leaving some breadcrumbs by adding into mailman.cfg: - - - [logging.subscribe] level: debug path: mailman.log - - - and restarting mailman led to no detectable change. Expecting no change, I even changed for one UNmoderated list: >>> dump_json('http://localhost:8001/3.1/lists/hc.cs.org' ... '/config/default_member_action', ... dict(default_member_action='accept'), 'PATCH', ... username='...', password='...') date: Mon, 29 May 2023 16:31:31 GMT server: gunicorn status: 204 the default_member_action from 'defer' to 'accept' to rule out some moderation process delay. How can I enable some kind of trace or gather more information to learn where this configuration is in error? Cheers, Nelson

5 17

Migration failure (2.1.29 to 3.3.8 on Debian testing)
by {16/7} 08 Jun '23

08 Jun '23

Hello, I have both the mailman and mailman3-full packages installed on my machine and I'm following the migration guide located here: https://docs.mailman3.org/en/latest/migration.html Running the command { mailman import21 mylist(a)mysite.com /var/lib/mailman/lists/mylist/config.pck } completes once I create the list but states that it cannot convert the msg_footer and digest_footer mailing list attributes. (I might also point out that the { mailman create mylist(a)mysite.com } command isn't actually documented on that webpage.) I can't seem to find the manage.py script in my $PATH and after searching, I find it as part of the mailman3-web package. When I run { sudo -H -u list python manage.py hyperkitty_import mylist(a)mysite.com /var/lib/mailman/archives/private/mylist.mbox/mylist.mbox }, it fails with "ImportError: No module named django.core.management". If I run the script directly as { sudo -H -u list /usr/share/mailman3-web/manage.py ... }, I get "PermissionError: [Errno 13] Permission denied: '/usr/share/mailman3-web/settings_local.py'". By default, settings_local.py's group is www-data, and not knowing where to go next, I decided to try changing that file's group to list. When I re-ran the command (as user list), I got a Python traceback that gives "PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/web/mailman-web.log'". Next, I changed the file's group back to list and decided to try running the manage.py script as the www-data user. This results in "/usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured." and "System check identified some issues:" followed by a list of "Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'" warnings for a number of Django tables. At the end of this list is "CommandError: The list address must be given on the command-line". But it *was* given. My questions are: 1. How do I undo any damage (if any) my efforts may have caused? 2. What's the correct way to run manage.py?

3 4

Subscribe to a list on a Mailman3 server without account registration
by c.buhtz＠posteo.jp 06 Jun '23

06 Jun '23

Hello, I might miss something here but I'm confused about a difference between Mailman2 and 3. On MM2 I just subscribed a mailinglist via my EMail address. I didn't need to create an account on the MM2 server first. But it seems on MM3 it is otherwise. For example I use MM3 on python.org. It seems I have to register first before subscribing to a mailing list. https://mail.python.org/mailman3/lists/twisted-web.python.org/ Is this observation correct? Kind Christian

2 1

mailman break DKIM signature by modifying body
by Peter Münster 06 Jun '23

06 Jun '23

Hi, I'm using mailman 3.3.8. Some messages with attachments from Google users get rejected by spam filters because of invalid DKIM signatures. It seems, that mailman alters some lines in the body. Here an example: Original message: --8<---------------cut here---------------start------------->8--- Lines: 2031 --000000000000f846c505fc494b7a-- --000000000000f846c705fc494b7c Content-Type: application/pdf; [...] Content-Disposition: attachment; [...] --8<---------------cut here---------------end--------------->8--- Altered message: --8<---------------cut here---------------start------------->8--- Lines: 2032 --000000000000f846c505fc494b7a-- --000000000000f846c705fc494b7c Content-Type: application/pdf; [...] Content-Disposition: attachment; [...] --8<---------------cut here---------------end--------------->8--- An empty line is added, and the spaces after the semicolons are removed. Perhaps related to https://gitlab.com/mailman/mailman/-/issues/1079. What could I do please, to prevent such modifications of the body? TIA for any help, -- Peter

2 8

Why are "Subscription options" left unselected if I don't manually select them?
by mrl＠psfc.mit.edu 01 Jun '23

01 Jun '23

When I subscribe to a mailing list, and I don't manually select some of the "Subscription options", they are left unselected when I go back to look at them. I would have thought that if I didn't make a selection, that they would be set to a default option. Or am I wrong? Thanks.

5 7

dmarc mitigation debug
by Thomas Krichel 01 Jun '23

01 Jun '23

Hi gang! I have a list with DMARC mitigation action "Replace From: with list address" DMARC Mitigate unconditionally "Yes". But list posts still have the poster's From:, breaking DMARC. How can I debug this? For a start, I looked in my sqlite database. Changes on the web interface list settings seem to be correctly applied to the database. But I don't see a "munge_from" in the fields of a list in the database. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21181st day.

2 3

Importing mailman 2 shows member's "Moderation Action" = "Default processing". But new members show = "None". Why
by mrl＠psfc.mit.edu 30 May '23

30 May '23

I imported my mailing lists from mailman 2. If I view the Members, it say "Moderation Action" = "Default processing". But when I now subscribe myself or other people to the list, and view the new Members, it say "Moderation Action" = "None" for them. Should that be happening? The mailing list 's "Default action to take when a member posts to the list" setting is set to "Default processing". Thanks. - Mark

2 9

How do you remove the Hold on all non-member forwarded emails?
by Sean Westfall 26 May '23

26 May '23

Hi Mailman3 users, I have recently started using mailman3 and it's a wonderful piece of software. But I am having trouble using one of its configurations. I configured my mailmain3 instance to accept all non-member emails, as I want all emails that are sent to the mailman client to go to all subscribers without having it held for moderation -- I did this by setting this setting: https://i.imgur.com/PGzaD0k.png Action to take for postings from non-members for which no explicit action is defined. (Details for generic_nonmember_action) -> "Accept" But this doesn't work for forwarded emails. Even if the email address that is being forwarded from is included in the "List of non-member addresses whose postings should be automatically accepted." I noticed that all emails that are forwarded to the mailing list are always held for moderation -- though this isn't the case for email that are sent to the mailing list directly. But I want it so that emails that are even forwarded to my mailman mailing list don't get held in moderation. How do I set mailman to do this? I was thinking if there is no way to configure this easily then I might have to do this from the code, which means I might have to ask on the developer mailing list -- or I have to go with an entirely different solution (using something other than mailman3). I hope someone here is willing to help, and in either case thanks for anyone that is willing enough to read this. Sincerely,

2 2

How to edit default 'Reject (with notification)' message
by Zaheer Abbas 26 May '23

26 May '23

Dear all, I want to modify the default text sent in response to when we select 'Reject (with Notification)' in 'Message Acceptance > Default action to take when a non-member posts to the list' settings. Currently, the default rejection text is as follows: "Your message to the $list was rejected for the following reasons: The message is not from a list member The original message as received by Mailman is attached." I have created a template with the option, "Notice sent to a poster when their message has been rejected by the list’s moderator." but it only works if message acceptance is set to 'Hold for Moderation' and then the moderator rejects the post manually. Is there any source file, which I can modify to replace the default rejection text mentioned above? Sincerely, Zee

3 2

Virtual alias + shell
by alopez＠ac.upc.edu 26 May '23

26 May '23

Hello, I want to have a mailman configured together with virtual alias. To do that I need to use alias_domain. I have tried to do it with mailman shell. The domain seams to be created but when I leave the shell and enter again, the domain is not longer there. On the other hand, If I create a domain in administrator interface, it is not listed in the shell. If I create in the web interface, which field correspond to the alias_domain : Domain Name, Display Name , Mail domain? The code I use in the shell is: mailman shell from mailman.interfaces.domain import IDomainManager from zope.component import getUtility manager = getUtility(IDomainManager) from operator import attrgetter def show_domains(*, with_owners=False): if len(manager) == 0: print('no domains') return for domain in sorted(manager, key=attrgetter('mail_host')): print(domain) owners = sorted(owner.addresses[0].email for owner in domain.owners) for owner in owners: print('- owner:', owner) manager.add('example.edu',alias_domain='x.example.edu') show_domains(with_owners=True) exit() Thanks in advance Albert

2 4

Subscribing users stuck in pending hell
by Quanah Gibson-Mount 25 May '23

25 May '23

Hi, We frequently end up with users who never receive their email to confirm their account, leaving them in a netherworld where they cannot become list members. If I try to subscribe them via the mass subscribe option, it says I can't because their subscription is pending. If I go to subscription requests, it says there are 0. If I go to "non-members" in the UI, I can find them, but I don't see an option to convert them to members. So what's the solution to getting these people subscribed and no longer stuck in limbo? Thanks! --Quanah

2 9

not correct language in subject(s)
by Jens Günther 24 May '23

24 May '23

When receiving all types of system mails from mailman3 (3.3.8) there are almost all the subjects in English, althought text is in German. Am I missing somehting? The option to have the list in german is toggled and so far all the mails are in german ... also templates on different levels work fine, either en or de, but obviously the subjects are not translated (?) or taken from an English template. Any hint is appreciated, regards, Jens.

2 6

Please contact me Odhiambo Washington...
by Marisa Giancarla 24 May '23

24 May '23

For some reason your mail got deleted, not sure why, and I don't have your email address saved :( Sorry to bother others... Marisa

2 1

Template URI gets written incorrectly
by Mark Dale 24 May '23

24 May '23

Hi, When I create a template, it writes the URI incorrectly into the template table in the mailman3 database and the list stops working. For example, it writes: http://localhost/mailman3/postorius/api/templates/list/markslist.lists.post… When I correct it like so, all is well: https://lists.postmark.io/mailman3/postorius/api/templates/list/markslist.l… Have I missed a config setting somewhere, or is this a bug with the older Debian Mailman 3.3.3 ? /Mark

2 2

Multiple server replicas
by Dave Hall 24 May '23

24 May '23

Hello. Our Mailman 2.1 setup included 4 replica servers, all with Mailman, Exim4, Apache, etc. The configuration for the 4 mailman server instances were synchronized by linking most of the directories in /var/lib/mailman to an NFS share that is mounted on all 4 servers. Cron jobs were staggered such that an hourly job would run every 4 hours on each server, yet still get run hourly. With Mailman 3 we would like to keep the same kind of setup. However, things have changed quite a bit. Having both mailman and mailman-web instances all share their respective MySql/MariaDB databases is the easy part. For /var/lib/mailman3 it is a little less clear. So far I have symlinked messages, archives, lists, data, and templates onto the NFS share. I'm wondering about cache, locks, queue, and web/fulltext_index. Is there any standard or documented way of doing this? Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 1

Apache shows No Lists
by ceo＠sartrack.nz 24 May '23

24 May '23

Running Debian 11. I have 6 mailing lists, but Apache2 says there are no lists. I have not been able to set up Postorius because nowhere is any information on *where* the configuration file is supposed to be located. I have found an example in /usr/share/doc/python3-django-hyperkitty/examples/settings.py But I don't know if this example is the right one, and I have no idea where the final file should go...

3 10

mass remove pending confirmation
by Jens Günther 23 May '23

23 May '23

Running Mailman 3.3.8 with docker. ----- Since we migrate some lists from mailman2 to 3, there are a lot of new users/subscribers and an admin made the mistake to not checkbox the 3. option that the users don't need to verify their address. Now we have a long list of pending confirmations in different lists. Is there an easy way in the shell to mass remove these pending mailaddresses so that we don't have to do that one by one? That would be awsome. Regards, Jens.

4 5

Mailman3 / Exim4: Router fails
by ceo＠sartrack.nz 22 May '23

22 May '23

After updating my Linux server, my old Mailman 2.1 was wiped out. I now spend 2 full days desperately trying to get Mailman3 to work with Exim4 (and Apache2) Nothing works so far. At this point I am stuck with a failing Exim4 "Router" I have set Mailman3 to use Exim in the config. In Exim4 I have set all required Mailman3 options. But it fails with this: MM3_LISTCHK=/var/lib/mailman3/lists/${local_part}@${domain} (Email to: templist(a)sartrack.nz - The list exists in Mailman3) Exim4 debug: 19:15:47 100472 --------> mailman3_router router <-------- 19:15:47 100472 local_part=info domain=sartrack.nz 19:15:47 100472 checking domains 19:15:47 100472 sartrack.nz in "sartrack.nz"? yes (matched "sartrack.nz") 19:15:47 100472 data from lookup saved for cache for +mm_domains: key 'sartrack.nz' value 'sartrack.nz' 19:15:47 100472 sartrack.nz in "+mm_domains"? yes (matched "+mm_domains") 19:15:47 100472 checking require_files 19:15:47 100472 ╭considering: /var/lib/mailman3/lists/${local_part}@${domain} 19:15:47 100472 ├──expanding: /var/lib/mailman3/lists/${local_part}@${domain} 19:15:47 100472 ╰─────result: /var/lib/mailman3/lists/info(a)sartrack.nz 19:15:47 100472 ╰──(tainted) 19:15:47 100472 file check: /var/lib/mailman3/lists/${local_part}@${domain} 19:15:47 100472 expanded file: /var/lib/mailman3/lists/info(a)sartrack.nz 19:15:47 100472 stat() yielded -1 19:15:47 100472 errno = 2 19:15:47 100472 mailman3_router router skipped: file check Can somebody please help. I have no idea what is wrong here.

3 7

Is there a correct way to remove the "Are you sure you want to logout" screen?
by Mark London 21 May '23

21 May '23

Hi - Is there a correct way to remove the "Are you sure you want to logout" screen, after I select to logout? It seems so impossible to accidentally logout. And even if I did, it's just very easy to log back in. I did hack logout.html, and used jquery to automatically click the button. But that feels like a real hack. Although it does work. :) - Mark

1 0

Heads Up - Downtime
by Mark Sapiro 20 May '23

20 May '23

We are moving the server that supports this list and that which supports our wiki to a different cloud VPS. In conjunction with this, there will be some time beginning around 16:30 UTC and continuing for about an hour when lists.mailman3.org, www.list.org and wiki.list.org will be unavailable. During this down time, mail to <mailman-users(a)mailman3.org> should be queued in the respective MTAs and delivered when service is restored. Nothing should be lost. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 2