[mel-base-devel] mel.mime:parts not working properly for rfc 2822 (reading from a file)

[Fred Gibson]

Hi Jochen,

On further looking at the problem, the scan and multipart-read seem to
work exactly as designed no matter the message complexity - very nice.
 The reason I'm getting strange results is when using
part-body-string, there seems to be a problem with not skipping enough
headers with increased message complexity, thereby giving a bad read
on a correctly parsed part.  I'm working on troubleshooting this now.

My best,

Fred Gibson

On Sun, Jan 24, 2010 at 5:36 AM, Jochen Schmidt <js at crispylogics.com> wrote:
> Am 24.01.2010 um 14:03 schrieb Fred Gibson <fred at streamfocus.com>:
>
>> Hi Jochen,
>>
>> Yes, that is a beautiful thing - works great now.  (I had to change
>> the peek flet to: ((peek ()   (peek-char nil in-stream nil :eof))  to
>> cure the eof problem.  All is well now.
>
> Yes that should be the right thing to do.
>
>>
>> I made the mistake in my version of thinking the result should give
>> just the low level parts (so 3 parts in the example case instead of a
>> new smaller message + 1 part), so that was part of my misunderstanding
>> about it.
>
> The nice thing of mel-base's body structures is that they actually don't
> reinvent the wheel. I generate just plain standard IMAP body structures.
> This allowed me to just use the IMAP server provided body structure for IMAP
> folders and the generated one for all others. The multipart code just
> demands correct body structures. This is also why these bugs never occured
> with IMAP folders.
>
> ciao,
> Jochen
>



-- 
Fred Gibson

Founder / Software Developer
http://www.streamfocus.com

(c)2010 Organon Technologies LLC