- Mailman-users - lists.mailman3.org

no bounce-processing with verp_probes: yes
by Stefan Bauer Dec. 7, 2023

Dec. 7, 2023

Dear Users, during one of our upgrades to 3.3.x we set verp_probes: yes according to upgrade notes[1]. However it looks like this disabled bounce handling completely. Howto verify (MM 3.3.9): Set verp_probes: yes verp_delivery_interval: 1 restart mailman3 create test-list add an undeliverable recipient to the list that is known to bounce. send 6 mails to list. see, that all the bounce-messages are received by mailman according to postfix log[2] check bounce.log - no entry. get bounce_score from API[3] - shows bounce_score 0. Can anyone confirm? Any help is greatly appreciated. Thank you. Stefan [1] https://docs.mailman3.org/en/latest/upgrade-3.2.html [2] from=<>, size=8565, nrcpt=1 (queue active) ... to=<v-test-bounces+undeliverable-recipient=realdomain.tld(a)lists.lists.tld>, relay=127.0.0.1[127.0.0.1]:8024 status=sent [3] curl -s -q --user a:b http://localhost:8001/3.1/members/find?subscriber=undeliverable-recipient@r…

2 2

Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line
by Thomas Ward Dec. 6, 2023

Dec. 6, 2023

We use a multi-hop SMTP system to go from the inside of our network out to the Internet at the domain test.lists.example.com. The setup is this way for ingress: {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 Connector) -> Mailman for delivery to listserv Egress is this: Mailman -> Postfix SMTP Relay (smtpproxy) -> INTERNET -- When a message is sent an invalid list (we'll call it invalid(a)test.lists.example.com) we end up with a nasty side effect in the system. The "no such recipient" response gets sent to the smtpproxy machine and then *it gets redelivered back to Mailman* as a redelivery as if it isn't accepting a permanent-failure condition code. This results in a nasty mail loop that results with a "too many hops" error that doesn't state "invalid recipient" and I have no idea why this is the case. Can anyone provide any insight into how to prevent this type of routing loop caused by the egress of messages? Thomas

2 4

mailman_web/urls.py changes in Postorius 1.3.10
by Lieuallen, Thomas Otis Dec. 5, 2023

Dec. 5, 2023

The latest release of Postorius includes these lines in mailman_web/urls.py: # Include alternate Postorius and HyperKitty URLs. path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), It appears that these paths override the originals (/mailman3 & /archive). I’m using apache and have had to add ProxyPass lines for these new alternate URLs, as /mailman3 and /archive don’t appear to be presented anymore by mailman-web. All the links at the top (Postorious, lists, domains, bans, system info, users, and archives) – all have /postorius or /hyperkitty as the start of their URLs. If I make a copy of that urls.py in /etc/mailman3 and point to it with ROOT_URLCONF – and comment out those alternate lines, the links go back to the way they were (/mailman3 and /archives). Or, as I mentioned, I can add the ProxyPass lines for /postorius and /hyperkitty to apache. One way or another, it doesn’t seem to be behaving as an alternate. Or have I overlooked something? Thank you Tom Lieuallen

2 1

Error message from monthly cronjob
by Johannes Rohr Dec. 5, 2023

Dec. 5, 2023

Dear all, Mailman3 on my system is installed in virtualenv. Each month I get the following error message. This error does not seem to have a serious impact on the functioning of mailman, still, what does it mean and how do I get rid of it? Thanks for any hints! Johannes -------- Weitergeleitete Nachricht -------- Betreff: Cron <mailman@*** /opt/mailman/venv/bin/mailman-web runjobs monthly Datum: Fri, 1 Dec 2023 05:56:40 +0100 (CET) Von: Cron Daemon <root(a)mail.rooot.de> An: mailman@*** ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django_extensions/management/commands/runjobs.py", line 40, in runjobs job().execute() File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/jobs/update_and_clean_index.py", line 37, in execute run_with_lock(update_index, remove=True) File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/utils.py", line 177, in run_with_lock with lock: File "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ self.unlock() File "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 420, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked

2 1

Does anyone use b4 tool with Mailman3 archive
by Prasanth Nair Dec. 5, 2023

Dec. 5, 2023

Hello all, I know this may not be the right place to ask. But, just in case someone has any experience using the b4 tool (https://github.com/mricon/b4) with the Mailman3 archives? Any idea, how to configure this tool to receive patch series from a mailman archive list? This tool is mainly used for the following purposes: - Retrieve patch series from a public mailing list (e.g. lore.kernel.org) - Compare patch series - Apply patch series to the git repository - Retrieve code-review trailers Kind regards, Prasanth Nair

2 2

nextcloud as auth provider for postorius
by mailman3＠huckley.de Dec. 2, 2023

Dec. 2, 2023

Hello, have anybody successful setup nextcloud auth provider for postorius? I have done configured the OAuth 2.0-Client in nextcloud/index.php/settings/admin/security. I have add the nexcloud as social application in mailman3/admin/socialaccount/socialapp/. If i try to login via nexcloud, postorius redirect me to the nextcloud, where i successful login, and redirected to postorius But i'm not logged in postorius. what I'm missing? Have anybody a howto? Thanks Falk

5 4

Captcha or similar for new signups?
by peter＠chubb.wattle.id.au Nov. 30, 2023

Nov. 30, 2023

Hi Folks, Does anyone have a recipe for adding captcha or similar to stop bot accounts signing up with Postorius? We're seeing a heap of fake signups resulting in confirmation emails going to people who haven't signed up, with user names like 'CAOXpYhPFPBFr' -- I'd like to make it just a little harder for bots to sign up. Too many confirmation emails going to non-existent email addresses reduces our mail reputation, and increases the likelihood that legit email is flagged as spam. Peter C

2 1

Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error'))
by Mark Labeste Nov. 30, 2023

Nov. 30, 2023

Hi Admin, Any idea on this error? It happen when you wrote a tread it send the mail but not save on the archive. Nov 28 20:34:51 2023 (8407) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) Nov 28 20:34:51 2023 (8407) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) Nov 28 20:34:51 2023 (8406) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) Nov 28 20:34:51 2023 (8400) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) Nov 28 20:34:51 2023 (8400) Could not archive the message with id <168853565119.17959.11384406081068301715(a)email1.example.com> Nov 28 20:34:51 2023 (8400) archiving failed, re-queuing (mailing-list testmaillist.example.com, message <168853565119.17959.11384406081068301715(a)email1.example.com>) Nov 28 20:34:51 2023 (8400) Exception in the HyperKitty archiver: ('Connection aborted.', OSError(0, 'Error')) Nov 28 20:34:51 2023 (8400) Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 710, in urlopen chunked=chunked, File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 386, in _make_request self._validate_conn(conn) File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn conn.connect() File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connection.py", line 429, in connect tls_in_tls=tls_in_tls, File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/util/ssl_.py", line 450, in ssl_wrap_socket sock, context, tls_in_tls, server_hostname=server_hostname File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl return ssl_context.wrap_socket(sock, server_hostname=server_hostname) File "/usr/lib64/python3.6/ssl.py", line 365, in wrap_socket _context=self, _session=session) File "/usr/lib64/python3.6/ssl.py", line 776, in __init__ self.do_handshake() File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake self._sslobj.do_handshake() File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake self._sslobj.do_handshake() OSError: [Errno 0] Error

