It appears that OE will barf if you send it an ENVELOPE response in
which the date element is malformed - like this (first part of response
only shown).
* 16 FETCH (ENVELOPE ("Fri, 11 Oct 00:24:58 2002 -0700"
Now, I can parse these ctime-format dates without any trouble (and it
depresses me how many systems generate them), but my reading of
RFC3501 is that an env-date is an nstring, and that there is no
expectation that I will necessarily ensure that it is semantically valid,
provided the nstring is itself syntactically correct.
Problem is, OE actually reports to the user that "the server has reported
an error", which to my way of thinking just isn't right.
What are other people doing in this case? Should I be parsing and
reconstructing the date in proper RFC2822 format? I can do that easily,
and it would fix the problem, but it seems kind of wrong to be messing
with the data in that way.
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
Advertisement in the Sydney Morning Herald:
NOMADIC RUG TRADERS,
Specialists in old Oriental Rugs and Kilms
HAVE MOVED.
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/imap/imap-list.html
-----------------------------------------------------------------
