Search results for "2021" - Mailman-users

Added two tasks for Google Summer of Code

by Stephen J. Turnbull

Based on recent threads, I've added two tasks to our 2021 GSoC ideas page: https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202021#List_Configura… https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202021#User_Profile_T… Bcc'd to David and Johannes because I referred to threads starting with their posts. If you want me to paraphrase in the task description, let me know, but I preferred to do it this way to encourage applicants to join the community. (Note: we haven't been selected yet, so this isn't any more public than the archived mailing lists.) Suggestions of other GSoC tasks and refinements to existing ones welcome. However, please discuss them on the list (or to a core dev privately) unless you have GSoC experience. Google has specific requirements for Summer of Code projects, so there are a lot of important tasks that should not be on that page. If you have an enhancement that you'd definitely like to put on our agenda, and also suggest for GSoC, feel free to file an issue on the tracker and point me, Mark, or Abhilash to it. Steve

4 years, 4 months

Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/9/21 12:59 PM, Duane Raymond wrote: >> What is the full error including traceback from Mailman's mailman.log >> for the shunted messages? > > My test just now raised the following error: > ...> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 174, in _lookup > pref = getattr(self.address.preferences, preference) > AttributeError: 'NoneType' object has no attribute 'preferences' > Mar 09 20:52:56 2021 (26271) SHUNTING: 1615323176.8137882+cd8501dd322d0ca6b4a3a187d57bc691cd0ec343 > > and running the following command raised the result below > root@mail:~# mailman qfile var/queue/shunt/1615323176.8137882+cd8501dd322d0ca6b4a3a187d57bc691cd0ec343.pck That result is as expected. It isn't the message that causes the problem. We are now back to <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> As I said there, Mailman is going through the roster of regular (non-digest) list members to find those with delivery enabled and it finds a member that has no associated address. Can you view the members of this list? -- 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: hyperkitty.views.mailman Could not archive the email with message-id '<snip>': A string literal cannot contain NUL (0x00) characters

by Gilles Filippini

Gilles Filippini a écrit le 12/03/2021 à 01:41 : > Mark Sapiro a écrit le 12/03/2021 à 00:59 : >> On 3/11/21 3:10 PM, Gilles Filippini wrote: >>> >>> Looking at the offending message with 'mailman qfile', it appears it is >>> a legitimate one actually, sent from an Android phone. >>> >>> Couldn't hyperkitty be a bit less strict? >> >> >> Possibly. It looks like this may be >> <https://gitlab.com/mailman/hyperkitty/-/issues/271>, fixed? by >> <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215>. What >> HyperKitty version is this? >> <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215> is in 1.3.2. >> >> If your HyperKitty is >= 1.3.2, please file a new issue at >> <https://gitlab.com/mailman/hyperkitty/-/issues> > > This is Hyperkitty 1.3.4. > I'll file an issue tomorrow. Here it is: https://gitlab.com/mailman/hyperkitty/-/issues/346 Thanks, _g.

4 years, 3 months

Re: Message-Footer after migrating to Mailman3

by Abhilash Raj

> On Jul 9, 2021, at 9:15 AM, christopher.claus(a)tgcamberg1848.de wrote: > > Mark Sapiro wrote: >>> ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. >>> WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer >>> It appears you created the new template with Postorius, but there is an >> issue for Postorius templates. Possibly your Django setting for >> POSTORIUS_TEMPLATE_BASE_URL needs to be adjusted. >>> Obviously I have a problem with the hostname. I set >>> [code] >>> POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 >>> [/code] >>> where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost >>> [code] >>> wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamberg... >>> [/code] >>> will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? >>> If that works, yes. > > Hi Mark, > > thanks for your reply and excuse my delay. I was very busy in the last weeks but made some tests. Newly created templates with POSTORIUS_TEMPLATE_BASE_URL=http://localhost:8000 did not work. I changed it to my fqdn - at the moment I am able to access the template via this URl (e.G. http://lists.example.de:8000/postorius/api/templates/list/homepage.lists.ex…) > But if I try to send an email I got the following error: You want the URL at which Postorius (postorius) is available from Core (mailman-core container). The default for that in the container images is set to http://mailman-web:8000. Does that not work for you? If you want to verify, you want to exec into the Core’s container (`docker exec -it mailman-core bash`) and see if you can curl the URL from inside there. If you are using the default docker-compose-postorius.yaml then there is a /etc/hosts entry created by docker for the mailman-web container, hence `http://mailman-web:8000` works there (but it won’t work on the host, since docker doesn’t modify the host’s /etc/hosts). There might also be a bug in play here which would cause such connection refused errors when subscribing/unsubscribing when there was a template configured for the list. Is that the case for you or are you seeing always when trying to send the email (which would imply that the Web container simply isn’t reachable from Core). -- thanks, Abhilash Raj (maxking)

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

4 years, 1 month

Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Quanah Gibson-Mount

--On Wednesday, March 3, 2021 8:28 AM +0100 Lars Schimmer <l.schimmer(a)cgv.tugraz.at> wrote: > >>> Distribution packages tend to be useful for really basic things like >>> libraries. For constantly evolving projects where you need to be >>> current, they're more of a detriment. >> >> So much this. > > You do not need a bleeding edge software on production servers. You just > need bug free, whihc is easy done with packages on distributions, if > maintainers do it well enough. If you think the versions of software provided by distributions are bug free, you're living in a very bizarre realm that doesn't mirror reality. I've been running production systems for over 20 years for anything from private educational institutions to large scale multinationals. You don't get reliable production services running the ancient bug-ridden software provided from distributions. Anyhow, that's getting way off topic for this list. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

4 years, 4 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 '^$|^.*#' :-)

3 years, 9 months

Re: List in list, mutiple reply-to addresses

by Stefan Bauer

Unfurtunately, this completely removes the reply-to: header and sets the list-address as a new and only reply-to. This way, a reply does not address the origin sender anymore :/ Am Mo., 22. Nov. 2021 um 19:17 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/22/21 6:27 AM, Stefan Bauer wrote: > > > > john receives following mail: > > > > from: iu-int@mydomain > > reply-to: mike@mydomain, iu-all@mydomain > > > > If john now hits reply in mailclient, mail goes to ALL instead of just > the > > from-address, as mailman extended the reply-to header. > > > > How can this be changed? > > > Set Settings -> Alter Messages -> First strip reply to to Yes on the > iu-int list. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/ >

3 years, 7 months

Re: Sad news - Brian Carpenter

by Steven Clift

Yes, very sad news. E-Democracy.org was plotting with Brian (due to his passion for pushing the envelope on making Mailman list much more web-friendly) a move to his services. He had great spunk and passion for online communities. Steven Clift <http://stevenclift.com> - Founder and Volunteer, E-Democracy.org clift(a)e-democracy.org - +1 612 234 7072 @Democracy <http://twitter.com/democracy> - Facebook <https://www.facebook.com/stevenlclift> - LinkedIn <http://linkedin.com/in/netclift> On Thu, May 13, 2021 at 12:37 PM Duane Raymond <duane(a)fairsay.com> wrote: > Thanks for letting us know. > > Brian was fantastic help on getting me up and going with mailman3 a few > months ago...and his work on friendlier interfaces for mm3 is excellent. > He will definitely be missed in this community and by me. He was always > helpful off list as well as on list. It was brilliant support to have. > > I hope his legacy at emwd.com and Harmony Lists continues. > > Rest in peace Brian. > _______________________________________________ > 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/ >

4 years, 1 month

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/

3 years, 8 months

Mailman-users search results for query "2021"