3 3

Re: [Mailman-Developers] Re: SSL error while connecting to hyperkitty
by Abhilash Raj Nov. 29, 2023

Nov. 29, 2023

On Sat, Aug 31, 2019, at 10:20 AM, sandeep kumar wrote: > Hi Abhilash > > Thanks for the reply. > > Just two more answers please -:) > > Can I use the sample apache.conf in example_project in my webserver virtual host...?? See this thread for the apache configuration: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… You'd need to adjust the paths and SSL configuration. > > And what should be the configuration details to be given in uwsgi server...?? http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-a-wsgi-server > > Regards > Sandeep > > > On Sat, Aug 31, 2019 at 10:25 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: >> __ >> On Sat, Aug 31, 2019, at 8:49 AM, sandeep kumar wrote: >>> Hi Abhilash >>> >>> Thanks for your reply. -:) >>> >>> We are using apache httpd as webserver to redirect. >>> >>> the proxy pass in webserver is >>> >>> ProxyPass / http://localhost:8000 >>> ReverseProxyPass / http://localhost:8000 >> >> >> Can you put `base_url: http://localhost:8000/hyperkitty` in your mailman-hyperkitty.cfg and see that it works? :) >> >> This should not try any funny SSL redirection. >> >>> I don't have idea of deploying this in production, so I just went on searching and I found wsgi (say uwsgi) is required to send the requests from webserver to mailman. Correct me if I am wrong. >>> >>> I have few queries listed below. Please reply to them. >>> >>> Should I use the wsgi.py present in the directory of mailman-suite ...?? >> >> Yes, that is the one which is supposed to be used. >> >>> >>> What should be the ProxyPass ..?? Where should the first hit go from webserver ---> uwsgi ---> ?? >> >> uwsgi is web server running Mailman's web componenet. It doesn't need to hit anything. You can restart it directly when you want to restart Mailman's web component, you don't need to do anything to your web server (httpd) for this. >> >> >> >>> >>> Can we run "python manage.py runserver" every time to start mailman suite..?? Can we make mailman-suite start/stop just by restarting the HTTPD..?? >> >> >> No, use a wsgi server, like uwsgi or gunicorn to run mailman-suote. `python manage.runserver` is a command used during development shouldn't be used at all in prod. >> >>> >>> What should be the entry in Hyperkitty.cfg file after all the above steps..?? I mean at the end >>> >>> Please reply to the above queries. Thanks for your help >>> Regards >>> Sandeep >>> >>> >>> >>> >>> >>> On Sat, Aug 31, 2019 at 8:45 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>> On Sat, Aug 31, 2019, at 1:36 AM, sandeep kumar wrote: >>>> > Hi Team >>>> > >>>> > Iam seeing following errors while mailman is trying to archive in >>>> > mailman.log >>>> > >>>> > >>>> > This is my base URL in mailman-hyperkitty.cfg >>>> > >>>> > base_url: http://localhost/hyperkitty >>>> >>>> Are you sure this is the URL? this is http and Mailman shouldn't try to connect to this using HTTPS. >>>> >>>> Is your web server configured to redirect all HTTP traffic to HTTPS? If that is the case, then it is going to fail. >>>> >>>> Which wsgi server are you using? uwsgi? >>>> >>>> Can you also show your ProxyPass configuration? >>>> >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > *During handling of the above exception, another exception >>>> > occurred:Traceback (most recent call last): File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/adapters.py", >>>> > line 449, in send timeout=timeout File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/urllib3-1.24.1-py3.6.egg/urllib3/connectionpool.py", >>>> > line 638, in urlopen _stacktrace=sys.exc_info()[2]) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/urllib3-1.24.1-py3.6.egg/urllib3/util/retry.py", >>>> > line 398, in increment raise MaxRetryError(_pool, url, error or >>>> > ResponseError(cause))urllib3.exceptions.MaxRetryError: >>>> > HTTPSConnectionPool(host='domain.com <http://domain.com>', port=443): >>>> > Max >>>> > retries exceeded with url: >>>> > /hyperkitty/api/mailman/archive?key=SecretArchiverAPIKey (Caused by >>>> > SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate >>>> > verify >>>> > failed (_ssl.c:841)'),))During handling of the above exception, another >>>> > exception occurred:Traceback (most recent call last): File >>>> > "/var/lib/mailman/mailman-hyperkitty/mailman_hyperkitty/__init__.py", >>>> > line >>>> > 154, in _archive_message url = self._send_message(mlist, msg) File >>>> > "/var/lib/mailman/mailman-hyperkitty/mailman_hyperkitty/__init__.py", >>>> > line >>>> > 201, in _send_message files={"message": ("message.txt", >>>> > message_text)}) >>>> > File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/api.py", >>>> > line 116, in post return request('post', url, data=data, json=json, >>>> > **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/api.py", >>>> > line 60, in request return session.request(method=method, url=url, >>>> > **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 533, in request resp = self.send(prep, **send_kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 668, in send history = [resp for resp in gen] if allow_redirects >>>> > else [] File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 668, in <listcomp> history = [resp for resp in gen] if >>>> > allow_redirects else [] File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 247, in resolve_redirects **adapter_kwargs File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 646, in send r = adapter.send(request, **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/adapters.py", >>>> > line 514, in send raise SSLError(e, >>>> > request=request)requests.exceptions.SSLError: >>>> > HTTPSConnectionPool(host=domain.com <http://domain.com>', port=443): Max >>>> > retries exceeded with url: >>>> > /hyperkitty/api/mailman/archive?key=SecretArchiverAPIKey (Caused by >>>> > SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate >>>> > verify >>>> > failed (_ssl.c:841)'),))* >>>> > >>>> > >>>> > Rgrds >>>> > Sandeep >>>> > >>>> > On Sat, Aug 31, 2019 at 10:20 AM sandeep kumar <sandeep7790(a)gmail.com> >>>> > wrote: >>>> > >>>> > > Team any help >>>> > > >>>> > > Sent from my iPhone >>>> > > >>>> > > > On 30-Aug-2019, at 11:18 PM, sandeep kumar <sandeep7790(a)gmail.com> >>>> > > wrote: >>>> > > > >>>> > > > Hi Team >>>> > > > >>>> > > > Iam using httpd to work with ssl on mailman 3 using proxy pass. >>>> > > > >>>> > > > After this configuration Iam not able to connect to hyperkitty. It is >>>> > > throwing ssl certificate error in mailman.log file. >>>> > > > >>>> > > > What should be the configuration of hyperkitty while using https in >>>> > > mailman..? >>>> > > > >>>> > > > Please help me with this Iam struck here from past 4 days >>>> > > > >>>> > > > Rgrds >>>> > > > Sandeep >>>> > > > >>>> > > > Sent from my iPhone >>>> > > >>>> > >>>> > >>>> > -- >>>> > Regards >>>> > Sandeep Kumar >>>> > +91-9642669192 >>>> > _______________________________________________ >>>> > Mailman-Developers mailing list -- mailman-developers(a)python.org >>>> > To unsubscribe send an email to mailman-developers-leave(a)python.org >>>> > https://mail.python.org/mailman3/lists/mailman-developers.python.org/ >>>> > Mailman FAQ: https://wiki.list.org/x/AgA3 >>>> > >>>> > Security Policy: https://wiki.list.org/x/QIA9 >>>> > >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>> >>> >>> -- >>> Regards >>> Sandeep Kumar >>> +91-9642669192 >>> >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> > > > -- > Regards > Sandeep Kumar > +91-9642669192 > -- thanks, Abhilash Raj (maxking)

4 3

Putting mailman3 server behind a netscaler
by Lieuallen, Thomas Otis Nov. 29, 2023

Nov. 29, 2023

(I sent this a week ago, but apparently it got lost, trying to resend.) We’ve been using MM2 for eons and are working on a migration to MM3. So, bear with me as I’m still coming up to speed. I’m running MM 3.3.8 and Postorious 1.3.8. Our mailing lists include members within our organization as well as a number outside. We don’t want to expose our MM3 server directly to the open internet, so wish to hide the web portion behind our netscaler and our regular pool of web servers. Those web servers will proxy MM3 web pages on over to our MM3 machine to handle. This seems to work. Email will meander in via MX and mail relay servers. I found and followed directions in this email regarding changing URL paths: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… So, say our MM3 server is: mm3.fqdn I am trying to publish and use urls like www.fqdn/mailman3-admin<http://www.fqdn/mailman3-admin>, www.fqdn/mailman3/lists<http://www.fqdn/mailman3/lists>. Again, that works for me. However, MM3 still has its concept of what URLs should be. I hoped I could fix that by way of templates, but I’m not sure there’s a template for everything. I added some templates, but have not replaced all. I was wondering and hoping that some central change could fix any default templates en-mass. Most recently, I changed the mailman admin email yesterday and the confirmation email directed me to mm3.fqdn/…/confirm-email/…. I looked at the stock templates and nothing there had that wording. I just looked at postorious docs and nothing jumps out at me there. 1. Have I gone down a bad rabbit hole? 2. Is there a way to change the advertised web server address? 3. Should I just continue rolling out my own templates and hope and assume that will take care of this issue? Thank you Tom Lieuallen Oregon State University

2 2

Importing archive from mm21
by Lars Bjørndal Nov. 29, 2023

Nov. 29, 2023

I imported an archive from a list created in September 2013 with the following command: mailman-web hyperkitty_import -l annonsering(a)hodr.no --since 2013-09-01 <mbox file> No errors reported. I then did mailman-web update_index_one_list annonsering(a)hodr.no No, when I go to https://hodr.no/archives/list/annonsering@hodr.no/, I cannot choose mails earlier than January 2023. What's the problem, do you think? Lars

2 3

All messages to a new list/domain shunted from "in" queue with no logged exceptions
by Jered Floyd Nov. 26, 2023

Nov. 26, 2023

OK -- my turn to ask a question... I created a new domain and lists in my (functioning) Mailman 3 install. Messages to these new lists are successfully delivered via LMTP to Mailman and then disappear. They are in the shunt queue, with a source queue of "in". There are no exceptions logged in my mailman.log. An example from a qfile: { '_parsemsg': False, 'envsender': 'noreply(a)[domain].com', 'lang': 'en', 'listid': '[listname].[domain].com', 'original_size': 2654, 'received_time': datetime.datetime(2023, 11, 25, 14, 0, 6, 968185), 'rule_hits': [], 'rule_misses': [], 'to_list': True, 'version': 3, 'whichq': 'in'} Unshunting the message has no effect, and no logs are generated. Any suggestions? Thanks, --Jered

3 12

Mailman3 stopped sending out mail
by Abhijith PA Nov. 22, 2023

Nov. 22, 2023

Hello. Recently my mailman3 instance stopped distributing mail. But mailman's own mail (notification, digest etc) and archiving are working OK. I couldn't figure what is going wrong From mail.log --- Dec 31 10:03:20 lists postfix/smtpd[10900]: Anonymous TLS connection established from mail.xxxx.xx[5.79.72.163]: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Dec 31 10:03:20 lists postfix/smtpd[10900]: Anonymous TLS connection established from mail.xxxx.xx[5.79.72.163]: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Dec 31 10:03:20 lists policyd-spf[10907]: prepend Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=5.79.72.163; helo=mail.xxxx.xx; envelope-from=abhijith(a)xxxx.xx; receiver=<UNKNOWN> Dec 31 10:03:20 lists policyd-spf[10907]: prepend Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=5.79.72.163; helo=mail.xxxx.xx; envelope-from=abhijith(a)xxxx.xx; receiver=<UNKNOWN> Dec 31 10:03:21 lists postfix/smtpd[10900]: 04C2412038F: client=mail.xxxx.xx[5.79.72.163] Dec 31 10:03:21 lists postfix/smtpd[10900]: 04C2412038F: client=mail.xxxx.xx[5.79.72.163] Dec 31 10:03:21 lists postfix/cleanup[10912]: 04C2412038F: message-id=<f875c144-a23c-baa2-7de2-1b102d3e7494(a)xxxx.xx> Dec 31 10:03:21 lists postfix/cleanup[10912]: 04C2412038F: message-id=<f875c144-a23c-baa2-7de2-1b102d3e7494(a)xxxx.xx> Dec 31 10:03:21 lists opendkim[450]: 04C2412038F: s=_teknikKey d=xxxx.xx SSL Dec 31 10:03:21 lists opendkim[450]: 04C2412038F: s=_teknikKey d=xxxx.xx SSL Dec 31 10:03:21 lists postfix/smtpd[10900]: disconnect from mail.xxxx.xx[5.79.72.163] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Dec 31 10:03:21 lists postfix/smtpd[10900]: disconnect from mail.xxxx.xx[5.79.72.163] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: from=<abhijith(a)xxxx.xx>, size=1699, nrcpt=1 (queue active) Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: from=<abhijith(a)xxxx.xx>, size=1699, nrcpt=1 (queue active) Dec 31 10:03:21 lists postfix/lmtp[10915]: 04C2412038F: to=<test3(a)lists.yyyy.yy>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.87, delays=0.62/0.02/0.04/0.2, dsn=2.0.0, status=sent (250 Ok) Dec 31 10:03:21 lists postfix/lmtp[10915]: 04C2412038F: to=<test3(a)lists.yyyy.yy>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.87, delays=0.62/0.02/0.04/0.2, dsn=2.0.0, status=sent (250 Ok) Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: removed Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: removed I am not sure why 'postfix/qmgr[13211]: 04C2412038F: removed' is happening. from /var/log/mailman3/smtp.log: Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) handling connection Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'LHLO lists.xxxx.xx' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'MAIL FROM:<abhijith(a)xxxx.xx>' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) sender: abhijith(a)xxxx.xx Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'RCPT TO:<test3(a)xxxx.xx>' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) recip: test3(a)xxxx.xx Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'DATA' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'QUIT' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) connection lost Dec 31 10:03:21 2018 (6323) Connection lost during _handle_client() Here again I am doubtful about 'Connection lost during _handle_client()'. Please help. Abhijith PA

