June 2020 - Mailman-users - lists.mailman3.org

Mailman 3.2.0 Hyperkitty fulltext index error
by Marvin Gülker July 31, 2020

July 31, 2020

Hi, I've just upgraded to Mailman 3.2.0 (finally everything Python 3 now, thanks!) and it appears to work. However, there's a repeating error message in mailman-suite's logfile for Hyperkitty that looks like this: ERROR 2018-07-12 14:28:33,895 2742 hyperkitty.lib.utils Failed to update the fulltext index: ord() expected a character, but string of length 0 found Traceback (most recent call last): File "/home/mailman/env3/lib/python3.5/site-packages/hyperkitty/lib/utils.py", line 179, in run_with_lock fn(*args, **kwargs) File "/home/mailman/env3/lib/python3.5/site-packages/hyperkitty/search_indexes.py", line 115, in update_index update_cmd.update_backend("hyperkitty", "default") File "/home/mailman/env3/lib/python3.5/site-packages/haystack/management/commands/update_index.py", line 276, in update_backend last_max_pk=max_pk) File "/home/mailman/env3/lib/python3.5/site-packages/haystack/management/commands/update_index.py", line 97, in do_update backend.update(index, current_qs, commit=commit) File "/home/mailman/env3/lib/python3.5/site-packages/haystack/backends/whoosh_backend.py", line 178, in update self.setup() File "/home/mailman/env3/lib/python3.5/site-packages/haystack/backends/whoosh_backend.py", line 126, in setup self.index = self.storage.open_index(schema=self.schema) File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/filedb/filestore.py", line 176, in open_index return indexclass(self, schema=schema, indexname=indexname) File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/index.py", line 421, in __init__ TOC.read(self.storage, self.indexname, schema=self._schema) File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/index.py", line 632, in read check_size("int", _INT_SIZE) File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/index.py", line 626, in check_size sz = stream.read_varint() File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/filedb/structfile.py", line 191, in read_varint return read_varint(self.read) File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/util/varints.py", line 102, in read_varint b = ord(readfn(1)) TypeError: ord() expected a character, but string of length 0 found The error repeats every minute, so I suppose it comes from the minutely cronjob. This cronjob looks like this: * * * * * mailman bash -c 'cd /home/mailman && . /home/mailman/env3/bin/activate && django-admin runjobs minutely --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' What's wrong here? Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

3 3

Update a member's display_name
by Nick Wynja July 8, 2020

July 8, 2020

Hi all, I want to update some list member's display_name either with mailman shell or mailmanclient. These mostly aren't users in Postorius so I only want to operate on the subscribed list member. I've tried everything I can find in the docs and am stuck. I've tried using `user_manager.get_user()` and then updating `user.display_name` followed by a `commit()` but it doesn't seem to persist the change. The `absorb_existing` flag for mailmanclient's `User.add_address()` looks promising but the docs read "It will import the existing user into the current one, not overwriting any previously set value." which in some cases, the member already has a display_name set. I haven't tried this yet. I'd appreciate any help pointing in the right direction. Thanks, Nick

5 10

Error after HyperKitty 1.3.x upgrade
by Florian Schulze July 6, 2020

July 6, 2020

Hi! After upgrading to HyperKitty 1.3.x I get the following error for qcluster: File ".../lib/python3.7/site-packages/django_q/cluster.py", line 300, in pusher task = SignedPackage.loads(task[1]) File ".../lib/python3.7/site-packages/django_q/signing.py", line 31, in loads serializer=PickleSerializer) File ".../lib/python3.7/site-packages/django_q/core_signing.py", line 38, in loads return serializer().loads(data) File ".../lib/python3.7/site-packages/django_q/signing.py", line 44, in loads return pickle.loads(data) AttributeError: Can't get attribute 'process_task_result' on <module 'hyperkitty.tasks' from '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> How do I recover from that? It seems like there are still persisted tasks in the qcluster queue using the old code from 1.2.x with the old locking implementation. Regards, Florian Schulze

2 4

Using external services for deliverability?
by tom＠gather.coop July 4, 2020

July 4, 2020

I have a Mailman 3 server up and running but I'm terrified to migrate to it from my existing Mailman 2 provider for fear that services like Gmail will randomly start blacklisting my IP with little I can do about it. I have SPF records set up so I'm hoping I'll be Ok but I'd like to have a backup plan. Has anyone ever tried using an external service like Mailgun or Sendgrid as a relay? I tried both but couldn't get either to work due to their sender authentication mechanism. They want all 'From:' headers to be from domains that are pre-authenticated as senders. But Mailman keeps the 'From' header from the original sender so it won't match any authenticated domains. Right? Is there anything to be done here or do I just have to migrate and pray?

3 6

Example Logrotate files for Mailman3
by Andrew Hodgson July 3, 2020

July 3, 2020

Hi, Does anyone have any usable Logrotate files for Mailman3 (especially for the web stuff)? Will look to create my own if no one comes forward but if anyone has anything they are willing to share it would be fab. Thanks. Andrew.

2 2

clarifying configuration
by trewtus+200629maitr＠gmail.com June 30, 2020

June 30, 2020

