Menu

#870 bad handling From header in archiver

2.1 (stable)
open
nobody
Pipermail (108)
8
2004-09-22
2004-05-13
No

2.1.4 mailman version
- there is problem with archiver. when body of message
contains blank line and continued with text 'From ' at
beggining of line, then archiver thing that this is a
new message and split it.

i see, there is a cleanarch script, which can escape
non-header From line but why i must change original
post adding "escape character"? is there possibility to
check only header of message instead of whole message
including body?

Discussion

  • David A. Desrosiers

    Logged In: YES
    user_id=3078

    I can confirm this bug in 2.1.4, and that it is also in
    2.1.5c2..

    MAJOR BLOCKER! Please assign to someone and fix!

     
  • David A. Desrosiers

    Logged In: YES
    user_id=3078

    I can confirm that this affects the public/stable release
    version of 2.1.5. Running bin/cleanarch on the suspect mbox
    DOES NOT fix the problem.

    I have a list with messages back in 2002, which have "parts"
    showing up at the end of my September 2004 archives. The
    messages contain "parts" of the body, and are missing most
    of the headers.

    Every time arch runs, it reduplicates the trashed/truncated
    messages from 2002 onto the end of the September 2004 archive.

    This is a MAJOR MAJOR MAJOR MAJOR blocker, and cleanarch is
    not a proper solution. There are reasons why valid messages
    can start with the word "From" at the beginning of a line,
    and not be part of the "From:" header.

    Here are two examples:

    http://lists.pilot-link.org/pipermail/pilot-link-general/2002-September/016304.html

    http://lists.pilot-link.org/pipermail/pilot-link-general/2002-June/016144.html

    I haven't yet found a fix for this, and adding the > in
    front of the "From" words at the beginning of the lines,
    DOES NOT fix the problem. In fact, deleting those messages
    (remember, they're from TWO YEARS AGO) from the .mbox,
    rm'ing the .html files, and re-running arch on the list,
    DOES NOT fix the problem.

     
  • Tibor Pittich

    Tibor Pittich - 2004-09-22
    • priority: 5 --> 8
     
  • Mark Sapiro

    Mark Sapiro - 2004-09-22

    Logged In: YES
    user_id=1123998

    I had this problem on 2.1.4 after importing a large archive
    from another service. I then fixed the "^From .*$" lines
    that were in the bodies of a few messages and ran "bin/arch
    --wipe" to rebuild the archive and that absolutely DID fix
    the problem.

     

Log in to post a comment.

MongoDB Logo MongoDB