3 5

Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html
by Michael.Sanderson＠ubc.ca Nov. 21, 2023

Nov. 21, 2023

Despite earlier comments that django-allauth 0.58.1 has been released to fix this issue (and presumably 0.58.2 would have the fix as well), there appears to still be an issue. As Odhiambo indicated with django-allauth==0.57.0, mailman-web compress completes without errors. With django-allauth 0.58.1 and 0.58.2, I still get (venv) $ mailman-web compress Compressing... Error parsing template socialaccount/signup.html: socialaccount/base.html done Compressed 2 block(s) from 78 template(s) for 1 context(s). The Invalid template errors for socialaccount/login_cancelled.html and account/verified_email_required.html are gone, but we still have a parsing error. This is an installation on RHEL9 with python 3.11 based on the virtualenv installation method at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… Michael Sanderson

6 6

moving lists to another server
by bryan.kartzman＠yu.edu Nov. 21, 2023

Nov. 21, 2023

I have both my mailman lists and django config in postgres databases. If I want to move my lists to another server that is running mailman 3, aside from copying the databases to the other server, what other things (perhaps all files under /var/lib/mailman3?, etc) would I need to bring over to the other server?

6 21

Migrating from Listserv 17 to Mailman 3
by Cooper, Robert A Nov. 21, 2023

