Thanks, this was helpful. It was a message I sent to the list that was just an image attachment with no body text. I noticed this other thread about messages with attachments, without text discarded silently <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/E...>. I am attaching the pickle file hoping that it helps anyone researching this issue.
Thank you, Paul 'Arte Chambers' Robey 502-408-6922
On Fri, Jan 31, 2025 at 2:55 AM Stephen J. Turnbull < turnbull@sk.tsukuba.ac.jp> wrote:
Arte Chambers via Mailman-users writes:
There is only 1 .pck file in $var_dir/archiver/hyperkitty/spool and it is only 3.5M - Is there a way I can see what this pck file is?
That file would be related to the response. The *request* in the HyperKitty protocol is going to be much smaller. I believe the normal upper limit is 4kB. The previous report raised the limit on the request to 16kb or maybe 64kB, but then ran into a different problem. None of these numbers should be big enough to cause consistent OOM conditions unless your memory is truly tiny.
To view the file content, su to mailman, activate the virtual environment if you are using one, and type
mailman qfile $var_dir/archiver/hyperkitty/spool/xxxx-xxxx.pck(with the correct name for the qfile, of course). mailman qfile -h will give you help, but IIRC qfile is one of the simplest subcommands: '-h' may be the only option it takes.
There are two parts to the output. The first is the Message object flattened to an RFC 822 message file. The second is a mapping of metadata that gives hints about what Mailman was doing with the file.
Steve
Mailman's content filtering has removed the following MIME parts from this message.
Replaced multipart/alternative part with first alternative.