chris burgess wrote:
>
>It was as you suggested - a message with an attachment containing an
>apostrophe in the filename. This had also knocked out a list a year
>ago, and the cause was identical (but we didn't find the solution for
>that list until now).
>
>Is this bug #1518281 on SF, or if not, w
Thanks, Mark.
It was as you suggested - a message with an attachment containing an
apostrophe in the filename. This had also knocked out a list a year
ago, and the cause was identical (but we didn't find the solution for
that list until now).
Is this bug #1518281 on SF, or if not, which release o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
chris burgess wrote:
>
> Here's an example of what I see in the mailman error log for any
> message to this list:
>
> ---
>
> Aug 17 15:39:16 2007 (29254) Uncaught runner exception: unpack list of
> wrong size
> Aug 17 15:39:16 2007 (29254) Tracebac
We run 159 lists for an organisation on Mailman 2.1.5 (Debian Stable).
All other lists appear to be behaving fine, but one list seems to be
having issues. This list (and others) have run fine for several years,
and I don't think
I have done as much debugging as I know how, but I can't get this one