Nov. 21, 2023

Howdy! Does anyone have or know of a guide to migrate from Listserv 17, including list archives, to Mailman 3? I've found documentation on moving to Mailman 2, but those don't seem to apply to the newer version. Thanks, RobertC

2 1

copies of sent "admin" messages
by David Bremner Nov. 21, 2023

Nov. 21, 2023

I'm dealing with (presumably bogus) spam reports for messages from foo-bounces(a)list.domain As far as I can tell these messages are triggered by the alleged-victim/apparent-attacker sending messages to foo-subscribe followed immediately by foo-unsubscribe. I have the size and time from postfix and/or mailman's smtp.log, but I don't have the message content. Are these messages stored somewhere by Mailman? Can I have them stored for a month or so in order to deal with these bureaucratic incidents? David

3 3

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

Template - "You can use these variables in the templates" - The variable for "leave" is missing
by Wikinaut Nov. 4, 2023

Nov. 4, 2023

The current template input page shows this text: You can use these variables in the templates. $hyperkitty_url: Permalink to archived message in Hyperkitty $listname: Name of the Mailing List e.g. ant(a)example.com $list_id: The List-ID header e.g. ant.example.com $display_name: Display name of the mailing list e.g. Ant $short_listname: Local part of the listname e.g. ant $domain: The domain part of the listname e.g. example.com $info: The mailing list's longer descriptive text $request_email: The email address for -request address $owner_email: The email address for -owner address $site_email: The email address to reach the owners of the site $language: The two letter language code for list's preferred language e.g. fr, en, de I suggest to add the variable for leaving a mailing list here. But what is the variable name?

4 6

Mailman 3 deployment: ok to use same database instance for core, web, and hyperkitty tables?
by s.dobrau＠ucl.ac.uk Nov. 4, 2023

Nov. 4, 2023

Hello, We are currently working on a migration plan for Mailman -> Mailman 3. We have around over 3000 mailing lists with a total of 50K members and 500 worth of archived data. Our plan is to have core+web (instance 1) and Hyperkitty (instance 2). With the archives on the FS local to the Hyperkitty. And all 3 tables (core, web, Hyperkitty) pointing to the same database on a remote SQL (mysql-enterprise) instance. Using class mailman.database.mysql.MySQLDatabase (and whatever necessary on the Django/Hyperkitty instance). Is this feasible, if so what would be the recommended compute/storage requirements. If not what other alternatives have we got ? A remote or local PostgreSQL instance is also possible if recommended. Thank you very much in advance and all the best ! Regards, Serban

4 4

Immediate notification to the administrator
by pau.baiges＠csuc.cat Nov. 2, 2023

Nov. 2, 2023

Hello In Mailman, I have all the lists marked with the "Immediate notification to the administrator" option. Should list moderators receive immediate notification of new requests as well as daily reminders about the pending ones? List moderators (and list administrators) receive daily reminders of pending requests for approval, such as subscriptions to a moderated list or submissions that are held for some reason. Enabling this option results in immediate notifications being sent upon the arrival of new requests. When there's a message being held because it needs approval, it automatically sends an email to the list owners. However, it also states that it sends a daily reminder if the email remains unapproved, but it's not doing that. I'll show you how I have /etc/postfix/transport configured. I receive the first "owner" email, but not the daily one. list-owner(a)llistes.csuc.cat relay:[ip]:25 list(a)llistes.csuc.cat .. list-admin(a)llistes.csuc.cat ... list-bounces(a)llistes.csuc.cat ... list-confirm(a)llistes.csuc.cat ... list-join(a)llistes.csuc.cat ... list-leave(a)llistes.csuc.cat ... list-request(a)llistes.csuc.cat ... list-subscribe(a)llistes.csuc.cat ...

5 9

Weird behavior with Outlook and any MM3 List
by Thomas Ward Nov. 1, 2023

Nov. 1, 2023

I'm seeing some *really* odd behavior with Mailman 3 and Microsoft Outlook clients (even Outlook Web Access). When messages come in with a subject prefix, of any way shape or form, Microsoft Outlook seems to *completely strip* the prefixes from any "reply" sent, which could be problematic. While the "In-Reply-To" header is still intact and such, Microsoft just seems to 'strip' prefixes from subject lines and that causes a problem in some cases. Has anyone observed this behavior before? If so, have you found any workarounds? Thomas

2 2

Reduction of spam - FROM_LOCAL_HEX
by Kyriakos Terzopoulos Oct. 31, 2023

Oct. 31, 2023

