Search results for "Postorius" - Mailman-users

Re: Patch/kludge suggestion and a question on adding accepted addresses

by Mark Sapiro

On 04/24/2017 07:07 AM, David Krantz wrote: > On Sun, Apr 23, 2017 at 11:04 PM, Barry Warsaw <barry(a)list.org> wrote: >> On Apr 23, 2017, at 10:33 PM, David Krantz wrote: > >>> I have another question: In the old mailman you could add accepted >>> senders without adding them to the list. Is that possible in Mailman >>> 3/Postorius? >> >> You do this by creating a "nonmember" subscription for the sender, and then >> setting that member's moderation_action to Action.accept. > > Okay. I see no way of doing that in my instance of Postorius but in > this case it is okay to do it in the command prompt. Yes. There are still quite a few things that aren't yet exposed in Postorius and probably some not yet exposed in the rest API. In these cases you have to resort to mailman shell (aka mailman withlist). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 6 months

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/13/21 2:27 PM, Odhiambo Washington wrote: > On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> Hey Everyone, >> >> I am pleased to announce new stable releases for Mailman Core, Postorius, >> Hyperkitty. >> >> These include both new features and bug fixes. Complete change log for >> each components: >> >> Mailman Core 3.3.3: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > > May I ask if this is a typo? > I am asking because Mailman Core 3.3.4 was announced on Marc 22nd. > So is this new one version 3.3.3 or 3.3.5? The text you are quoting is from the Feb 2 announcement <https://mail.python.org/archives/list/mailman-announce@python.org/message/N…> of the release of Mailman core 3.3.3. Mailman 3.3.4 was released and announced at https://mail.python.org/archives/list/mailman-announce@python.org/message/H… on March 21 and is the current release. There is no "new one". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Re: template head/footer questions.

by Mark Sapiro

On 4/8/22 11:04, bob B via Mailman-users wrote: > I migrated from mailman 2 to mailman3 and had head/footer questions. > > In the mailman 3 GUI see the templates section, so where do those files get edited/stored? in the postorius_emailtemplate table in the database. > I added a footer to a list via the GUI, but I do not see it in: > /var/templates/lists/[listNAME]/en Because when you set a template in Postorius it makes an entry in the template table in the database with a URI pointing to its own API to retrieve the template. > I see some directories corresponding to list names in /var/templates/lists/ But I do not have a directory for all my lists and for the footer one I just added. > > Bottom line, > > I assume I should not edit or create any files in /var/templates/lists/ and just use the GUI? That's up to you. The default search path for templates in the absence of a template table entry (or even with one with a mailman:/// URI) includes the var/templates/lists/list_id directory. is this directory leftover from migrating from mailman 2 to 3? No I have a list admin who has made some head and footer files and wants me to put them in /var/templates/lists/[listNAME]/en/.... but I think that may not be the best option. Again, it's up to you. If you have Postorius and want list admins to be able to create, modify, break, etc. templates without involving you, then Postorius is a good option, but it isn't in all cases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Mark Sapiro

