Search results for "Postorius" - Mailman-users

Re: Converting discussion list to read-only list (settings)

by Paul Arenson

Mark Sapiro wrote: > Issue is HyperKittyb-when replying to a message in an existing thread instead of >using the 'reply' action on that message, they use the Start a new thread button. So then >If by "read only" you mean the "Announce only mailing list style" as >opposed to the "Ordinary discussion mailing list style" the only >difference is that for the Announce only style the list attribute >allow_list_posts is False and for the Discussion style, it's True. > >This is the setting in Postorius -> Settings -> Alter Messages -> >Include the list post header an all it does is include or not include >the List-Post: header in mail from the list. Ok...there is no specific setting I see "allow_list_posts" but you wrote "Include the list post header " later on. So i set THAT one to NO? Thank you.

6 years, 6 months

Re: Sanity check of upgrade procedure

by Mark Sapiro

On 10/26/22 17:30, David Newman wrote: > > OK, thanks. Before getting to mistune, this command, run as mailman in a > venv: > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web > uwsgi Mailmanclient > > produced this error: > > .. > > Attempting uninstall: mailman-web > Found existing installation: mailman-web 0.0.6.dev9+gc606169 > Uninstalling mailman-web-0.0.6.dev9+gc606169: > Successfully uninstalled mailman-web-0.0.6.dev9+gc606169 > ERROR: Could not install packages due to an OSError: [Errno 13] > Permission denied: 'WHEEL' > Check the permissions. > > The command also said I needed to upgrade pip. Doing that produced a > similar error. > > How to resolve this error? Thanks again. Was the venv initially created as the `mailman` user? Maybe sudo chown mailman:mailman /path/to/venv will fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Re: MM2 -> MM3 Migration

by Mark Sapiro

On 12/29/22 23:17, Odhiambo Washington wrote: > On Thu, Dec 29, 2022 at 10:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> The default without the since= option is to import only those messages >> from the mbox which are newer than the newest message in the existing >> archive which is exactly what you want. >> > > So I ended up using this and I can see the list metrics indicating that the > last post was on 29Dec22, but > I don't seem to be able to see those posts in the archives. If Postorius list metrics show the last post was 29 Dec, that was a post to the MM3 list and if it was archived, then running hyperkitty_import without a since= option will not import any messages older than that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Re: Template Ignored?

by Mark Sapiro

On 2/17/22 08:04, Stephen Daniel wrote: > Mailman3 people -- > > I created a new list, and used postorius to create a template for " > list:user:notice:welcome". I then used the mass subscription feature to > add myself to the list, having checked "pre-confirmed", "pre-approved", and > "pre-verified". > > I received a welcome message that appears to be the default welcome > message. It certainly wasn't what I put into my template. > > Any suggestions on how I get mailman to use my template? Things I might be > doing wrong? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a full URL by appending `/api/templates/list/list.example.com/list:user:notice:welcome` to that where `list.example.com` is the actual list_id of your list, and go to that URL, what do you get? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/27/22 05:22, Stephan Krinetzki wrote: > > I think there is a communication problem in the chain: > > apache -> uwsgi -> mailmancore/API ->database > > but i can't dig deeper there. Let me know if i should provide more details or logs It seems that this part of the chain apache -> uwsgi -> mailmancore/API is not experiencing delay. It is involved with every Postorius request, most of which seem to have no issues. It is only this one piece mailmancore/API ->database that seems to have an issue and only with this one DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX query. However, like you, I have no idea as to what you could do further to debug this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 11/11/22 10:23, Stephen J. Turnbull wrote: > > The two database configuration is not really a recommendation. I > suppose the practice derives from an abundance of caution, as there > are concepts like "User" that must be implemented in somewhat > different ways across components (core doesn't authenticate users, > while Postorius's primary function is authentication of users). I > myself would worry that there might be name collisions among tables, > which would cause mayhem, but that's probably excessive. FWIW, the Mailman3 installations at both mail.python.org and lists.mailman3.org use a single database and with the exception of Mailman core's tables and Postorius' `template` table, tables are prefixed with application names like `auth`, `django_` and `hyperkitty_`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

Re: Docker mailman3 delete social logins, did something change?

by bob B

Got, Per someones advice I waiting and the bad gateway error cleared. I was being impatient. But I looked at the variables using (docker exec -it mailman-web python3 manage.py print_settings) and INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google'] so in /opt/mailman/web/settings_local.py. I added a modified version INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount'] And the social are gone!!!!!!!

4 years, 7 months

Re: Internal Server Errors in mailmanweb.log

by Mark Sapiro

