Search results for "Postorius" - Mailman-users

Re: Auto discard after max_days_to_hold not working.

by Mark Sapiro

On 4/28/25 10:55, Mark Sapiro wrote: > > `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. This is now implemented for the next release. See https://gitlab.com/mailman/mailman/-/issues/1215 and https://gitlab.com/mailman/mailman/-/merge_requests/1346 for Mailman core and https://gitlab.com/mailman/postorius/-/issues/628 and https://gitlab.com/mailman/postorius/-/merge_requests/1001 for Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

Re: Finding all held messages

by Mark Sapiro

On 11/28/25 5:43 PM, Peter Chubb via Mailman-users wrote: > > Hi Folks, > Is there a way from the Web UI to find all lists with held > messages? In the next release of Postorius The count of members, held messages and held subscription requests is displayed in the list overview page, but until then, No. See https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-14 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

Re: Finding all held messages

by Peter Chubb

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 11/28/25 5:43 PM, Peter Chubb via Mailman-users wrote: >> >> Hi Folks, Is there a way from the Web UI to find all lists with >> held messages? Mark> In the next release of Postorius The count of members, held Mark> messages and held subscription requests is displayed in the list Mark> overview page, but until then, No. See Mark> https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-1 Great! and thankyou! Peter C

3 months, 2 weeks

Re: How to upgrade to 3.10

by Paul Tomblin

On Sun, Mar 8, 2026, at 6:37 PM, Mark Sapiro wrote: > Does your > /opt/mailman/venv/lib/py<version>/site-packages/postorius/forms/domain_forms.py > match > <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/forms/doma…>? No, it doesn't have the base_url field. Well, that' solves one mystery and gives me another. Why didn't pip update it? Could it be because the version number isn't incremented? What would happen if I just git cloned that repo into a local directory and copied it over? -- Paul Tomblin

1 week, 3 days

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

by Abhilash Raj

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)

6 years, 6 months

remove website example.com via django interface

by Alexander Inzinger-Zrock

remove website 'example.com' via django interface or "how to rush jourself off your feet" **Disclaimer: don't try this at home** in believe to replace the display of 'example.com' in the postorius-webinterface i logged into django-interface, under 'website' (very bottom of the left menu) i added my new website and then deleted 'example.com'. Result: i can't access my webinterfaces any more, neither django nor postorius. Questions: 1. Does somebody know about the correct approach to change the displayed url in the postorius-webinterface? 2. does somebody perhaps know how to revert those removal via CLI or other ways? greetings aiz

11 months, 2 weeks

Unadvertised lists accessible even if not signed in

by Peter Chubb

Hi folks, I'm running Mailman3 3.3.10, with postorius and hyperkitty. I want unadvertised lists to be visible only to the people who are subscribed to them and to site administrators. Right now, anyone who has the name of a list can construct a URL to the signup page, even for unadvertised lists. So, I can go to: https://site.name/postorius/lists/test.site.name/ and get to the test list, even if it is unadvertised. I see people scanning URLs like this in the NGINX logs, looking for lists. How can I prevent anyone not logged in, and not a member of an unadvertised list, from seeing it? Peter C

2 months, 1 week

Re: New releases

by Mark Sapiro

On 6/8/20 1:01 PM, Danil Smirnov wrote: > > I have Postorius verson 1.3.3 but I still see horizontal tabs not vertical > menus. > > Could you elaborate more on this? The first row of horizontal tabs is unchanged, but the `Settings` tab used to have a second horizontal row and now has a vertical list on the left. After you upgraded did you run these django-admin commands? ``` django-admin collectstatic --clear --noinput --verbosity 0 django-admin compress django-admin compilemessages django-admin migrate ``` These 4 commands should be run after every update to Postorius, HyperKitty or django_mainlman3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/13/21 11:39 AM, Stephen J. Turnbull wrote: > Brian Carpenter writes: > > > I think treating all disabled options the same is short-sighted. They > > are all not the same. > > > > -- Some list members will disable their subscription for good reasons > > and will be really upset if a List Owner renables it through ignorance. > > So it is important to know a disable member is done by the member > > itself. > > This is true in principle, but (1) I don't think that the user cares; > if they're looking at it, they know whether they want enabled or > disabled, how it got that way doesn't matter to them, and (2) I can't > see why an admin would disable delivery except on request from a user, > so I can't see why an admin would reenable except on request from a > user. The only case I can see would be a mass reenabling, but that's > not going to happen in the future (I hope). > > > -- Some mailing lists will have multiple list owners managing them. So > > it is important for one List Owner to know when a subscription has been > > disabled by the actions of another List Owner. > > I don't see why, see above. > > > -- A List Owner may not know that some of his List Members are bouncing > > messages for various reasons, so reviewing their Membership roster, they > > see that they have some list members disabled due to bounces and can > > then address those particular problematic members. > > This query is an important use case. But it's the only one, I think, > unless you really have List Owners arbitrarily disabling members' > subscriptions. And if you're thinking about reenabling from that > page, I think you need a lot more information. For example, if the > admin disabled, you need to know if that was a user request or > something else (what?). If bounce disabled, you want to know what the > bounce was ("no such mailbox"? probably not a good candidate for > reenabling), and when (5 minutes ago? ditto). I guess you could just > reenable and see what happens, but that could be risky (eg, sending > mail to non-existent users is frowned upon by some providers). > > > @Abhilash, I highly recommend that you contact me off list about getting > > access to Affinity so you can see what I am talking about. I would love > > to show you what I have done for Member Management. I offered the same > > to Steve but he never was interested in taking a look. > > It's not that I lack interest, it's that life got in the way. > Unfortunately, until I get enough time (man-weeks, I've never worked > on Postorius and very little in Django) to work on Postorius, or > somebody else starts to do it, a look at Affinity is low priority. > Also, it's pretty clear that a quick look isn't going to be very > helpful. The Mailman developers know what Mailman 2 looks like. I > think the benefits to a hands-on admin are pretty obvious vs the > current Postorius, as are Web 2.0 improvments like sorting on the > options. The more subtle improvements you've made are going to > require a guided tour and/or some study to identify and understand. > > Aside: I have to assume that Postorius is aimed at the kind of > subscriber that most of us are, and that list administration was > something of an afterthought, and assumed to be mostly hands-off. > That's the only rationale I can come up with for the design where > list admins need to go to the individual pages to see user options -- > it was easier to reuse the user option page and just give the admin > permission to access and change it, than to provide a (sortable) list > with user details. > > Steve > _______________________________________________ > 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/ I was going to respond in detail but it will be an effort in futility. My opinions are DEFINITELY not valued by you and that is your right as it my right to leave Postorius behind, permanently. Moving to my own interface was one of the best decisions I made and that decision continues to be shown to be a great one when I read threads like this. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

Re: Postorius no connection to REST API

by Richard Rosner

Mark Sapiro wrote: > > 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' They do match. Even the port (still on 8001). > > The REST API is apparently not listening on the host/port this is trying > to connest to. Apparently. The question is why. > > What is executing the manage.py command to start Django. Is it user list? Probably. It depends on who is calling it. I understand too little of the new architecture. But mailman3.service is run as list, mailman3-web.service as root. > > 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 I too have no experience in the combination ow apache and uwsgi. The only other uwsgi app I'm running is on another server and running under nginx.

4 years, 7 months

Mailman-users search results for query "Postorius"