On 2/11/21 10:22 PM, hansen(a)rc.org wrote: > I just had my Mailman suite upgraded. When it got started, I starting receiving messages that hundreds of subscribers to the lists had been disables, including several of the list moderators. This version started supporting bounce processing, but how in the world was this upgrade allowed to act on bounces that were being collected PRIOR to enabling bounce processing?? I'm sorry about that. It's too late now, but the avoidance is discussed at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > I got many angry emails, messages and phone calls asking what was going on, as they were bona fide list members. I was very surprised myself. > > I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? If the user has a Django account, she can see all that info at (e.g. for this list) <https://lists.mailman3.org/mailman3/accounts/subscriptions/> She gets there from `Mailman settings` in the dropdown under her user name. She can also get there via the `Manage Subscription` button on the list's Info page. That takes her to `List-based preferences` for the list. Any setting not selected there is inherited from the Address-based preferences or Global Mailman preferences > Further, even after the upgrade, the moderators still cannot access the list memberships even though all the lists are set to allow that. I would have asked the moderators to do this if this access bug had been fixed, but they can't get there. You've already reported this at <https://gitlab.com/mailman/postorius/-/issues/462>, and it's been previously reported at <https://gitlab.com/mailman/postorius/-/issues/369>. > As a result of these bugs, after consulting with Brian, who helped with the upgrade, I spent many hours re-enabling the several hundred accounts that had been disabled. I had to go through each email notification to find the address of a disabled account, then find the list, then the member, in Postorius, and finally enable the account (at which time Postorius DID show the enabled status). I'm sorry you had to go through this. The potential issue and the avoidances should be better documented. Unfortunately, they aren't. > Please, can the next upgrade include these very basic fixes/enhancements, which I requested a long time ago: > > a. The ability of moderators to see the list membership (a bug). As I note above, this is a known issue. We are a small project with very feew core developers, all of whom are volunteers. There is a merge request at <https://gitlab.com/mailman/postorius/-/merge_requests/423> which purports to fix <https://gitlab.com/mailman/postorius/-/issues/369>, but as you can see from the comment thread, it is not complete and the author has apparently disappeared. If you would like to take it over and address the deficiencies, we would welcome that. > b. The ability of members to change their addresses for all lists they are subscribed to. Users can add addresses to their account and can then change their subscribed address at (again, e.g. for this list) <https://lists.mailman3.org/mailman3/accounts/list-options/mailman-users.mai…> (Get there via the `Manage Subscription` button on the list's Info page.) If one is subscribed to lists via their `primary` address, one can go to `E-mail Addresses` in their account settings and make a new address `primary` and that will change all their subscriptions. > and further, now: > > c. That when members go to look at their subscription info, they can actually see the settings. They can if they go to `Mailman settings` in the dropdown or the `Manage Subscription` button on the list's Info page and look at all the tabs. -- 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: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Stefan Bauer

So i fixed it by myself, just think about it again. ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ Note the trailing slash at the end. After removing it, the webinterface is up again. But i have no idea, why this is NOW a problem and was not in the past. Maybe something has changed in the way, apache is handling this now. Anyway, problem solved for me. Am Mo., 25. Okt. 2021 um 10:45 Uhr schrieb Stefan Bauer <cubewerk(a)gmail.com >: > Dear Users, > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > web-interface via > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > I receive > > Not Found: /mailman//postorius/lists/ > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core > 1) > > Where does the wrong path come from (mailman vs. mailman3) > > After enabling Debug, i see in the browser the following: > > > Page not found (404) > Request Method: GET > Request URL: https://my.mailinglistserver.local/mailman//postorius/lists/ > > Using the URLconf defined in urls, Django tried these URL patterns, in > this order: > > ^$ > ^postorius/ > ^hyperkitty/ > ^user-profile/delete$ [name='mm_user_account_delete'] > ^user-profile/$ [name='mm_user_profile'] > ^accounts/ > ^admin/ > > The current path, /postorius/lists/, didn't match any of these. > > You're seeing this error because you have DEBUG = True in your Django > settings file. Change that to False, and Django will display a standard 404 > page. > > My apache configuration is very simply: > > # more /etc/apache2/conf-enabled/mailman3.conf > Alias /mailman3/favicon.ico > /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > > I dont see where the path gets traversed in the wrong way. Any help is > greatly appreciated. > > thank you. > > Stefan >

5 years

"Something went wrong | Mailman REST API not available. Please restart Mailman core.

by Hirayama, Pat

Greetings, Some of my lists have started displaying this behavior — when you try to access the list page(s), you get a page with this message: Something went wrong Mailman REST API not available. Please restart Mailman core. My mailman-core docker container is running, as are mailman-django-uwsgi, mailman-nginx and mailman-postfix. Restarting the containers doesn't change this behavior. Google suggests restarting mailman core. Or that we might not be using the correct account name, password or port. The weird thing is that it is not all lists. Most of them seem to be fine. Which suggests to me that the issue is with a few lists, but not systemwide, so I think my settings in mailman.cfg, settings.py, settings_local.py are likely correct. For the problem lists, I see this in the log: ERROR 2025-10-29 18:38:56,784 7 postorius Mailman REST API not available ERROR 2025-10-29 18:38:56,790 7 django.request Service Unavailable: /postorius/lists/obfuscated.name.lists.fhcrc.org/ ERROR 2025-10-29 18:38:56,790 7 django.request Service Unavailable: /postorius/lists/obfuscated.name.lists.fhcrc.org/ So, Postorius can't communicate with the API, I guess? I look at settings_local.py: MAILMAN_REST_API_URL = 'http://mailman-core:8001' I believe 8001 is the default, and since I haven't specified one in the [webservice] section of mailman.cfg, I'm assuming 8001 is correct (plus, it works for other lists). There are a few messages waiting for moderator approval — otherwise, I'd probably try just deleting the list and recreating it. Anyone have any suggestions on what else I should look at? Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856 phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org>

