- Mailman-users - lists.mailman3.org

KeyError: 'subject_prefix'
by Torge Riedel 18 Nov '20

18 Nov '20

Hi, today I had the following error in my inbox: KeyError: 'subject_prefix' AttributeError: 'MailingList' object has no attribute 'subject_prefix' I checked the database, there is a column "subject_prefix", so I feel it is something in the code causing the error. It's mailman 3.3.1 and I don't see a fix for such an error in the Changes of 3.3.2 Kind regards Torge Traceback (most recent call last): File "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'subject_prefix' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/models/mailinglist.py", line 197, in update_from_mailman value = getattr(mm_list, propname) File "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'MailingList' object has no attribute 'subject_prefix' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/web/venv/lib/python3.6/site-packages/django_extensions/management/commands/runjobs.py", line 36, in runjobs job().execute() File "/opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/jobs/sync_mailman.py", line 36, in execute sync_with_mailman() File "/opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/lib/mailman.py", line 132, in sync_with_mailman mlist.update_from_mailman() File "/opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/models/mailinglist.py", line 199, in update_from_mailman value = mm_list.settings[propname] File "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) File "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] File "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 500: <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) START TRACEBACK: END TRACEBACK

3 6

Templates
by Odhiambo Washington 18 Nov '20

18 Nov '20

