Menu

#453 Incorrect scan line shown for msg with malformed header

mh-e-8.1
open
nobody
None
6
2013-02-23
2008-09-19
Chris Lott
No

MH-E shows incorrect contents in scan line (carry-over from previous message) when the headers have problems.
I noticed this in my outbox.

I have attached a test case. To reproduce this, unpack the attached archive. Put "nospam@research.telcordia.com" in your .mh_profile Alternate-Mailboxes line. Then scan the folder using MH-E. The MH-E scan yields garbage for message 2:

1 03/03 To:"SAUTER, ROBER Re: Promotion to Auto/Auto: Can you promote both T
2+-03/04 To:"SAUTER, ROBER Re: AETG<<foo bar baz

The plain old MH system's scan command yields the expected output:

1 2008/03/03 To:"SAUTER, ROBER Re: Promotion to Auto/Auto: Can you promote
2+-2008/03/04 To:"Gummuluri, Kr Re: AETG<<foo bar baz >>

Ignore the date-format difference. The "To" content of message 2 is what drives me nuts. MH-E apparently shows leftover data from message 1. I note that message 2 has some oddly formatted headers, and I strongly suspect those are triggering the problem, because when I delete them, the scan result is OK.

Just in case, here is my config.

MH-E 8.1

MH-E compilation details:
Byte compiled: no
Gnus (compile-time): N/A
Gnus (run-time): Gnus v5.10.8

GNU Emacs 21.4.2 (sparc-sun-solaris2.7, X toolkit)
of 2007-01-08 on hazy

MH 6.8.4
mh-progs: /opt/mh/bin
mh-lib: /opt/mh/lib
mh-lib-progs: /opt/mh/lib

SunOS hazy 5.7 Generic_106541-11 sun4u sparc SUNW,Ultra-Enterprise

Discussion

  • Chris Lott

    Chris Lott - 2008-09-19

    Archive of MH folder with 2 sent msgs

     
  • Bill Wohler

    Bill Wohler - 2008-11-26
    • priority: 5 --> 6
     
  • Bill Wohler

    Bill Wohler - 2011-12-27
    • status: open --> open-accepted
     
  • Bill Wohler

    Bill Wohler - 2013-02-23
    • labels: General -->
     
  • Bill Wohler

    Bill Wohler - 2013-02-23

    Ticket moved from /p/mh-e/feature-requests/139/

     
  • Bill Wohler

    Bill Wohler - 2013-02-23
    • Status: open-accepted --> open
     

Log in to post a comment.