Re: mailbox stream

[Sergey Poznyakoff]

> Or we could decide, forget it, this type of functionnality is not need it
> they should always read messages via the message_t and
> mailbox_{s,g}et_stream () means the to give the __tcpip__ stream.

I'd think the messages should really be read via
mailbox_{s,g}et_stream () -- this makes the interface consistent no
matter what kind of protocol we're using. But instead of returning
raw tcpip output maybe it would be better to implement some kind
of `translation function' in mailbox_t, so that when one is reading
from the stream he would get clean message without protocol quirks.
What do you think?

In the meantime I was stuck with implementation of append command
in imap4d: all was ready and working fine, except that I had to
add mailbox_destroy_folder() function to mailbox.c, which just
destroys the folder associated with the mailbox. After this I
can safely call mailbox_set_stream (tmp, stream) and obtain
the needed functionality.

Cheers,
Sergey