New messages are not archived - may be a path issue
(I read thoroughly https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/2... "New messages not being archived", but could not find what's wrong on my machine.)
This is what I found in /var/log/mailman3/mailman.log : HyperKitty failure on https://mail.opteryx.org/mailman3/archives/api/mailman/archive: This page either doesn't exist, or it moved somewhere else.
I have double checked all settings in the /etc/mailman3/ configuration files and are not able to get message archived. There is not REST error message any more, but perhaps a problem with the paths. I have no idea any more where to fix this.
On 10/20/23 14:55, Wikinaut wrote:
(I read thoroughly https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/2... "New messages not being archived", but could not find what's wrong on my machine.)
This is what I found in /var/log/mailman3/mailman.log : HyperKitty failure on https://mail.opteryx.org/mailman3/archives/api/mailman/archive: This page either doesn't exist, or it moved somewhere else.
I have double checked all settings in the /etc/mailman3/ configuration files and are not able to get message archived. There is not REST error message any more, but perhaps a problem with the paths. I have no idea any more where to fix this.
I am not sure how you installed Mailman3, but you need to update the URL at which Hyperkitty is available in mailman-hyperkitty.cfg config file, which most probably exists in /etc/mailman3 if you are using our virtualenv guide to install.
[general] base_url: http://127.0.0.1:8000/archives/ api_key: Secret_Hyperkitty_API_Key
In the ^ file, you probably have something like
base_url: https://mail.opteryx.org/mailman3/archivesinstead of
base_url: https://mail.opteryx.org/archives(note the additional /mailman3/ in the path).
-- thanks, Abhilash Raj (maxking)
ok, fixed, works!
(I installed the complete venv-Solution, which was suggested to me. I changed this and that, everything and restarted always, but then it did not work. But now it does. Thank you)
@Mark:
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/
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Abhilash Raj -
Mark Sapiro -
Wikinaut