[Mailman-Users] Archive looping

[Mark Sapiro]

On 09/01/2015 07:27 AM, Joseph Brennan wrote:
> 
> Yesterday the archive got into a weird state that I could not break by a
> shutdown and fresh start. For each incoming message, it rewrites all of
> the old messages with one extra newline. This useless activity takes
> quite a while and has caused mail to accumulate in the in/ directory.


This really shouldn't affect the /in queue as IncomingRunner only puts
the message in the archive/ queue for ArchRunner.


> Inspection of a sample message in a backup from about 24 hours ago shows
> hundreds of newlines added to the message in that time. The newlines are
> always added at the same place, between this:---
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <<A HREF="https://lists.columbia.edu [detail omitted] </A>>
> </PRE>
> 
> and this:---
> 
> <!--endarticle-->
>    <HR>
>    <P><UL>
>     <!--threads-->


and in a followup wrote:
> Second-- Not all messages are getting rewritten one newline at a time. Only those with "An HTML attachment was scrubbed..." get the rewrite. 


It is totally unclear how this happens. Have you tried restarting Mailman?

The "An HTML attachment was scrubbed..." stuff is created by
Scrubber.py, but the "</PRE>" and "<!--endarticle-->" are created by
HyperArch.py and I don't think HyperArch.py knows or cares if what
Scrubber.py did. Then the whole thing is written at once by
pipermail.py. Nothing in Mailman would be writting one \n at a time to
disk in the middle of an article.

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