- Mailman-users - lists.mailman3.org

Where do I find the check_hk_archive script
by Lars Bjørndal Nov. 19, 2023

Nov. 19, 2023

In https://docs.mailman3.org/en/latest/migration.html I'm adviced to run the check_hk_archive script found in hyperkitty/contrib. When trying `git clone https://gitlab.com/mailman/hyperkity`I get: Username for 'https://gitlab.com': Is it possible to get the script without an account on gitlab? Thanks, Lars -- Lars Bjørndal <lars(a)lamasti.net> Ostadalsveien 64, 0753 Oslo. Mobil: 958 37 537

2 3

configuration to send to recipients in a spread out manner to avoid being considered spam
by testeur Nov. 19, 2023

Nov. 19, 2023

Hi, I s there a mean to configure the list for that emails be sent to recipients in a spread out manner to avoid being considered spam ? cause AOL, YAHOO seems to consider emails sent to recipients as spam or an "Excessively high volume of emails". there's just 40 (aol, yahoo) emails suscribed to the list. thx.

2 2

How to Personalise Email Content with Usernames in Mailman 3
by Zaheer Abbas Nov. 18, 2023

Nov. 18, 2023

Hello, I am currently working with Mailman 3 and looking to enhance the personalization of the emails sent through our mailing list. Specifically, I wish to include the recipient's username in the email content, similar to a personalized greeting (e.g., "Dear [username]"). My questions are: 1. Does Mailman 3 support the inclusion of personalized data (like usernames)? 2. If yes, how can I do that? Is there any placeholder for that? Any guidance or suggestions on how to achieve this would be greatly appreciated. Thank you for your time and assistance.

3 4

Add rule to auto-discard "AutoReply" messages from list members
by Thomas Ward Nov. 18, 2023

Nov. 18, 2023

When people are communicating on Mailman3 lists, some set up automatic responders for out-of-office, etc. and get let through the system to list recipients. Unfortunately, this is bad behavior and appears to not be caught by default. I'd like to set up some kind of rule globally rather than per-list that would check if a message is an automatic reply (based on a set of criteria we've come up with programmatically on our previous custom implementation of lists) and then default-discard those messages. Is there a way with custom rules to implement this? We're looking for certain strings on the subject line or other headers to determine "Discard" cases in our custom list implementations, but we are hoping we can implement this with customized rules in Mailman3 to achieve this goal. How would we structure that type of rule, and do we check the message object or the msgdata instead? Thomas

5 6

Possible SQLAlchemy 2.0.23 incompatibility (requires investigation)
by Jered Floyd Nov. 15, 2023

Nov. 15, 2023

I just did a container rebuild and Mailman failed to load, with the below errors on the console. Pinning SQLAlchemy 2.0.22 resolved this; I haven't tried to further debug. (2.0.23 was release on November 3.) --Jered Traceback (most recent call last): File "/opt/app-root/src/.local/bin/mailman", line 8, in <module> sys.exit(main()) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/commands/cli_control.py", line 109, in start call_name(config.mta.incoming).regenerate() File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/mta/postfix.py", line 109, in regenerate self._generate_lmtp_file(fp) File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/mta/postfix.py", line 148, in _generate_lmtp_file for list_name, mail_host in list_manager.name_components: File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/model/listmanager.py", line 140, in name_components for mail_host, list_name in result_set.with_entities( File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 2833, in __iter__ result = self._iter() File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 2847, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 2308, in execute return self._execute_internal( File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 2180, in _execute_internal conn = self._connection_for_bind(bind) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 2047, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) File "<string>", line 2, in _connection_for_bind File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 1143, in _connection_for_bind conn = bind.connect() File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 3268, in connect return self._connection_cls(self) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 145, in __init__ self._dbapi_connection = engine.raw_connection() File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 3292, in raw_connection return self.pool.connect() File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/pool/base.py", line 452, in connect return _ConnectionFairy._checkout(self) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/pool/base.py", line 1378, in _checkout del fairy File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/pool/base.py", line 1306, in _checkout result = pool._dialect._do_ping_w_event( File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 709, in _do_ping_w_event return self.do_ping(dbapi_connection) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/dialects/mysql/pymysql.py", line 104, in do_ping if self._send_false_to_ping: File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/util/langhelpers.py", line 1146, in __get__ obj.__dict__[self.__name__] = result = self.fget(obj) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/dialects/mysql/pymysql.py", line 93, in _send_false_to_ping insp = langhelpers.get_callable_argspec(Connection.ping) AttributeError: 'function' object has no attribute 'ping'

1 1

Database problem after system upgrade
by Lars Bjørndal Nov. 15, 2023

Nov. 15, 2023

I've upgraded from Fedora 37 to 38, and the postgresql server will not start: nov. 14 23:22:18 dalen.lamasti.net postgresql-check-db-dir[1410]: An old version of the database format was found. nov. 14 23:22:18 dalen.lamasti.net postgresql-check-db-dir[1410]: Use 'postgresq l-setup --upgrade' to upgrade to version '15' nov. 14 23:22:18 dalen.lamasti.net postgresql-check-db-dir[1410]: See /usr/share /doc/postgresql/README.rpm-dist for more information. When I run `postgresql-setup --upgrade` I get: runuser: warning: cannot change directory to /opt/postgresql: no such file or directory * Upgrading database. /usr/bin/postgresql-setup: line 307: cd: /opt/postgresql: no such file or directory ERROR: pg_upgrade tool failed ERROR: Upgrade failed. * See /var/lib/pgsql/upgrade_postgresql.log for details. Why does the upgrade tool look for files in /opt/postgresql and not in /var/lib/pgsql? How to fix it? Thanks, Lars

3 6

Mailserver Log entries following through mailman?
by Andreas Barth Nov. 11, 2023

Nov. 11, 2023

Hi, is there some way to find an ID to follow an email through mailman? In the exim logfile there is only something like C="250 Ok" (whereas in mails sent to another exim there is something like C="250 OK id=…"). (What I sometimes need to do is to follow an mail whether it is sent through mailman and to where.) Or should I raise an issue as whishlist request? Regards, Andi

3 3

ModuleNotFoundError: No module named 'mailman_web'
by gordon＠dickens.com Nov. 10, 2023

Nov. 10, 2023

I have had mailman3 working great on Debian 11, however, I just upgraded to Debian 12 and, following the upgrade, mailman3 is not working and I am getting the following error message: ModuleNotFoundError: No module named 'mailman_web' Does anybody have any recommendations? Thanks! Gordon

5 24

Default templates
by Steve Brown Nov. 10, 2023

Nov. 10, 2023

I'm new to this list and newly a Mailman list administrator. I know I can customize message templates and have done so for my list's Welcome message. My problem is knowing what I'm replacing when I create a "new" template. How/where can I see he default content? Steve Brown

2 2

user disabled other problems
by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia Nov. 6, 2023

Nov. 6, 2023

Good morning, I have to understand something more about disabled users. I renabled some users, but they continue to non teceive the newsletter. Is there a more detailed log that I can analize to discover dis problem? Thank you -- Roberto Burceni Servizio informatico sezionale Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00 E-mail: servizioinformatico(a)uicibrescia.it Sito web: https://www.uicibrescia.it

4 5