Search results for "Postorius" - Mailman-users

About the path forward [was: ... regarding message acceptance]

by Stephen J. Turnbull

I'm not Mark, but .... :-) "Plans", you ask? Hmm.... Pawel Grzywaczewski writes: > Any plans to implement message acceptance based on another list? I think that most Mailman 2.1 features are plausible proposals for Mailman 3. While we don't make decisions based on user voting, we do care about user requests. If you want to make a formal request, post a request for enhancement (ie, issue) on our GitLab issue tracker, and post a link here so other interested people can follow it. > What about adding list1 as member to list2? In Mailman 2.1 there > was an 'umbrella' feature I think it doesn't exist in Mailman3. > Any plans to add it? Same as above. I don't know Mark's plans, but he's been active on these lists. I myself hope to have some time for development later in the summer, but I've been away from the code for quite a while, and have at least two prior projects I've expressed interest in. I have no idea about Abhilash or Terri's time, except that they're always busy, and there are a couple of other developers who might drift back in at some point if something exciting starts happening. However, these kinds of additions described above are somewhat more complicated in Mailman 3 than they were in Mailman 2. We have added the ability to identify groups of lists as domains (and therefore have multiple lists by the same name if they are each in a different domain), and the ability to identify groups of email addresses as users. This means that there are more opportunities for unfortunate things to happen. For example, a user might have a particular address for posting to a particular list, and be unhappy if they were accidentally "unmasked" when they posted by a different address, and that post was accepted because those addresses are both owned by the same user. Whether you think this one is a "real problem" or not, we need to do more than a little thinking about such things as we improve Mailman. We missed the window for GSoC this year. We've had excellent success in getting students (I don't think we were ever denied a slot we asked for), so prospects for next year are good. I myself am looking at mandatory retirement in a couple of years, and am planning to ramp up development/consulting activity over this period. So I know a year is a long time, but we are actively supporting existing features, and intend to continue development for the foreseeable future. Finally, Brian Carpenter and EMWD are actively developing alternatives to Postorius and HyperKitty. (Affinity and Empathy, respectively; I believe Affinity is already in beta, Empathy I don't know about status). You can find out more about them in the Mailman Developers <mailman-developers(a)python.org> archives and in the archives of this list. These are independent friendly projects, not hostile forks. You may find them to provide more straightforward access to configurations you want, although they do depend on Mailman core for much "back office" functionality, and obviously they're less mature than Postorius and HyperKitty. But they have the advantage of targeting a much more mature Mailman core, so they'll catch up fast. EMWD hosts a lot of Mailman lists and hosts, so I for one would consider a request for features from Affinity developers to be representative of many list owners.[1] Footnotes: [1] Not to deprecate Empathy, but the relationship between core and any archiver is pretty much "arm's length". Archiver features are mostly independent of the core.

6 years, 1 month

Re: message duplication and an NNTP related error

by Mark Sapiro

On 2/23/26 13:56, Laurens Kils-Huetten wrote: > > I have recently installed mailman3 on a Debian trixie system. How? By following <https://docs.mailman3.org/en/latest/install/virtualenv.html>, installing Debian packages or ?? > While I managed to set up most of it (the mailing lists, postorius and > also a working gateway to our inn2 news server) I'm seeing a weird > duplication of messages, that seems to be related to the error > messages posted below. What is the result from the command `mailman conf -s nntp`? What are all the settings for the list at Settings->Newsgroup Gateway in Postorius? > When I switch off gating to nntp the duplication stops. Also only mail > messages are duplicated, not the postings on the news server. > > Any pointers as to what to look into, or how to remedy this problem > are greatly appreciated :) > > Thanks, > > Laurens > > here come the error logs: > Feb 23 20:39:08 2026 (2776528) ACCEPT: <e4938b85cbd75c0b04867514fc0b8ad9(a)betola.de> > Feb 23 20:39:10 2026 (2776528) ACCEPT: <e4938b85cbd75c0b04867514fc0b8ad9(a)betola.de> The above duplicate post comes before the following error, so I don't think the error is related to the duplication. > Feb 23 20:39:12 2026 (2776530) <e4938b85cbd75c0b04867514fc0b8ad9(a)betola.de> NNTP error for test(a)grenzland.club > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/runners/nntp.py", line 94, in _dispose > conn.post(fp) > ~~~~~~~~~^^^^ > File "/usr/lib/python3/dist-packages/nntplib/__init__.py", line 916, in post > return self._post('POST', data) > ~~~~~~~~~~^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/nntplib/__init__.py", line 909, in _post > return self._getresp() > ~~~~~~~~~~~~~^^ > File "/usr/lib/python3/dist-packages/nntplib/__init__.py", line 492, in _getresp > raise NNTPTemporaryError(resp) > nntplib.NNTPTemporaryError: 441 Can't set system Injection-Info header field This is a response from your nntp server. Note: the above traceback indicates that this nntplib is standard-nntplib from PyPI which is normally only installed if Python is 3.13. If this is Python 3.13 and you have installed Mailman from other than the head of the gitlab branch, see <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 4 weeks

Re: Postorius no connection to REST API

by Mark Sapiro

On 8/8/21 6:44 AM, rrosner5(a)gmail.com wrote: > > I just installed Mailman3-full from debian stable repository (Mailman 3.2.1 to be precise). Mailman itself is working, also are all mailing lists imported from Mailman 2.1. But I just can not get the web interface of Postorius to work. Please see <https://wiki.list.org/x/12812344>. > I did manage to get it running through apache2 after I figured out what I had to remove from the old site config and replace it with the stuff in the automatically created config. Upon loading the site, I was able to log in and verify the mail address, but it kept showing that it wasn't able to connect to the REST API. > > I double and triple checked, that mailman-web.py and mailman-hyperkitty.cfg contain the same API key (api_key in hyperkitty and SECRET_KEY and MAILMAN_ARCHIVER_KEY in mailman web), but that didn't help. Because those aren't the settings that matter for this. What if anything are your settings in the mailman.cfg [webservice] section for hostname: port: admin_user: admin_pass: use_https: (defaults in our distribution are localhost, 8001, restadmin, restpass and no respectively - I don't know if Debian changes these). These need to match the Django settings MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' I also saw a recommendation, that it can cause problems, when the API key uses symbols like / so I switched it to _ in all three places, but that didn't help. The configuration for mailman, mailman-web and hyperkitty all are set to using https, switching them to http doesn't solve any of the problems. > Meanwhile, the site only shows "Internal Server Error" even though I did not change anything. But probably not that relevant while it can't be used either way. What I can provide on logs: > > /usr/share/mailman3-web/manage.py mmclient > Python 3.7.3 (default, Jan 22 2021, 20:04:44) > [GCC 8.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> client.system > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in request > (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1049, in connect > raise socket_err > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1010, in connect > sock.connect((self.host, self.port)) > ConnectionRefusedError: [Errno 111] Connection refused The REST API is apparently not listening on the host/port this is trying to connest to. > An excerpt from /var/log/mailman3/web/mailman-web.log: > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_\ > command_line > utility.execute() > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 308, in execute > settings.INSTALLED_APPS > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 56, in __getattr__ > self._setup(name) > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 41, in _setup > self._wrapped = Settings(settings_module) > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 110, in __init__ > mod = importlib.import_module(self.SETTINGS_MODULE) > File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1006, in _gcd_import > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 728, in exec_module > File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed > File "/usr/share/mailman3-web/settings.py", line 486, in <module> > from settings_local import * > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 724, in exec_module > File "<frozen importlib._bootstrap_external>", line 859, in get_code > File "<frozen importlib._bootstrap_external>", line 916, in get_data > PermissionError: [Errno 13] Permission denied: '/usr/share/mailman3-web/settings_local.py' > [uwsgi-daemons] throttling "python3 manage.py qcluster" for 25 seconds > > not sure where the Permission denied comes from/what permissions should be. /usr/share/mailman3-web/settings_local.py is a symlink owned by root to /etc/mailman3/mailman-web.py owned by list:list with 640 permission. What is executing the manage.py command to start Django. Is it user list? > The apache2 error log contains nothing from the last restart of mailman3 and mailman3-web and trying to load the web page, the only interesting lines to the end of the log are > [Sun Aug 08 14:40:33.642119 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed > [Sun Aug 08 14:40:33.644627 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11893] AH10101: failed to make connection to backend: httpd-UDS:0 > [Sun Aug 08 14:54:22.555229 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed > [Sun Aug 08 14:54:22.555293 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11913] AH10101: failed to make connection to backend: httpd-UDS:0 > [Sun Aug 08 14:58:24.376278 2021] [mpm_event:notice] [pid 2247:tid 140583610946688] AH00492: caught SIGWINCH, shutting down gracefully > [Sun Aug 08 14:58:34.534966 2021] [mpm_event:notice] [pid 3696:tid 140070763447424] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 Python/3.7 configured -- resuming normal operations > [Sun Aug 08 14:58:34.535159 2021] [core:notice] [pid 3696:tid 140070763447424] AH00094: Command line: '/usr/sbin/apache2' I don't use uwsgi and know little about it so I don't know what the Unix domain socket /run/mailman3-web/uwsgi.sock connection is for, but this appears to be some miscunfiguration between apache and uwsgi. Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via tcp port 8000 and uwsgi is configured with [uwsgi] uwsgi-socket = 0.0.0.0:8000 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Re: Configure administrative users via command line?

by kjohnson＠eclypse.org

Thank you for the prompt and informative reply. Mark Sapiro wrote: > ... If you are an owner or moderator of a list > or a superuser, you can handle moderation requests via Postorius. If you > are a list owner or a superuser, you can manage owners and moderators > via Postorius. Yes, I would like to do that. > You can add superusers via the command line django admin > createsuperuser command. For the reference of others like me, createsuperuser will allow you to create a user with a non-unique email address. I strongly recommend against that. mailman shell gave me: >>> from django.contrib.auth.models import User >>> User.objects.filter(is_superuser=True) <QuerySet [<User: admin>, <User: xxxx>]> I dredged a password for admin out of my memory and was able to perform the moderation request. I also set a new list owner.

3 years, 2 months

Re: Auto discard after max_days_to_hold not working.

by Mark Sapiro

On 4/28/25 07:59, Stephen J. Turnbull wrote: > > This doesn't seem to be exposed in Postorius. It's not all that old > in Mailman 3 (April 2020) so it's possible that it is not moved from > Mailman 2 to Mailman 3 by the migration scripts. This is comments in postorius/forms/list_forms.py ``` # TODO: Expose after this functionality actually works in Core. # max_days_to_hold = forms.IntegerField( # min_value=0, # label=_('Discard held posts after'), # required=False, # help_text=_( # 'No. of days after which held messages will be automatically' # ' discarded.')) ``` `mailman import21` will import the setting, but per the above comment, it doesn't yet work. The setting exists and is exposed in REST, but it appears it is not actually implemented. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

Re: Can't Start Mailman3 Core on Fresh Install

by Jonathan Green

I've triple checked the password in mailman.cfg and used the same username/password directly in MySQL and was able to get to the mailman3 database. I did run a test script in python3 using the PyMySQL connector and got the same error. Is there some permissions issue I need to look for? I ran the install as user root - perhaps the user running the python script doesn't have access somehow? On Thu, Jul 21, 2022 at 7:48 AM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Mail Person writes: > > > Hi Everyone. I'm installing Mailman3 on a Ubunu 18.03 server using > > MySQL as the backend. After installing using the mailman3-full > > package and configuring it, I'm getting the following error when > > trying to start the mailman3 service: > > > Jul 21 04:28:44 eps mailman3[81963]: > > sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) > > (1045, "Access denied for user 'mailman3'@'127.0.0.1' (using > > password: YES)") > > I would guess that the password doesn't match. This can happen > because some configuration is done with Python modules (.py files, the > configuration is Python code) where strings are *delimited* by quote > marks (which are not part of the value) and some (.cfg files) are > .ini-style, where all values are read as strings, and so quote marks > become part of the value. > > The web database (mostly user information) and the mailing list > database are separate (because not all Mailman installations use > Postorius and HyperKitty). Are you sure you have the right user and > password for the mailing list database configured in mailman.cfg? > > Other reasons would be in this reference: > > > Jul 21 04:28:44 eps mailman3[81963]: (Background on this error at: > > http://sqlalche.me/e/e3q8) > > > I'm not sure why the access issue is happening. Mailman3-web is > > running fine and I can see the site at mailman3/postorius/lists > > (but it says Page Not Found). > > "Page not found" is probably a consequence of the same access error. > You can probably see it in the database logs. > >

