Search results for "Postorius" - Mailman-users

Re: very few moderation capabilities for moderators

by Mark Sapiro

On 9/16/21 2:39 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > Hi all: > > I need to provide the list moderators a way to change the moderation > flag for users from whichever it is (normally "list default processing") > to "hold for moderation" and viceversa (to "list default" or to "accept") > > I understand that it could be done via console script (That's the way I > did on mailman2: I made two commands using "withlist", one to hold, > moderar.py, and other one to accept, desmoderar.py. I show you below) Are you asking what the equivalent MM 3 scripts would be? > But I think I'm not the only one that could use as an improvement a way > to do this on postorius/web. Postorius allows a list owner or site admin to set Moderation for list members and non members at e.g. https://www.example.com/mailman3/lists/list.example.com/members/(non)member/. Currently, a list moderator who is not an owner cannot do this, but a moderator can set Moderation for the sender of a held post when handling the post. -- 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: including a template failed

by Mark Sapiro

On 9/19/20 2:47 PM, Wolfgang Bock via Mailman-users wrote: > Hi, > > I created a new mailinglist and got during the test-process the following > errormessage in my mailman.log after: > ... > Sep 19 22:55:08 2020 (1433) ACCEPT: > <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> > > Errors: > > Sep 19 22:55:09 2020 (1436) Cannot connect to SMTP server localhost on port > 25 > HTTPSConnectionPool(host='webmail.domain-02.de', port=443): Max retries > exceeded with url: > /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member > :regular:footer (Caused by NewConnectionError('<urllib3.connec > tion.VerifiedHTTPSConnection object at 0x7fc8380f1748>: Failed to establish > a new connection: [Errno -2] Name or service not known')) > ... This is wierd. It looks like we are trying to establish a connection to host='webmail.domain-02.de', port=443 in order to GET /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member:regular:footer, but the error says "Cannot connect to SMTP server localhost on port 25". I have no idea how port 25 is coming into it. Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.l… on the Mailman machine? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? -- 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: Can't subscribe on new site/domain

by Flo

On 10/10/25 04:13, Mark Sapiro wrote: > >> I have deleted site - group - list now. And created the site again. If >> I go to 'view site' I see all mailing lists on the server and not only >> from this site/domain. This is the first thing where it shows >> irregularities. > > I'm not sure what you mean by `view site` but if you mean the VIEW SITE > link at the top of the Django admin UI, that is just a link to the host > site. I.e., if the Django admin page is https://www.example.com/admin/ > site/, its VIEW SITE link just goes to https://www.example.com/ and it's > always the same link regardless of what Django admin page you are on. > The url of the Django view is lists.example.com/mailman3/admin. The 'VIEW SITE' is in the header on the right side. It's a link to lists.example.com/mailman3 which apparently gets redirected to lists.example.com/mailman3/postorius/lists. The difference I am talking about is that lists.example1.com/postorius/lists shows only its mailing lists while lists.example2.com/postorius/lists shows all mailing lists on the server (ie. also mailing lists of example1.com) Flo

11 months, 1 week

Re: Python 3.13 compatibility

by Mark Sapiro

On 3/29/26 7:57 PM, Thomas Krichel wrote: > Thomas Krichel writes > >> What now? > > Actually it looks I could do > > pip install -U mailman==3.3.9 postorius django-mailman3 hyperkitty mailman-web > > To get back to a working system > > But that still leaves me without 3.3.11 which I apparently need for my > import21. If you do that and it results in a working system, you can then patch mailman/utilities/i18n.py as follows --- a/src/mailman/utilities/i18n.py +++ b/src/mailman/utilities/i18n.py @@ -114,8 +114,7 @@ def search(resources, template_file, mlist=None, language=None): languages.append(language) languages.reverse() # The non-language qualified $template_dir paths in search order. - templates_dir = str(resources.enter_context( - files('mailman').joinpath('templates'))) + templates_dir = str(files('mailman').joinpath('templates')) paths = [templates_dir, os.path.join(config.TEMPLATE_DIR, 'site')] if mlist is not None: # Don't forget these are in REVERSE search order! However there are other incompatibilities between the released Mailman versions and Python 3.13. At the moment, until updated packages are released, in a Python 3.13 environment it is best to install all of mailman, django-mailman3, postorius, hyperkitty and mailman-web from the heads of the gitlab branches. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

Additional info/tags on Members

by Stephen J. Turnbull

mkoerber--- via Mailman-users writes: > I have a need to be able to search the membership by association, > ie whether they belong to any of a number of named groups That's just a mailing list that rejects (or discards) all posts. Mailman core (actually, the backend RDBMS) is perfectly happy to manage millions of rows. Postorius is another matter, it's not highly performant when you get into "thousands", and it would just be "list of members", no "tag algebra" searches. > If not can this be counted as a feature request: > - in mailman3 itself: > + add a facility that allows storing additional info to each > member , either as a (largish) comment field or an array of tags > ++ if tags, it should support managing thousands of them (but > each member is likely to only need a few associated) > + if tags are used, each list should have its own set of tags > (though a means to designate a list to participate in a global > tag collection might be useful). > > - in postorious: > + allow modifying the comment field, or adding/removing/modifying > one or more tags to each list-member > + allow searching a group's membership by tags (or substring in > the comment field), > ++ following which mass-operations (deletion, setting > moderation flags etc) should be possible based on > individual selection of the found fields As a volunteer maintainer, I would oppose working to put this in the Mailman distribution. This is a general relational database design, and I am sure if it were available, it would attract many further feature requests. The search and destroy functions would also likely be bug and user error magnets (and both mass deletion and mass moderation are potential disasters). I'm pretty sure that performance in Postorius would be a disaster all of its own -- we'd need to drop a couple levels of abstraction down to raw SQL if you want to query the conjunction or disjunction of multiple tags. We don't have the manpower for this (unless you want to pay for it, there are plenty of consultants who can do it, including my employer). -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 2 weeks

Re: sqlite3 Database "read only" error on mailman_sync job

by Ugnius S

Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. May mailman processes are next: 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 Looks like there are no double. Nothing more is running. 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: > On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: > > > I have installed using documentation. My linux distribution version has no > full package available. I have installed step by step: > $ sudo pip3 install mailman > $ sudo pip3 install postorius > > $ sudo pip3 install hyperkitty > > $ sudo pip3 install mailman-hyperkitty > > And of course all mandatory components... Everything without errors, I > can drop db files and I can download mailman-suite again and start from > empty page again. But it will not guarantee that DB will not become READ > ONLY again. Here should be logic. No developing support here? > > > Could you be running two separate processes such that the database is > locked by one and so other finds it as READ Only? When you find a read only > database, can you check if it is open in some other process? > > > > > 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: > > > > On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: > > Hi. All the project installation is under the same user / path and > > it works. Archiving working as well, (just one remark: no matter what > > to set in postorius, hyperkitty shows list as public) > > I have found work around - it is possible to change list as private in > > "admin" page. > > I started to get issues with runjobs after I have created couple of > > new lists with "no archive" option. > > How did you install all these components. It seems there the installation > is broken in weird ways. > > > > > If as owner user from project home I run: > > > > django-admin mailman_sync > > > > Traceback (most recent call last): > > File > > > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", > > line 84, in _execute > > return self.cursor.execute(sql, params) > > File > > > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", > > line 383, in execute > > return Database.Cursor.execute(self, query, params) > > sqlite3.OperationalError: attempt to write a readonly database > > > > "django-admin runjob sync_mailman " - makes read only errors as well. > > "django-admin runjob new_lists_from_mailman" > > django.db.utils.OperationalError: attempt to write a readonly database > > END TRACEBACK > > > > I did not find information how to fix this. It was worked without errors > > before. > > I noticed, that if I stop mailman, "django-admin mailman_sync" starts > > to work. > > If I start "mailman start", then "django-admin mailman_sync" failing > > again. > > I did not check other jobs, but I think what is related to database, > > will get errors. > > Seems mailman locking the database. It is not a file permissions issue. > > Mailman db location is: /project_directory/var/data/mailman.db > > > > if to rename /project_directory/var/data/mailman.db to something, > > mailman creates database file size 0, django-admin runjobs start > > working, but of course postorius stops working. I did it for testing. > > I have returned this database file back, postorius started to work > > again, but django-admin runjobs does not work, error: "database read > > only". > > Please help me how to fix this issue. > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > -- > thanks, > Abhilash Raj (maxking) > > > -- > thanks, > Abhilash Raj (maxking) > > >

7 years

Re: Change digest frequency and default threshold

by Mark Sapiro

On 9/21/18 6:21 AM, Henrik Rasmussen wrote: > When creating a new list in Mailman 3, the Digest Size Threshold is set to 30KB, which is not much in my opnion. > > 1) How do I set another default for Digest Size Threshold for new lists. It's hard coded in mailman/styles/base.py. It should be a config setting, but I think it's not. > 2) How do I change the default for existing lists Postorius -> Settings -> Digest > When Digest Size Threshold is not reached, mails seems to be sent according to digest_volume_frequency': which is set to 'monthly'. The web interface doesn't seem to have a setting for this. No. digest_volume_frequency only controls how often the digest volume number increments (and issue number resets). In order to send periodic digests, you need to run 'mailman digests --periodic' via cron. > How do I change this setting, both on a single list and the default for new lists? The only setting is the lists digest_send_periodic which again is hard coded (to True) in mailman/styles/base.py. For existing lists, it is exposed in REST, but not yet in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Stephen J. Turnbull

