Search results for "Postorius" - Mailman-users

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

3 years, 11 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

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, 2 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, 4 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

5 days, 4 hours

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, 2 months

Re: Welcome Message

by Abhilash Raj

On Tue, Apr 16, 2019, at 7:40 AM, brian(a)emwd.com wrote: > So I create a template with just one line of text and I save it. When I > go subscribe to the list, Postorius throws this error message: > > "A server error occurred. Please contact the administrator." > > The core mailman.log records a whole bunch of exemptions: > <snip> > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='mailman-web', > port=8000): Read timed out. (read timeout=5) > > Removing the template allows normal subscriptions and the generic > welcome message is sent out. > How are you deploying your images? With the default compose file provided with the images, `mailman-web` container should be reachable from `mailman-core` container at "http://mailman-web:8000". If that does not work, there is something wrong in how you are deploying the images. You can set an environment variable to wherever Django from Mailman-web container is listening at " POSTORIUS_TEMPLATE_BASE_URL=http://IP:port" -- thanks, Abhilash Raj (maxking)

6 years, 9 months

Re: footer template priority

by Mark Sapiro

On 6/19/25 15:42, Sam Darwin via Mailman-users wrote: > It takes time to figure out a new feature. I see what is happening. :-) Or, merely one step further. > > After a template is stored in the DB you can remove POSTORIUS_TEMPLATE_BASE_URL because the value is cached in the DB. That explains the caching. > > Next, without POSTORIUS_TEMPLATE_BASE_URL, it assumes http://localhost:8000/mailman3/ . On our server this is not correct, because it's listening on a unix socket, as well as 80 and 443, but not 8000. Actually, it assumes whatever the default is which might be `http://localhost:8000`. See https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/settings/m…. It's Postorius that adds the /mailman3/... when setting the template table entry. If that is not correct for your server, you need to set the correct value in settings.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

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, 1 month

Re: list footer web customization procedure

by Mark Sapiro

On 11/29/21 8:13 PM, Philippe B wrote: > I am new to Mailman 3 and I've been reading all the documentation that I could find, but I haven't been able to figure out how a list owner can use the web interface to customize the footer that appears at the end of each e-mail from the list. > > We're actually after something much simpler (in theory), which is to eliminate the built-in footer altogether for some of our lists. > > Could someone share the instructions for doing that? Thanks. In Postorius go to the Templates tab for the list, click New Template, then in the Name dropdown select [list:member:regular:footer], leave the Data box empty and Save. Do the same for [list:member:digest:footer] if you want to eliminate that one too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Mailman-users search results for query "Postorius"