[7877] in SIPB bug reports

home help back first fref pref prev next nref lref last post

pine refiling bug

daemon@ATHENA.MIT.EDU (Laura Baldwin)
Mon Nov 19 15:42:15 2001

Date: Mon, 19 Nov 2001 15:42:11 -0500 (EST)
Message-Id: <200111192042.PAA21699@geskekelud.mit.edu>
From: Laura Baldwin <boojum@MIT.EDU>
To: bug-sipb@mit.edu


Short version: 
Refiling a particular sort of base64 encoded message in pine
causes the header to become repeated.  This means anything trying to
decode base64 is no longer able to.

Long version: 
I receive a piece of mail from a particular sender with base64
encoding, character set utf-8.  If I incorporate it, nmh show is able
to display it properly.  Netscape is able to display it properly.
Pine is also able to display it properly, *in my INBOX folder*, albeit
with the following warning:

    [ The following text is in the "utf-8" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]            

If I refile this message via pine, I get a transient warning:

[Note: deleted message parts NOT included in saved copy] 

The refiled message is no longer readable by any mail client I've
tried.  Pine says

   [Error: Formatting error: Internal base64 decoder error]

If I refile it to #mh/inbox, nmh show says 

mhshow: invalid BASE64 encoding -- continuing
        (content text/plain in message 84)

a whole bunch of times.  Netscape under IMAP refiles it fine, so I
think it's a Pine glitch rather than a mail-server-IMAP glitch.  

I've placed copies of a sample message before and after filing, in
/mit/boojum/Pine-Bug.  It looks like the header is being duplicated,
and since the header isn't *in* base64, the decoder bails.  

If I refile it multiple times from place to place, the headers
continue to multiply.

-Laura

home help back first fref pref prev next nref lref last post