Hello good people, So today I decided that I should be looking at MM3 to see how far it can take me. I started from the templates and created one for a footer for non-digest messages. When I sent a test mail to the list I am using for testing, the following errors popped up: --- Logging error --- Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/model/template.py", line 110, in get contents = protocols.get(actual_uri, **auth) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/utilities/protocols.py", line 39, in get response.raise_for_status() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/requests-2.24.0-py3.7.egg/requests/models.py", line 941, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://localhost:8000/mm3/mailman3/api/templates/list/kictanet-2.lists.kict… During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/core/logging.py", line 76, in emit msg = self.format(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 869, in format return fmt.format(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 611, in format s = self.formatMessage(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 580, in formatMessage return self._style.format(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 422, in format return self._fmt % record.__dict__ KeyError: 't' Call stack: File "/opt/mailman/mm/venv/bin/runner", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.3b1', 'console_scripts', 'runner')()) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click-7.1.2-py3.7.egg/click/core.py", line 829, in __call__ return self.main(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click-7.1.2-py3.7.egg/click/core.py", line 782, in main rv = self.invoke(ctx) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click-7.1.2-py3.7.egg/click/core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click-7.1.2-py3.7.egg/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click-7.1.2-py3.7.egg/click/decorators.py", line 21, in new_func return f(get_current_context(), *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/bin/runner.py", line 188, in main runner.run() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/core/runner.py", line 134, in run filecnt = self._one_iteration() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/mta/deliver.py", line 86, in deliver refused = agent.deliver(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/mta/base.py", line 167, in deliver callback(mlist, message_copy, msgdata_copy) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/mta/decorating.py", line 32, in decorate decorator.process(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/handlers/decorate.py", line 264, in process process(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/handlers/decorate.py", line 89, in process footer = decorate('list:member:regular:footer', mlist, d) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/handlers/decorate.py", line 226, in decorate template = getUtility(ITemplateLoader).get(name, mlist, **extradict) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/model/template.py", line 189, in get name, lookup_context, **substitutions) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/model/template.py", line 118, in get actual_uri, auth.get('auth', '<no authorization>'))) File "/usr/local/lib/python3.7/logging/__init__.py", line 1413, in exception self.error(msg, *args, exc_info=exc_info, **kwargs) File "/usr/local/lib/python3.7/logging/__init__.py", line 1407, in error self._log(ERROR, msg, args, **kwargs) File "/usr/local/lib/python3.7/logging/__init__.py", line 1514, in _log self.handle(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 1524, in handle self.callHandlers(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 1586, in callHandlers hdlr.handle(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 894, in handle self.emit(record) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/core/logging.py", line 85, in emit self.handleError(record) Message: 'Cannot retrieve template at http://localhost:8000/mm3/mailman3/api/templates/list/kictanet-2.lists.kict… (<no authorization>)' Arguments: () I am unable to guess the cause of this. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

2 3

warning: database postfix_domains.db is older than source file postfix_domains
by Torge Riedel 15 Nov '20

15 Nov '20

Hi, I frequently get this warning mail.log. stat'ing the files give: # stat /opt/mailman/var/data/postfix_domains File: /opt/mailman/var/data/postfix_domains Size: 361 Blocks: 8 IO Block: 4096 regular file Device: 801h/2049d Inode: 1573095 Links: 1 Access: (0660/-rw-rw----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) Access: 2020-10-24 19:52:16.887258326 +0200 Modify: 2020-10-20 07:09:48.792000000 +0200 Change: 2020-10-20 07:09:48.792000000 +0200 Birth: - # stat /opt/mailman/var/data/postfix_domains.db File: /opt/mailman/var/data/postfix_domains.db Size: 12288 Blocks: 24 IO Block: 4096 regular file Device: 801h/2049d Inode: 1583965 Links: 1 Access: (0640/-rw-r-----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) Access: 2020-10-26 07:46:54.569935782 +0100 Modify: 2020-10-20 07:09:47.575889000 +0200 Change: 2020-10-20 07:09:47.575889000 +0200 Birth: - I do not have the feeling that this is really a problem, cause everything works well. But it is confusing and misleading and might makes me missing a problem in the future, when the database is really outdated. Could this be easily fixed in mailman? It's mailman core 3.3.1. Kind regards Torge

3 6

MIMEDefang to fix footers
by Ryan Morash 15 Nov '20

15 Nov '20

Does anyone know how to use MIMEDefang to fix the footer as attachment issue when using Mailman3? I've seen several guides/scripts referring to its use with Mailman2, but I'm unsure of how they would match with Mailman 3. Other ways of fixing this issue are also welcome. Ryan Morash IT Support Technician Questar III BOCES Confidential Transmission This correspondence is confidential and may contain privileged materials or information. It is intended for the use of the addressee only and all others are prohibited from copying or disseminating this message or its contents. If you have received this transmission in error, delete it immediately and notify the sender.

3 2

Hyperkitty Error Curiosity
by Brian Carpenter 12 Nov '20

12 Nov '20

Hello Everyone, There was a message sent to a list that could not be archived by Hyperkitty for the following reason: WARNING 2020-11-03 17:20:54,507 800 hyperkitty.views.mailman Could not archive the email with message-id '<67BEBD75-B3DC-45E3-9C2F-55482F811238(a)ispdomain.com>': A string literal cannot contain NUL (0x00) characters. It looks like there was a problem with the email message itself. What causes such an error? Thank you for any insight. -- Brian Carpenter Harmonylists.com Emwd.com

2 8

digest summary heavily cluttered with hrml code
by Mohsen Masoudfar 11 Nov '20

11 Nov '20

Hi, I am running Mailman 3.1.1 on Ubuntu 18.04. The user complains that the digest summary is cluttered with HTML code. I thought, I may fix it by: Members > {user} > Member options > Delivery mode set to [Plain Text Digest]. After setting the value and clicking [save changes], I tried to check the value by getting back to Members setting for the user, it shows the value as "Regular", which was the value before I tried to update it. Question 1: How may I be sure that the value is set, if it is set? Question 2: How may set it for all members of the list? Question 3: Is there a CLI way to do this? I tried "mailman members " command. But it seems not supporting this option. Any help is much appreciated. Thanks Mohsen

2 4

How to Increase outgoing mail volume for Mailman 3
by Brian Carpenter 10 Nov '20

10 Nov '20

Hello everyone, We had a new client come on board that brought a list that had the largest out-going mail volume that I have ever dealt with. So I did what any sane server administrator would do that is running Mailman 3: I ran to Mark Sapiro for help! Here is what the Sage of all things Mailman counseled me to do: 1. Disabled VERP delivery. VERP can help improve mail delivery by delivering 1 message per SMTP transaction (I think I got that right). Using VERP is counter-productive as it can seriously delay outgoing mail delivery for a high-volume list. So you can use something like the following in the MTA section of your mailman.cfg: [mta] verp_confirmations: no verp_personalized_deliveries: no verp_delivery_interval: 0 2. I configured Mailman 3 to run 4 outgoing runners. The default is 1. This action was the game changer. It allows Mailman to handle 4 incoming messages at a time instead of 1. My client's incoming list volume was high enough where it was overwhelming the single outgoing runner. Here is what I added to the mailman.cfg file: [runner.out] instances: 4 Doing this step immediately solved the backlog in var/queue/out. 3. If you start up with a new server for a list that is high volume then keep an eye out for Proofpoint and Vade Security as they will block your new IP address quicker than Mark Sapiro can say "This is a bug. See <some Gitlab.com url>" Mark, thank you! -- Brian Carpenter Harmonylists.com Emwd.com

3 7

members list in Postorius
by Peter Münster 10 Nov '20

10 Nov '20

Hi, Where can I display the members list of a mailing list please? The setting of "Members List Visibility" is "Only mailing list members". So I guess that a member should be able to see the members list somewhere... I'm using Postorius 1.3.3 and Mailman 3.3.1. TIA for any help, -- Peter

2 1

Mailman3 don't work if aliases are enabled
by Massimo Zappalà 09 Nov '20

09 Nov '20

Hi everybody, Using the following postfix configuration file, email messages and mailing lists works fine with mailman3. But if I send an email to an alias, the message is not received. My main.cf alias_maps = hash:/etc/aliases compatibility_level = 2 content_filter = amavis:[127.0.0.1]:10024 inet_protocols = ipv4 local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp mailbox_size_limit = 0 message_size_limit = 20480000 milter_default_action = accept milter_protocol = 2 myhostname = glugct.catania.linux.it non_smtpd_milters = inet:localhost:12301 owner_request_special = no recipient_delimiter = + relay_domains = smtp_header_checks = regexp:/etc/postfix/header_checks smtp_mime_header_checks = regexp:/etc/postfix/header_checks smtp_tls_CApath = /etc/ssl/certs smtp_tls_cert_file = $smtpd_tls_cert_file smtp_tls_key_file = $smtpd_tls_key_file smtp_tls_security_level = may smtp_use_tls = yes smtpd_banner = $myhostname ESMTP smtpd_milters = inet:localhost:12301 smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_hostname, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_unauth_destination, check_policy_service inet:[127.0.0.1]:10023, reject_rbl_client zen.spamhaus.org, reject_rbl_client bl.spamcop.net, reject_rbl_client cbl.abuseat.org, permit smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot smtpd_tls_CApath = /etc/ssl/certs smtpd_tls_cert_file = /etc/letsencrypt/live/mail.catania.linux.it/fullchain.pem smtpd_tls_eecdh_grade = strong smtpd_tls_key_file = /etc/letsencrypt/live/mail.catania.linux.it/privkey.pem smtpd_tls_security_level = may tls_preempt_cipherlist = yes transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp virtual_gid_maps = static:5000 virtual_mailbox_base = /var/vmail virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_mailbox_domains.cf virtual_transport = lmtp:unix:private/dovecot-lmtp virtual_uid_maps = static:5000 #virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_emails.cf, mysql:/etc/postfix/mysql_virtual_alias_maps.cf #virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf ----------------------------------------------------------------------------------------- My /etc/postfix/mysql_virtual_alias_emails.cf user = postfix password = postfixpass hosts = 127.0.0.1 dbname = postfix query = SELECT email FROM users WHERE email='%s' ----------------------------------------------------------------------------------------- My /etc/postfix/mysql_virtual_alias_maps.cf user = postfix password = postfixpass hosts = 127.0.0.1 dbname = postfix query = SELECT destination FROM aliases WHERE source='%s' ----------------------------------------------------------------------------------------- My /etc/postfix/mysql_virtual_mailbox_domains.cf user = postfix password = postfixpass hosts = 127.0.0.1 dbname = postfix query = SELECT 1 FROM domains WHERE domain='%s' ----------------------------------------------------------------------------------------- My /etc/postfix/mysql_virtual_mailbox_maps.cf user = postfix password = postfixpass hosts = 127.0.0.1 dbname = postfix query = SELECT 1 FROM users WHERE email='%s' ----------------------------------------------------------------------------------------- If I try to uncomment the last two rows in main.cf virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_emails.cf, mysql:/etc/postfix/mysql_virtual_alias_maps.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf The aliases and email messeges works fine but the mailman3's mailinglist don't work. How can I solve this? Thank You in advance.

2 2

Digest Formatting
by mailman＠manygoodideas.com 07 Nov '20

07 Nov '20

It appears that a digest is formatted as: list:member:digest:masthead 1. Thread 1 ... N. Thread N foreach thread list:member:digest:header thread list:member:digest:footer A number of my testers are complaining about the formatting: 1) it's hard to visually identify each of the threads (the TOC numbers them, but the numbers aren't shown next to each thread, for example) and 2) it's hard for a novice to know how to reply to a digest thread I'm wondering how other admins have customized their digests to make them more useful. For example, if there was a way in list:member:digest:header to display a link to the archived thread, that would be a good start. list:member:digest:header could emit a horizontal line to separate each thread, but it would be nice to be able to show the number of the thread, etc. Yahoo! Groups used to send out HTML digests that had the thread titles nicely distinguished, live links to the thread, and links to Reply to sender, Reply to All, etc. Thanks for any suggestions!

4 8