Search results for "Postorius" - Mailman-users

Re: New Mailman Releases

by Abhilash Raj

On 10/26/22 13:48, Odhiambo Washington wrote: > Ideally, `pip` shouldn't have allowed you to install aiosmtpd in a > Python venv with 3.10, but that depends on which version of pip you are > using since the newer versions have better support for such management. > > > I followed the HOWTO by the late BC > <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> for my > installation. I did not have to choose any specific version of pip. > I just used what was in the system at that time, which was based on the > Python version on the system. So, actually, it isn't the fault of pip or yours. I check aiosmtpd and it doesn't declare an upper bound on the supported python versions since when the last release came out, the max version was 3.9 and it supported that. There hasn't been a release since 3.10 came out. > > > 2. Is it possible to downgrade the Python in a Venv down to 3.9 > without > > breaking the installation? > > You can keep the current installation running and create a 2nd > installation by simply creating a 2nd venv with 3.9. Something like, > `/opt/mailman/mm/venv-3.9/`. You can install things into that venv and > when you are done and ready to switch, you can update all the paths in > various places to use update 'venv-3.9' instead of 'venv'. > > > That procedure seems way too much work for someone not so well versed > with the PATHs used in MM3. > Since I don't remember ever having to install aiosmtpd (not even sure > what it is!) I believe I should not worry. You basically just need to follow the install instructions again, skipping any parts about creating configs, data mta etc. with the new path to venv. > > 'pip3 list | grep smtpd' yielded nothing in my install. Is that > expected? Or aiosmtpd is part of the core? Yes, it is a dependency of Core and you _should_ find it in the venv. Not sure if you have that activated, but it should result in an installed package if you are inside venv. > > In case you encounter any issues, you can always revert back to older > 'venv' in the paths wherever the are needed and bring back the old > install. Venvs are good for multiple installs so you can switch back > and > forth pretty easily. > > > Talking of moving between VENVs, you did not mention about migrating the > lists/list data between then :-) You don't need to migrate lists, as long as you keep the same configs & database, the 2nd install will just pickup the old data. Make sure you aren't downgrading the version of Mailman though when switching between VMs (which typically won't happen if you just use "pip install", unless you specify version constraints like mailman==3.3.0 for old versions). > > > > > And finally, is there documentation/procedure to upgrade a VENV > install > > in this case? > > You don't want to upgrade venv is what i've heard, you should always > create a new one if you are bumping python versions. > > > Noted. And only Python versions, right? Like 3.10 to 3.11? Yes, only Python versions! Packages inside can be upgraded. > (3) Upgrade package > Finally, upgrade your packages: > > Here, I am a little confused. The official MM3 documentation says the below: > *(venv) $ pip install -U mailman postorius django-mailman3 hyperkitty > mailman-web* > > However, thee howto by BC, there was no installation for django-mailman3 > and mailman-web. So I am unable to map 1:1 what needs to be done > to upgrade to these 5 components of > 1. Mailman Core 3.3.6 [1] > 2. Postorius 1.3.7 [2] > 3. Hyperkitty 1.3.6 [3] > 4. Mailmanclient 3.3.4 [4] > 5. Django-mailman3 1.3.8 [5] > > What should I add to the command line below so that everything is updated? > > (venv) mailman@lists:~$ pip install -U mailman postorius hyperkitty > mailman-hyperkitty This will work! Yeah, basically upgrade only the packages you installed previously. The official documentation asks you to explicitly specify all Mailman packages (even the downstream libraries like django-mailman3 and mailmanclient, which will already be upgraded when you install new version of Postorius or Hyperkitty) and mailman-web. You probably don't need "mailman-web". I'd recommend just specifying all the released packages, except mailman-web since you aren't using that. > Sorry to bother you so much. No worries :-) -- thanks, Abhilash Raj (maxking)

3 years, 1 month

Re: {Spam?} Server name in new account confirmation email

by Mark Sapiro