On 1/22/26 00:53, Washington Odhiambo via Mailman-users wrote: > On Thu, Dec 25, 2025 at 10:46 AM Washington Odhiambo <odhiambo(a)gmail.com> > wrote: > > For some reason, my mailmanweb (I am using Gunicorn) has been misbehaving > lately. > The last change I ever made to my MM3 installation is when I applied the > patch mentioned in this thread. > The misbehavior manifests in the Postrorius web UI becoming inaccessible, > much as mailmanweb is running. It looks like all the logged errors result from an attempt to export a thread from HyperKitty. Is it this export that precipitates the issue? I.e, can you access Postorius first thing after a clean start of mailman web? If so, is it only when you try to export a thread from HyperKitty that the issues start? -- 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: Hyperkitty import from mailman2

by Sten Aus

Hi Thank you Mark and Simon for your input! I can see imported list from Hyperkitty GUI, but it's inactive. I can confirm that I can see those emails from command line (python shell shows Email Objects). Import shows everything is OK: # python2 manage.py hyperkitty_import --settings settings --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox Only emails after 2010-01-01 00:00:00+02:00 will be imported Importing from mbox file /tmp/test.mbox to test(a)list.domain.com /--some 22 emails being imported here --/ 22 emails read 22 email added to the database 22 emails are stored into the database Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index will be updated every minute. Run the 'manage.py runjob update_index' command to update it now. # python2 manage.py update_index --settings settings Indexing 50 emails NB! Only 6 of them are archived from new list (which has been created from Apache). I have imported 2 times 22 emails from /tmp/test.mbox file (to different lists). I am using Apache2.4 with mod wsgi and Postorius and Hyperkitty are in the same django application. Also tested with running server directly and then connecting to a port 8000, but I guess it does not matter, because both of them are using Python script. I have not yet managed to set up cron tasks, as this is relatively new installation, but I have ran them manually. Also, I have done update_index (runjob update_index and manage.py update_index, both ways). SQLite database shows emails, for example there's a thread FMXQVFDRQVRMINVXI4DJB4SHYTJ3EPWP, but If I insert it to web URL I get Django error: No Thread matches the given query. As Postorius and Hyperkitty are in the same Django, they share sqlite database (mailman/web/database.db). Mailman has it's own database in mailman/var/data/mailman.db. Happy holidays Sten On 22/12/2017 21:09, Simon Hanna wrote: > On 12/22/2017 03:39 PM, Sten Aus wrote: >> Hi >> >> I have installed mailman3 - it looks very great! >> >> Now I wanted to try import from mailman2 mbox, so i did: >> >> python2 manage.py hyperkitty_import --settings settings >> --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com >> /tmp/test.mbox >> >> It shows that it have sucessfully imported all emails and I can see >> them from database (sqlite3), but I cannot see them from GUI >> (hyperkitty). Only thing I can see is this inactive "test" list. >> > How did you try to access them using Hyperkitty? Can you try doing > that while logged in as a django superuser? Could you try using a > permalink for a message? If you can access the files from the database > you should be able to construct the urls using the list name and the > message_id_hash of a message. You should try this using DEBUG=True in > the settings.py. The URL would be similar to > http://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/… > > > Another option would be to check if you can access the data using a > python shell. > > `python manage.py shell` to open a python shell preconfigured for > Hyperkitty and then input the following two lines: > > from hyperkitty.models.email import Email > Email.objects.all() > > > This should print out all the messages that are stored in the > database. (You can limit them by appending "[10:]", or any other > python slice) > > What do you see in the UI? Is it somewhat similar to > http://lists.mailman3.org/archives/list/mailman-users@mailman3.org ? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 4 months

Re: Digest Formatting

by mailman＠manygoodideas.com

mailman＠manygoodideas.com wrote: > I have 2 more digest questions, which I'm hoping to get insight on: > 1) Is there a way to trigger a digest for a user (for testing purposes)? Specifically, > is there a function that can be revealed via the REST api to an interface like Postorius > and Affinity? > 2) I have customized list:member:digest:header, but am not seeing the custom text where > I thought it should be. The documentation seems to imply that both > list:member:digest:header and list:member:digest:footer surround each message in the > digest, with the digest starting with list:member:digest:masthead. What I'm seeing is > list:member:digest:masthead, which is followed by list:member:digest:header, then the TOC, > then all the digest entries. I also have a feature request (I didn't see it in the docs), consider creating list:member:digest:mastfoot – a chunk of text that could be at the end of the digest. Thanks.

5 years, 6 months

Mailman-users search results for query "Postorius"