On Sat, Jan 15, 2000 at 10:57:00PM -0500, Russell Nelson wrote:
> Bruce Guenter writes:
> > - message state storage (read, replied to, forwarded, flagged, etc.)
> > seperate from content delivery (a "Status:" header line)
>
> I wonder if that couldn't be handled by the Maildir code writing
> Status: XXXXXXX as the very first line in each message?
Um, am I missing something? I thought the whole point of the "info"
portion of the filename of the message in the maildir?
> > - explicit message size notification
> You get this already.
In what?
> > - message upload (for draft messages ...
> Couldn't you just send it to $USER-draft, and direct $USER-draft into
> a draft Maildir?
That is an option, but messy, considering that the act of delivery will
cause header manipulation and IMHO saving messages should keep them
intact.
Another option is to do it in reverse: no direct email sending, but
rather a procedure that uploads a message to a folder, and then sends
that email (by some unique identifier).
> > On the
> > other, all your content is still in the clear, so it would be better to
> > assume a SSL link where necessary.
> I'd assume ssh, now that there's http://openssh.org .
Good thought, especially with the tunneling options, but unless things
have changed, SSH still requires shell access -- something that should
not be required for mailbox access.
--
Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/
