On 12/04/2014 05:05 PM, Stephen J. Turnbull wrote:

After a quick look at the patch I'd guess a 50% change that nothing relevant to MHonArc except the version number has changed since 2.1.12, and a 90% chance that any fixes needed are *very* simple. Have you tried that patch and had it fail? If not, give it a try, please. We'll be happy to help debug any issues.

Just for fun, I applied both the prerequisite modinc-2.1.12-0.1.patch and the mhonarc-2.1.12-0.1.patch to Mailman 2.1.18-1

Both patches failed to patch Mailman/Version.py because the 2.1.18-1 DATA_FILE_VERSION is 105 and in 2.1.12 it was 97. This is trivial to fix. Just increment DATA_FILE_VERSION to 105.2.

The only other failure was in Mailman/Mailbox.py because Mailman 2.1.18 adds a skipping() method to the end of the module. Again, it is very simple to manually add the intended changes.

Everything else applied with at most line number offsets.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Mark Sapiro wrote:

Just for fun, I applied both the prerequisite modinc-2.1.12-0.1.patch and the mhonarc-2.1.12-0.1.patch to Mailman 2.1.18-1

OK, it's raining here (hooray!) and a slow day, so I went further and created <http://www.msapiro.net/mm/mhonarc-2.1.18-1.1.patch>.

This is Richard's patch with all conflicts resolved, the dependency on <http://openinfo.co.uk/mm/patches/760567/index.html> removed and code added to Mailman/versions.py to add the new list attributes to existing lists.

This last is the whole point of bumping DATA_FILE_VERSION; i.e. when Mailman detects that Mailman.Version.DATA_FILE_VERSION is greater that that in the list's data_version, it calls Mailman.versions.Update to update the list to the current DATA_FILE_VERSION. If the code isn't in Mailman.versions.Update, nothing gets updated except the list's data_version.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 12/05/2014 01:14 PM, Karl Zander wrote:

Pipermail seems place the file into separate URL and give it a generic filename. Maybe I am missing some setting and Pipermail can keep the message and attachment together?

You're probably not overlooking any setting.

The pipermail archiver removes and stores aside all MIME parts of the message except those with Content-Type: text/plain and a known character set.

There are some optional settings for ARCHIVE_HTML_SANITIZER for dealing with HTML, but none of these allow storing HTML inline in the archive in a way that it will be 'rendered'. Read about these in the documentation in Defaults.py.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 12/04/2014 05:05 PM, Stephen J. Turnbull wrote:

After a quick look at the patch I'd guess a 50% change that nothing relevant to MHonArc except the version number has changed since 2.1.12, and a 90% chance that any fixes needed are *very* simple. Have you tried that patch and had it fail? If not, give it a try, please. We'll be happy to help debug any issues.

Just for fun, I applied both the prerequisite modinc-2.1.12-0.1.patch and the mhonarc-2.1.12-0.1.patch to Mailman 2.1.18-1

Both patches failed to patch Mailman/Version.py because the 2.1.18-1 DATA_FILE_VERSION is 105 and in 2.1.12 it was 97. This is trivial to fix. Just increment DATA_FILE_VERSION to 105.2.

The only other failure was in Mailman/Mailbox.py because Mailman 2.1.18 adds a skipping() method to the end of the module. Again, it is very simple to manually add the intended changes.

Everything else applied with at most line number offsets.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Mark Sapiro wrote:

Just for fun, I applied both the prerequisite modinc-2.1.12-0.1.patch and the mhonarc-2.1.12-0.1.patch to Mailman 2.1.18-1

OK, it's raining here (hooray!) and a slow day, so I went further and created <http://www.msapiro.net/mm/mhonarc-2.1.18-1.1.patch>.

This is Richard's patch with all conflicts resolved, the dependency on <http://openinfo.co.uk/mm/patches/760567/index.html> removed and code added to Mailman/versions.py to add the new list attributes to existing lists.

This last is the whole point of bumping DATA_FILE_VERSION; i.e. when Mailman detects that Mailman.Version.DATA_FILE_VERSION is greater that that in the list's data_version, it calls Mailman.versions.Update to update the list to the current DATA_FILE_VERSION. If the code isn't in Mailman.versions.Update, nothing gets updated except the list's data_version.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 12/05/2014 01:14 PM, Karl Zander wrote:

Pipermail seems place the file into separate URL and give it a generic filename. Maybe I am missing some setting and Pipermail can keep the message and attachment together?

You're probably not overlooking any setting.

The pipermail archiver removes and stores aside all MIME parts of the message except those with Content-Type: text/plain and a known character set.

There are some optional settings for ARCHIVE_HTML_SANITIZER for dealing with HTML, but none of these allow storing HTML inline in the archive in a way that it will be 'rendered'. Read about these in the documentation in Defaults.py.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan