Search results for "Postorius" - Mailman-users

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 ^[^#] :-)

5 years, 2 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/

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

5 years

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

7 years, 5 months

Re: How to upgrade to 3.10

by Mark Sapiro

On 3/8/26 15:48, Paul Tomblin via Mailman-users wrote: > > No, it doesn't have the base_url field. Well, that' solves one mystery and gives me another. Why didn't pip update it? Could it be because the version number isn't incremented? No, it's not the version number. Did you run the `pip install` command with your venv active? If not, pip installed it somewhere other than in your venv. > What would happen if I just git cloned that repo into a local directory and copied it over? You could do that, but better after cloning the repo you could do (with your venv active) `pip install path/to/cloned/repo` but first you should ensure you actually installed all the GitLab heads for mailman, mailmanclient, postorius and mailman-web in your venv. If with your venv active you do `pip freeze` you should see those things as items similar to mailman @ git+https://gitlab.com/mailman/mailman@... mailmanclient @ git+https://gitlab.com/mailman/mailmanclient@... mailman-web @ git+https://gitlab.com/mailman/mailman-web@... postorius @ git+https://gitlab.com/mailman/postorius@... -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 week, 4 days

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

Re: integrate subscribe form in Website -> CSRF-token

by Mark Sapiro

On 6/21/21 11:58 AM, Jens Günther wrote: > > We wanted to do the same with Mailman3 (Docker, 3.3.3, Postorius 1.3.4): > > <form method="POST" > action="https://$domain/postorius/lists/$short_lisname.$domain/anonymous_subscribe"> > > <input name="email" value="" type="text"><br> > <input name="email-button" value="Anmelden" type="submit"> > </form> > > When I now enter a mailaddress, the quoted error occurs. This is Django protecting against CSRF. You need to GET the for with the (hidden) CSRF token before you can POST it. > Checking another answer directly to me, there seems to be another hint :-) > > > I believe you are attempting to use the MM Core API via http > GET/POST, rather than via Postorius? That you have tried and get the > CSRF error reported? > > > > Typically this is because you need to add a token to the request to > indicate to the MM Core that your request isn't a forgery. Typically > this token is requested from Core and then presented with subsequent > requests. Have you tried this? > > > > Therefor it is needed to send also a token!? Or use another URL, not > postorius in order to subscribe!? How can I submit such a token? To submit the Token, you need to first GET the form which will have the token. Then you can include it in the POST data. This is not a satisfactory solution for your case. As hinted above, you need to use the REST API. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

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

8 years, 1 month

Re: Are the gitlab repositories kept in sync?

by Abhilash Raj

On 9/13/21 1:56 PM, Brett Delmage wrote: > See > https://gitlab.com/search?search=mailman&group_id=&project_id=&snippets=fal… > > > I see that core is update frequently but other packages such as Mailman > web have not been. Mailman-web is less frequently updated, that's right. It is essentially a python package which packages all the web fron-tends together, so doesn't need updating frequently. > mailman-suite is two weeks old. Mailman-suite is a pre-cursor of mailman-web, so it follows the same philosophy. It will retired at some point in favor of mailman-web. > > Mailman Web has not been updated for wo weeks. > > Does that mean I can download that Postorius and it will work with the > latest mailman core updated in the past day? We run the git master branches of all the components on this server, so it should be compatible, yes. Although, if you are planning to run them in production, I'd recommend using released versions from PyPI (or git tags) instead of git master branch. > > I expect that most changes don't break interfaces. Is that correct? That is true as a general statement ;-) We support compatibility between the latest version of each components only. So, an older version of Postorius may not be fully compatible with latest Mailman Core, although, in theory, it shouldn't break. We'll bump versions in the REST API of Mailman Core if some breaking change in made and older versions of Postorius _should_ be able to talk to the old API version to function. This hasn't been tested very well in practice though since we haven't made a huge breaking change in the API so far, so YMMV. -- thanks, Abhilash Raj (maxking)

4 years, 6 months

Re: Verification Failed Error

by Stephen J. Turnbull

Abhilash Raj writes: > You probably have > > verify = sender > > somewhere in your exim.conf, which is causing this. No, that seems unlikely. This is in the default exim.conf. > You can either modify the > > DEFAULT_FROM_EMAIL > > in your settings_local.py so that it is a real address that Exim can verify, He's already modified that, since the default in settings.py is "postorius(a)localhost.local" (which is a bug: this should default to a mailbox, and the domain should be added automatically if only a mailbox is given). It seems likely that what needs to be done is to set up a mailbox for Postorius, which can be done in several ways. When does Postorius receive mail? I guess it *sends* mail for the mailbox owner confirmation dialogs on subscription or password reset, but that confirmation is normally done by a web transaction, right? If <postorius> rarely gets mail, the obvious thing to do would be to alias to site owner or postmaster. (It looks like Django doesn't know how to receive mail, so any facility for postorius to receive mail would have to be configured in the MTA.) If it's not that, then the problem likely has something to do with the containerization, and the MTA getting confused about which host is which. > or, you can remove verify = sender from your Exim configuration. Don't do this. If you set up a separate Exim router for "postorius" (to do something fancy like a autoreply bot or delivery to /dev/null ;-), you can put the no_verify option in the Requires stanza for it. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

7 years, 2 months

Mailman-users search results for query "Postorius"