Arpad Horvath via Mailman-users writes:
> I moved from mailman to mailman3 in 2021. I hadn't have the time to
> fix the archiving. I can see the emails older then that in
> Hyperkitty, but none of the once still there is mailman3. What can
> be the problem?
I don't understand "none of the once still there is mailman3". Do you
mean none of the emails sent since the upgrade from Mailman 2 to
Mailman 3 are not visible in HyperKitty?
> It's a Debian 12, I use the packages from the repo.
> ERROR 2025-02-26 06:47:31,705 861 hyperkitty.views.mailman Access to the
> archiving API endpoint was forbidden from IP xxx.xxx.xxx.xxx, your
> MAILMAN_ARCHIVER_FROM setting may be misconfigured
[...]
> I have this line in /etc/mailman3/mailman-web.py
>
> MAILMAN_ARCHIVER_FROM = ('https://lists.somewhere.xx/hyperkitty', '::1')
Where did that line come from? Did you put it there? If so, don't
worry about it, we'll figure out what goes there. If not, investigate
a bit and if it seems like it came from debconf, you may want to
report an issue to Debian.
I think Django is failing to parse that. It expects hosts, not URLs.
The default is:
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1')
I would just comment out that line in mailman-web.py and restart. If
it starts working, then I suggest removing it entirely.
Steve
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@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/LPVUR5HMCZZLQRPH3TFKTMVVV2KZ32V2/
This message sent to arch...@mail-archive.com
