May 2021 - Mailman-users - lists.mailman3.org

Can't deliver mails in queue
by Nathanael Schneider May 20, 2021

May 20, 2021

Hello, I have stumbled upon some weird issues with my migration to mailman3.. I've followed the step by step instructions for installing mm3 manually in a venv with postfix and virtual aliases (if that is of any significance). Now the Problem is, that some lists don't deliver EMails at all. The list was one which I migrated with the mailman21 command. But the Mail I sent did not get through to no one and the mailman logs did not show anything. I then created a completely new List which did not exists in mm2.1, subscribed two addresses and sent myself an EMail. That one worked as intended. I then deleted the whole broken list and created it cleanly, added the same two people, sent an email and nothing. Did not show up in the Moderation Queue or anywhere. it also doesn't get shunted. It just never arrives. I then turned the log level to debug on the smtp module. And I only get the following statement, ever repeating, never ending: [...] May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb49b143780> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4974541d0> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4978db438> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb497f05f28> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4978adb38> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net [...] I have no clue what to do with this. I then turned the debug module loglevel to debug. Also nothing useful. Just an endless list of [...] May 19 18:17:29 2021 (7209) [outgoing] <function deliver at 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> May 19 18:17:29 2021 (7203) [ArchiveRunner] starting oneloop May 19 18:17:29 2021 (7203) [ArchiveRunner] ending oneloop: 0 May 19 18:17:29 2021 (7209) [OutgoingRunner] finishing filebase: 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd May 19 18:17:29 2021 (7209) [OutgoingRunner] doing periodic May 19 18:17:29 2021 (7209) [OutgoingRunner] committing transaction May 19 18:17:29 2021 (7209) [OutgoingRunner] checking short circuit May 19 18:17:29 2021 (7209) [OutgoingRunner] ending oneloop: 1 May 19 18:17:29 2021 (7209) [OutgoingRunner] starting oneloop May 19 18:17:29 2021 (7209) [OutgoingRunner] processing filebase: 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e May 19 18:17:29 2021 (7209) [OutgoingRunner] processing onefile May 19 18:17:29 2021 (7209) [outgoing] <function deliver at 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> [...] Which also tells me nothing I can understand. I have no clue what's going wrong. (I've turned on debugging both on the original member list and the reduced member list. Both hang on the first delivery they do). If I restart mailman, the message gets correctly shunted as it is interrupted mid-delivery. My maillogs don't register any activity beside the listpost. Any ideas what I need to do to figure out what's not working here or where the culprit could be? Not sure if it is related to the mailinglist being in mailman2.1 before. -- Nathanael Schneider

2 5

Bounce counter visibility for List Admins
by smorytko＠gmail.com May 19, 2021

May 19, 2021

As you may know, we use MM3 but the Affinity/Empathy flavor and we only have List Administrator using the Postorious/Affinity. Unlike many here, we have no access to any server-based files. Can someone tell me if Postorious gives list administrators visibility into the bounce counters? While List Admins get to set various bounce counters we have no visibility of those counters until, all of a sudden, an entire source of subscribers hits the bounce threshold and gets bounced off the list. It would be really nice to be able to see the bounce counters and possibly head off trouble before users/subscriber mail hosts. It can serve as an effective early warning system that something is wrong. Assuming Postorious cannot, is there another way List Admins can inspect bounce counters? Email command? Thanks - Steve

3 3

Re: [EXTERNAL] [Mailman-Users] Re: Help with 'The message has no valid senders'
by Mark Sapiro May 19, 2021

May 19, 2021

Putting this back on the list. On 5/19/21 9:46 AM, McGuire, Tommy M. (MSFC-IS90)[EAST2] wrote: >> -----Original Message----- >> From: Mark Sapiro <mark(a)msapiro.net> ... >> Have you set >> ``` >> [mailman] >> sender_headers: ... >> ``` >> in mailman.cfg?, and if so, to what? > > We have not changed it: > > [mailman] sender_headers: from from_ reply-to sender > > According to the smtp.log, there was an envelope sender ("MAIL FROM:.."), which matched the From header. In the example I'm looking at right now, the sender was not a member of the list, but the Accept these non-members box in the list settings has a regexp that matches the sender's domain. In another example from this morning, to a different list, the envelope sender and From header match, and is a member of the list. > > I don't see any obvious reason or configuration setting that would make either address invalid. First of all, the discard has nothing to do with whether the sender has any connection to the list. It only says the message had no sender at all. Assuming the message had a From: with a syntactically valid email address, this discard should not occur. Also, if the envelope (MAIL FROM:) was a syntactically valid email address, this discard should not occur. The address is validated by mailman/email/validate.py by first splitting it into `local_part`, `@`, `[domain_parts]` where domain_parts are the `between dots` parts of the domain and then validating the local_part and domain with regexps defined per > # What other characters should be allowed? > _valid_local = re.compile("[-0-9a-z!#$%&'*+./=?@_`{}~]", re.IGNORECASE) > # Strictly speaking, both ^ and | are allowed and others are allowed in quoted > # local parts, but this can open the door to certain web exploits so we don't > # allow them. > _valid_domain = re.compile('[-a-z0-9]', re.IGNORECASE) > # These are the only characters allowed in domain parts. Does the From: local part or the MAIL FROM: contain any characters not in the [-0-9a-z!#$%&'*+./=?@_`{}~] class? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

[Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/
by Mark Dadgar May 19, 2021

May 19, 2021

I have a user attempting to access the list archives and he’s generating this login error. I have verified that he does have a django account. I’ve never seen this one before and I didn’t find anything relevant in the lit archives. Any ideas what’s going on here? - Mark ----- mark(a)pdc-racing.net | 408-348-2878 ----------------------------------------------- From: noreply(a)pdc-racing.net Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/ Date: May 18, 2021 at 2:38:20 PM PDT To: mark(a)pdc-racing.net Internal Server Error: /accounts/login/ MultipleObjectsReturned at /accounts/login/ get() returned more than one EmailAddress -- it returned 2! Request Method: POST Request URL: https://mail.pdc-racing.net/accounts/login/ Django Version: 3.0.12 Python Executable: /opt/mailman/mm/venv/bin/python Python Version: 3.8.5 Python Path: ['/opt/mailman/mm', '/opt/mailman/mm/', '/opt/mailman/mm/bin', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/opt/mailman/mm/venv/lib/python3.8/site-packages'] Server time: Tue, 18 May 2021 14:38:20 -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') 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 (most recent call last): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/mm/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 "/opt/mailman/mm/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 "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/utils/decorators.py", line 43, in _wrapper return bound_method(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/views.py", line 146, in dispatch return super(LoginView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/views.py", line 74, in dispatch response = super(RedirectAuthenticatedUserMixin, self).dispatch( File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/views.py", line 102, in post response = self.form_valid(form) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/views.py", line 159, in form_valid return form.login(self.request, redirect_url=success_url) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/forms.py", line 195, in login ret = perform_login( File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/utils.py", line 174, in perform_login if not _has_verified_for_login(user, email): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/utils.py", line 134, in _has_verified_for_login emailaddress = EmailAddress.objects.get_for_user(user, email) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/managers.py", line 54, in get_for_user ret = self.get(user=user, email__iexact=email) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/query.py", line 419, in get raise self.model.MultipleObjectsReturned( Exception Type: MultipleObjectsReturned at /accounts/login/ Exception Value: get() returned more than one EmailAddress -- it returned 2! Request information: USER: AnonymousUser

2 4

OS upgrade - anything to take care of?
by Torge Riedel May 15, 2021

May 15, 2021

Dear MM3 users, today I upgraded one of two servers from Ubuntu 18.04 to 20.04 and - besides some minor config updates - postfix & dovecot worked well afterwards. So I am very optimistic that the upgrade of the second server from 18.04 to 20.04 will also work fine. But the second server is running MM3 (installed in venv) and I saw that on upgrade Python 3.8 is installed. Is there anything I have to take care of? Anything to do / change in venv? Kind regards Torge

4 10

Re: Core, Hyperkitty and Postorius releases
by Odhiambo Washington May 15, 2021

May 15, 2021

On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > > > On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > > /bin/sh: sass: Permission denied* > > > > Did you check the permissions on your sass binary? > My mailman installed in /opt/mailman/mm find /opt/mailman/ -type f -name sass yielded nothing! pip3 install sass generated so many errors then ended with: ERROR: Command errored out with exit status 1: /opt/mailman/mm/venv/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-cltizg93/sass_9783b9d070744303b5c04271674abc23/setup.py'"'"'; __file__='"'"'/tmp/pip-install-cltizg93/sass_9783b9d070744303b5c04271674abc23/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-1g2omozl/install-record.txt --single-version-externally-managed --compile --install-headers /opt/mailman/mm/venv/include/site/python3.7/sass Check the logs for full command output. I will have to blow away mailman and start afresh. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 17

Core, Hyperkitty and Postorius releases
by Abhilash Raj May 15, 2021

May 15, 2021

Hey Everyone, I am pleased to announce new stable releases for Mailman Core, Postorius, Hyperkitty. These include both new features and bug fixes. Complete change log for each components: Mailman Core 3.3.3: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… Postorius 1.3.4 https://docs.mailman3.org/projects/postorius/en/latest/news.html Hyperkitty 1.3.4 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Minimum supported Python version is 3.6. You can install them using: $ pip install --upgrade postorius hyperkitty mailman We have also recently been working on making the installation instructions[1] to be more detailed and added a new FAQ[2] section for administrators where I hope to capture common questions from mailman-users list. Feedback or Merge Requests to improve these docs are welcome. You can either send an email or open an issue on Gitlab (easier to track) here[3]. [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html [2]: https://docs.mailman3.org/en/latest/faq.html [3]: https://gitlab.com/mailman/mailman-suite-doc/issues Thanks to everyone who helped out with with this release and contributed if any way! :) thanks, Abhilash Raj On behalf of Mailman Core Team

4 10

Hyperkitty download mbox
by Andrew Hodgson May 14, 2021

May 14, 2021

Hi, Hyperkitty 1.3.4. I am trying to download a complete list mbox by going to all threads view and using the download option. I have tried a couple of tools (Gunzip and Winrar) and both are giving me an unexpected end of file when trying to decompress the gz file. Here is the list URL I am using: https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil… Any suggestions? Thanks. Andrew.

5 15

Sad news - Brian Carpenter
by smorytko＠gmail.com May 13, 2021

May 13, 2021

https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… I mentioned some "unfortunate circumstances" in a recent post. An inquiry from Mark Sapiro prompted me to do a search and I sadly found this. Brian's company managed our list and on 4/22 we became aware that he was hospitalized with Covid. Rest in peace Brian. Steve Morytko

7 6

Problems with New MM3 Installation
by Jeff May 12, 2021

May 12, 2021

After using Mailman 2 (and possibly 1 though I don’t remember) for almost 20 years, I have just upgraded to Mailman 3. I followed the instructions here: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… Things generally work, but I have run into a couple of small problems: 1) The uwsgi-error.log is filling with errors that seem to culminate in "ModuleNotFoundError: No module named ‘settings’”. My settings.py is located in “/etc/mailman3” and seems to be found by other components of MM3. This error must be coming from the cron jobs. Does anyone have any ideas how to fix this problem? 2) While old messages were imported without issue, new emails are not being archives. I see them in: mailman3/mm/var/archives/prototype/[listname]@[domain]/new But they are not being delivered. I have added this to my mailman.cfg: [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /usr/local/mailman3/mailman-hyperkitty.cfg And created the "/usr/local/mailman3/mailman-hyperkitty.cfg” as such: base_url: http://localhost/archives/ api_key: [key that matches “MAILMAN_ARCHIVER_KEY” in my settings.py] Some documentation says that the url should be "http://localhost/hyperkitty/“, but url generates a page not found error on my setup while the archives are available at the “archives” url. I would greatly appreciate any assistance with these two issues. Thanks much, Jeff

4 7