New messages not being archived
I have 2 active lists that are properly mailing out and working, plus an admin testing list that is as well. The list info pane correctly shows the mail volume and the imported archives from the previous 2.1 installation are present for both active lists. None of the 3 lists are generating new entries in the archive, all 3 are set up with default settings except 1 active and admin are set to private.
I know that hyperkitty is showing some new content as admin was created in postorius and the list is present in hyperkitty and working in mailman. None of the logs show anything of note, mailmanweb.log has no new entries since it caused a serious issue when I changed the domain, uwsgi-error is the same and uwsgi.log has proper access logs.
When trying to add a new thread via the hyperkitty interface I can see the email go through the maillog, I get the email with the entered content and everything else works, it just doesn't add a new thread to the archive.
The installation is set up with the default settings from the virtualenv installation guide. Any assistance would be appreciated.
On 7/8/21 8:35 AM, Sarah H wrote:
When trying to add a new thread via the hyperkitty interface I can see the email go through the maillog, I get the email with the entered content and everything else works, it just doesn't add a new thread to the archive.
What if anything is in Mailman's var/archives/hyperkitty/spool/ directory?
Do you have something like
[archiver.hyperkitty]
class: mailman_hyperkitty.Archiver
enable: yes
configuration: /opt/mailman/mm/mailman-hyperkitty.cfg
in your mailman.cfg? Do you then have
[general]
base_url: ...
api_key: ...
in the mailman-hyperkitty.cfg file and is base_url set to a url tha accesses hyperkitty and is api_key set to the same value as the MAILMAN_ARCHIVER_KEY is your Django settings - quoted in settings but not in mailman-hyperkitty.cfg, i.e.,
api_key: xxx
MAILMAN_ARCHIVER_KEY = 'xxx'
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 7/8/21 1:03 PM, Mark Sapiro wrote:
On 7/8/21 8:35 AM, Sarah H wrote:
When trying to add a new thread via the hyperkitty interface I can see the email go through the maillog, I get the email with the entered content and everything else works, it just doesn't add a new thread to the archive.
What if anything is in Mailman's var/archives/hyperkitty/spool/ directory?
Do you have something like
[archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfgin your mailman.cfg? Do you then have
[general] base_url: ... api_key: ...in the mailman-hyperkitty.cfg file and is base_url set to a url tha accesses hyperkitty and is api_key set to the same value as the MAILMAN_ARCHIVER_KEY is your Django settings - quoted in settings but not in mailman-hyperkitty.cfg, i.e.,
api_key: xxx MAILMAN_ARCHIVER_KEY = 'xxx'
I see that these settings are not covered in the virtualenv installation guide at https://docs.mailman3.org/en/latest/install/virtualenv.html. This is now https://gitlab.com/mailman/mailman-suite-doc/-/issues/32 and we'll fix that.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Originally the MAILMAN_ARCHIVER_KEY field in settings.py was not present, added as listed above and I'm still not seeing messages added to the archives in the admin list where I have been testing. before I started looking into the issue all of the lists were set to use the prototype archiver which was in the default config on the virtualenv install guide, hyperkitty was absent from that guide entirely actually. I added most of what you had mentioned just this morning while troubleshooting.
here are the current configs and the files in spool.
in var/archives/hyperkitty/spool/
-rw-rw---- 1 mailman mailman 5.9K Jul 8 13:55 1625777713.5186543+0b1e6ae782342e699116994a4cc5968e8e01701c.pck -rw-rw---- 1 mailman mailman 5.8K Jul 8 13:55 1625777713.642453+2e79e4d69d3f91f72646af26822566116a98f92e.pck
mailman.cfg:
# /etc/mailman3/mailman.cfg [paths.here] var_dir: /opt/mailman/mm/var
[mailman] layout: here # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: xxxx
[database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://mailman:xxxxxxxx@localhost/mailman
[archiver.prototype] enable: yes
[archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg
[shell] history_file: $var_dir/history.py
[mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1
mailman-hyperkitty.cfg
# This is the mailman extension configuration file to enable HyperKitty as an # archiver. Remember to add the following lines in the mailman.cfg file: # # [archiver.hyperkitty] # class: mailman_hyperkitty.Archiver # enable: yes # configuration: /path/to/here/mailman-hyperkitty.cfg #
[general]
# This is your HyperKitty installation, preferably on the localhost. This # address will be used by Mailman to forward incoming emails to HyperKitty # for archiving. It does not need to be publicly available, in fact it's # better if it is not. # 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: https://lists.siteurl.org/archives/
# Shared API key, must be the identical to the value in HyperKitty's # settings. api_key: thisisnotreallymykey
settings.py
# Mailman Web configuration file. # /etc/mailman3/settings.py
from mailman_web.settings.base import * from mailman_web.settings.mailman import *
#: Default list of admins who receive the emails from error logging. ADMINS = ( ('Mailman Suite Admin', 'root@localhost'), )
# Postgresql database setup. DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailmanweb', 'USER': 'mailman', # TODO: Replace this with the password. 'PASSWORD': 'xxxxxxxx', 'HOST': 'localhost', 'PORT': '5432', } }
# 'collectstatic' command will copy all the static files here.
# Alias this location from your webserver to /static
STATIC_ROOT = '/var/www/docroot'
# Make sure that this directory is created or Django will fail on start. LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log'
#: See https://docs.djangoproject.com/en/dev/ref/settings/#allowed-hosts ALLOWED_HOSTS = [ "*", # Archiving API from Mailman, keep it. # "lists.your-domain.org", # Add here all production domains you have. ]
#: Current Django Site being served. This is used to customize the web host #: being used to serve the current website. For more details about Django #: site, see: https://docs.djangoproject.com/en/dev/ref/contrib/sites/ SITE_ID = 2
# Set this to a new secret value. SECRET_KEY = 'notreallymyotherkey'
MAILMAN_ARCHIVER_KEY = 'thisisnotreallymykey'
#email configuration EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = '' EMAIL_HOST_PASSWORD = ''
On 7/8/21 2:01 PM, Sarah H wrote:
here are the current configs and the files in spool.
in var/archives/hyperkitty/spool/
-rw-rw---- 1 mailman mailman 5.9K Jul 8 13:55 1625777713.5186543+0b1e6ae782342e699116994a4cc5968e8e01701c.pck -rw-rw---- 1 mailman mailman 5.8K Jul 8 13:55 1625777713.642453+2e79e4d69d3f91f72646af26822566116a98f92e.pck
There should be errors in Mailman's mailman.log for these. You can see
the actual message in the .pck by pointing mailman qfile at it.
mailman.cfg:
...
[archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg
OK
mailman-hyperkitty.cfg
# This is the mailman extension configuration file to enable HyperKitty as an # archiver. Remember to add the following lines in the mailman.cfg file: # # [archiver.hyperkitty] # class: mailman_hyperkitty.Archiver # enable: yes # configuration: /path/to/here/mailman-hyperkitty.cfg #
[general]
# This is your HyperKitty installation, preferably on the localhost. This # address will be used by Mailman to forward incoming emails to HyperKitty # for archiving. It does not need to be publicly available, in fact it's # better if it is not. # 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: https://lists.siteurl.org/archives/
I assume that you have the real URL to hyperkitty here. I'm not sure, but https might be an issue.
# Shared API key, must be the identical to the value in HyperKitty's # settings. api_key: thisisnotreallymykey
settings.py
...
MAILMAN_ARCHIVER_KEY = 'thisisnotreallymykey'
OK
It looks OK. You should now see log messages regarding the messages in var/archives/hyperkitty/spool/. They should help.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I took a look at the pickle files, this last one didn't have the archive locations but another had
Archived-At: <> List-Archive: <>
as well, so it looks like it's not being passed properly to the archive location?
(venv) [mailman@sysname spool]$ mailman qfile 1626122072.7275724+5f84b41c279cea5ae5476554fefbfc514222f582.pck [----- start pickle -----] <----- start object 1 -----> Received: from sysname (localhost [IPv6:::1]) by sysname.localdomain (Postfix) with ESMTP id E01A9DDA309 for <admin@lists.client.org>; Mon, 12 Jul 2021 13:34:29 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: sarah@email To: admin@lists.client.org Date: Mon, 12 Jul 2021 20:34:29 -0000 Message-ID: <162612206991.3661556.4632729438422001860@sysname> User-Agent: HyperKitty on http://lists.client.org/ Message-ID-Hash: JZP2CHGVCD4THRJ5KPF3GFAK2MOW26VN X-Message-ID-Hash: JZP2CHGVCD4THRJ5KPF3GFAK2MOW26VN X-MailFrom: sarah@email X-Mailman-Rule-Hits: member-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address X-Mailman-Version: 3.3.4 Precedence: list Subject: [Admin] one last test List-Id: admin testing list <admin.lists.client.org> List-Help: <mailto:admin-request@lists.client.org?subject=help> List-Owner: <mailto:admin-owner@lists.client.org> List-Post: <mailto:admin@lists.client.org> List-Subscribe: <mailto:admin-join@lists.client.org> List-Unsubscribe: <mailto:admin-leave@lists.client.org>
try this one more time.
<----- start object 2 -----> { '_parsemsg': False, 'mlist': <mailing list "admin@lists.client.org" at 0x7f34eecc1a20>, 'version': 3} [----- end pickle -----]
On 7/12/21 1:40 PM, Sarah H wrote:
I took a look at the pickle files, this last one didn't have the archive locations but another had
Archived-At: <> List-Archive: <>
as well, so it looks like it's not being passed properly to the archive location?
Messages in the spool were not successfully delivered to HyperKitty[1] and will be retried each time there is a new post.
There should be log messages in mailman.log about the failures.
Likely issues are problems with the base_url or api_key settings in mailman-hyperkitty.cfg
[1] It doesn't matter if they originated from HyperKitty or elsewhere. Messages originating as replies or new threads from HyperKitty are posted to Mailman core for processing and only archived when core sends them back to HyperKitty.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
the logs definitely look like it's the hyperkitty URL. I have tried several different variations of the default URL, the sites URL, and anything else I can find but they all return either a not found or bad response error. is there any way I can find specifically what the URL is aside from changing the config and making a new post each time?
On 7/15/21 11:08 AM, Sarah H wrote:
the logs definitely look like it's the hyperkitty URL. I have tried several different variations of the default URL, the sites URL, and anything else I can find but they all return either a not found or bad response error. is there any way I can find specifically what the URL is aside from changing the config and making a new post each time?
Have you tried the base URL that you use to access HyperKitty from your web browser?, E.g., for this list 'https://lists.mailman3.org/archives/'
Also, it should be a URL you can get from a shell on the server with curl.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I have, it just ends up printing out the pages html in the error message after:
</html> Jul 14 10:52:31 2021 (471314) Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib64/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>Organic BC</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"> <link rel="stylesheet" href="/static/postorius/libs/fonts/font-awesome/css/font-awesome.min.css" type="text/css" media="all" />
<!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="/static/postorius/libs/html5shiv/html5shiv.min.js"></script>
<script src="/static/postorius/libs/respond/respond.min.js"></script>
<![endif]--></head> <body> <nav class="navbar navbar-expand-md navbar-light bg-light navbar-default"> <div class="container"> <div class="navbar-header"> <button type="button" class="navbar-toggler collapsed" data-toggle="collapse" data-target="#header-nav" aria-expanded="false"> <span class="sr-only">Toggle navigation</span> <span class="fa fa-bars"></span> </button> <a class="navbar-brand" href="/mailman3/lists/"><span><img src="/static/postorius/img/mailman_logo_small_trans.png" alt="Mailman logo"/> Postorius</span></a> </div> <div class="collapse navbar-collapse" id="header-nav"> <ul class="nav navbar-nav mr-auto"> <li class="nav-item"><a href="/mailman3/lists/" class="nav-link"> <span class="fa fa-envelope"></span> Lists </a></li> <li class="nav-item"><a href="/archives/" class="nav-link"> <span class="fa fa-comment"></span> Archives </a></li> </ul> <ul class="nav navbar-nav navbar-right"> <li class="nav-item"><a class="nav-link" href="/accounts/login/?next=/hyperkitty/api/mailman/archive"> <span class="fa fa-sign-in"></span> Login </a></li> <li class="nav-item"><a class="nav-link" href="/accounts/signup/?next=/hyperkitty/api/mailman/archive"> <span class="fa fa-user-plus"></span> Sign Up </a></li> </ul> </div> </div> </nav>
<div class="container" role="main">
<h1>Page not found</h1>
<div class="alert alert-danger">This page either doesn't exist, or it moved somewhere else.</div>
</div>
<footer class="footer">
<div class="container">
<p class="text-center">
<a href="https://postorius.readthedocs.org">Postorius Documentation</a>
•
<a href="http://list.org">GNU Mailman</a>
•
Postorius Version 1.3.4
</p>
</div>
</footer>
<script src="/static/postorius/libs/jquery/jquery-1.11.3.min.js"></script>
<script src="/static/postorius/libs/popperjs/popper-v1.11.0.min.js"></script>
<script src="/static/postorius/libs/bootstrap/js/bootstrap.min.js"></script>
<script src="/static/django-mailman3/js/main.js"></script>
<script src="/static/postorius/js/script.js"></script></body> </html>
On 7/15/21 11:28 AM, Sarah H wrote:
I have, it just ends up printing out the pages html in the error message after:
</html> Jul 14 10:52:31 2021 (471314) Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError:
...
I'm interested in what's before that in the log. I.e., the message that says
HyperKitty failure on <the url>: <the returned data> (<the http status>)
Or, is there some redirect in your web server that is maybe redirecting
http to https and returning some 3xx status? We really need to see
the status from the above message.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
The site is behind a proxy, yes. apache serves the client site redirecting 80 to 443 and serving SSL for the site then proxying to Nginx for postorius/hyperkitty at 8080. I've also tried going straight to 8080 bypassing the proxy internally using localhost or loopback to the same end result.
The log is mostly these three errors repeatedly with the same above wall of html between them, some of them end with (404) after the last html tag indicating url not found and browsing to them gives the same custom 404 page for postorius.
Jul 15 12:37:08 2021 (471314) HyperKitty failure on http://lists.client.org/hyperkitty/api/mailman/archive: Jul 15 12:37:08 2021 (471314) Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: Jul 15 12:37:08 2021 (471314) Exception in the HyperKitty archiver:
I was able to find (about 5000 lines up in the log for a single post attempt... it's a bit excessive to print the html response every error) this when I dug through instead of tailing the last 500 lines.
[15/Jul/2021:12:37:06 -0700] "GET /3.1/addresses/sarah.h@email HTTP/1.1" 200 380 "-" "GNU Mailman REST client v3.3.2"
and at the start of the block:
[15/Jul/2021:12:37:03 -0700] "GET /3.1/lists/admin.lists.client.org/member/sarah.%40email HTTP/1.1" 200 516 "-" "GNU Mailman REST client v3.3.2" Jul 15 12:37:05 2021 (471317) ACCEPT: <162637782380.3116.619498070458942231@sysname>
On 7/15/21 12:55 PM, Sarah H wrote:
The log is mostly these three errors repeatedly with the same above wall of html between them, some of them end with (404) after the last html tag indicating url not found and browsing to them gives the same custom 404 page for postorius.
The code is
if result.status_code != 200:
logger.error("HyperKitty failure on %s: %s (%s)",
url, result.text, result.status_code)
raise ValueError(result.text)Jul 15 12:37:08 2021 (471314) HyperKitty failure on http://lists.client.org/hyperkitty/api/mailman/archive:
So the above log entry should be followed by result.text and
result.status_code. The next entry below is from the raise ValueError(result.text)
What do you get from
curl http://lists.client.org/hyperkitty/api/mailman/archive
and what if you change the scheme in the base_url setting to https?
Jul 15 12:37:08 2021 (471314) Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError:
And this one below is is because of the above exception.
Jul 15 12:37:08 2021 (471314) Exception in the HyperKitty archiver:
I was able to find (about 5000 lines up in the log for a single post attempt... it's a bit excessive to print the html response every error) this when I dug through instead of tailing the last 500 lines.
[15/Jul/2021:12:37:06 -0700] "GET /3.1/addresses/sarah.h@email HTTP/1.1" 200 380 "-" "GNU Mailman REST client v3.3.2"
and at the start of the block:
[15/Jul/2021:12:37:03 -0700] "GET /3.1/lists/admin.lists.client.org/member/sarah.%40email HTTP/1.1" 200 516 "-" "GNU Mailman REST client v3.3.2" Jul 15 12:37:05 2021 (471317) ACCEPT: <162637782380.3116.619498070458942231@sysname>
These are from the Mailman REST API and are not relevant to your issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I get a 301 when I go to http and the full html page not found text that is above if I go to https. if I curl loopback on html I get the same html response, https I get:
curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number
On 7/15/21 2:11 PM, Sarah H wrote:
I get a 301 when I go to http and the full html page not found text that is above if I go to https. if I curl loopback on html I get the same html response, https I get:
curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number
A 301 from http will be an issue always.
I'm not sure where the wrong version number comes from. This could be
the issue.
If I do for example,
curl -X POST https://lists.mailman3.org/archives/api/mailman/archive
I get the response
<html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html>
This is the expected response. You need to figure out what base_url will give you a similar response.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
so there should be inside the docroot created by collectstatic a location /docroot/archives(or hyperkitty)/api? or is there another location that this particular page should be served from? at present the hyperkitty directory there is only css, fonts, img and js dirs.
if I can find where this should be served from in the file system that'll give me some way to figure out what I'm actually looking for URL wise...
I apologize if this is off-track, but when I originally was setting up lists in mm3 I made the mistake of using the Postorius "Create List" button. I found that when I did this, I saw no archives and I don't recall if mails flowed OK. The setup was incomplete for me. I had to delete, and then create my lists using the mailman command and then everything just magically worked.
matt
On 7/15/21 2:11 PM, Sarah H wrote:
I get a 301 when I go to http and the full html page not found text that is above if I go to https. if I curl loopback on html I get the same html response, https I get:
curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 7/19/21 9:42 AM, Sarah H wrote:
so there should be inside the docroot created by collectstatic a location /docroot/archives(or hyperkitty)/api? or is there another location that this particular page should be served from? at present the hyperkitty directory there is only css, fonts, img and js dirs.
if I can find where this should be served from in the file system that'll give me some way to figure out what I'm actually looking for URL wise...
Hyperkitty is not serving a web page. HyperKitty has an API at base_url/api with a few endpoints and generates responses to various GETs and POSTs to those endpoints.
Mailman core makes calls to methods in mailman_hyperkitty/__init__.py which in turn call the HyperKitty APi and return the result.
The list_url(mlist) method is called to get the URL to the list's
archive for the List-Archive: header. It in turn does a GET for
base_url/api/mailman/urls with query fragments key=<api_key> and
mlist=<the fully qualified list name> to get the URL
The permalink(mlist, msg) method is called to get the link to where
HyperKitty will store the message for the Archived-At: header. It in
turn does a GET for base_url/api/mailman/urls with query fragments
key=<api_key>, mlist=<the fully qualified list name> and msgid=<the
message-id from the message> to get the URL
The archive_message(mlist, msg) method is called to actually archive
the message. It in turn does a PUT for base_url/api/mailman/archive with
the api_key, the fully qualified list name and the text of the message.
See https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/mailman_hyperkit... for the full detail.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 7/19/21 7:47 PM, Mark Sapiro wrote:
The
archive_message(mlist, msg)method is called to actually archive the message. It in turn does a PUT for base_url/api/mailman/archive with the api_key, the fully qualified list name and the text of the message.
Typo above - should be POST, not PUT.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Sarah H wrote:
The site is behind a proxy, yes. apache serves the client site redirecting 80 to 443 and serving SSL for the site then proxying to Nginx for postorius/hyperkitty at 8080. I've also tried going straight to 8080 bypassing the proxy internally using localhost or loopback to the same end result.
But then Nginx then proxies to Django (via uWsgi or Gunicorn or ?) at probably port 8000. Have you tried setting base_url to http://127.0.0.1:8000/hyperkitty/?
going to port 8000 directly results in
http.client.RemoteDisconnected: Remote end closed connection without response
I have confirmed that uWsgi is listening at that port.
$ netstat -tulnp
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN 2864/uwsgi
attempting to curl the suggested addresses from earlier in the thread return the same results.
[sarah@]$ curl http://127.0.0.1:8000/hyperkitty/api/mailman/archive curl: (52) Empty reply from server [sarah@]$ curl http://127.0.0.1:8000/archive/api/mailman/archive curl: (52) Empty reply from server
Matt: The admin list I am working with was created by the postorius web ui, but I am seeing the same behaviour on the 2 lists imported from mailman 2.1 as well, which were created and imported directly in bash. All 3 lists are sending and receiving mail properly.
On 7/20/21 12:55 PM, Sarah H wrote:
going to port 8000 directly results in
http.client.RemoteDisconnected: Remote end closed connection without response
Is this from mailman.log? In any case, what are all the messages in mailman.log related to this?
attempting to curl the suggested addresses from earlier in the thread return the same results.
[sarah@]$ curl http://127.0.0.1:8000/hyperkitty/api/mailman/archive curl: (52) Empty reply from server [sarah@]$ curl http://127.0.0.1:8000/archive/api/mailman/archive curl: (52) Empty reply from server
You only need to try one of these - hyperkitty and archive are
synonyms for the same things. What if you try
curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive
and
curl -X POST https://127.0.0.1:8000/hyperkitty/api/mailman/archive
(Does Nginx proxy to uWsgi as http or https?)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
here is the full error message. Nginx proxies on http.
https://pastebin.com/raw/TUf5dYi8
the curl commands above result in.
(venv) [mailman@sysname sarah]$ curl -X POST https://127.0.0.1:8000/hyperkitty/api/mailman/archive curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to 127.0.0.1:8000 (venv) [mailman@sysname sarah]$ curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive curl: (52) Empty reply from server
the apache proxy serves the SSL.
(venv) [mailman@sysnamesarah]$ cat /etc/nginx/conf.d/mailman.conf server {
listen 8080 default_server; listen [::]:8080 default_server;
server_name lists.client.org; location /static/ { alias /var/www/lists.client.org/; }
location / { include uwsgi_params; uwsgi_pass 0.0.0.0:8000;
} #ssl_certificate /path-to-ssl-certs/cert.pem; #ssl_certificate_key /path-to-ssl-certs/privkey.pem;
}
On 7/22/21 11:41 AM, Sarah H wrote:
here is the full error message. Nginx proxies on http.
Thanks for the log. It is basically just confirming what we see with this.
the curl commands above result in.
...
(venv) [mailman@sysname sarah]$ curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive curl: (52) Empty reply from server
I am at a loss to understand why HyperKitty isn't responding. Are you able to access HyperKitty normally from a web browser?
Do you get a response from
curl http://127.0.0.1:8000/hyperkitty/
If so, what?
What you should get from
curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive
is
<html><title>Auth required</title><body>
<h1>Authorization Required</h1><p>Please check whether
the MAILMAN_ARCHIVER_KEY is provided by you and it is
correct.
</p></body></html>
You should get the same response as a web page if you go to https://example.com/hyperkitty/api/mailman/urls. Do you?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hyperkitty works fine in browser at https://lists.client.org/archives/ and the vast majority of my testing messages are made through the web browser, though I've tried via email as well with the same results.
curl to http://127.0.0.1:8000/hyperkitty/ results in the same error as above.
Navigating to the URL gives me the custom postorious 404 page.
On 7/22/21 12:34 PM, Sarah H wrote:
Hyperkitty works fine in browser at https://lists.client.org/archives/ and the vast majority of my testing messages are made through the web browser, though I've tried via email as well with the same results.
curl to http://127.0.0.1:8000/hyperkitty/ results in the same error as above.
What if you
curl http://127.0.0.1:8000/archives/
and what to you get in a browser from
https://example.com/archives/api/mailman/urls
And what's in urlpatterns in /opt/mailman/mm/urls.py? I'm sure it contains
url(r'^archives/', include('hyperkitty.urls')),
but I'm suspecting it doesn't contain
url(r'^hyperkitty/', include('hyperkitty.urls')),
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I'm having exactly the same problem as Sarah. I've built the server using the virtualenv instructions (https://docs.mailman3.org/en/latest/install/virtualenv.html) but archiving of messages is not working.
/opt/mailman/mm/var/archives/hyperkitty/spool contains a number of "pck" files.
/opt/mailman/mm/var/logs/mailman.log contains entries like this:
Sep 03 09:38:17 2021 (3011) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.8/site-packages/urllib3/connectionpool.py", line 699, in urlopen httplib_response = self._make_request( File "/opt/mailman/venv/lib/python3.8/site-packages/urllib3/connectionpool.py", line 445, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/opt/mailman/venv/lib/python3.8/site-packages/urllib3/connectionpool.py", line 440, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.8/http/client.py", line 1344, in getresponse response.begin() File "/usr/lib/python3.8/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib/python3.8/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" http.client.RemoteDisconnected: Remote end closed connection without response
curl http://127.0.0.1:8000/archives/ reports:
curl: (52) Empty reply from server
https://example.com/archives/api/mailman/urls reports:
Access is forbidden Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file.
/opt/mailman/mm/urls.py doesn't exist on my machine. I've found the following files called urls.py beneath /opt/mailman:
790264 4 -rw-rw-r-- 1 mailman mailman 138 Aug 16 09:23 ./venv/lib/python3.8/site-packages/falcon/bench/dj/dj/urls.py 538719 4 -rw-rw-r-- 1 mailman mailman 615 Aug 16 09:52 ./venv/lib/python3.8/site-packages/rest_framework/urls.py 539156 4 -rw-rw-r-- 1 mailman mailman 1052 Aug 16 09:52 ./venv/lib/python3.8/site-packages/rest_framework/utils/urls.py 1050019 8 -rw-rw-r-- 1 mailman mailman 7222 Aug 16 09:52 ./venv/lib/python3.8/site-packages/postorius/urls.py 797890 8 -rw-rw-r-- 1 mailman mailman 7783 Aug 16 09:52 ./venv/lib/python3.8/site-packages/hyperkitty/urls.py 1298485 4 -rw-rw-r-- 1 mailman mailman 3246 Aug 16 09:52 ./venv/lib/python3.8/site-packages/django/core/checks/urls.py 1051696 4 -rw-rw-r-- 1 mailman mailman 1310 Aug 16 09:52 ./venv/lib/python3.8/site-packages/django/contrib/admindocs/urls.py 1052065 4 -rw-rw-r-- 1 mailman mailman 498 Aug 16 09:52 ./venv/lib/python3.8/site-packages/django/contrib/staticfiles/urls.py 1052096 4 -rw-rw-r-- 1 mailman mailman 179 Aug 16 09:52 ./venv/lib/python3.8/site-packages/django/contrib/flatpages/urls.py 1052339 4 -rw-rw-r-- 1 mailman mailman 1054 Aug 16 09:52 ./venv/lib/python3.8/site-packages/django/contrib/auth/urls.py 785525 4 -rw-rw-r-- 1 mailman mailman 1481 Aug 16 09:23 ./venv/lib/python3.8/site-packages/pip/_internal/utils/urls.py 1050826 4 -rw-rw-r-- 1 mailman mailman 1289 Aug 16 09:52 ./venv/lib/python3.8/site-packages/mailman_web/urls.py 539863 4 -rw-rw-r-- 1 mailman mailman 752 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/urls.py 539871 4 -rw-rw-r-- 1 mailman mailman 1404 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/account/urls.py 539927 4 -rw-rw-r-- 1 mailman mailman 414 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/urls.py 539944 4 -rw-rw-r-- 1 mailman mailman 162 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/zoom/urls.py 539956 4 -rw-rw-r-- 1 mailman mailman 172 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/nextcloud/urls.py 539968 4 -rw-rw-r-- 1 mailman mailman 174 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/dataporten/urls.py 539982 4 -rw-rw-r-- 1 mailman mailman 134 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/persona/urls.py 539999 4 -rw-rw-r-- 1 mailman mailman 174 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/salesforce/urls.py 540011 4 -rw-rw-r-- 1 mailman mailman 170 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/basecamp/urls.py 540023 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/feedly/urls.py 540035 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/baidu/urls.py 540047 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/naver/urls.py 540061 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/stripe/urls.py 540073 4 -rw-rw-r-- 1 mailman mailman 209 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/vimeo_oauth2/urls.py 540087 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/figma/urls.py 540099 4 -rw-rw-r-- 1 mailman mailman 233 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/keycloak/urls.py 540111 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/yandex/urls.py 540123 4 -rw-rw-r-- 1 mailman mailman 162 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/ynab/urls.py 540135 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/asana/urls.py 540149 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/azure/urls.py 540163 4 -rw-rw-r-- 1 mailman mailman 169 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/linkedin/urls.py 540175 4 -rw-rw-r-- 1 mailman mailman 209 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/draugiem/urls.py 540187 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/dwolla/urls.py 540201 4 -rw-rw-r-- 1 mailman mailman 527 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/oauth/urls.py 540213 4 -rw-rw-r-- 1 mailman mailman 224 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/auth0/urls.py 540225 4 -rw-rw-r-- 1 mailman mailman 165 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/flickr/urls.py 540237 4 -rw-rw-r-- 1 mailman mailman 206 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/discord/urls.py 540249 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/amazon/urls.py 540261 4 -rw-rw-r-- 1 mailman mailman 224 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/jupyterhub/urls.py 540273 4 -rw-rw-r-- 1 mailman mailman 174 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/stocktwits/urls.py 540285 4 -rw-rw-r-- 1 mailman mailman 201 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/openid/urls.py 540311 4 -rw-rw-r-- 1 mailman mailman 172 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/angellist/urls.py 540323 4 -rw-rw-r-- 1 mailman mailman 172 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/pinterest/urls.py 540335 4 -rw-rw-r-- 1 mailman mailman 398 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/apple/urls.py 540351 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/yahoo/urls.py 540365 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/twitch/urls.py 540377 4 -rw-rw-r-- 1 mailman mailman 200 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/agave/urls.py 540389 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/strava/urls.py 540401 4 -rw-rw-r-- 1 mailman mailman 163 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/vimeo/urls.py 540413 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/douban/urls.py 540425 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/weibo/urls.py 540437 4 -rw-rw-r-- 1 mailman mailman 529 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/oauth2/urls.py 540449 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/disqus/urls.py 540461 4 -rw-rw-r-- 1 mailman mailman 162 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/daum/urls.py 540475 4 -rw-rw-r-- 1 mailman mailman 203 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/globus/urls.py 540487 4 -rw-rw-r-- 1 mailman mailman 171 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/box/urls.py 540499 4 -rw-rw-r-- 1 mailman mailman 180 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/odnoklassniki/urls.py 540511 4 -rw-rw-r-- 1 mailman mailman 168 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/shopify/urls.py 540523 4 -rw-rw-r-- 1 mailman mailman 209 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/steam/urls.py 540535 4 -rw-rw-r-- 1 mailman mailman 201 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/patreon/urls.py 540549 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/mailru/urls.py 540561 4 -rw-rw-r-- 1 mailman mailman 137 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/telegram/urls.py 540571 4 -rw-rw-r-- 1 mailman mailman 179 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/fivehundredpx/urls.py 540585 4 -rw-rw-r-- 1 mailman mailman 169 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/evernote/urls.py 540597 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/kakao/urls.py 540611 4 -rw-rw-r-- 1 mailman mailman 162 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/cern/urls.py 540623 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/reddit/urls.py 540635 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/orcid/urls.py 540647 4 -rw-rw-r-- 1 mailman mailman 160 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/edx/urls.py 540659 4 -rw-rw-r-- 1 mailman mailman 165 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/tumblr/urls.py 540671 4 -rw-rw-r-- 1 mailman mailman 170 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/doximity/urls.py 540683 4 -rw-rw-r-- 1 mailman mailman 170 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/frontier/urls.py 540695 4 -rw-rw-r-- 1 mailman mailman 172 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/instagram/urls.py 540707 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/hubic/urls.py 540719 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/weixin/urls.py 540733 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/google/urls.py 540745 4 -rw-rw-r-- 1 mailman mailman 168 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/untappd/urls.py 540759 4 -rw-rw-r-- 1 mailman mailman 217 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/eventbrite/urls.py 540771 4 -rw-rw-r-- 1 mailman mailman 174 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/foursquare/urls.py 540786 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/meetup/urls.py 540800 4 -rw-rw-r-- 1 mailman mailman 172 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/authentiq/urls.py 540812 4 -rw-rw-r-- 1 mailman mailman 172 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/battlenet/urls.py 540828 4 -rw-rw-r-- 1 mailman mailman 227 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/gitlab/urls.py 540840 4 -rw-rw-r-- 1 mailman mailman 224 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/netiq/urls.py 540852 4 -rw-rw-r-- 1 mailman mailman 168 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/cilogon/urls.py 540864 4 -rw-rw-r-- 1 mailman mailman 172 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/robinhood/urls.py 540876 4 -rw-rw-r-- 1 mailman mailman 170 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/coinbase/urls.py 540888 4 -rw-rw-r-- 1 mailman mailman 171 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/bitbucket/urls.py 540900 4 -rw-rw-r-- 1 mailman mailman 360 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/facebook/urls.py 540925 4 -rw-rw-r-- 1 mailman mailman 174 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/soundcloud/urls.py 540937 4 -rw-rw-r-- 1 mailman mailman 172 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/eveonline/urls.py 540949 4 -rw-rw-r-- 1 mailman mailman 234 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/amazon_cognito/urls.py 540963 4 -rw-rw-r-- 1 mailman mailman 162 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/line/urls.py 540977 4 -rw-rw-r-- 1 mailman mailman 184 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/fxa/urls.py 540991 4 -rw-rw-r-- 1 mailman mailman 182 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/linkedin_oauth2/urls.py 541003 4 -rw-rw-r-- 1 mailman mailman 180 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/trainingpeaks/urls.py 541015 4 -rw-rw-r-- 1 mailman mailman 176 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/windowslive/urls.py 541027 4 -rw-rw-r-- 1 mailman mailman 180 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/stackexchange/urls.py 541039 4 -rw-rw-r-- 1 mailman mailman 182 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/microsoft/urls.py 541053 4 -rw-rw-r-- 1 mailman mailman 186 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/quickbooks/urls.py 541067 4 -rw-rw-r-- 1 mailman mailman 179 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/openstreetmap/urls.py 541079 4 -rw-rw-r-- 1 mailman mailman 214 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/mailchimp/urls.py 541091 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/bitly/urls.py 541103 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/paypal/urls.py 541115 4 -rw-rw-r-- 1 mailman mailman 167 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/twitter/urls.py 541127 4 -rw-rw-r-- 1 mailman mailman 183 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/bitbucket_oauth2/urls.py 541139 4 -rw-rw-r-- 1 mailman mailman 179 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/spotify/urls.py 541151 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/exist/urls.py 541163 4 -rw-rw-r-- 1 mailman mailman 178 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/digitalocean/urls.py 541175 4 -rw-rw-r-- 1 mailman mailman 186 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/twentythreeandme/urls.py 541187 4 -rw-rw-r-- 1 mailman mailman 179 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/dropbox/urls.py 541199 4 -rw-rw-r-- 1 mailman mailman 162 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/okta/urls.py 541211 4 -rw-rw-r-- 1 mailman mailman 172 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/sharefile/urls.py 541223 4 -rw-rw-r-- 1 mailman mailman 164 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/slack/urls.py 541237 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/edmodo/urls.py 541249 4 -rw-rw-r-- 1 mailman mailman 191 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/feishu/urls.py 541263 4 -rw-rw-r-- 1 mailman mailman 166 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/github/urls.py 541275 4 -rw-rw-r-- 1 mailman mailman 161 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/xing/urls.py 541287 4 -rw-rw-r-- 1 mailman mailman 165 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/trello/urls.py 541299 4 -rw-rw-r-- 1 mailman mailman 158 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/vk/urls.py 541311 4 -rw-rw-r-- 1 mailman mailman 162 Aug 16 09:52 ./venv/lib/python3.8/site-packages/allauth/socialaccount/providers/zoho/urls.py 538780 4 -rw-rw-r-- 1 mailman mailman 1121 Aug 16 09:52 ./venv/lib/python3.8/site-packages/django_mailman3/urls.py 539115 4 -rw-rw-r-- 1 mailman mailman 1076 Aug 16 09:52 ./venv/lib/python3.8/site-packages/django_mailman3/lib/auth/fedora/urls.py 536453 4 -rw-rw-r-- 1 mailman mailman 156 Aug 16 09:52 ./venv/lib/python3.8/site-packages/haystack/urls.py 537504 4 -rwxrwxr-x 1 mailman mailman 132 Aug 16 09:52 ./venv/lib/python3.8/site-packages/django_q/tests/urls.py
Abhilash Raj (maxking) has made a change to the installation documentation for setting up Mailman 3 in a virtual env (switching from uwsgi to http) and that gets my system further.
I'm now at the point where Mark's suggestion regarding urlpatterns is the blocker, in that querying "https://example.com/archives/api/mailman/urls" works but "https://example.com/hyperkitty/api/mailman/urls" doesn't.
As I noted in my previous reply, I don't have a file /opt/mailman/mm/urls.py on my system. I have found venv/lib/python3.8/site-packages/mailman_web/urls.py that looks to be the file that needs to be updated. I'm on the latest version of that package, 0.0.4.
If I hack that urls.py file to include the hyperkitty URL and send a new message, it all works!
Regards
Philip
On 9/6/21 12:32 AM, Philip Colmer wrote:
Abhilash Raj (maxking) has made a change to the installation documentation for setting up Mailman 3 in a virtual env (switching from uwsgi to http) and that gets my system further.
Hopefully I am replying correctly this time to the list instead of private.
I'm now at the point where Mark's suggestion regarding urlpatterns is the blocker, in that querying "https://example.com/archives/api/mailman/urls" works but "https://example.com/hyperkitty/api/mailman/urls" doesn't. > As I noted in my previous reply, I don't have a file /opt/mailman/mm/urls.py on my system. I have found venv/lib/python3.8/site-packages/mailman_web/urls.py that looks to be the file that needs to be updated. I'm on the latest version of that package, 0.0.4.
You don't *need* to update urls.py to change suburl from /archives' to /hyperkitty`, you can just change the reference to it.
As it turns out, it is another mistake in the install docs :(
Can you update /opt/mailman/mm/mailman-hyperkitty.cfg in to use
base_url: http://127.0.0.1:8000/archives/
instead of the original
base_url: http://127.0.0.1:8000/hyperkitty/
That should fix the issue without having to edit the urls.py.
I'll go ahead and push a fix in the docs for this too.
-- thanks, Abhilash Raj (maxking)
On Mon, 6 Sept 2021 at 20:48, Abhilash Raj <maxking@asynchronous.in> wrote:
You don't *need* to update urls.py to change suburl from
/archives' to/hyperkitty`, you can just change the reference to it.As it turns out, it is another mistake in the install docs :(
Can you update /opt/mailman/mm/mailman-hyperkitty.cfg in to use
base_url: http://127.0.0.1:8000/archives/
instead of the original
base_url: http://127.0.0.1:8000/hyperkitty/
That should fix the issue without having to edit the urls.py.
Thank you - that has, indeed, fixed it (and I did back out my change to urls.py as well).
Regards
Philip
On 9/7/21 1:11 AM, Philip Colmer wrote:
On Mon, 6 Sept 2021 at 20:48, Abhilash Raj <maxking@asynchronous.in> wrote:
You don't *need* to update urls.py to change suburl from
/archives' to/hyperkitty`, you can just change the reference to it.As it turns out, it is another mistake in the install docs :(
Can you update /opt/mailman/mm/mailman-hyperkitty.cfg in to use
base_url: http://127.0.0.1:8000/archives/instead of the original
base_url: http://127.0.0.1:8000/hyperkitty/That should fix the issue without having to edit the urls.py.
Thank you - that has, indeed, fixed it (and I did back out my change to urls.py as well).
Great!
I've pushed the update to the docs to reflect this as well!
https://gitlab.com/mailman/mailman-suite-doc/-/merge_requests/91
-- thanks, Abhilash Raj (maxking)
participants (5)
-
Abhilash Raj -
Mark Sapiro -
Matt Wilbur EFS -
Philip Colmer -
Sarah H