Hi, After fixing all issues with mailman I want to reduce the chance for email being marked as spam, especially from Gmail. I have added SPF and DKIM records and I am now using dkimvalidator to debug the emails being sent. Here is what I'm getting from spam evaluation: *0.3 FROM_LOCAL_HEX From: localpart has long hexadecimal sequence* My guess is that the From address is very large, for example: mylist-confirm+3eafa5bd24e52738c900e2e3fd05e366b7ea7580(a)myproject.eu Is there any way to mitigate this problem? Thank you, *Kyriakos Terzopoulos* Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d>

4 3

psycopg2 error?
by Odhiambo Washington Oct. 30, 2023

Oct. 30, 2023

This is the first time I am seeing this with MM3 so maybe it's something new in the latest releases? Using the virtualenv method to install MM3 in a fresh Debian 12 VM, I have run into an error while starting the mailman3 service. I cannot figure out what this error means. <CUT> root@debian12:/home/wash# systemctl status mailman3.service × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Thu 2023-10-26 09:36:41 EAT; 8s ago Process: 1893842 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 789ms Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: dbapi = dbapi_meth(**dbapi_args) Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: ^^^^^^^^^^^^^^^^^^^^^^^^ Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 690, in import_dbapi Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: import psycopg2 Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", line 51, in <module> Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: from psycopg2._psycopg import ( # noqa Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: SystemError: initialization of _psycopg raised unreported exception Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Failed with result 'exit-code'. Oct 26 09:36:41 debian12.wash.lan systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. </CUT> No log entry in any of the log files in /opt/mailman/mm/var/logs/. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 11

disabled users
by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia Oct. 27, 2023

Oct. 27, 2023

Hello, Wher I find the disabled user of a mailing list and wher I can reactivate them? I do not find this nor in web interface neither in command line utility. Thank you best regards -- 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

3 6

(Custom) Plugins: Proper file path(s) for adding a handler?
by Thomas Ward Oct. 25, 2023

Oct. 25, 2023

I want to add a custom handler that implements customized thread IDs in the system. I already have the DB logic worked out, but the documentation for plugins is NOT clear on how to define a handler in a plugin, nor does the example plugin in the documentation on Gitlab have any custom handlers. I'm looking to add a custom handler so that the private pipeline for threaded-subject-list can use thread-subject (the custom handler) instead of subject-prefix (builtin). I'm unclear how to add this properly in a plugin that would be read properly by Mailman, though. Any tips on the filestructure needed for the Python code/plugin package in order to properly be set up and work? Thomas

3 14

rDNS issue? Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid
by Kyriakos Terzopoulos Oct. 25, 2023

Oct. 25, 2023

Hi all, I'm on the latest mailman installation in a HestiaCP server. The past few days I have been investigating some spam issues and by using dkimvalidator.com I found the following: 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -1.0 MAILING_LIST_MULTI Multiple indicators imply a widely-seen list manager* 3.2 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (IP addr 1)* Note the last line on the above debug information which raises the spam score of the email. Some research showed me that I needed a rDNS entry in my server. I'm on a Hetzner cloud VM so I used the Hetzner console to change the rDNS entry from: static.XXX.XXX.XXX.XXX.clients.your-server.de to my initial server hostname for example: *hestia.myserver.com <http://hestia.myserver.com>* However, after some propagation, I found today that even though I can send email to any normal address created in the server's control panel, mailing list emails do not get sent. I see the following in the logs: Mailman SMTP log: Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> *response exception: (550, b'Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid'*, 'testlist-bounces+myusername=myproject.eu(a)myproject.eu') Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> smtp to testlist(a)myproject.eu for 1 recips, completed in 45.07745146751404 seconds Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> post to testlist(a)myproject.eu from testlist-confirm+07d3315fa11a75588857fc93d1832ba74fb09fdd(a)myproject.eu, 1633 bytes, 1 failures Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> delivery to myusername(a)myproject.eu failed with code 550, b*'Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid'* Exim4 log: 2023-10-24 14:17:47 H=([127.0.0.1]) [XXX.XXX.XXX.XXX] rejected MAIL <testlist-bounces+myusername=myproject.eu(a)myproject.eu>: *Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid* The weird thing is that when I do a mailman-web sendtestemail this email is sent successfully. Also please note that before the rDNS change I did not have an issue with mail sending. Last but not least, after some search I set in Exim4 the following: PRIMARY_HOST_NAME = *hestia.myserver.com <http://hestia.myserver.com>* Any help would be greatly appreciated. *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d>

2 4

Without being logged in, at least one mailing list - flagged as no-show - is listed in https://mydomain/hyperkitty/
by Wikinaut Oct. 25, 2023

Oct. 25, 2023

The list is not yet used (i.e. "inactive"), but clearly flagged as " Show list on index page = no" I regard this as a bug.

1 1

More Mailman releases!
by Abhilash Raj Oct. 24, 2023

Oct. 24, 2023

