Search results for "Postorius" - Mailman-users

Incorrect error log message in OutgoingRunner._dispose()

by Stephen J. Turnbull

Craig Leres via Mailman-users writes: > One feature the existing mailman 2 lists uses that I can't get > working with mailman 3 are templates. After using "mailman > import21" I found files with names such as > list:member:regular:footer.txt in the list tree. However they were > ignored so I removed them I tried tried creating a template using > the web postorius gui. When a message is injected, I see an error > log from the out runner: > > Apr 25 12:32:22 2026 (82977) Cannot connect to SMTP server > 127.0.0.1 on port 25 > > Following the error message, the out runner goes cpu bound, > creating and deleting queue files in queue/out with .pck and .bak > extensions, very quickly. That is a bug. The error isn't a temporary failure, at least not if it occurs several times. Also, I don't see how that error could result from the exception below. > I updated the code to print the exception and it tells a completely > different story: > > Apr 25 12:38:15 2026 (83339) Cannot connect to SMTP server > 127.0.0.1 on port 25 (HTTPConnectionPool(host='localhost', > port=8000): Max retries exceeded with url: > /api/templates/list/test.example.com/list:member:regular:footer > (Caused by NewConnectionError("HTTPConnection(host='localhost', > port=8000): Failed to establish a new connection: [Errno 61] > Connection refused"))) That suggests that Postorius isn't running. Port 8000 is the default port used by Postorius (and if running, HyperKitty). The problem is that Postorius and HyperKitty are intentionally separate applications because a lot of sites wanted the ability write their own. I don't really understand the design, but what happens is that when you configure a template via Postorius, it gets stored in storage accessible to Postorius. What Postorius returns to Mailman is a URL for Mailman core to query to retrieve the template from Postorius. Core fetches from that URL, then applies it to the outgoing message. The first thing to do is to check that all your host and port configurations are consistent. The defaults are all localhost (but you should specify either 127.0.0.1 or ::1 because Postfix doesn't look in /etc/hosts at all and we've seen cases where one program thinks it's using IPv4 and the other IPv6), and the ports are 8000 for Django (Postorius and HyperKitty, configured in settings.py) and 8001 for the core REST API (configured in mailman.cfg). (If the defaults are satisfactory you may not see any settings for those in settings.py and mailman.cfg, depending on how you created those conffiles.) Then make sure Postorius is running. At least try running Postorius and then "mailman unshunt" to see if that is the problem. If for some reason you want to normally run Mailman core without Postorius, then you will have to either edit the templates in place in the Mailman package, or add local directory to the search path (offhand I don't know if there is one, the fallback template directory may be hard-coded). I guess it would also be possible to write a very lightweight template manager process that emulates the Postorius API endpoint, but that wouldn't give you a GUI for template management. You'd still need to run Postorius for that unless you're really into web development. > I'm using the default webservice port (8001) "webservice" in mailman.cfg refers to the REST API. The web UIs run in different processes and use 8000 (by default). > so I would not expect anything to ever be listening on 8000. > > When I stop the runners, the problematic queue file is moved to the > shunt queue. That's normal. Once you get the configuration straightened out, "mailman unshunt" should cause those posts and other mail to flow properly. > ! except socket.error: Ah, that's quite generic, and I see now why that would catch the attempt to fetch the template. It's obnoxious that the dev who wrote the code chose to throw away the exception data in favor of a generic "something's broke" message, but that happens. It was probably written before the web GUI for managing templates was added. Regards, Steve -- 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: FILTER_VHOST fix - was: Postorius & multi domain

by Mark Sapiro

On 1/6/22 10:56 AM, jdanitxu(a)gmail.com wrote: > Hi, > we are writing from the NGO Engineering Without Borders - Spain. > After having migrated from mailman2 to mailman3 in a server with Debian 11, our domains are like these: > https://listas.isf.es/mailman3/ > https://listas.andalucia.isf.es/mailman3/ > https://listas.aragon.isf.es/mailman3/ > ... > I have set FILTER_VHOST = True and restarted postorius (systemctl restart mailman3-web), but when we enter in every URL, we see all the lists. Any hint to search? How did you install Mailman. If you are using the Debian packages, they are out of date. I'm not exactly sure the state of Postorius in them. The latest Debian mailman3-web package is 0+20200530-2 which may or may not include https://gitlab.com/mailman/postorius/-/merge_requests/500. What is your Postorius version? if it is less than 1.3.3, FILTER_VHOST doesn't work. Even if it is 1.3.3 or newer there is an issue with FILTER_VHOST. Namely, Postorius doesn't filter lists based directly on web domain. It filters based on the email host associated with the web host. There are two possibilities. If more than one domain has the same web host but different email hosts, no filtering is done. If domains with different web hosts have the same email host, all the lists with that email host will be shown. In short, FILTER_VHOST only works well with Postorius if each web host domain has a unique email host. I'm guessing that in your case, the email host for all three domains is `isf.es` so all lists are shown. > P.S: apart from this conversation, I suggest to include in documentation related to migrations the fact that is important to have 'charset': 'utf8mb4' if MariaDB/MySQL is used, in order not to get migration errors doubt to encodings. We had 75 GB of mbox messages and some of them have had trouble doubt to not setting it before. I think this should be fixed in Mailman core 3.3.5 which defines the charset and collation for many columns/tables as utf8mb4 for MariaDB/MySQL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

Re: Ann: Postorius 1.3.6 is now out

by Odhiambo Washington

On Wed, Sep 29, 2021 at 6:28 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hey Everyone, > > I just tagged and released Postorius 1.3.6. This release includes both bug > fixes and > new features. > > Some of the notable features include > - Ability to list and handle un-subscription requests to the list > - Option to choose delivery mode and delivery_status directly when > subscribing to a list > - Addition of a user management interface, which allows updating a users > password, > manually verifying their email addresses, update user’s Display Name > etc. > - Expose a number of Bounce processing related options in List’s settings > > A full list of changes is available here > > > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 > > You can install this release using pip > > $ pip install postorius django-mailman3 mailmanclient —upgrade > root@svr:/usr/local/mailman # pip install postorius django-mailman3 mailmanclient —upgrade ERROR: Invalid requirement: '—upgrade' Why do you think I got this? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

5 years, 1 month

mailman3 postorius cannot retrieve template at ... (<no authorization>)

by Wolfgang Bock

Hello, the question is: postgres - mailman3web-postorius_emailtemplate table vs mailman3 - templates table I installed a brand new mailman3 with mailman Core 3.3.3, Api 3.1, Core Python 3.9.2 postgres12 nginx on debian bullseye. I created a template via postorius -> lists -> (testliste01) -> templates -> new template -> [list:member:regular:footer] and [list:member:digest:footer] They are shown in the postgres database mailman3 table templates: id name context uri username password 14 list:member:digest:footer testliste01.mydomain.de http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m ember:digest:footer 15 list:member:regular:footer testliste01.mydomain.de http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m ember:regular:footer First there where no templates in the /var/lib/mailman3/templates folder, which was empty after installation. Later I created in /var/lib/mailman3/templates theses folders and the files /list/testliste01.mydomain.de/list:member:digest:footer + list:member:regular:footer owned by list:list 644 A testmail went through but instead of the default footer no footer was shown. In the sys.log I found the following error message: Oct 29 11:28:04 myserver mailman3[33015]: Message: 'Cannot retrieve template at http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m ember:regular:footer (<no authorization>)' How can I solve this problem? What kind of authorisation is meant? list? restadmin? I read in https://docs.mailman3.org/en/latest/config-core.html#configure-templates ... list specific templates invar/templates/lists/LIST-ID/LC/ ... I guess the LC means Language Code. But in the database table templates no LC subdirectory is mentioned (in my case must be de). And I read (dont know where) .... The templates created in Postorius are created in the postorius_emailtemplate table in Mailman's database and referenced via URLs like 'https://example.com/mailman3/api/templates/list/<list-id>/<template-name>'. I.e., they are not stored in the file system. ... That's true. I found in postgres database mailman3web in the table mailman3web postorius_emailtemplate my id name data language created_at modified_at context identifier 15 list:member:digest:footer postorius footer digest 1x linefeed 2021-10-29 11:17:40.664689+02 2021-10-29 11:26:48.692628+02 list testliste01.mydomain.de 16 list:member:regular:footer postorius footer non-digest 1x linefeed 2021-10-29 11:18:29.166241+02 2021-10-29 11:27:24.519024+02 list testliste01.mydomain.de But my question is how to integrate this into the mailman3-system. The language isn't set either. Thanks in advance! Regards Wolfgang

5 years

Re: Where is postorius.wsgi?

by Andrew Hodder

Peter, You need to install uwsgi or antoher wsgi service and setup the socket for apache/django to speak to each other through. In mine, I use uwsgi service, configured and pointed it to the wsgi-file in the postorius django project. Then pointed nginx (I don't use apache, but same difference) to the uwsgi socket I created. It was actually one of the trickiest parts of the setup (it can be strict about how it expects the Django modules to be "advertised" back to the web server). And then did the same thing for hyperkitty (it and postorius are on separate wsgi sockets). Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Thu, Jan 25, 2018 at 8:27 AM, Peter Münster <pmlists(a)free.fr> wrote: > Hi, > > I try to install Postorius, but I don't find the file postorius.wsgi. > Where should I get it please? > > This is, what I've done so far: > - git clone https://gitlab.com/mailman/postorius.git > - cd postorius > - python3 setup.py install > - cd example_project > - virtualenv venv > - . venv/bin/activate > - pip3 install -r requirements.txt > - in venv/lib/python3.6/site-packages/django_mailman3/lib/mailman.py: > replace "urllib2" by "urllib.error" > - python3 manage.py migrate > - python3 manage.py createsuperuser > - python3 manage.py compilemessages > - python3 manage.py collectstatic > > Now I try to follow > https://postorius.readthedocs.io/en/latest/deployment.html# > apache-with-mod-wsgi > but I don't find postorius.wsgi ... > > TIA for any help. Kind regards, > -- > Peter > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 9 months

Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/18/19 11:13 PM, Paul Arenson wrote: > Thank you Mark. I appreciate the response. Let me respond in two messages. The first is to confirm the rules for signing off for both types of used: > > The second is to clarify my problems with the signup procedure and how I might deal with it. (Mostly a very small change on your part and an explanation on my website for my users) > > 1) So, for both subscribers vi postorius only and hyperkitty users: > email to discuss-leave(a)list.tokyoprogressive.org (or > discuss-unsubscribe(a)list.tokyoprogressive.org) Yes, but you seem to have some confusion about how things work. Mailman 3 consists of several pieces. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/introduction.html…>. As it says there, Postorius and HyperKitty are separate, web based applications for list management and archiving respectively. Both of these are Django projects - Django is a Python web framework. What you refer to as hyperkitty users are actually Django Users. When you create and account and/or log in at Postorius or HyperKitty, you are creating/logging in to a Django account. When you are logged in, Django, and thus Postorius and HyperKitty know who you are. If you aren't logged in, they don't. > 2) Only for hyperkitty users, you can login, go to > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > and click the big red unsubscribe button. You need to be logged in for this so Postorius knows who to unsubscribe. > 3) Also only for hyperkitty users, log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to > https://list.tokyoprogressive.org/user-profile/ and click the Delete > Account tab or go directly to > https://list.tokyoprogressive.org/user-profile/delete This deletes your Django account, but does not affect your list memberships. > (Guessing that #3 will not unsubscribe the person and--if they have already done 1 or 2, failing to do number 3 is not going to be a big problem. Am I right?) That's right. The important thing is Postorius itself knows nothing about lists or list settings or list members. It gets and/or sets this information by communicating with Mailman core. You saw an example of this when you changed an archive from public to private. Postorius told Core to make it private and Postorius would then tell you it was private because it would get that information from Core. But, it required a daily cron job to propagate that setting to HyperKitty, so HyperKitty didn't get the memo until later. I hope this helps rather than adding confusion. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