On 12/3/20 9:26 AM, Meehan, John wrote: > Hi, when someone creates a new account (Sign Up), an email is sent to them to confirm their email address. It has the form below. Does anyone know how I can change the server name in the URL (From server.example.com to something else)? I have an SSL proxy server that I want to direct users through. Thanks. - John This message comes from django_allauth. The domains come from the django_site database table. If you have Postorius >= 1.3.3 The Domains view will show you the SITE_ID for the domain and has an `Edit` link the the Django admin UI entry for that site. Otherwise, you can go to the Django admin `Sites` view and see the DOMAIN NAME and DISPLAY NAME for each defined site, and you can edit the domain name. You may also need to adjust the SITE_ID setting in your Django settings to match the site you want. The trick here is the SITE_IDs aren't displayed in the Django admin UI or in Postorius < 1.3.3, and they may not be sequential or start at 1. If you query the database with `SELECT * FROM django_site;` you'll see entries with columns id, domain and name which will tell you the SITE_ID. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Re: Unable to update templates

by Mark

On 5/28/25 01:14, Mark wrote: >> >> Then I created a template using Postorius and updated the uri in >> mailman.templates to: >> >> file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use… >> - and that works. >> >> It's looking promising. Now I just need to modify my script that >> periodically copies the data from the >> "mailmanweb.postorius_emailtemplate" table to a file and updates the >> uri. On 2025-05-28 19:17, Mark Sapiro wrote: > Which says get the template from the file system at that location and > don't ask for it from Postorius at all. This would be the default > action if there were no entry for this template in the > mailman.template table at all. I.e. you now have a template in > Postorius, but it is not used. I have jumped the gun on thinking that the template as a file was working. It's not. It's the same story: the initial file template is good, but it's for sure getting cached somewhere, and an updated file is ignored. The same as when the template was being drawn from the database. Restarting mailman3 and mailmanweb didn't help, neither did rebooting the server. Looking at Gunicorn status, I see a failing connection to 127.0.0.1 which is the error message I was getting when adding a new subscriber - with the custom Welcome template in the database (which is why I moved it to file). 127.0.0.1 and locahost are in the ALLOWED_HOSTS and CSRF_TRUSTED_ORIGINS of the settings.py file I'm at a loss with this caching problem. Any other clues happily received. $ gunicorn --version gunicorn (version 21.2.0) $ gunicorn status [2025-05-29 02:29:41 +0000] [17838] [INFO] Starting gunicorn 21.2.0 [2025-05-29 02:29:41 +0000] [17838] [ERROR] Connection in use: ('127.0.0.1', 8000) [2025-05-29 02:29:41 +0000] [17838] [ERROR] Retrying in 1 second. [2025-05-29 02:29:42 +0000] [17838] [ERROR] Connection in use: ('127.0.0.1', 8000) # ps -ef | grep gunicorn root 1522331 1521736 0 22:57 pts/1 00:00:00 grep gunicorn mailman 1608073 1 0 May20 ? 00:01:24 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application mailman 1608075 1608073 1 May20 ? 02:24:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application

6 months

Re: Postorius no connection to REST API

by Richard Rosner

