- Mailman-users - lists.mailman3.org

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