Re: message awaits moderator approval

by Mark Sapiro

On 12/21/22 08:53, Eggert Ehmke via Mailman-users wrote: > > Now it turned out that there were several relicts of the old list in the > database, in particular in the template table. I removed them using direct SQL > commands. > > Now my new mailing lists work as expected. > > Is this a bug in postorius? I think when I delete a mailing list, all relicts > should be deleted from the database. Were there Postorius custom templates for that list?, I.e. did the template table entries have Postorius URLs. If so, this is probably a Postorius issue. I haven't actually looked, but when Postorius deletes a list, it should delete any of it's templates from the postorius_emailtemplate table and revert the template table entries. Beyond that, Postorius is just telling Mailman core to delete the list, and when Mailman core does that it should probably also remove any var/templates/lists/<list_id> directory and any entries from the template table with context = the list_id. If it doesn't, this is a core issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

So, why are css & js files only served with "DEBUG = yes" ?

by Simon Liebold

Hello List, I did see this discussed in #180 <https://gitlab.com/mailman/postorius/issues/180>, but I didn't quite understand if this is an issue or not. Why is it that I can run the development server just fine. [07/May/2017 13:23:47] "GET /static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/css/style.css HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/django-mailman3/js/main.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/django-mailman3/css/main.css HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/js/script.js HTTP/1.1" 304 0 [07/May/2017 13:23:47] "GET /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 304 0 And as soon as I comment out # SECURITY WARNING: don't run with debug turned on in production! # DEBUG = True in mailman-suite/mailman-suite_project/settings.py and restart it 404s on me. [07/May/2017 13:41:36] "GET /static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 404 127 [07/May/2017 13:41:36] "GET /static/django-mailman3/css/main.css HTTP/1.1" 404 109 [07/May/2017 13:41:36] "GET /static/postorius/css/style.css HTTP/1.1" 404 104 [07/May/2017 13:41:36] "GET /static/django-mailman3/js/main.js HTTP/1.1" 404 107 [07/May/2017 13:41:36] "GET /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 404 125 [07/May/2017 13:41:36] "GET /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 404 123 [07/May/2017 13:41:36] "GET /static/postorius/js/script.js HTTP/1.1" 404 103 [07/May/2017 13:41:36] "GET /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 404 123 So the choice is insecure vs. ugly? Neither of those sounds very tempting. I guess, I am missing something, or no? Simon

