Martin Duerst <duerst(_at_)w3(_dot_)org> wrote:
look for "Mail actions: [ respond to this message ]". The
functionality is limited to what can be done with the 'mailto' URI,
and only preserves some headers, and not the body. If you have ideas
on how to implement improvements, that would be great.
My first idea is to add a "raw message" link to a message/rfc822
resource. The browser could invoke an internal or affiliated MUA, or
provide the ability to save it to a local mailbox (so that you could
then use your favorite MUA), or provide the ability to resend the
message to yourself (again, so that you could then use your favorite
MUA). Those would all involve some special browser support for
message/rfc822. Without such support, users of Unix-like systems could
save the message to a file and then run sendmail to send it to their own
address.
This suggests a second idea: the archive server accepts requests to mail
a copy of a message to the user. There are various ways such requests
could be issued (typing your address into a form field, logging in and
having a saved preference, sending the request via mail [via a mailto:
link] and having the server reply), but they all raise the possibility
that the system could be abused and made to send arbitrary messages to
arbitrary recipients.
A third idea is for the HTML version to provide a link to
imap://server/msg-id, which would refer to a public (anonymous)
read-only virtual mailbox that contains one message. Your browser might
be able to invoke an MUA and point it at that mailbox, or you might be
able to paste the URI into your favorite MUA.
AMC