4 years, 2 months

Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/21/20 6:21 AM, r.woithe(a)callassoftware.com wrote: > Hello, > Version: > Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) > Mailman Core API Version 3.0 > Mailman Core Python Version 3.8.2 (default, Jul 16 2020, 14:00:26) [GCC 9.3.0] > > But the Error was there allready before the update have been done. That means the Mailman-Core changed but the error persisted. What is the full traceback from this error? Mailman 3 has not supported Python 2 since 3.0 beta4. It is not clear what is invoking /usr/lib/python2.7/httplib.py, but if it is Mailman core, something is seriously amiss in the way it's installed. Even Postorius and HyperKitty have not supported Python 2 for quit some time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 6:05 PM, William Oliver wrote: > > So.. if I need to do it myself, can you point me to what file I need to > create/modify in the /opt/mailman/mm tree to set up the alias? Assuming you have Postorius working, just go to the Domains view, edit your domain and add an Alias Domain. Otherwise, you can do this in mailman shell, e.g. ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> dm = getUtility(IDomainManager) >>> d = dm.get('example.com') >>> d.alias_domain = x.example.com >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 11:21 PM, David Partain via Mailman-users wrote: > > I removed /usr/share/mailman3-web/settings_local.pyc quite some time > ago, have restarted both mailman3 and mailman3-web numerous times since > then, and today I restarted uwsgi this morning. > > No new settings_local.pyc has yet been created. Ideas..? No. Restarting Mailman core won't help with this. I don't know what's involved in restarting mailman3-web, but I think that restarting it and uwsgi should be enough and a new settings_local.pyc would be created the next time a django process is invoked (e.g., by visiting a Postorius or HyperKitty web page). If this isn't happening, I don't know why. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Flo

On 8/25/25 23:36, Mark Sapiro wrote: > On 8/25/25 12:42, Flo via Mailman-users wrote: >> Hi, >> >> I have setup in Debian Trixie mailman3-full and came that far, that I >> have created a mailing list. I can sent emails to the members. > > Your primary support resource for the Debian package is Debian. See > https://wiki.list.org/x/12812344 > That's right. > > You need to add 'django.contrib.humanize' to the INSTALLED_APPS list in > settings.py. If you Debian packages don't do this, it should definitely > be reported to Debian. > In /usr/share/mailman3-web/settings.py there is: INSTALLED_APPS = ( ... 'django.contrib.humanize', ... ) And POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8001' I think this has also something to do with it. But looks correct for me. Flo But maybe the path

1 year

Mailman-users search results for query "Postorius"