Search results for "Postorius" - Mailman-users

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)

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

1 year, 10 months

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)

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

5 years, 5 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.

2 years, 9 months

Re: New messages are not archived - may be a path issue

by Mark Sapiro

On 10/20/23 05:31, Wikinaut wrote: > > The built-in template (mailman-hyperkitty.cfg) perhaps needs to be fixed as well (hyperkitty wrong, archive correct)? > # However, if your Mailman installation is accessed via HTTPS, the URL needs > # to match your SSL certificate (e.g. https://lists.example.com/hyperkitty). > # base_url: http://localhost/mailman3/hyperkitty/ > > this line perhaps needs to be changed to > # base_url: http://localhost/mailman3/archives/ I agree that this is confusing because some of our docs recommend that urls.py contain ``` path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), ``` and docs recommend ``` path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), ``` I.e. following the first suggestion, you would access Postorius and HyperKitty via `https://www.example.com/postorius/` and `https://www.example.com/hyperkitty/` respectively, but with the second, the urls would be `https://www.example.com/mailman3/` and `https://www.example.com/archives/` respectively. I'm going to address this by adding ``` path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), ``` to mailman_web's urls.py so the either urls will work. See https://gitlab.com/mailman/mailman-web/-/issues/24 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

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

by Stephen J. Turnbull

朱超 writes: > 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". > 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. > 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. > 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. Steve

1 year, 10 months

Re: Hyperkitty Missing Theme/Style Sheets?

by Abhilash Raj

Hi Andrew, On Wed, Nov 1, 2017, at 12:43 PM, Andrew Hodder wrote: > Well, that can't be true, I'm running DEBUG = False and Django is > certainly > trying to provide static files (as you'll see below): > > I found the issue in the nginx logs (it's connecting to both postorius > and > hyperkitty via uwsgi), it appears when I'm only viewing Hyperkitty's > pages, > I'm getting these type of errors (some changes inserted to hide my server > details): > > 2017/11/01 19:22:04 [error] 64082#0: *75 open() "/opt/mailman/postorius/ > example_project/static/CACHE/js/4ce1260ef558.js" failed (2: No such file > or > directory), client: 10.10.44.29, server: blah.blah.blah, request: "GET > /static/CACHE/js/4ce1260ef558.js HTTP/1.1", host: "blah.blah.blah", > referrer: "https://blah.blah.blah/hyperkitty/hyperkitty/list/ > mailinglist(a)domain.com/2017/10/" I see here that you are running Postorius and Hyperkitty a bit differently that presented in our docs. Settings inside example_project for each repositories are just examples, we use it for testing, and may not work best in production. We recommend that you instead use the mailman-suite[1] to run Postorius & Hyperkitty using a single Django installation. The process for doing so is documented here[2]. [1]: https://gitlab.com/mailman/mailman-suite [2]: http://docs.mailman3.org/en/latest/prodsetup.html#installing-web-ui > So it appears Hyperkitty is attempting to load static files from > postorius's side instead of it's own (I have postorius running under > https://domain.tld and hyperkitty running under > https://domain.tld/hyperkitty/ via nginx). I checked and confirmed the > variables in settings.py: > > STATIC_ROOT = os.path.join(BASE_DIR, 'static') > STATIC_URL = '/hyperkitty/static/' > STATICFILES_DIRS = ('/opt/mailman/hyperkitty/example_project/static/') > > And for good measure, here's the nginx config: > > ------------------------------ > > > > server { > listen 80; > server_name DOMAIN.TLD; > #Redirect to SSL > if ($scheme = http) { > return 301 https://$server_name$request_uri; > } > } > > server { > listen 443 ssl http2 default_server; > listen [::]:443 ssl http2 default_server; > server_name DOMAIN.TLD; > > ssl_certificate "/etc/pki/nginx/DOMAIN.TLD.crt"; > ssl_certificate_key "/etc/pki/nginx/private/DOMAIN.TLD.key"; > ssl_session_cache shared:SSL:1m; > ssl_session_timeout 10m; > ssl_ciphers HIGH:!aNULL:!MD5; > ssl_prefer_server_ciphers on; > > location / { > include uwsgi_params; > uwsgi_pass unix:/opt/mailman/postorius.sock; > } > > location ~ /hyperkitty(?<path_info>/.*|$) { > include uwsgi_params; > uwsgi_pass unix:/opt/mailman/hyperkitty.sock; > uwsgi_param PATH_INFO $path_info; > uwsgi_param SCRIPT_NAME /hyperkitty; > } > > #Make nginx aware of postorius static > location /static/ { > alias /opt/mailman/postorius/example_project/static/; > } > > #for hyperkitty static > location /hyperkitty/static/ { > alias /opt/mailman/hyperkitty/example_project/static/; > } I believe static files are all supposed be rooted at `/static` instead of `/hyperkitty/static`. > > error_page 404 /404.html; > location = /40x.html { > } > > error_page 500 502 503 504 /50x.html; > location = /50x.html { > } > } > > Any thoughts would be appreciated, I'm getting stumped on this one. I have never tried to run 'example_project' in production before, so I am not exactly sure about the reason. This seems overly complicated and I strongly recommend that you run Postorius and Hyperkitty from a single installation, unless you have a very good use case to run them separately. > > > Sincerely, > > Andrew Hodder > Systems Administrator > Support Operations, Afilias > E-mail: drew(a)afilias.info > Phone: +1 416.673.4164 > Fax: +1 416.646.1541 > > On Fri, Oct 27, 2017 at 11:01 AM, Simon Hanna <simon(a)hannaweb.eu> wrote: > > > > > On 10/27/2017 04:58 PM, Andrew Hodder wrote: > > > >> Sure thing: > >> > >> https://imgur.com/a/EXv3B > >> > >> Looks like your stylesheets aren't loaded. > > > > if you are running in production (with DEBUG=False) django won't serve > > static files > > You need to configure your webserver to do that. > > You need to make sure to load all the static files using > > `python manage.py collectstatic` > > to gather everything and put them in one directory that can then be served > > by your webserver > > > > > > > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

7 years

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

5 years, 2 months

Rolling releases for Container Images and Funding Campaign for Mailman

by Simon Hanna

>>> These images are built using git-heads *only* if they are passing our >>> test suite and are re-generated weekly. You should be aware that while >>> all these components are tested with their individual test suites, their >>> combination might sometimes not be stable. This will get you >>> updates/bug-fixes much faster :) >> This contradicts what you said in my merge request for Postorius >> https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 >> >> You either use released versions, or make sure that the master branches >> are always compatible. You can't have both with the current development >> model. > Not exactly, I still believe all our git-heads should be compatible with > released (i.e. stable) versions of dependencies, regardless of the fact > that we maintain those dependencies. > > Also, there is at least one test per-project which tests with git-heads > of dependencies we maintain, so that we know if we make any incompatible > changes. > > I am not sure what in the current development model prevents us > to do both? > > The story for container images is different than testing with git-heads. > We need better integration testing for the entire suite to be stable in > conjunction, rather than independently. In fact, containers might be the > perfect way to actually do the integration testing. Scenario: Core changes something about rest that is backwards incompatible. The change is commited to master. Since your containers use the master branches, all future builds will fail until mailmanclient and postorius/hyperkitty. If you want to always have Postorius (and others) compatible with the latest release of master, development for Postorius will be a Pain, because you can't use the master branch of mailman for testing and quick changes. Also your containers and all integration tests that can be done with them will always fail. Until you fix Postorius and the other clients... So why not just have the master branches always compatible and make life easier for developers. I don't see a good reason why you want to do it the other way round... Any bug in core that affects Postorius will also just remain there until you release a new version of core. If you really really want to have it your way, there have to be more frequent releases. >>> - Improve the container images to work with new micro-services >>> architecture, >>> to achieve scaling and redundancy in services. >> The current bottleneck is the rest api from core. IMO bulk actions, >> filtering and sorting should be added there before trying to have >> multiple postorius/hyperkitty instances serving the same core... > I didn't say they will be served from the same core ;-) > > Yes, the Core's API can be further improved to be more efficient. But > that > doesn't prevent us from scaling. I understand there are issues around > multiple > instances of containers, but I have ideas to get around most of them. I just don't want that people that have issues with big installations get the answer: We know of that issue, please deploy Mailman on X containers/machines as a workaround

7 years

Mailman-users search results for query "Postorius"