I included now: SSLProxyEngine on SSLProxyMachineCertificateChainFile /etc/ssl/certs/dfnca.pem (same as SSLCertificateChainFile, I hope that's correct) SSLProxyMachineCertificateFile /etc/ssl/certs/lists.domain.de.cert_key.pem (basically just copied SSLCertificateFile and SSLCertificateKeyFile into one file; and since the keyfile starts with "BEGIN RSA PRIVATE KEY" it seems to fulfill the criteria). SSLProxyProtocol all -SSLv3 -TLSv1 -TLSv1.1 but no change. From apache error log: [Sun Aug 15 09:19:52.318582 2021] [core:notice] [pid 19706:tid 140315143705728] AH00094: Command line: '/usr/sbin/apache2' [Sun Aug 15 09:19:52.732381 2021] [proxy_http:error] [pid 19707:tid 140314912167680] (20014)Internal error (specific information not available): [client 37.201.214.82:9292] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:19:53.929213 2021] [proxy_http:error] [pid 19707:tid 140314912167680] (20014)Internal error (specific information not available): [client 37.201.214.82:9292] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:19:59.463974 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9311] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:20:03.328416 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9311] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:20:04.605617 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9311] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:20:10.178979 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9305] AH01102: error reading status line \ from remote server 127.0.0.1:8000

4 years, 3 months

Re: Social signup?

by Duane Raymond

Thanks Stephen, With support to dip in on how to do this, I would hope it is the start of a series of contributions to the platform :-) My starting point these days is asking chatGPT how to add the functionality. The response looks convincing but often has some glaring errors in it...but at least it helps me narrow down where I start and give me an idea of the steps/complexity of the task. I'll jump over to the developers list when I start this (I'm about to travel for a week to run an annual event in Oxford - so the far removed from programming)...but which chatGPT suggested so far was 1. Extending postorius/signups.html with a loop to get the configured social login providers PLUS adding a csrf_token field to the form 2. Modifying postorius/views.py (which doesn't seem to exist but there is a postorius/views folder) - so perhaps this is views/urls.py So with dev community support and chatGPT support I should be able to muddle through it! Probably as practice I'll convert a recent simple Flask app I built into django to get familiar with Django as a framework before I dip into postorius & hyperkitty Cheers, Duane On Wed, 15 Mar 2023 at 08:26, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Duane Raymond writes: > > > I'll dip into the code in the next weeks and see if I can figure > > out how to add it (using the example of the login page) > > Welcome to the team! :-D > > I doubt you need any Python code; I think you just need to add buttons > in HTML in the page template, and an explanation of where the user > will end up (probably not where they expect ;-). I forget how this > works, but you might even be able to ensure a redirect to where they > expect to go in pure Django templating language. If not, it will > likely need a straightforward one-line change to the view. > > If all that makes sense to you, great! If not, feel free to ask > questions, here, or perhaps more appropriately on > mailman-developers(a)python.org. > > Steve >

2 years, 8 months

Re: How to set up mailman 3

by David Krantz

On Sat, Mar 25, 2017 at 10:35 PM, Barry Warsaw <barry(a)list.org> wrote: > Yes, I'm sorry you went down a dead end with mailman-bundler. I'm trying to > purge the world of it so others won't get led astray. I've clobbered the > README in the GitLab repo and we may at some point just archive and delete the > whole project, but I'm not quite ready to do that yet. I did get things working with the bundler at last. Quite tricky and I have deactivated archival. But I suspect that I should retrace a bit of that work and upgrade to the latest versions. I miss a few functions from mailman2, especially setting a limit for message size to discourage sending larger files to the list. I also notice that there are no modbits per user that I can reach from the web as admin. > Where did you find out about the bundler? I'd like to make sure we steer > people to the current best recommendations: The documentation can be found on several places. The one that is best formatted is this one. I used a worse formatted version of the same text but right now I cannot find the link. https://mailman-bundler.readthedocs.io/en/latest/ I notice that you changed the text on the githlab project. Better. Now I have no idea of how upgrading the different components. I might start from scratch although it probably should be possible to upgrade the parts. The best option is probably to switch to mailman2, but that has disadvantages when handling lists for multiple domains if I am correctly informed and I already have a few domains... I also found that sending mails manually (telnet to port 25) with no headers other than "Subject:" causes the "Held messages" tab to crash with a 500-error. Log below my signature. cheers // David ERROR 2017-03-25 22:54:41,762 base 17632 140529157728000 Internal Server Error: /mailman3/lists/MYLIST.COM.COM/held_messages Traceback (most recent call last): File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/generic.py", line 67, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/utils/decorators.py", line 34, in _wrapper return bound_func(*args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/auth/decorators.py", line 81, in wrapper return fn(*args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/utils/decorators.py", line 30, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/list.py", line 387, in get held_messages = utils.paginate(request, self.mailing_list.held, 20) File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", line 443, in held moderation_reasons=entry['moderation_reasons'], KeyError: u'moderation_reasons'

8 years, 8 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 12:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 2:16 PM, Odhiambo Washington wrote: > > > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > > total 104 > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > > > I imagined I needed an executable. > > > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass > > > Those are headers for compiling some sass. Possibly you actually have a > `sassc` installed in which case you may need > > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > ) > > This change makes the error I was getting to go away. However, I cannot login to manage lists, even after restarting mailman. The error details are here: https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 6 months

Re: Postorius fails to show list because of a large message being held

by Brian Carpenter

