RFC2060 section 6.4.5 has this text:
-------------------------- Cut here ----------------------------
Any partial fetch that attempts to read beyond the
end of the text is truncated as appropriate. A
partial fetch that starts at octet 0 is returned as
a partial fetch, even if this truncation happened.
-------------------------- Cut here ----------------------------
I'm hoping someone can give me a little clarification on this; assume we
have a message with 384 bytes, and the client issues this command:
A30 FETCH 42 (BODY[TEXT]<385.16384>)<cr><lf>
Am I correct in assuming that the correct return for this command is:
* 42 FETCH (BODY[TEXT]<385> {0})<cr><lf>
There are two points here:
* Is the zero-length literal declaration mandatory? (I'm sure it is, but
I'd like this confirmed by greater minds).
* Is the proper partial startpoint in the response "385", even though
that value is effectively invalid?
I've just discovered a client that appears to do partial fetching beyond
the end of the message as a matter of routine and it looks as though
this is something I hadn't anticipated in my server code. If some kind
soul can give me some guidance, I'll amend my server code at once.
Cheers!
-- David --
------------------ David Harris -+- Pegasus Mail ----------------------
Box 5451, Dunedin, New Zealand | e-mail: [EMAIL PROTECTED]
Phone: +64 3 453-6880 | Fax: +64 3 453-6612
Fire extinguisher instructions in a tavern in Richmond:
In case of fire, stand on head and bang knob on ground.
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/imap/imap-list.html
-----------------------------------------------------------------
