[Pine-info] Error code: richtext token over 40 characters

[Matthew Kozak]

Exactly.
PINE fails the whole process and doesn't even tell you from whence the 
error occurs (OK, so which email, of the 5,000+ being archived, failed?!).

:^(


I agree with you, but am also having the user try to debug (to see if the 
debug shows any more info.) and/or try exporting to find the culprit 
email(s) using a binary search sort of method (export half of your 
messages and then the other half and keep dividing until you find this 
offending email)...although it seems awfully silly to have to do it this 
way!

I'm not likely to mess with the source, since this is one user of the 
entire University that has access to PINE.  We use a centrally-compiled 
version from our main campus here, and I don't have easy (if any?) 
permission to replace binaries with my own tweaked versions...

FYI,
-Matt


On Mon, 3 Apr 2006, Eduardo Chappa wrote:


> *** Matthew Kozak (bamkozak at camden.rutgers.edu.comm) wrote in the pine-info...:

>

> :) Anyone know how to deal with the below, aside from having her use a GUI

> :) mail program to do her exporting (drag and drop or such)?

> :)

> :) One of our users is trying to export VERY MANY emails and this rich

> :) text needle in a haystack (I suspect a crummy Outlook-generated email,

> :) but I may be mistaken...) keeps failing the process.

>

> Matthew,

>

>  The error is due to the existence of a token which is longer than 40

> characters. The text below is from rfc1341:

>

>            The syntax of "richtext" is very simple.  It is assumed, at

>            the top-level, to be in the US-ASCII character set, unless of

>            course a different charset parameter was specified in the

>            Content-type field.  All characters represent themselves, with

>            the exception of the "<" character (ASCII 60), which is used

>            to mark the beginning of a formatting command. Formatting

>            instructions consist of formatting commands surrounded by

>            angle brackets ("<>", ASCII 60 and 62).  Each formatting

>            command may be no more than 40 characters in length, all in

>            US-ASCII, restricted to the alphanumeric and hyphen ("-")

>            characters.

>

> Having said that, I think it is not good that Pine stops decoding such

> messages as it currently does. In my opinion, it should just ignore the

> error up to the extent of saying "this is not a token, therefore I ignore

> it", rather than say "This is not conforming to rfc1341, therefore I do

> not output anything". The only thing you can do is to modify the source

> code. Take a look at the file pine4.64/pine/filter.c around line 2471.

> There is a block which if you remove, you will probably get the text fully

> decoded.

>

> I hope this helps you.

>

> -- 

> Eduardo

> Patches/Help: http://www.math.washington.edu/~chappa/pine/

> XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml

> Please send spam to webmaster at localhost

>

>


Matthew Kozak, CLAW'99, GSBC'04
Systems Programmer/Administrator
--------------------------------
Camden Computing Services
BSB, Room 126
227 Penn Street
Camden, NJ   08102
email:  mkozak at camden.rutgers.edu
phone:  856-225-6065
fax:    856-225-6436
web:    http://computing.camden.rutgers.edu