9 years, 6 months

Re: FILTER_VHOST fix - was: Postorius & multi domain

by Mark Sapiro

On 4/22/20 11:52 AM, Mark Sapiro wrote: > > I'm currently working on a better fix. I'll post here on my progress. I've got a tentative fix at <https://gitlab.com/mailman/postorius/-/merge_requests/500/>. You can see the changes there to the file src/postorius/views/list.py. This fix is limited in that it should enable FILTER_VHOST work in an environment where there are domains with web host different from mail host, but if there are multiple domains with the same web host but differing mail hosts, going to that domain's Postorius lists view will show all domains as if FILTER_VHOST is False. I.e. consider the following set of domains: mail host web host example.com lists.example.com example.net example.net example.org lists.example.org example.edu lists.example.org With the fix installed and FILTER_VHOST = True https://lists.example.com/postorius/lists/ will show only the example.com lists https://example.net/postorius/lists/ will show only the example.net lists but https://lists.example.org/postorius/lists/ will show all lists, not just the example.org and example.edu lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

Where is postorius.wsgi?

by Peter Münster

Hi, I try to install Postorius, but I don't find the file postorius.wsgi. Where should I get it please? This is, what I've done so far: - git clone https://gitlab.com/mailman/postorius.git - cd postorius - python3 setup.py install - cd example_project - virtualenv venv - . venv/bin/activate - pip3 install -r requirements.txt - in venv/lib/python3.6/site-packages/django_mailman3/lib/mailman.py: replace "urllib2" by "urllib.error" - python3 manage.py migrate - python3 manage.py createsuperuser - python3 manage.py compilemessages - python3 manage.py collectstatic Now I try to follow https://postorius.readthedocs.io/en/latest/deployment.html#apache-with-mod-… but I don't find postorius.wsgi ... TIA for any help. Kind regards, -- Peter

8 years, 9 months

Mailman-users search results for query "Postorius"