Hello Everyone, I am pleased to announce several new releases for GNU Mailman project. Thanks to all the contributors for making these releases possible! 1. Postorius 1.3.10 [1] 2. Hyperkitty 1.3.8 [2] 3. Django-mailman3 1.3.10 [3] 4. Mailman-web 0.0.7 [4] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of change logs are available below: [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 [2]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst Do note that for Postorius, I released 1.3.9, but I forgot to update dependency metadata to require `django-mailman3>=1.3.10` (which is required for the new bootstrap 5 upgrade across packages) and so I also released Postorius 1.3.10 just after. Installation documentation is available at https://docs.mailman3.org/en/latest/install/install.html and if you are upgrading an existing virtualenv install you can refer https://docs.mailman3.org/en/latest/upgrade-3.2.html If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available at https://docs.mailman3.org/en/latest/. Finally, similar to Mailman Core, note that PyPI doesn't accept signatures anymore so each packages' release page now has the tarball uploaded to them along with the signature: Django-mailman3: https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 -- thanks, Abhilash Raj (maxking)

9 17

120 gmail users removed from lists !
by elemac＠free.fr Oct. 24, 2023

Oct. 24, 2023

Hello, on 15th October, 120 users with gmail address where suddenly removed from lists in mailman3, something changed in google ?

8 11

Gmail bounces as a result to high send rate
by Mohsen Masoudfar Oct. 24, 2023

Oct. 24, 2023

I managed to receive the bounced emails to my mailbox and I can now see the stated reason for th eissue, the bulk of the emails are marked as "expired" due to the following response: "smtp; Message expired: unable to deliver in 840 minutes.< Our system has detected an unusual rate of unsolicited mail. To protect our users from spam, mail has been temporarily rate limited. Please visit https://support.google.com/mail/?p=UnsolicitedRateLimitError to review our Bulk Email Senders Guidelines." The issue is exclusive to Gmail, no other email provider responded with a comparable message. I followed their recommendation, but I am not sure how to reduce the rate on Postfix side. Can I do it per list? or once per server? Thanks.

2 1

Internal Server Error: /mailman/accounts/fedora/login/
by Kilian Kilger Oct. 24, 2023

Oct. 24, 2023

Hi mailing list, I own a mailman box. I regularily (many times a day) get mail with an internal server error. I am using Debian and the included mailman3-full package. I guess someone tries to hack my instance. But I don't understand why this leads to the internal server error. I am also wondering why the request URL is /mailman/accounts/fedora/login, as I am using Debian (understandable if the request happens via an outside trigger). I have no clue about the internal workings of mailman though. I use Debian 11 bullseye and thus version 3.3.3. I can trigger the internal server error by myself by visiting the request URL. Despite these emails the instance seems to work fine. Best regards, Kilian. Internal Server Error: /mailman/accounts/fedora/login/ TypeError at /accounts/fedora/login/ _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request Method: GET Request URL: <URL>/mailman/accounts/fedora/login/?process=login&next=/mailman/accounts/password/reset/ Django Version: 2.2.24 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: Fr, 17 Sep 2021 06:12:57 +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/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/generic/base.py" in view 71. return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch 97. return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in get 56. return self.post(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in post 67. client = _openid_consumer(request) Exception Type: TypeError at /accounts/fedora/login/ Exception Value: _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request information: USER: AnonymousUser

3 2

General question mailman3: message sender acceptance "always"
by Wikinaut Oct. 23, 2023

Oct. 23, 2023

I received one mail from a sender who's not a member for moderation (=ok). Mailman2 had the moderation option "allow this sender to sender further mails" (I call this: to add this sender to the additional "white list" of white-listed addresses.) I could not find such an option (in the moderation dialog) in Mailman3 (only "accept" or "reject" and "discard", but "accept and add to white-list = accept always"). Is it a bug or feature?

2 4

pip install -U mysqlclient
by Odhiambo Washington Oct. 23, 2023

Oct. 23, 2023

Hello everyone, After successfully updating my MM3 venv install, I thought I could also keep everything else up to date. One app refuses - mysqlclient. All the rest did update. PS: I have a full backup of the venv so no worries there :) <CUT> (venv) [mailman@gw /opt/mailman/mm]$ pip install -U mysqlclient Requirement already satisfied: mysqlclient in ./venv/lib/python3.11/site-packages (2.1.1) Collecting mysqlclient Using cached mysqlclient-2.2.0.tar.gz (89 kB) Installing build dependencies ... done Getting requirements to build wheel ... error error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> [25 lines of output] Trying pkg-config --exists mysqlclient Command 'pkg-config --exists mysqlclient' returned non-zero exit status 1. Trying pkg-config --exists mariadb Command 'pkg-config --exists mariadb' returned non-zero exit status 1. Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module> main() File "/opt/mailman/mm/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main json_out['return_val'] = hook(**hook_input['kwargs']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel return hook(config_settings) ^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-usp5tphe/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 355, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=['wheel']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-usp5tphe/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 325, in _get_build_requires self.run_setup() File "/tmp/pip-build-env-usp5tphe/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 341, in run_setup exec(code, locals()) File "<string>", line 154, in <module> File "<string>", line 48, in get_config_posix File "<string>", line 27, in find_package_name Exception: Can not find valid pkg-config name. Specify MYSQLCLIENT_CFLAGS and MYSQLCLIENT_LDFLAGS env vars manually [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. </CUT> -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 4

no access to Postorius web pages after upgrade
by David Newman Oct. 22, 2023

Oct. 22, 2023

Upgrading to MM3 3.39, Postorius 1.3.10, Hyperkitty, 1.3.8, Django-mailman3 1.3.11, and Mailman-web 0.0.8 in a venv all seemed to go OK. Mailman3 lists work as expected, and admins can log in via Django. However, any attempt to reach lists, domains, users, etc. now returns a 404 Not Found error. All the Postorius stuff worked as expected before the upgrade. In the nginx server logs, any Hyperkitty and Postorius URLs are now appended to /opt/www/roundcubemail, which is this web server's root directory but not the root for Mailman3 (I run Roundcubemail and MM3 on the same server; don't judge me :-). Here is the nginx error, with obfuscation of client and server info: 2023/10/22 10:43:24 [error] 2264140#2264140: *135 "/opt/www/roundcubemail/postorius/domains/index.php" is not found (2: No such file or directory), client: 1.2.3.4, server: lists.example.com, request: "GET /postorius/domains/ HTTP/2.0", host: "lists.example.com", referrer: "https://lists.example.com/mailman3/listinfo" And here are the relevant bits of the Nginx config. Again, this worked before the upgrade. server { listen 443 ssl http2; server_name lists.example.com; root /opt/www/roundcubemail; # begin mailman3 stuff location /static/ { alias /opt/mailman/web/static/; } location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /mailman/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } # end mailman3 stuff } Also, I'm not sure if it's relevant but after upgrading, the migrate command throws a warning like this: (venv) mailman@mail10:~$ mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Thanks in advance for clues on getting all Postorius/Django links working again. dn

