Search results for "Postorius" - Mailman-users

Re: [Django] ERROR (EXTERNAL IP): Internal Server Error:

by Wolfgang Bock

Hello Mark, thanks for your reply. I'll check it out and report. Reagrds Wolfgang Am 18.11.2019 um 18:57 schrieb Mark Sapiro: > On 11/18/19 9:26 AM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> I got an errormessage via mail to root@[domain-01]. >> >> The complete text is attached in a utf-8-text-file. >> >> In the lines ...6, 8, 12, 119, 138, 141, 149, 150, 151, 155, 161, 162, >> 165, 166, 169, 187, 247, 251, 321 ....you can find links to different >> domains anonymised as [domain-01], [domain-02], [domain-03], [domain-04]. > > You attempted to delete testliste02.[domain-01] via Postorius and > Mailman's REST API returned a 500 status. You may find more information > in mailman.log. > > I'm only guessing, but possibly this is because you posted to the URL > <https://[domain-02]/mailman3/postorius/lists/testliste02.[domain-01]/delete>. > I.e., you were accessing Postorius at > https://[domain-02]/mailman3/postorius/ (domain-02) and deleting a > domain-01 list. >

5 years

Re: Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Jonas Meurer

Jonas Meurer: > Abhilash Raj: >> On Mon, Jan 28, 2019, at 2:39 PM, Jonas Meurer wrote: >>> Abhilash Raj: >>>> On Sat, Jan 26, 2019, at 5:10 AM, Jonas Meurer wrote: >>>>> Hey Abhilash, >>>>> >>>>> Thanks a lot for your work on mailman3! >>>>> >>>>> Abhilash Raj: >>>>>> I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. >>>>>> >>>>>> The full set of changelog can be found in the documentation[1][2]. The most notable feature that >>>>>> I can think of is non-member management in Postorius. >>>>>> >>>>>> New releases are available on PyPI[3][4]. >>>>> >>>>> For earlier releases, you provided GnuPG signature files to >>>>> cryptographically verify that the release files were not tampered with. >>>>> >>>>> I couldn't find such signature files for the two latest releases. Would >>>>> you mind adding them? When packaging for Debian, I prefer to check the >>>>> GnuPG signatures before uploading new releases. Also, the signature >>>>> files get uploaded to the Debian archive as well so they can be checked >>>>> by everybody. That way we can cryptographically proof that the Debian >>>>> package is based on the original tarball that got packaged and signed by >>>>> upstream. >>>> >>>> >>>> Ah, sorry about that. I completely forgot about that. >>>> >>>> I am not sure if I can upload signatures after uploading the tarballs, I'll try to find out if that is possible. >>> >>> Thanks a lot, that would be awesome. I'll wait for it before doing the >>> Debian package uploads. >> >> If it is not possible to upload signatures, I'll bump up patch versions >> and push out new tarballs with signatures. > > Perfect, thanks a lot! For the record: Abhilash released mailmanclient 3.2.2 and postorius 1.2.4 with tarball signatures in the meantime. Thanks a lot for doing this, Abhilash! Both are uploaded to Debian already. Cheers jonas

5 years, 9 months

Re: mm3 installation question

by Mark Sapiro

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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

Re: mailman.cfg (use_https: yes) fails

by Wolfgang Bock

Hi again, in this case I'll check out either and report. Regards Wolfgang Am 18.11.2019 um 05:06 schrieb Mark Sapiro: > On 11/16/19 4:54 AM, Wolfgang Bock via Mailman-users wrote: > I will look at the https issue further when I get time. > > >> In this context I faced a strange behavior: >> >> In the database mailman3web in table django_site are listed several >> domains, either in the django-domain-management site >> https://[mydomain]/mailman3/admin/sites/site/ >> >> id domain name >> 1 example.com Example.com >> 2 [mydomain-1] [mydomain_name_1] >> 3 [mydomain-2] [mydomain_name_2] >> 4 [mydomain-3] [mydomain_name_3] >> >> In case I delete line 1 with the id 1, in the database or in the >> django-web-site, postorius fails to work. After re-inserting this line, >> postorius works again. > > In your settings.py, you probably have SITE_ID = 1. Thus, when you > delete the site with id = 1, Postorius fails. You need to set SITE_ID to > an existing site in settings_local.py. >

5 years

Re: Rejection Reason for refusing a subscription request

by Mark Sapiro

On 3/27/21 2:08 PM, Brian Carpenter wrote: > I was testing out the process of rejecting an incoming subscription > request. Choosing the reject option for a moderated subscription request > does send out a rejection notice but it gives no reason for the > rejection. ... > Is there a place somewhere in Postorius to provide a rejection reasons > for moderated subscription requests? Does Mailman 3 core provide this > via its REST api but it is just not revealed in Postorius yet? It's in Postorius since 1.3.3. If in the held message view, you click the subject of a held message, you get a popup dialog the shows the message with options to also show headers or the raw message. There is also a dropdown t=o set the poster's moderation action and a box for a reject reason if you click the reject button in the dialog. Do you not see this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

Re: Time Zone Problem In Postorius

by Abhilash Raj

On Thu, May 28, 2020, at 2:02 PM, Brian Carpenter wrote: > I have the server TZ set to EST. I have the TZ for Postfix set to EST. > I have the following set in my settings_local.py file: > > TIME_ZONE = 'America/New_York' > USE_TZ = True > > However messages showing up in the pending moderation queue box shows > UTC date. I am seeing this behavior in Affinity as well so I figured it > is either a Mailman core setting or perhaps database? Can anyone shed > light on that? I think that's because we display as-is values in the UI. Core really doesn't need to be aware of the TZ related info IMO, it is the responsibility of UI (Django!) to record the user's/UIs preferred timezone info and use that with the datetime objects. The offending line[1] for held messages is this, which simply formats the datetime to a specific "format" but we need to also format it to localtime using perhaps [2]. There would be similar values for other places where date time objects are presented in the UI. The change is simple enough, if you can open a ticket, it should be simple enough to fix I think. [1]: https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/templates/… [2]: https://docs.djangoproject.com/en/3.0/topics/i18n/timezones/#std:templatefi… > 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/ > -- thanks, Abhilash Raj (maxking)

