Nirmal J via Mailman-users writes:
Yes, There are files in that Directory.
root@list1:/var/lib/mailman3/archives/hyperkitty/spool# ls 1761648373.8935+904b919ee2129941efb5359d7fbc08cc66e154c8.pck 1761648373.917401+f2d75be071a12b44949318373ebcb0b05cf8341e.pck root@list1:/var/lib/mailman3/archives/hyperkitty/spool#
This indicates that HyperKitty is not picking up the queued files. Is mailman-hyperkitty installed? Is it configured correctly and enabled in mailman.cfg?
The Mailmans var.logs/mailman.log contains root@list1:/var/log/mailman3# cat mailman.log
This is today's log and shows no evidence of mail being received. Please look for older rotated logs (they typically look like mailman.log.1 and mailman.log.2.gz).
Specifically, in the log there should be notification that the mail was accepted like: Jan 02 20:46:31 2025 (167424) ACCEPT: <26486.63741.632755.297346@ip-192-168-11-5.eu-west-1.compute.internal>
What we are now looking for in that file is evidence of attempts to send to HyperKitty which look like these: Jan 02 20:46:32 2025 (167421) HyperKitty archiver processing queued filebase: 1735850598.983 318+a12b7afd6b238d1547d6ebda2f6b8e58ddd56046 Jan 02 20:46:32 2025 (167421) hyperkitty archiver: sending message <26486.64097.918721.71938@ip-192-168-11-5.eu-west-1.compute.internal>
and information about any failures.
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan