Search results for "Postorius" - Mailman-users

Re: mailman import21 passwords

by Sam Darwin

> There is no guarantee that any Mailman Core installation into which a MM 2.1 list is imported actually also supports Django users for Postorius and/or HyperKitty. There is no guarantee that a mailman-core installation also includes Postorius and/or HyperKitty. However we can imagine that the vast majority do utilize all those components. If you've installed mailman3, you are probably installing Postorius and HyperKitty. To account for the fact that it's not 100% guaranteed, the import script could require a flag such as --django-accounts. Or it could even be another script entirely. So, the step wouldn't be automatic, but at least it would be an option. > inherently not secure The passwords were good enough for mailman2. If a mailman2 instance has been in production for 20 years and users aren't complaining about security, maybe it's not a show stopper. The point is to make the upgrade seamless. That means... being able to say that everyone gets to keep their user account and password. To be able to easily tell the users "Your account is still the same. Just log in. Change your password when you like." In the current context, passwords are associated with django accounts rather than mailman-core accounts. So this is about creating django users. > creating a django user is "expensive". "poor performance" I didn't follow what that means. What is expensive? What is poor performance? Creating new django accounts en masse would be a one-time operation. It doesn't matter if it's slow, or expensive, since it only happens once. And it would be optional. With the --django-accounts flag. Or another separate script. Then you can tell users "Your account is the same as before. A transparent upgrade. Just log in".

10 months, 1 week

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)

6 years

Re: New releases

by Danil Smirnov

Hi Abhilash, Thank you for the releases! I've updated my installation and I'm confused by this Postorius announcement: > Settings page is also slightly different with all the sections on the > vertical menu on left instead of horizontal tabs. I have Postorius verson 1.3.3 but I still see horizontal tabs not vertical menus. Could you elaborate more on this? Best regards, Danil Smirnov On Tue, 2 Jun 2020 at 22:21, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hi Everyone, > > I am pleased to announce new stable releases for: > > - Postorius: 1.3.3 > Changelog: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#id1 > Download: https://pypi.org/project/postorius/1.3.3/ > - Hyperkitty: 1.3.3 > Changelog: https://hyperkitty.readthedocs.io/en/latest/news.html#id1 > Download: https://pypi.org/project/HyperKitty/1.3.3rc1/ > - Mailmanclient: 3.3.1 > Changelog: > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > Download: https://pypi.org/project/mailmanclient/3.3.1/ > - Django-mailman3: 1.3.3 > Changelog: > https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > Download: https://pypi.org/project/django-mailman3/1.3.3 > > Python 3.6+ and Django 2.0+ is supported for all of them. Django 3.0 > support for Hyperkitty requires manually upgrading a dependency > (django-haystack>=3.0b2, once a stable version of this has been released, > it shouldn't require manually upgrading). > > There are tons of bug-fixes across the board and some new features. > > Biggest visible change is switch to Bootstrap 4, which has been long > pending for us. Bootstrap 4 completely changes the CSS grid model using the > new Flexbox. There might be some small changes or breakages when using on > mobile. Please report such issues to us via Gitlab! > > Some other notable changes are in Postorius, which includes many more list > settings exposed include content filtering settings, bounce processing > (which was added in the previous release of Mailman Core) settings and some > other ones. Settings page is also slightly different with all the sections > on the vertical menu on left instead of horizontal tabs. You can now also > specify a reason when rejecting held messages. > > There was also a gnarly bug, which caused the name of some members to be > the string "None". For the longest time, I couldn't figure out the reason > for it, but it ended up being a simple fix in mailmanclient's json > serialization of display_name, which would result in Python's None value > being passed as string "None" to Mailman's API for subscription. > > There is also better support for filtering visible lists based on the > current vhost, which I see a few people are already waiting for from > mailman-users list. > > A full changelog has been added to each project in the top. > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > 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, 1 month

Re: Separating Lists by Domain

by Mark Sapiro

On 1/3/19 2:34 PM, Abhilash Raj wrote: > > > On Thu, Jan 3, 2019, at 2:27 PM, brian(a)emwd.com wrote: >> So who manages Postorius? Is that a whole separate application from >> Mailman 3? Is there a way we can get whoever the developer is to update >> it where we can separate lists by domain the way Hyperkitty does? Mark >> Sapiro refers to this in the following post: >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > You can file an issue at https://gitlab.com/mailman/postorius/issues Yes, filing a GitLab issue is the best way to get things on the record. It's no guarantee that things will be addressed immediately, but they are there, and merge/pull requests are always welcome. As far as your question goes, Mailman Core, Postorius and HyperKitty are separate entities and they were mostly developed by separate people/groups and some important players have either overtly or implicitly retired from the project. Not long ago I write in another context > MM3 is much more complex than MM2.1 and there's a lot that I don't fully > understand myself. > > There is a basic core engine which does all the work of > creating/managing lists and users and receiving and sending mail. It has > no web UI per se. It exposes a RESTful API on the host server. > > The web management UI is Postorius and it is based on the Django web > framework and communicates with core via the REST API. The Archiver is > HyperKitty and it is fairly independent. It is also based on the Django > web framework. Account creation and web login is via django-allauth. > > Postorius, HyperKitty and the core were all developed separately by > different people and no one understands all of it. That said, Abhilash is currently the lead developer for all of Mailman 3 and he's doing a great job. I and a few others are also involved (I'd be more involved if I didn't have Mailman 2.1 to distract me), but we are a small group and things take time. And as I said, merge/pull requests for GitLab issues are always welcome. -- 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

List creation error

by Odhiambo Washington

I am running this on a test environment - a Debian10 VM. Postorius comes up and I create a domain. All is fine. Then I create a list and see that the list is created, but there is an error below the message: Something went wrong HTTP Error 500: <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> mailmansuite.log has the following entry: INFO 2021-01-06 10:31:48,062 4177 hyperkitty.lib.mailman Imported the new list testlist(a)mm3.washington.home from Mailman ERROR 2021-01-06 10:31:48,511 4177 postorius Un-handled exception: HTTP Error 500: <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py", line 264, in get 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 File "/usr/lib/python3.7/_collections_abc.py", line 666, in __contains__ self[key] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/connection.py", line 112, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 500: <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> ERROR 2021-01-06 10:31:48,529 4177 django.request Internal Server Error: /mm3/mailman3/lists/testlist.mm3.washington.home/ ERROR 2021-01-06 10:31:48,529 4177 django.request Internal Server Error: /mm3/mailman3/lists/testlist.mm3.washington.home/ PS: I could probably have caused the error with some weird operation I did: Initially when postorius comes up, it has the domain - *example.com <http://example.com>*. I am not sure where it gets this. Using MySQL, I dumped the DB and s/ example.com/lists.washington.home/g then re-imported the DB, restarted mailman and apache2. Might that be the issue??? I am relying on https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 as the guide and where it gets the *example.com <http://example.com> *from still remains a mystery for me. I have blown away everything - except the config files and the scripts mentioned in this guide - twice and re-installed and still get the example.com domain as the default. There must be something obvious I am missing. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 years, 6 months

Re: only show mail domains from web host on web-host-url

by Mark Sapiro

On 3/19/21 6:38 AM, Jens Günther wrote: > Thank you for your answer. I should have seen that in the Docs, but > somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html > > I set it in the corresponding file, but unfortunately it doesn't work > :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS > works, changed here from '*' to 'localhost' and my example-domains, this > works). It seems to be the same as this user describes (a while ago): > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… FILTER_VHOST is problematic. It works fairly well for HyperKitty, but not so well for Postorius. In particular with Postorius it doesn't work if there is more than one mail host domain with the current web host. See these issues and MRs for more detail. https://gitlab.com/mailman/hyperkitty/-/issues/254 https://gitlab.com/mailman/hyperkitty/-/merge_requests/243/diffs https://gitlab.com/mailman/hyperkitty/-/merge_requests/244/diffs https://gitlab.com/mailman/postorius/-/issues/394 https://gitlab.com/mailman/postorius/-/merge_requests/500/diffs -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: Can't remove footer(s)

by Mark Sapiro

On 10/11/2018 02:04 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: >> The templates named list_member_digest_footer.txt and >> list_member_regular_footer.txt (with underscores) were created by >> import21 and set as the URIs for those templates. Had you just copied >> /dev/null (or otherwise made empty) those files and done nothing else, >> that would have done what you wanted, but since you deleted the template >> URIs for the list, the template names are now the default > > How do I make these not default? You can set them via ITemplateManager. > Or when I upgrade to V3.2.2 will I be able to just empty the templates in /postorius/lists/LISTNAME/templates? You could except Postorius won't let you set an empty value for a template and deleting a template in Postorius just reverts to using the default - e.g., 'list:member:regular:footer'. What you need to do is copy /dev/null to files in (in your case) /opt/mailman/core/var/templates/lists/[LISTNAME_FQDN]/da/ named list:member:digest:footer.txt and list:member:regular:footer.txt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

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

Re: [Mailman-Developers] Countdown to the 3.1 release

by Simon Hanna

> Please take a look at any other bugs not assigned to milestone 3.1 and let me > know if you think any are serious enough to block the 3.1 release. I'll say > in advance that I'm going to be brutal in assessing them, because 3.1 really > needs to be released soon! I guess https://gitlab.com/mailman/mailman/issues/219 should be fixed in the next release. If 3.1 find its way into repositories, we will get lot's of issue reports for this I suppose. > Note too that there may be blockers for Postorius, Hyperkitty, and > mailman.client, but I haven't looked at those subprojects yet. How close are > they to being release ready? Terri was working on this one, it's not critical but nice to have for usability https://gitlab.com/mailman/postorius/merge_requests/159 I have a mr pending for mailmanclient that should be included in the next release https://gitlab.com/mailman/mailmanclient/merge_requests/10 Postorius has a number of merge requests open. I'm not sure which of them should be merged before the next release Does your template branch in core need any immediate modifications to mailmanclient and/or postorius? cheers, Simon

9 years

Re: setup of URLs

by Abhilash Raj

On Sun, Jan 28, 2018, at 12:24 PM, Peter Münster wrote: > Hi, > > I would like to point "https://my-domain.org/" to the list of > mailing-lists of this domain. How should I setup my Apache configuration > and/or the urlpatterns please? > > With my actual configuration, the above URL is always rewritten to > https://my-domain.org/postorius/lists/ > > These are my urlpatterns: > > urlpatterns = [ > url(r'^$', RedirectView.as_view( > url=reverse_lazy('list_index'), > permanent=True)), ^ This is responsible for re-writing your URL to `/postorius/lists/` as Redirect from `/`. This patch should do what you want: ``` index a5ea108..bff54f3 100644 --- a/example_project/urls.py +++ b/example_project/urls.py @@ -25,11 +25,10 @@ try: except ImportError: from django.urls import reverse_lazy from django.views.generic import RedirectView +from postorius.views.list import list_index urlpatterns = [ - url(r'^$', RedirectView.as_view( - url=reverse_lazy('list_index'), - permanent=True)), + url(r'^$', list_index), url(r'^postorius/', include('postorius.urls')), ``` Just as an FYI, my browser would always re-direct me to /posotrius/lists, even after I applied this patch, not sure if it was some sort of caching or something else. I tried it from an incognito-mode and it seemed to work. -- Abhilash Raj maxking(a)asynchronous.in

7 years, 5 months

Mailman-users search results for query "Postorius"