Hey Team, I'm new to Mailman and after some failed attempts to install from git on CentOS8, I have just installed it on Ubuntu 20.04 using mostly aptitude. But it's not quite working and I want to increase the log level to better understand the problem. I did see another post that suggested that I add to /etc/mailman3/mailman.cfg [logging.template] level: debug But that doesn't work for me. For example, after using that `mailman conf` doesn't list and debug values and as far as I can tell, the service, even after restarting, is not logging any more than it was. On the other hand, if I add [logging.smtp] level: debug Invoking `mailman conf` will reflect that new loglevel. This started me down the path of trying to figure out the configuration system of mailman in hope that that will save me time down the road. I have read https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html but that doesn't seem to agree with what I'm seeing. For an additional example, my mailman.cfg file has a "logging.debian" section, but I don't see that section listed in the `mailman conf` output. Why would that be? I don't see in the documentation if `mailman conf` only sees values after the service is restarted. Nevertheless, restarting mailman hasn't helped. What guidance can you give? Context: `mailman info` produces: GNU Mailman 3.2.2 (La Villa Strangiato) Python 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] config file: /etc/mailman3/mailman.cfg db url: sqlite:////var/lib/mailman3/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:KI5TuWE/v.....

2 1

Moderation of posts via email is not working in mailman 3
by Shashikanth Komandoor June 30, 2020

June 30, 2020

Hi Team, In mailman 2, few of my users used to approve the held messages through the mail by writing Approved: header and the password of the list in the first line of the reply mail to the "confirm" attachment in the mail notification of the held messages. But after I started migrating my distribution lists from mailman 2 to mailman 3, my users are complaining that they could not approve the posts or the held messages through the mail as they usually do while they were browsing their lists in mailman 2. Is there any bug or limitation in mailman 3 or if I am doing any wrong at the server side? Please suggest. -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 3

User settings triggers error
by Mark Dadgar June 29, 2020

June 29, 2020

If one of my users (including admin) goes to their user drop-down in the upper-right of Postorius and clicks Mailman Settings, it triggers an error: Here’s the error log: Internal Server Error: /mailman3/postorius/accounts/subscriptions/ KeyError at /postorius/accounts/subscriptions/ 'file' Request Method: GET Request URL: https://mail.pdc-racing.net/mailman3/postorius/accounts/subscriptions/ <https://mail.pdc-racing.net/mailman3/postorius/accounts/subscriptions/> Django Version: 2.2.12 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.2 Python Path: ['.', '', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Tue, 16 Jun 2020 10:31:56 -0700 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py" in _wrapped_view 21. return view_func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/user.py" in user_subscriptions 307. memberships = [m for m in mm_user.subscriptions] File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py" in subscriptions 62. for address in self.addresses: File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in __iter__ 221. for entry in self.rest_data: File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in rest_data 197. response, content = self._connection.call(self._url) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call 99. raise HTTPError(url, response.status, content, response, None) During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/postorius/middleware.py" in __call__ 39. return self.get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 36. response = response_for_exception(request, exc) File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in response_for_exception 91. log_response( File "/usr/lib/python3/dist-packages/django/utils/log.py" in log_response 222. getattr(logger, level)( File "/usr/lib/python3.8/logging/__init__.py" in error 1463. self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.8/logging/__init__.py" in _log 1577. self.handle(record) File "/usr/lib/python3.8/logging/__init__.py" in handle 1587. self.callHandlers(record) File "/usr/lib/python3.8/logging/__init__.py" in callHandlers 1649. hdlr.handle(record) File "/usr/lib/python3.8/logging/__init__.py" in handle 950. self.emit(record) File "/usr/lib/python3/dist-packages/django/utils/log.py" in emit 119. reporter = ExceptionReporter(request, is_email=True, *exc_info) File "/usr/lib/python3/dist-packages/django/views/debug.py" in __init__ 254. self.template_info = getattr(self.exc_value, 'template_debug', None) File "/usr/lib/python3.8/tempfile.py" in __getattr__ 607. file = self.__dict__['file'] Exception Type: KeyError at /postorius/accounts/subscriptions/ Exception Value: 'file' Request information: USER: admin GET: No GET data POST: No POST data FILES: No FILES data Anyone got a solution to this? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 21

Server 500 error for just one list, just one page
by kelly.close＠lrewater.com June 28, 2020

June 28, 2020

I am having a curious problem with just ONE list management page for ONE list on my server. Every other list I've checked, and every other management page for this affected list, seem fine. But when I go to the Subscribers page for this one list I get a Server 500 error, and I can't find anything in the apache or mailman logs to give me a clue (granted I'm not sure I know for sure where all the different logs are). So specifically this page: https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org… For a list called "alarms-all" obviously. Any ideas? I'm able to review the list, it's members, etc in the PostsgreSQL tables and I'm not seeing any members with funky characters in their address - the one thing I could think of to check. Thanks, ~Kelly

2 1

Null sender?
by tom＠gather.coop June 28, 2020

June 28, 2020

Does Mailman generally send email with a null sender? This is what I see in the log: Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) handling connection Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'LHLO mail.example.coop' Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'MAIL FROM:<>' Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) sender: <> Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'RCPT TO:<techque-bounces(a)example.org>' Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) recip: techque-bounces(a)example.org Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'DATA' Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'QUIT' Notice the empty MAIL FROM. Sendgrid seems to be choking on that because it needs to check if sending domain has been validated. If there is no sending domain it seems to reject. Why does Mailman do this? Can it be changed? I've been trying to find the relevant section of the code to no avail.

2 3