2 3

[migration] to a another server - one year database apparently lacks fields for newer mailman3/django suite
by Wikinaut Oct. 22, 2023

Oct. 22, 2023

As suggested by @Mark last week, I exported my databases mailman3, mailman2web of what was mailman 3.3.0 (or so) and imported these on my new working system. Apparently, a database migration step is needed to run the new mailman3 with some older databases: because when I want to login to view my mailing lists, I got "An error occurred while processing your request." in the web. Log files and error mail messages say inter alia: Internal Server Error: /accounts/login/ OperationalError at /accounts/login/ (1054, "Unknown column 'socialaccount_socialapp.provider_id' in 'field list'" and Internal Server Error: /archives/ OperationalError at /archives/ (1054, "Unknown column 'hyperkitty_mailinglist.archive_rendering_mode' in 'field list'") Please can you assist: How can I add the missing tables, is there an update script (running "python migrate.py" was not fixing this).

2 2

New messages are not archived - may be a path issue
by Wikinaut Oct. 21, 2023

Oct. 21, 2023

(I read thoroughly https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… "New messages not being archived", but could not find what's wrong on my machine.) This is what I found in /var/log/mailman3/mailman.log : HyperKitty failure on https://mail.opteryx.org/mailman3/archives/api/mailman/archive: This page either doesn't exist, or it moved somewhere else. I have double checked all settings in the /etc/mailman3/ configuration files and are not able to get message archived. There is not REST error message any more, but perhaps a problem with the paths. I have no idea any more where to fix this.

3 3

(venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"
by Wikinaut Oct. 21, 2023

Oct. 21, 2023

I followed all single steps until this: https://docs.list.org/en/latest/install/virtualenv.html#run-database-migrat… (I will improve the documentation with the missing parts later today), Now I got this and got stucked and need your help: django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE full stack: (venv) mailman@mail:/run$ mailman-web migrate Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 420, in execute django.setup() File "/opt/mailman/venv/lib/python3.11/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/opt/mailman/venv/lib/python3.11/site-packages/django/apps/registry.py", line 124, in populate app_config.ready() File "/opt/mailman/venv/lib/python3.11/site-packages/allauth/account/apps.py", line 15, in ready raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE

6 28

[Bug] Archiver: when deleting an archive, the control flow is lost (return-to should go to https://example.com/archives/ but does not)
by Wikinaut Oct. 21, 2023

Oct. 21, 2023

How to reproduce: When deleting an archive, the confirmation page for the requested delete action is (correct) https://example.com/archives/list/test@example.com/delete/ When you now click the button DELETE, then the web control flow ist lost. BUG Instead of https://example.com/archives/ the https://example.com is shown, which appears to be a bug. REMARK: The archive-to-be-deleted was indeed deleted. This behaviour was observed with both installations on a fresh server: - debian12 install (package mailman3-full) ; and - venv install (recommended on your page)

2 1

Message of migrated list showing "unsubscribe@%(host_name)s" in footer
by alex＠presland.net Oct. 21, 2023

Oct. 21, 2023

Apologies if I've not found a previous post for this; I did look before starting a new thread. We migrated a number of mailman lists last weekend and I spotted this evening that an email from the list contained a footer along the lines of the following (all bits in CAPITALS were successfully representing the list. ===== LISTNAME mailing-list -- LISTNAME@DOMAIN To unsubscribe, email LISTNAME-unsubscribe@%(host_name)s ===== 1) I don't know why %(host_name)s hasn't been automagically substituted 2) I can't find anywhere to change this footer in the Mailman3 Postorius interface

2 3

After importing my old databases, the mail local_recipient map is suddenly not working any more
by Wikinaut Oct. 20, 2023

Oct. 20, 2023

After importing old databases everythimng looks fine now. But the mail local_recipient maps are not working (/etc/postfix/main.cf looks fine, as before, and postfix was restarted). Mails to test(a)example.org rejected with Error 550 Recipient address rejected: User unknown in local recipient table /* as in your installation guide */ transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains The files appears to be present: /var/lib/mailman3/data# dir 4 -rw-rw---- 1 mailman mailman 339 Oct 20 21:13 postfix_domains 8 -rw-r----- 1 mailman mailman 12288 Oct 20 21:13 postfix_domains.db 4 -rw-rw---- 1 mailman mailman 2714 Oct 20 21:13 postfix_lmtp 12 -rw-r----- 1 mailman mailman 12288 Oct 20 21:13 postfix_lmtp.db What else is needed to get the list-addresses working and not rejected? It worked before the import.

1 3