Mailman/pipermail/MHonArc integration patch

[ppsys]

This patch tightly integrates the MHonArc mail-to-HTML
convertor with Mailman and its internal pipermail
archiving code.

The purpose of the patch is to produce a fusion of
(hopefully) the best features of pipermail and MHonArc
for handling Mailman mailing list archives.

For more detail see patch content or
http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

Under some circumstances, when a single message is passed to
MHonArc for archiving via a pipe, MHonArc may finish its
processing and exit, closing its STDIN before the Mailman
process that invoked it has finished output of the message
to the pipe. Mistakenly, the patched pipermail code treated
this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake.

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself
defined in Defaults.py is the empty string and, until this is
changed, the option to select MHonArc instead of pipermail for
per-list archiving is not offered on the web admin GUI.

[ppsys (ppsys-users)]

The file mhonarc-2.1.3-0.4.patch.gz was added: Revised patch for MM 2.1.3

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

mhonarc-2.1.3-0.6.patch better supports the use of MHonArc
-saveresources option. Also fixes minor HTML syntax error in
mhonarc.mrc and author.mrc that affected generated date and
author index pages.

[ppsys (ppsys-users)]

The file mhonarc-2.1.3-0.6.patch.gz was added: Revised patch for MM 2.1.3

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of
this patch

[ppsys (ppsys-users)]

The file mhonarc-2.1.4-0.1.patch.gz was added: MM 2.1.4 compatible version of the patch

[mmokrejs (mmokrejs-users)]

Logged In: YES
user_id=696559

I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it
works great for me. Would someone apply to offcial cvs tree?
Thanks.

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the
patch

[ppsys (ppsys-users)]

The file mhonarc-2.1.5-0.1.patch.gz was added: Patch revised for MM 2.1.5 compatibility

[dfragos (dfragos-users)]

Logged In: YES
user_id=1310569

what about MM 2.1.6?

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

mhonarc-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

mhonarc-2.1.6-0.2.patch.gz corrects an error in the modified code of
$prefix/bin/arch introduced by the mhonarc-2.1.6-0.1.patch.gz - the
problem was not present in patches for previous MM versions. In some
circumstances, after running $prefix/bin/arch --wipe, subsequent post to a
list my be generated using the wrong archiver. Examining index pages in
the archives of a list will show if this problem has affected that list.
Reinstallation with this revised patch and rerunning $prefix/bin/arch --wipe
should resolve the problem.

[ppsys (ppsys-users)]

The file mhonarc-2.1.6-0.2.patch.gz was added: Corrected patch for MM 2.1.6

[ppsys (ppsys-users)]

The file mhonarc-2.1.7-0.1.patch.gz was added: Patch revised for MM 2.1.7 compatibility

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

mhonarc-2.1.6-0.3.patch.gz corrects a long standing omission in the code of
Mailman/Cgi/create.py which fails to get the initial setup of lists created
through the web quite right. This leads to spurious errors being logged on
message archiving until bin/arch --wipe is run for such a list affected. Lists
created with bin/newlist did not have this problem.

[ppsys (ppsys-users)]

The file mhonarc-2.1.6-0.3.patch.gz was added: Corrected patch for MM 2.1.6

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

Use mhonarc-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

mhonarc-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of
the patch

[ppsys (ppsys-users)]

The file mhonarc-2.1.9-0.1.patch.gz was added: Patch revised for MM 2.1.9 compatibility

[mmokrejs (mmokrejs-users)]

Logged In: YES
user_id=696559