4 years, 5 months

Re: modify subscription page by mailinglist?

by Lars Schimmer

On 10/01/2022 14:14, Stephen J. Turnbull wrote: > Lars Schimmer writes: > > > Is it (easy) possible to modify the subscription page individual per > > mailinglist? > > > > If so, since which version? And how? Is there a guide? > > Not sure which page you have in mind, or how substantial the > modifications you propose are. There are several subscription-related > Django templates under postorius/src/postorius/templates/postorius, > which could be customized to using various Mailman variables known to > Postorius/Django. Not sure where they end up in your installation. Ok, for debian thats /usr/lib/python3/dist-packages/postorius/templates/postorius And I think I could fiddle out how it works. But in general, e.g. a custom page per mailinglist for the "list information page" is a bit more work than expected and I will not follow this idea. (e.g. adding a logo per list, ...) Thank you so far. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

2 years, 10 months

Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

Mark, Thank you for your thoughts so far. On 6/23/20 3:22 PM, Mark Sapiro wrote: > I have done further testing. See my comment at > <https://gitlab.com/mailman/mailman/-/issues/735#note_366074014>. > > You need to set hostname: in mailman.cfg to the actual external IP > address of the Mailman host machine or to a name which resolves to that > IP both internally and externally, and also set that host name/IP in the > MAILMAN_REST_API_URL setting on the Postorius machine. I've done that, but there is no observed change in the browser (still get same 404 error). Specifically, I reset hostname to be a newly-added CNAME of the actual host address, and ensured that the 0.0.0.0 addresses were no longer there. > >> However I then get another issue. From the mailman.log file I now see in >> the last few lines. For clarity I've numbered them like this "{1}": >> >> {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" >> "GNU Mailman REST client v3.3.1" >> {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk >> HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" >> {3} [22/Jun/2020:00:58:24 +0000] "GET >> /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 >> HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" >> >> At this point the browser screen reports "Something went wrong" and the >> message "HTTP Error 404: {"title": "404 Not Found"}" > Make the above changes and see if that solves this. If not, let us know > and we'll try to help. A tcpdump now shows the GET of /3.1/domains/mailman-web.ivimey.org/lists&advertised=true&count=0&page=1 directed at mailman-core and the reply being 404 not found. The extract from core's mailman.log is now: [24/Jun/2020:20:41:11 +0000] "GET /3.1/domains/mailman-web.ivimey.org/lists?advertised=true&count=0&page=1 HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" And the entry for postorius in mailmansuite.log: ERROR 2020-06-24 21:41:11,191 13310 postorius Un-handled exception: HTTP Error 404: {"title": "404 Not Found"} Traceback (most recent call last): File "/opt/mailman3/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) [snip] File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 116, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 404: {"title": "404 Not Found"} Note that the mailman-web.ivimey.org address is the newly-added CNAME of greyarea-web1, mailman-core is likewise the CNAME of greyarea-post. There is nothing I can see in the other logs that looks out of the ordinary. I guess this indicates that my earlier wondering if I had something left over from a past install is dispelled, as that name didn't exist until today.

4 years, 5 months

Re: Error -- postorius Un-handled exception

by admin＠bclug.ca

Mark wrote: > After working my way through your suggestions with no joy I discovered > to my embarrassment that I hadn't created the "mailman-hyperkitty.cfg" > file. Once created all was well. I'm having the exact same error, but I already have a file at "/etc/mailman3/mailman-hyperkitty.cfg". After `systemctl restart mailman3.service mailman3-web.service` I'm still getting: > ERROR 2024-04-10 10:19:19,739 104735 postorius Un-handled exception: HTTP Error HTTP Error 500: {"title": "500 Internal Server Error"} > File "/opt/mailman/venv/lib/python3.10/site-packages/mailmanclient/restbase/connection.py", line 161, in call > raise HTTPError(params.get('url'), response.status_code, > urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} > ERROR 2024-04-10 10:19:19,744 104735 django.request Internal Server Error: /mailman3/lists/new_test.domain.tld/ > ERROR 2024-04-10 10:19:19,744 104735 django.request Internal Server Error: /mailman3/lists/new_test.domain.tld/ > ERROR 2024-04-10 10:19:19,745 104735 django.server "GET /mailman3/lists/new_test.domain.tld/ HTTP/1.0" 500 8667 Anyone have suggestions? (venv) mailman@mail:~$ GNU Mailman 3.3.9 (Tom Sawyer) Python 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] config file: /etc/mailman3/mailman.cfg

7 months, 2 weeks

Re: hidden list is hidden even to the owner

by Mark Sapiro

On 7/1/20 2:05 PM, Abhilash Raj wrote: > > Which version of Postorius are you running? > > Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. That's correct, but it's tricky. If as an owner of an unadvertised list, you go to a URL like https://www.example.com/postorius/lists/ you will see the unadvertised list(s) that you own as well as any that you are a member or moderator of. Likewise you will see the unadvertised list(s) you own at https://www.example.com/postorius/lists/?role=owner and if you are a member as well as owner of an unadvertised list, you will see it at https://www.example.com/postorius/lists/?role=member. But (here's the tricky part) if you go to https://www.example.com/postorius/lists/?all-lists, you will not see any unadvertised lists, not even ones you own. -- 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

Mailman-users search results for query "Postorius"