On 1/30/23 13:17, Onyeibo wrote:
The mails don't have that header. I suspect I may have to investigate SELinux.
I think it's unlikely a SELinux issue unless you mean it's an issue writing the log, but if there are any entries at all in mailman.log, that should be OK.
what does mailman conf -s archiver.hyperkitty -k configuration show?
The default is /etc/mailman3/mailman-hyperkitty.cfg. Whatever it is,
what's in that file. It should be something like
[general]
base_url: http://127.0.0.1:8000/archives/
api_key: some_key
some_key needs to match
MAILMAN_ARCHIVER_KEY = 'some_key'
in /etc/mailman3/settings.py and the base_url setting needs to access hyperkitty. It could be as above or it could be the URL that accesses HyperKitty externally as in
base_url: http:://example.com/archives/
Is all of that correct?
To verify base_url, you can do
curl http://127.0.0.1:8000/archives/api/
where the initial part of that is the base_url setting. That should return the html for a page of documentation.
Look at https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/mailman_hyperkit.... This is Mailman Core's interface to the archiver.
If any of the methods there fail to connect to HyperKitty or get an appropriate response, they all log errors.
In particular, the archive_message() method at line 171 is saving the message in the spool queue. Immediately before that at lines 164 and 167 it is writing log messages. You should be seeing them.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan