[Mailman-Users] Archive merge and search

Mark Sapiro mark at msapiro.net
Wed Dec 10 20:07:29 CET 2014

On 12/10/2014 01:41 AM, Hal wrote:
> On 18/11/2014 17:31, Mark Sapiro wrote:
>> In Mailman's Content filtering msection you want the following:
>> filter_content: Yes
>> filter_mime_types: empty
>> pass_mime_types:
>>      multipart
>>      text/plain
>>      text/html
>> filter_filename_extensions: irrelevant, default list OK
>> pass_filename_extensions: empty
>> collapse_alternatives: Yes
>> convert_html_to_plaintext: Yes
>> filter_action: as desired, this will only apply to a message which
>> contains no text/html or text/plain part.
> All my settings were the same as above except "pass_mime_types:" where
> "message/rfc822" was also included.

And that's OK. If you want to allow the text content from a post with an
attached message, then include message/rfc822. If you want to remove
everything from a message attached to a post (e.g. a message forwarded
"as attachment" to the list), then don't include message/rfc822.

> My list isn't very active but has come alive in the past few days, but
> strangely none of those messages are available in the archive.
> So I rechecked my settings and quickly removed "message/rfc822" once I
> found it. Still, this hasn't made any difference (new messages have been
> posted to the list since I made that change -I believe you've already
> pointed out that any changes don't affect messages already posted) and
> as far as I can see this shouldn't be the cause of this problem anyway
> (as you explained earlier, including "message/rfc822" only defines if
> attachements should be content filtered or not.

Yes. the presence or absence of message/rfc822 in pass_mime_types
doesn't affect whether or not messages which are delivered to the list
are archived.

> Any idea what could be causing list messages not to be archived? My
> "Archiving options" seem fine:
> archive:        yes
> archive_private:    private
> archive_volume_freq.:    monthly

Lot's of things. ArchRunner not running, permissions issues in the
archive, other things causing exceptions in ArchRunner.

Check that ArchRunner is running (ps -fAww|grep ArchRunner).

Look in Mailman's error log. If you find errors and shunted messages,
you can archive the shunted messages by running 'bin/unshunt' after
fixing the underlying problem and after removing any unwanted message
entries from qfiles/shunt. Run 'bin/show_qfiles qfiles/shunt/*' to see
what's there/

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

More information about the Mailman-Users mailing list