Search results for "Postorius" - Mailman-users

Re: templates

by Odhiambo Washington

If you don't have any templates in the file system and none in the DB table, then you must go to Jerusalem and pray, because you don't have any and nothing will work the way you want. It's either or! On Thu, May 4, 2023, 21:14 Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists have > templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that > Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in Mailman's > var/templates (as I stated, I do not even lave a 'lists' subdirectory under > Mailman's var/templates). My subscribers are not receiving message > distributions from my lists, even while some of them are listed in the > archives. > > > > > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Thursday, May 4, 2023 10:58 AM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: templates > > On 5/4/23 10:33, Christian via Mailman-users wrote: > > I'm having issues with my lists. For each list I have created a > > template [ list:user:action:subscribe ]which has a prospective > > subscriber have to consent to list rules before they are subscribed. > > This template I created is listed in Postorius for each list. I have > > noticed that there are no other templates listed in Postorius. > Furthermore, there is no 'lists' > > subdirectory under Mailman's var/templates/. > > > When you set a template in Postorius it saves it in the > postorius_emailtemplate table in the database and tells Mailman core to get > the template from Postorius via a URI to a Postorius API. > > -- > 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/ > Archived at: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ > QIHCMEBWANR67HV3NKBK5MCQNSNZRF2A/ > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > This message sent to csa(a)web-analysts.net > > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 11 months

Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/19/19 6:33 PM, kevin(a)coastalaska.org wrote: > We have a couple of people trying to subscribe to our list but receive an error similar to: > {"title": "409 Conflict", "description": "Subscription request already pending"} > > If I try to Mass Subscribe them in Postorius I get this error: > HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}' > > In Postorius I don't see them hung up in Subscription requests. Postorius since 1.2.3 does not show subscription requests waiting user confirmation, only those waiting moderator approval. Thus, if the list's subscription policy is confirm or confirm then moderate, the subscribing user will be sent an email requesting confirmation. If the user hasn't answered that email, the request is pending user confirmation, and since 1.2.3, you won't see it in Postorius. [Update: this is fixed in 1.2.4] > What to do? 1) have the user find the confirmation request email and confirm, or 2) wait for the request to expire (default 3 days) 3) using mailman shell or the REST api or direct interaction with the database, find the token and confirm it. A shell example is ``` mailman shell -l your.list.id Welcome to the GNU Mailman shell The variable 'm' is the your.list.id mailing list >>> util = getUtility(IPendings) >>> list(util.find(mlist=m,pend_type='subscription')) ``` This returns a list of items like ('hex_token'), {'token_owner': 'subscriber', 'email': 'user(a)example.com', 'display_name': 'Jane User', 'when': '2019-04-09T01:26:08', 'type': 'subscription', 'list_id': 'your.list.id'}) You then do ``` >>> util.confirm('hex_token') ``` Note that https://gitlab.com/mailman/postorius/issues/314 which was responsible for removing the subs waiting user confirmation from the Postorius listing suggested "there could be a different place to see the ones pending user approval, so that a moderator can look and/or delete those.", but that hasn't been done. [Update: this is fixed in 1.2.4] -- Mark Sapiro mark(a)msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Re: postorius ssl-certificates for virtual hosts

by Wolfgang Bock

Am 15.11.2019 um 02:21 schrieb Mark Sapiro: > Your Apache config needs to define separate a VirtualHost for each > domain, either by IP address or ServerName, and each VirtualHost points > to its own SSL certificates. Thanks for your info, that did it. I had to include the text of the apache.conf in all my apache-config-files for my virtual-domains. >> If I set use_https to yes in mailman.cfg I get on the website for all lists: >> >> postorius: Something went wrong >> Mailman REST API not available. Please start Mailman core. >> >> >> Does your setting in settings(_local).py for MAILMAN_REST_API_URL have >> an https scheme? That doesn't solve the problem. I changed that in mailman-web.py (MAILMAN_REST_API_URL = https://localhost:8001) and after that in mailman.cfg (use_https: yes). But got the same errormessage on postorius website. Regards Wolfgang

6 years, 5 months

Re: django request error

by Mark Sapiro

On 10/13/21 3:38 AM, eggert--- via Mailman-users wrote: > What's strange, my mailman-web is referred to by > https://lists.tdl/mailman3/ > this show the message as above: > This page either doesn't exist, or it moved somewhere else. > The links in that page refer to urls like: > https://lists.tld/mailman/postorius/lists/ > This URL does not exist, of course. Where is the mailman3 replaced by mailman? All my config files refer to mailman3. How have you installed Mailman? We usually use links like https://example.com/mailman3 and https://example.com/archives in docs for Postorius and HyperKitty respectively. These are the ones in urlpatterns in mailman-web/urls.py We have also used https://example.com/postorius and https://example.com/hyperkitty as alternatives. To enable these, you need to add ``` url(r'^postorius/', include('postorius.urls')), url(r'^hyperkitty/', include('hyperkitty.urls')), ``` to the definition of urlpatterns in urls.py so it becomes something like ``` urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), url(r'^postorius/', include('postorius.urls')), url(r'^hyperkitty/', include('hyperkitty.urls')), ] However, that doesn't explain why your `mailman3` URLs get munged to `mailman`. That is apparently a uWSGI thing, and since I've never used uWSGI, only gunicorn and mod_wsgi, I can't help with that other than to suggest that you might have neglected to restart uWSGI after removing the trailing slash. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

Re: hello， Discussion on how to subscribe to themailing list

by 朱超

At 2023-01-18 13:41:56, "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: > > Yes, I know why 404 is reported，The url should be postorius not be > > mailman3, > >In the stock configuration both "mailman3" and "postorius" invoke the >same view, and I'm fairly sure several templates invoke "mailman3" >rather than "postorius". I believe the logic was that casual users >will recognize "mailman3" more readily than "postorius", and similarly >for "archive(s)" vs. "hyperkitty". ok,I got it, I use the mailman-web not is https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py, that is https://github.com/maxking/docker-mailman/blob/main/web/mailman-web/urls.py > > > https://www.example.com/postorius/lists/$list_id/confirm/?token=$token, > > and it report success. I am curious why there is no similar > > processing logic for unsubscribing in postorius。 > >I don't understand what you're suggesting. A subscribed user >necessarily has a confirmed address, and if a web administration app >is running, they can log in and with a couple of clicks unsubscribe. >Unsubscribe by mail does involve a confirmation step. As explained >before, the reply confirmation is surely available to core; if you >want I believe you can craft email templates to use the web >confirmation either as an option or the preferred method. I am thinking that we can unsubscribe in postorius without logging in. Refer to the subscription process of postorius, fill in the email address that needs to be unsubscribed on mailman-web, and send an email template to the filled email address, but the electronic template carries confirmation The url of the link, click the url to confirm and unsubscribe successfully. > > Can we optimize for this？ > >What do you mean by "optimize"? > >If you mean fewer steps for the user, I believe the FAQ explains how to >create a one-click unsubscription URL (at least that was possible with >Mailman 2). There is a mild denial of service possibility, of course, >but it doesn't involve third parties and is usually recoverable since >the unsubscribe generates an email to the "victim" who can check >archives in the majority of cases and easily resubscribe. Could you give more information about one click unsubscribe url in mailman3? > > If you use mailman-web (include postorius and django-mailman3 and > > django-allauth and so on) to set the template information, the > > template obtained by mailman-core is obtained by requesting > > mailman-web, > >No, the templates used by core and by Postorius are stored in >different databases. It's true that you can use Postorius to set >core's templates, but they're still stored in core's database, not in >Django. They *must* be, because core needs to be able to send email >even if there is no web interface at all. I suppose you could arrange >that one could be set by the other. If you want to define a protocol >so that any application that speaks the REST API can do this, I >suppose it could be added to Mailman. But we can't depend on web >administration being installed at all, and we can't depend on it being >Postorius. Yes, when mailman-web is connected to mailman-core, the core stores uri information, that is the link, not the detailed information of the template. Of course, you can read the local template file and use it by configuring related parameters. From Tom

3 years, 3 months

Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Abhilash Raj