On 7/14/20 1:06 PM, Mark Sapiro wrote: > It's confusing, but after adjusting that setting, you need to restart > Mailman core, not gunicorn. > > If you are running a gunicorn service, that is what is providing WSGI > support for Django (Postorius and/or HyperKitty). You may be using > gunicorn for this or uWSGI or Apache mod_wsgi, but is any case, that is > not the gunicorn we are considering here. > > Regardless of what you use to provide WSGI support for Django, Mailman > core uses gunicorn to support the REST API, and that is the gunicorn > affected by the settings in the gunicorn.cfg pointed to by > > [webservice] > configuration: /opt/mailman/mm/gunicorn.cfg > > If, with the above configuration, you do `ps -fwwA|grep runner=rest` you > will see something like: > > mailman 20582 20561 0 01:21 ? 00:00:16 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20722 20582 0 01:21 ? 00:01:19 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20725 20582 0 01:21 ? 00:01:18 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20726 20582 0 01:21 ? 00:01:18 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20727 20582 0 01:21 ? 00:01:50 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > > The first of these, pid 20582, is Mailman's actual REST runner. The > other 4 with parent pid 20582 are the 4 gunicorn worker processes forked > from the REST runner. > > It's the REST runner or Mailman core that needs to be restarted to pick > up that change. Thanks Mark. I knew that once but forgot it. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 4 months

500 error on one list

by Seth Seeger

Hello, One of my lists is return a 500 error when I try to visit the list's home page: HTTP Error 500: {"title": "500 Internal Server Error"} mailmanweb.log says: ERROR 2024-07-13 15:22:30,073 1668 postorius Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3.8/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3.8/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3.8/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3.8/site-packages/postorius/views/list.py", line 275, in get 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 File "/usr/lib/python3.8/_collections_abc.py", line 666, in __contains__ self[key] File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/connection.py", line 127, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR 2024-07-13 15:22:30,079 1668 django.request Internal Server Error: /postorius/lists/XXXX/ ERROR 2024-07-13 15:22:30,079 1668 django.request Internal Server Error: /postorius/lists/XXXX/ mailman.log says: [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX HTTP/1.1" 200 466 "-" "GNU Mailman REST client v3.3.2" [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX/roster/owner HTTP/1.1" 200 2401 "-" "GNU Mailman REST client v3.3.2" [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.2" [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXX@XXXX/config HTTP/1.1" 200 14262 "-" "GNU Mailman REST client v3.3.2" 2024-07-13 15:23:44 [FALCON] [ERROR] GET /3.1/lists/XXXX/archivers => Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/falcon/app.py", line 361, in __call__ responder(req, resp, **params) File "/usr/lib/python3.8/site-packages/mailman/rest/lists.py", line 405, in on_get archiver_set = IListArchiverSet(self._mlist) File "/usr/lib/python3.8/site-packages/zope/component/_api.py", line 152, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib/python3.8/site-packages/zope/interface/registry.py", line 354, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/mailinglist.py", line 619, in __init__ exists = store.query(ListArchiver).filter( File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3467, in one_or_none raise orm_exc.MultipleResultsFound( sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX/archivers HTTP/1.1" 500 38 "-" "GNU Mailman REST client v3.3.2" Did this one list get corrupted somehow? I'm running GNU Mailman 3.3.4 (Tom Sawyer) in Docker containers on Debian Stretch. Emails to that list are not getting processed. I'm not out of disk space. Anything I should check? Thank you, Seth

1 year, 4 months

Re: Log Owner/Moderator actions ban address matching.

by Stephen J. Turnbull

Hitashi mancho writes: > *May 01 13:11:43 2025 (673989) list1(a)example.com <list1(a)example.com>: > Discarded posting: From: user1(a)example.com <user1(a)example.com> > Subject: subject 2025 - Reg.* > > In this log, it is unclear which moderator discarded this message. Is there > any way we can add that to the log? Not easily. That log comes from Mailman core (the list database/post distribution component). The authority core sees to act on that is "you know the REST access user and password", but that's known by Postorius, not by moderators. Weirdly, Postorius doesn't seem to keep a log of user logins at all. If you *need* to know, you can trace back through the logs like this: mailman/vette: <DATE> (<PID>) <LIST>: Discarded posting: From: <EMAIL ADDRESS> Subject: <TEXT> mailman/mailman: [DATE] "POST /3.1/lists/<LIST>/held/8 HTTP/1.1" 204 0 "-" "GNU Mailman REST client v3.3.5" postorius/access: 127.0.0.1 - - [<DATE>] "POST /mailman3/lists/<LIST>/held_messages HTTP/1.0" 200 15228 "<REFERRER>" "<USER AGENT>" nginx/access: <MODERATOR IP> - - [<DATE>] "POST /mailman3/lists/LIST/held_messages HTTP/1.1" 200 3080 "<REFERRER>" "<USER AGENT>" where the DATE should match within a few seconds across the logs and you can probably ID the moderator from the IP address. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months

Mailman-users search results for query "Postorius"