Re: bug in ::mime::copymessage
- From: blacksqr <stephen.huntley@xxxxxxxxxxxx>
- Date: Fri, 02 Nov 2007 15:23:19 -0700
On Nov 2, 1:32 pm, "M. Strobel" <yykontak...@xxxxxxxxxxxxxxxxxx>
wrote:
Hi,
I am trying to find a bug with missing characters at the end of "some"
mime attachments.
The problem is that some extracted files are shorter than the original.
I extracted the attachement with mime::copymessage, and there was one
byte missing at the end of the extracted base64 encoded file.
So the error seems to occur where the mime package builds up its state
array where the offset and length of parts are stored.
Same problem in Win ActiveStateTCL 8.5.0.0 beta-6, the last base64
encoded line has 63 chars, the original 64 chars.
I fell out of the debugging session 3 times trying to trace the error.
Can someone confirm the length problem? Am I the only one using
::mime::? Should I file a bug report on sourceforge?
Max
You should definitely file the bug at sourceforge, and attach the test
file you're using to the bug report so others can duplicate the
behivior you see.
Steve H.
.
- Follow-Ups:
- Re: bug in ::mime::copymessage
- From: M. Strobel
- Re: bug in ::mime::copymessage
- References:
- bug in ::mime::copymessage
- From: M. Strobel
- bug in ::mime::copymessage
- Prev by Date: Re: Problem with expansion variable
- Next by Date: How to dispose of the unwanted gap?
- Previous by thread: bug in ::mime::copymessage
- Next by thread: Re: bug in ::mime::copymessage
- Index(es):
Relevant Pages
|