Subject: "invalid char in quoted string" message essentially hanging pine

From: Matt Ackeret <[email-masked]>
Date: Mon, 5 Nov 2001 10:37:09 -0800 (PST)

So I've got a spam message, and even going past it in the message list ends up
hanging pine (I haven't tried letting it sit for a very long time)..

What it's saying at the bottom is:
  N 1867 Nov  3 ¹q¸£¤[email-masked]   (77K) [big5] ±À¼s³n¥ó¤Î©Û¶Ò¤À¥N²z
                  [>Invalid CHAR in quoted string: ffffffa4<]

and the last 2 hex digits are changing.. every few seconds.

Aaah, so it FINALLY stopped (after a minute or two)..

What's up with this?  Seems to me it shouldn't be ignoring my keystrokes in
this time.

[email-masked]

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Joel Boonstra <[email-masked]>
Date: Tue, 6 Nov 2001 14:58:54 -0500 (EST)

> So I've got a spam message, and even going past it in the message list
> ends up hanging pine (I haven't tried letting it sit for a very long
> time)..
>

*YES*

I get this as well, but have not found a solution.  A number of generous
folks on this list volunteered to test out the problem, but so far, none
seem to have been able to replicate the problem.

What version of pine are you using?  I can only replicate this with 4.40
-- 4.33 doesn't bat an eye.

It also seems that some keystrokes still work, but others won't.  Those
end up being queued until the error messages end, and all get executed
when the error messages stop being displayed.

Did anyone make headway on this when I posted about a month or so ago?
Can anyone else besides myself and Matt replicate the problem?  I would
*love* to hear a solution, or any ideas that folks might have.

Thanks!

-- 
[ joel boonstra | [email-masked] ]

---

From: Matt Ackeret <[email-masked]>
Date: Tue, 6 Nov 2001 12:35:05 -0800 (PST)

>-- 4.33 doesn't bat an eye.

I'm using 4.40, unfortunately it looks like I didn't save the message.