Franklin Weng writes: > However in the Archive section I couldn't see anything and all the > lists were "inactive" and hence were hidden by default. If you can see that much, HyperKitty is running. > There is no systemd service for Hyperkitty. systemd runs Apache, which loads mod_wsgi, which runs Python, which imports the HyperKitty package, which responds to web requests by building pages dynamically using Django from information from Django's database, which may be backed by MySQL, PostgreSQL, or sqlite3. Sounds complicated, but it performs well once you get it properly configured. Have you sent mail to the lists? Has it been delivered to subscribers? > I confirmed that api_key set in the /etc/mailman3/mailman-hyperkitty.cfg > and /etc/mailman3/mailman-web.py is the same. I also confirmed that the > apache2 wsgi module has been loaded. > > In the mailman.cfg database is set to mysql and in the mailman-web.py > database is set to sqlite3. Does it matter? I don't think they need to be the same. The HyperKitty and Postorius databases are a Django database backed by an RDBMS (typically sqlite3, PostgreSQL, or MySQL). The databases used by the Mailman core and the Django webservices HyperKitty and Postorius are conceptually separate, although they can be backed by the same RDBMS server. However, sqlite3 is likely to result in poor performance compared to PostgreSQL or MySQL. You have to configure HyperKitty's database. In my sqlite3 test installation it looks like this: # Top of settings.py. BASE_DIR is the directory containing settings.py. BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__))) # 30-50 lines later: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', # This database file is in the same directory as settings.py. 'NAME': os.path.join(BASE_DIR, 'hyperkitty.db'), # Not used with sqlite3: 'USER': '', 'PASSWORD': '', 'HOST': '', 'PORT': '', } } Does the database file named by 'NAME' exist? I would recommend getting your sqlite3 configuration running, then you know that HyperKitty is partly working if the hyperkitty.db file is getting updated as you test Mailman by sending messages, and you can check if it's fully working by using HyperKitty's web pages. Then convert to MySQL for performance. Steve