1 year

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

by Wolfgang Bock

Dear friends, regarding my mail before, here an additional information. I can show the templates with following command (anonymized): https://active_domain.de/postorius/api/templates/list/testliste01.active_dom ain.de/list:member:regular:footer The complete syslog Oct 30 11:49:52 active_server mailman3[107631]: Oct 30 11:49:52 2021 (107631) post to testliste01(a)active_domain.de from "Sender_Name" <sender_address(a)active_domain.de> anonymized Oct 30 11:49:52 active_server postfix/submission/smtpd[107895]: disconnect from unknown[ ipv6 ] ehlo=2 starttls=1 auth=1 mail=1 rcpt=1 data=1 quit=1 commands=8 Oct 30 11:49:52 active_server mailman3[107630]: --- Logging error --- Oct 30 11:49:52 active_server mailman3[107630]: Traceback (most recent call last): Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 110, in get Oct 30 11:49:52 active_server mailman3[107630]: contents = protocols.get(actual_uri, **auth) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 39, in get Oct 30 11:49:52 active_server mailman3[107630]: response.raise_for_status() Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/requests/models.py", line 943, in raise_for_status Oct 30 11:49:52 active_server mailman3[107630]: raise HTTPError(http_error_msg, response=self) Oct 30 11:49:52 active_server mailman3[107630]: requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://localhost/postorius/api/templates/list/testliste01.active_domain.de/l ist:member:regular:footer Oct 30 11:49:52 active_server mailman3[107630]: During handling of the above exception, another exception occurred: Oct 30 11:49:52 active_server mailman3[107630]: Traceback (most recent call last): Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 430, in format Oct 30 11:49:52 active_server mailman3[107630]: return self._format(record) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 426, in _format Oct 30 11:49:52 active_server mailman3[107630]: return self._fmt % record.__dict__ Oct 30 11:49:52 active_server mailman3[107630]: KeyError: 't' Oct 30 11:49:52 active_server mailman3[107630]: During handling of the above exception, another exception occurred: Oct 30 11:49:52 active_server mailman3[107630]: Traceback (most recent call last): Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 76, in emit Oct 30 11:49:52 active_server mailman3[107630]: msg = self.format(record) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 923, in format Oct 30 11:49:52 active_server mailman3[107630]: return fmt.format(record) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 662, in format Oct 30 11:49:52 active_server mailman3[107630]: s = self.formatMessage(record) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 631, in formatMessage Oct 30 11:49:52 active_server mailman3[107630]: return self._style.format(record) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 432, in format Oct 30 11:49:52 active_server mailman3[107630]: raise ValueError('Formatting field not found in record: %s' % e) Oct 30 11:49:52 active_server mailman3[107630]: ValueError: Formatting field not found in record: 't' Oct 30 11:49:52 active_server mailman3[107630]: Call stack: Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/mailman3/bin/runner", line 33, in <module> Oct 30 11:49:52 active_server mailman3[107630]: sys.exit(load_entry_point('mailman==3.3.3', 'console_scripts', 'runner')()) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/click/core.py", line 829, in __call__ Oct 30 11:49:52 active_server mailman3[107630]: return self.main(*args, **kwargs) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/click/core.py", line 782, in main Oct 30 11:49:52 active_server mailman3[107630]: rv = self.invoke(ctx) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/click/core.py", line 1066, in invoke Oct 30 11:49:52 active_server mailman3[107630]: return ctx.invoke(self.callback, **ctx.params) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/click/core.py", line 610, in invoke Oct 30 11:49:52 active_server mailman3[107630]: return callback(*args, **kwargs) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/click/decorators.py", line 21, in new_func Oct 30 11:49:52 active_server mailman3[107630]: return f(get_current_context(), *args, **kwargs) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/bin/runner.py", line 188, in main Oct 30 11:49:52 active_server mailman3[107630]: runner.run() Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 134, in run Oct 30 11:49:52 active_server mailman3[107630]: filecnt = self._one_iteration() Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration Oct 30 11:49:52 active_server mailman3[107630]: self._process_one_file(msg, msgdata) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file Oct 30 11:49:52 active_server mailman3[107630]: keepqueued = self._dispose(mlist, msg, msgdata) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 93, in _dispose Oct 30 11:49:52 active_server mailman3[107630]: self._func(mlist, msg, msgdata) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 86, in deliver Oct 30 11:49:52 active_server mailman3[107630]: refused = agent.deliver(mlist, msg, msgdata) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/mta/base.py", line 167, in deliver Oct 30 11:49:52 active_server mailman3[107630]: callback(mlist, message_copy, msgdata_copy) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/mta/decorating.py", line 32, in decorate Oct 30 11:49:52 active_server mailman3[107630]: decorator.process(mlist, msg, msgdata) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 264, in process Oct 30 11:49:52 active_server mailman3[107630]: process(mlist, msg, msgdata) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 89, in process Oct 30 11:49:52 active_server mailman3[107630]: footer = decorate('list:member:regular:footer', mlist, d) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 226, in decorate Oct 30 11:49:52 active_server mailman3[107630]: template = getUtility(ITemplateLoader).get(name, mlist, **extradict) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 188, in get Oct 30 11:49:52 active_server mailman3[107630]: contents = getUtility(ITemplateManager).get( Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper Oct 30 11:49:52 active_server mailman3[107630]: return function(args[0], config.db.store, *args[1:], **kws) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 117, in get Oct 30 11:49:52 active_server mailman3[107630]: log.exception('Cannot retrieve template at {} ({})'.format( Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 1477, in exception Oct 30 11:49:52 active_server mailman3[107630]: self.error(msg, *args, exc_info=exc_info, **kwargs) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 1471, in error Oct 30 11:49:52 active_server mailman3[107630]: self._log(ERROR, msg, args, **kwargs) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 1585, in _log Oct 30 11:49:52 active_server mailman3[107630]: self.handle(record) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 1595, in handle Oct 30 11:49:52 active_server mailman3[107630]: self.callHandlers(record) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 1657, in callHandlers Oct 30 11:49:52 active_server mailman3[107630]: hdlr.handle(record) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3.9/logging/__init__.py", line 948, in handle Oct 30 11:49:52 active_server mailman3[107630]: self.emit(record) Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 85, in emit Oct 30 11:49:52 active_server mailman3[107630]: self.handleError(record) Oct 30 11:49:52 active_server mailman3[107630]: Message: 'Cannot retrieve template at http://localhost/postorius/api/templates/list/testliste01.active_domain.de/l ist:member:regular:footer (<no authorization>)' Oct 30 11:49:52 active_server mailman3[107630]: Arguments: () Oct 30 11:49:52 active_server postfix/smtpd[107755]: connect from localhost.localdomain[127.0.0.1] Oct 30 11:49:52 active_server postfix/smtpd[107755]: CF83E13800E8: client=localhost.localdomain[127.0.0.1] Oct 30 11:49:52 active_server postfix/cleanup[107898]: CF83E13800E8: message-id=<000401d7cd73$782717c0$68754740$(a)active_domain.de> Oct 30 11:49:52 active_server postfix/qmgr[1156]: CF83E13800E8: from=<testliste01-bounces(a)active_domain.de>, size=2342, nrcpt=4 (queue active) Oct 30 11:49:52 active_server postfix/smtpd[107755]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Oct 30 11:49:53 active_server postfix/lmtp[107902]: CF83E13800E8: to=<receiver_address(a)active_domain.de>, relay=mail.domain.de[private/dovecot-lmtp], delay=0.44, delays=0.05/0/0.01/0.38, dsn=2.0.0, status=sent (250 2.0.0 <xyz(a)active_domain.de> JcUfNkAVfWGBpQEAs/T6Vg:4 Saved) Oct 30 11:49:53 active_server postfix/qmgr[1156]: CF83E13800E8: removed Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Wolfgang Bock via Mailman-users <mailman-users(a)mailman3.org> Gesendet: Freitag, 29. Oktober 2021 12:42 An: mailman-users(a)mailman3.org Betreff: [MM3-users] mailman3 postorius cannot retrieve template at ... (<no authorization>) 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 _______________________________________________ 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

