On Mon, Jan 30, 2023 at 10:58 PM Onyeibo <onyeibo@schemefusion.com> wrote:
On Mon, 30 Jan 2023 16:01:16 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') So an array??
These are defaults. I have also added my IPs. Nothing is happening.
Perhaps I did something wrong here. Any documentation on this?
https://mailman-web.readthedocs.io/en/latest/settings.ht
My instance is not archiving.
Things to check: the same as api_key in mailman-hyperkitty.cf (unquoted here!)?
- Is your MAILMAN_ARCHIVER_KEY value in settings.py (quoted here!)
I have double-checked this. Yes ... I got it right
- Your MM3 log files - do they say anything?
Nothing! No new errors. It is very strange and frustrating
Simply put:
Mailman3 uses the following components for archiving:
Archiver: responsible for storing messages and metadata, such as message header information, in the archive database. Archiver API: provides an interface for accessing the archived messages. Archiver REST API: allows access to the archives through a RESTful interface.
To configure Mailman3 archiving, you can:
Choose an archive backend, such as the built-in HyperKitty backend, or a third-party archive backend. Set up the archive backend, including database connection details and other required configurations. Configure Mailman3 to use the chosen archive backend. This typically involves updating the Mailman3 configuration file and specifying the backend's configuration information. You can find more information about Mailman3 archiving and its configuration in the Mailman3 documentation.
Now you need to go over the archiver configuration/enablement with a toothcomb :)
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)