6 years, 10 months

Re: including a template failed

by Wolfgang Bock

Dear Mark, Q: Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li sts.domain-03.de/list:member:regular:footer on the Mailman machine? A: No Q: What is your setting for POSTORIUS_TEMPLATE_BASE_URL? A: was: POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' Changed it to: POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' Now another problem occurs: Sep 23 22:51:34 2020 (13492) Cannot connect to SMTP server localhost on port 25 HTTPSConnectionPool ... 'localhost' doesn't match either of 'blog.domain-04.de', 'lists.domain-04.de', 'mail.domain-04.de', 'domain-04.de', 'www.domain-04.de'"))) Port 25 entry results from the manual regarding the postfix configuration: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht ml e.g.: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Sonntag, 20. September 2020 01:05 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: including a template failed On 9/19/20 2:47 PM, Wolfgang Bock via Mailman-users wrote: > Hi, > > I created a new mailinglist and got during the test-process the > following errormessage in my mailman.log after: > ... > Sep 19 22:55:08 2020 (1433) ACCEPT: > <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> > > Errors: > > Sep 19 22:55:09 2020 (1436) Cannot connect to SMTP server localhost on > port > 25 > HTTPSConnectionPool(host='webmail.domain-02.de', port=443): Max > retries exceeded with url: > /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list: > member :regular:footer (Caused by NewConnectionError('<urllib3.connec > tion.VerifiedHTTPSConnection object at 0x7fc8380f1748>: Failed to > establish a new connection: [Errno -2] Name or service not known')) > ... This is wierd. It looks like we are trying to establish a connection to host='webmail.domain-02.de', port=443 in order to GET /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member :regular:footer, but the error says "Cannot connect to SMTP server localhost on port 25". I have no idea how port 25 is coming into it. Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li sts.domain-03.de/list:member:regular:footer on the Mailman machine? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 11 months

Re: mailing list aliases

by Mark Sapiro

On 01/19/2018 03:09 PM, Dmitry Makovey wrote: > Not sure whether to mark this "SOLVED" yet - but when I manually updated > postgres DB with the aliases I wanted - everything started to work as > expected. > > so it does sound like a bug in mailman-core 3.3.0 . Shall I file it or > was it already fixed in 3.3.1 (anouncement page didn't list that fix) As far as I know, this is not a bug in core. It is <https://gitlab.com/mailman/postorius/issues/58> however, this may in fact be a bug in the REST API in which case I don't think it's fixed in API 3.3.1 >> 2. Related to #1 - we've migrated our mailing lists from foo(a)my.com to >> foo(a)lists.my.com however we've preserved old addresses. But in new setup >> mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: >> implicit-dest" . What's the best course of action here to get mailing >> list respond to multiple email addresses? acceptable_aliases is the way to address this, but as you note, it can't be properly set via Postorius and possibly via REST. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 8 months

Mailman-users search results for query "Postorius"