Re: customized welcome message

by Nils

Forget the previous message. Thank you very much for your help, Mark. I looked at the configuration files once more, and changing POSTORIUS_TEMPLATE_BASE_URL in mailman-web.py fixed the issue for me. Kind regards On 12/7/23 23:09, Nils wrote: > On 12/7/23 22:40, Mark Sapiro wrote: >> How and to what did you set the URL for the template? What does the >> database query >> >> SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; >> >> show? > http://localhost/postorius/api/templates/list/testliste.lists.DOMAIN.TLD > > This value can't work. Now it makes sense that it gets redirected and > the use of localhost also explains why it didn't show in any of the > virtual hosts log files that I was checking until it was redirected. > > However, I didn't set that value. I edited the template at > postorius/lists/testliste.lists.DOMAIN.TLD/templates and there I can > just select a template type and then I get one textarea input field > for the content. > The value in the database is set automatically, when I create a > template in postorius (and is also automatically removed when I delete > a template there). I can't edit this value without manually changing > it in the database. > >> This is very old. Current Postorius is 1.3.10. 1.2.4 is from February >> 2019. The Debian/Ubuntu packages are out of date. We recommend >> installing via the doc at >> https://docs.mailman3.org/en/latest/install/virtualenv.html > > The server will be updated from Ubuntu 20.04 (focal) to 22.04 (jammy) > very soon. The Debian/Ubuntu packages sure have their downsides but > once they work, they update automatically and require very little > maintenance.

