Last modified: 2012-09-21 17:03:34 UTC
http://lists.wikimedia.org/pipermail/wikitech-l/2010-September/049543.html is unexpectedly truncated. The full version of the message is available at http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/49879/focus=49886 Perhaps the wikitech-l archive needs to be rebuilt or something? The full message definitely went through to the mail server; it appears that the only place it's not showing up properly is in that particular pipermail archive link.
I think this is related to https://bugs.launchpad.net/mailman/+bug/266068 ("From" at line start fools archiver, loses/splits message body)
Bah, and another one: http://lists.wikimedia.org/pipermail/toolserver-l/2010-November/003601.html
Another one: http://lists.wikimedia.org/pipermail/foundation-l/2011-February/063760.html Updating the bug summary. I looked at the launchpad.net link (and from it the Debian bug tracker link), but I don't see the issue. Everyone seems to call this "upstream."
*** Bug 27043 has been marked as a duplicate of this bug. ***
http://mail.python.org/pipermail/mailman-users/2010-November/070550.html seems to indicate that a mailman upgrade (to at least 2.1.13) would fix this issue. Anyone know which version is currently deployed?
According to http://lists.wikimedia.org 2.1.9 is currently deployed.
Then, from looking at http://packages.ubuntu.com/search?keywords=mailman, I'm guessing lists runs Ubuntu Hardy. If you want the mailman package upgraded, I'd recommend asking them for the next LTS release, Lucid: http://releases.ubuntu.com/lucid/
Adding upstream tag + fixing as INVALID since we can't help this, and it seems to have been already in the latest version. I'd say ask someone (or file a bug) to update mailman and/or to "Lucid"
(In reply to comment #8) > Adding upstream tag + fixing as INVALID since we can't help this, and it seems > to have been already in the latest version. > > I'd say ask someone (or file a bug) to update mailman and/or to "Lucid" What? Who's running the latest version? Re-opening this, as the problem isn't solved (and it certainly isn't an "invalid" bug). The bug for updating mailman is listed as a dependency of this bug already (bug 22708).
Another possibly related (unescaped characters?) bug: bug 22973.
After mailman has been updated, I guess rebuilding the archives would fix the bug?
(In reply to comment #11) > After mailman has been updated, I guess rebuilding the archives would fix the > bug? After mailman has been updated, this bug needs to be tested again to see if the behavior still exists. If the truncation has stopped, this bug can be resolved. If the truncation is still happening, this bug needs further investigation and would remain open/unresolved. Rebuilding the archives (to fix this or other issues) would be a separate bug.
The examples seem to be working now (Guessing a rebuild happened during the move?) but can't confirm against gname since it appears to be down.
(In reply to comment #13) > The examples seem to be working now (Guessing a rebuild happened during the > move?) but can't confirm against gname since it appears to be down. Which examples seem to be working?
It seems pipermail is now prefixing lines that begin with "From" with a ">", because it's still 1983: <http://lists.wikimedia.org/pipermail/wikitech-l/2012-September/063361.html>.
un-be-lie-vable.