ribosome mailman-2.1.9 # gzip -dc
../mailman-2.1.9-patches/antispam-2.1.9-0.1.patch.gz | patch -p1
patching file Mailman/Cgi/private.py
patching file Mailman/Defaults.py.in
ribosome mailman-2.1.9 # gzip -dc
../mailman-2.1.9-patches/mhonarc-2.1.9-0.1.patch.gz | patch -p1
patching file INSTALL.mhonarc-mm
patching file Mailman/Archiver/Archiver.py
patching file Mailman/Archiver/HyperArch.py
patching file Mailman/Archiver/pipermail.py
patching file Mailman/Cgi/create.py
patching file Mailman/Defaults.py.in
Hunk #2 succeeded at 1390 (offset 73 lines).
patching file Mailman/Errors.py
patching file Mailman/Gui/Archive.py
patching file Mailman/Mailbox.py
patching file Mailman/Version.py
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file
Mailman/Version.py.rej
patching file bin/arch
patching file bin/newlist
patching file templates/Makefile.in
patching file templates/en/author.mrc
patching file templates/en/mhonarc.mrc
patching file templates/en/subject.mrc
ribosome mailman-2.1.9 # less Mailman/Version.py.rej
***************
*** 39,45 ****
  # config.pck schema version number
  # DATA_FILE_VERSION = 96
  # 96.1 to take account of extra moderate_inc_body list
attribute
- DATA_FILE_VERSION = 96.1

  # qfile/*.db schema version number
  QFILE_SCHEMA_VERSION = 3
--- 39,50 ----
  # config.pck schema version number
  # DATA_FILE_VERSION = 96
  # 96.1 to take account of extra moderate_inc_body list
attribute
+ # DATA_FILE_VERSION = 96.1
+ # 96.2 to take account of extra which_archiver and
+ # archiver_when_wiped list attributes
+ # must be applied AFTER the modinc-2.1.7-0.1.patch
+ DATA_FILE_VERSION = 96.2
+

  # qfile/*.db schema version number
  QFILE_SCHEMA_VERSION = 3
ribosome mailman-2.1.9 #

So, which patch do I have to apply before applying the 2.1.9
-0.1 version of this? It is a pitty this is not yet in the
official releases. I am using mailman-20041012.tar.bz2 with
these for some years and see only 2 or three types of error
in the logs. But damn mailman ignores some subscription
confirmation messages and breaks on some non-us-ascii
encoded messages so I should upgrade to see if it helps. :((

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

The file INSTALL.mhonarc-mm installed by this patch contains the following
words. The same information is also on the openinfo web page whose URL is
above.

Necessary Precursors
--------------------

The following patch must be applied to Mailman before applying this patch:

1. Mailman Patch #760567: both this patch and #760567 update the
version number ...

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166

Apologies, but the URL cited above had to be changed when I changed hosting
service provider as they have co-opted the /mailman/ URI root. See instead:

http://www.openinfo.co.uk/mm/patches/mhonarc/index.html

[mmokrejs (mmokrejs-users)]

Logged In: YES
user_id=696559

Yes, that helped. Thanks. After years I documented a bit
which patches I use for mailman:

#!/bin/sh
gzip -dc mailman-2.1.9.tgz | tar xvf -
cd mailman-2.1.9
patch -p1 < ../mailman-2.1.9-patches/modinc-2.1.9-0.1.patch
gzip -dc
../mailman-2.1.9-patches/antispam-2.1.9-0.1.patch.gz | patch -p1
gzip -dc ../mailman-2.1.9-patches/mhonarc-2.1.9-0.1.patch.gz
| patch -p1
cat ../mailman-2.1.9-patches/11_handle_propfind.patch |
patch -p0
cat ../mailman-2.1.9-patches/72_fblast_add_shebang.patch |
patch -p0
cat
../mailman-2.1.9-patches/75_emaillist_only_show_bad_emails.dpatch
| patch -p1
cat ../mailman-2.1.9-patches/passwd-rfc3834.patch | patch -p0
cat ../mailman-2.1.9-patches/mailman-2.1.6rc3-relpath.patch
| patch -p1

[ppsys (ppsys-users)]

Logged In: YES
user_id=75166
Originator: YES

File Added: mhonarc-2.1.10-0.1.patch.gz

[ppsys (ppsys-users)]

The file mhonarc-2.1.10-0.1.patch.gz was added: Patch revised for MM 2.1.10 compatibility

[Mark Sapiro (msapiro)]

This patch has been updated for Mailman 2.1.18-1 and can be found at <http://www.msapiro.net/mm/mhonarc-2.1.18-1.1.patch> (mirrored at <http://fog.ccsf.edu/~msapiro/mm/mhonarc-2.1.18-1.1.patch>.

The documentation at <http://openinfo.co.uk/mm/patches/mhonarc/index.html> is still relevant.