On Sat, Mar 28, 2020, at 1:59 PM, Ralph Seichter wrote: > I have struggled for hours but cannot seem to figure it out. After > registering new user accounts in Postorius, the "confirm your address" > emails don't get sent via SMTP (my MTA does not even log connection > attempts), but their content is displayed in uwsgi-error.log. > > I think I disabled developer mode in Core and Postorius: > > $ mailman conf | grep devmode > [devmode] enabled: no > [devmode] recipient: > [devmode] testing: no > [devmode] wait: 60s > > $ grep ^DEBUG settings.py > DEBUG = False > > Users can subscribe via list-join(a)domain.tld, including confirmations. > Account registration using the WebUI works as well, it's just the emails > that don't get sent. What am I missing, I wonder? Have you setup email settings for Postorius separately? https://docs.mailman3.org/en/latest/config-web.html#setting-up-email-requir… Core and Django unfortunately need to be configured separately to send out emails. Abhilash > > -Ralph > _______________________________________________ > 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: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Abhilash Raj

On Sat, Jun 8, 2019, at 2:12 AM, andrew.bernard(a)gmail.com wrote: > I'm new to Mailman. I have a Ubuntu 19 production server. I attempted > to get Mailman 3 and the web components going with the system packages, > but I encountered a few showstopper errors (such as indexing not > working at all) which I know have been fixed in the codebase. To that > end I erased my installation, and installed mailman from the gitlab > source. That all works much more nicely now and I feel I have a lot > more control of the layout of all the files (the various Ubuntu > packages smear the parts all over the place, confusingly). > > Now I want to get Postorius and Hyperkitty going again, independently > of Ubuntu packages. I would like to run Postorius and Hyperkitty under > one Django project. So I downloaded the git source for mailman_web. I > do not know if this is the right way to install. Mailman Web works okay, there are very few things actually in there. If you want to install things from source, consider using the mailman_suite project as a starting point. https://gitlab.com/mailman/mailman-suite Mark wrote down his experience installing Mailman 3 on two machines, which is currently running this very list. https://wiki.list.org/DOC/Mailman%203%20installation%20experience > I am partially familiar with Django, but to come to the point, I have > no idea once having obtained the source from git how to setup and > install the project, where it lives in the filesystem, and so on. Are > there any pointers to help in this area? The very nice readthedocs > format files for Postorius and Hyperkitty are very silent on basic > matters like this, which is not of much help! The git README files also > define a new level of brevity. > > I need some initial hand holding here. If any help is forthcoming, such > as links to more full documentation for newbies to Mailman, I would be > most grateful. I'll try to write the steps in short, let me know if you need me to expand on any of these. 1. Choose a directory to get all the sources. I usually prefer /opt. So, create /opt/mailman 2. Create a Python 3 virtual environment. $ cd /opt/mailman $ python3 -m venv vevn $ source venv/bin/activate 3. Get all the sources and install in this virtualenv, you neeed: 1. Mailman Core (mailman/mailman) 2. Mailman Client (mailman/mailmanclient 3. Mailman-Hyperkitty (mailman/mailman-hyperkitty 4. Django-Mailman3 (mailman/django-mailman3 5. Postorius (mailman/postorius) 6. Hyperkitty (mailman/hyperkitty) You can also just `pip` install those packages, instead of using git sources. I would actually recommend using the release versions if you are not ready to deal with the instability of the git heads. 4. Finally, you need to create config files in right places: - Mailman Core's config lives at `/etc/mailman.cfg - Django config lives in the django project, mailman-suite. I am not going to dive into actual runtime configuration here. > _______________________________________________ > 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, 10 months

Re: Confirmation for subscriptions

by Mark Sapiro

On 6/23/19 7:24 AM, andrew.bernard(a)gmail.com wrote: > Suddenly stopped working. For all the lists I have created, suddenly the confirm setting is ignored for subscriptions and users are subscribed right away. I assume you are looking at the Postorius List Settings -> Subscription Policy. That should reflect the setting in core. How are these users requesting subscription/being subscribed? > This only happened after I added another domain - surely that can't be the cause? Unlikely, but not impossible. > Where to look to troubleshoot this? You could use `mailman shell` to examine the setting in Mailman core, but it's unlikely that would be different from what Postorius shows. Other than that, you can look in logs, but there is not very much logged for the subscription workflow. To be more help, I'd like to know exactly when this happens. First, for Postorius Mass subscribe, this is expected. Other than that, does it happen on email to the list-join address? Does it happen with subscription via the form on the Postorius list Info page? Is it possible the user has a 'vacation' program that is responding to the confirmation request? See <https://gitlab.com/mailman/mailman/issues/23> (we should fix that) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

Re: Customise Postorius templates?

by Duane Raymond

On Mon, 7 Feb 2022 at 19:30, Abhilash Raj <maxking(a)asynchronous.in> wrote: > I hadn’t tried it when I sent email, but when I tried it locally on > Postorius, > it seems to work for me. > Good to know it seems to work for you. Means it is possible and I was missing something obvious ;-) In the end, using the full path and spelling postorius correctly were the two crucial steps. Now off to customise. Is anyone out there working on an overhaul of the web interface templates (e.g. more mobile friendly, classes or selectors on all key html tags, css updates, re-ordering individual HTML file structure, etc)? I'm not currently anticipating adding/changing any of the includes. I'm wanting to make the web interfaces look like 2022 and would love to then share that with the community (may take 6 ish months) - something that could make the project more attractive (literally) to people. Cheers, Duane.

4 years, 2 months

Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Mark Sapiro

On 9/20/19 5:39 AM, Henrik Rasmussen wrote: > I know this is quite long (sorry), but I hope this part of the mailman.log may provide some clue to what went wrong. It doesn't. > As mentioned, Mailman stopped receiving mails some days ago and I have been restarting Mailman (without solving anything) at Sep 18 13:30:03 2019. On Sep 20 07:05:23 2019 everything started working again by itself. > > / Henrik Rasmussen > I'm snipping a bunch of irrelevant stuff having to do with web interactions, etc. > Sep 20 06:42:22 2019 (35) HOLD: listname(a)lists.example.com post from someone(a)foo.bar held, message-id=<4E8DB72B-66D9-456E-B51C-2A49423CF29F(a)foo.bar>: The message comes from a moderated member > Sep 20 06:42:23 2019 (35) ACCEPT: <CALcvC6H5ko14LT8F_z_nbddp0DmDgfb-Rt32s+0TbpPrY3BL_g(a)mail.foo.bar> There are lots of these indicating messages have been received via LMTP and passed to Core. > Sep 20 06:42:48 2019 (35) ACCEPT: <CAG3z+4+67M9jAjbVtSqUdUCU6cS1dOYBsmMTAdePL3+O+Nn+sQ(a)mail.foo.bar> > Sep 20 06:42:56 2019 (32) Exception in the HyperKitty archiver: 'url' > Sep 20 06:42:56 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 217, in _send_message > archived_url = result["url"] > KeyError: 'url' > Sep 20 06:42:57 2019 (32) Exception in the HyperKitty archiver: 'url' > Sep 20 06:42:57 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 217, in _send_message > archived_url = result["url"] > KeyError: 'url' > Sep 20 06:42:57 2019 (32) HyperKitty failure on http://mailman-web:8000/hyperkitty/api/mailman/archive: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > (500) > Sep 20 06:42:57 2019 (32) Exception in the HyperKitty archiver: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > Sep 20 06:42:57 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > > Sep 20 06:42:57 2019 (32) HyperKitty failure on http://mailman-web:8000/hyperkitty/api/mailman/archive: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > (500) > Sep 20 06:42:57 2019 (32) Exception in the HyperKitty archiver: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > Sep 20 06:42:57 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > > Sep 20 06:42:57 2019 (32) Exception in the HyperKitty archiver: 'url' > Sep 20 06:42:57 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 217, in _send_message > archived_url = result["url"] > KeyError: 'url' > Sep 20 06:42:57 2019 (32) Exception in the HyperKitty archiver: 'url' > Sep 20 06:42:57 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 217, in _send_message > archived_url = result["url"] > KeyError: 'url' There are lots of the above errors/tracebacks. They are a problem, but not specifically the one affecting Postfix delivery. There are two different tracebacks. The ValueError is because the mailman_hyperkitty shim has called Hyperkitty via http://mailman-web:8000/hyperkitty/api/mailman/archive to archive the message and HyperKitty returned a 500 status with the HTML <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css">    </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Then the KeyError occurs because the response did not include the URL of the archived message. When this occurs, mailman_hyperkitty retries the message until it succeeds. For more information on the HyperKitty issue, look in the Django log whose path is defined in LOGGING['handlers']['file']['filename'] in the Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

Mailman-users search results for query "Postorius"