2 years, 11 months

Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 3:13 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/5/24 1:52 PM, advorkin(a)cs.princeton.edu wrote: > > > > I went with the apache/uswgi configuration. The site is up and running, > but if I click Postorius, it gets redirected to > https://mysite.com/postorius/lists and I get not found error message. > > > > The same goes for Lists and Archives. > > Compare your urls.py to > < > https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py?re…>. > > Some of the `path` settings are probably not in the same order as in > that file. The > > ``` > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > ``` > settings should come after the > ``` > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > ``` > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > order). Or you can just delete the 'postorius/' and 'hyperkitty/' ones > or you can add > ``` > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > ``` > to your Apache config. > The odd thing is that the HOWTO that he followed never involves the manipulation of any urls.py at all - it's not even mentioned at any point. So obviously the issue is caused by something else and I suspect something within Apache needs to be re-evaluated in the guide. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 8 months

Re: List nonmembers

by Abhilash Raj

On Mon, Jul 8, 2019, at 8:40 PM, Stephen J. Turnbull wrote: > Andrew Bernard writes: > > > Under Users for a list, there is a category for List > > nonmembers. What does this term mean? [It's rather curious > > philosophically when you think about it, because I would have > > thought that the category [all humans - list members] fits that > > category term.] > > I don't recall the exact definition of "list member", but I can't > resist explaining the "philosophy". :-) > > In the mail system as a whole, what we can confirm is a mailable > mailbox. That corresponds to an *address* in Mailman. But users > (typically humans) often have multiple addresses, that they would like > to configure together (eg, single signon, same setting for not-me-too, > etc). Thus we have a *user* concept, which requires a agent to log in > and establish a *user* and attach addresses to it. I don't remember > the exact details, but both *users* and *addresses* can exist > independently of the other, though they are normally linked. Finally, > a *subscription* is a link between an *address* and a *mailing list*. > > ISTR that merging *users* in the database is kind of annoying, so > instead of automatically creating a *user* to back every known > *address* (eg, when banned or moderated), the *address* is allowed to > participate in the list as a banned or moderated address without being > related to a *user*. There may be other cases where an *address* > lacks a *user*. > > I'm pretty sure there are ways in Postorius to create a *user* that > has no *addresses*, although I've not tried, and I don't know if such > Postorius users would be reflected in the core database. That's not True anymore, signing in to Postorius/Hyperkitty requires you to have an email address and that address is propagated to Core (unless, Core is down, which wouldn't block the sign-up process and would result in a Postorius only user) synchronously using sign-up and sign-in hooks in Django. > > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 4 months

Mailman-users search results for query "Postorius"