Alexey Melnikov wrote:
That's not an issue is it? Just add a new/custom header field. MTAs pass
through header data unchanged if it doesn't understand it.
Tony Finch wrote:
I was thinking that my LMTP server can also support this extension and
will set IMAP flags on delivery.
On Mon, 19 May 2008, Alexey Melnikov wrote:
Regarding metadata transfer: it might be handy. I was thinking about
extension for passing IMAP flags from sender to recipient, for
example I can
annotate a message with flags using Thunderbird [something I can do
then forward the annotated message [something I can't].
The message envelope is lost at final delivery time, so MUA-to-MUA data
transfer has to be done via the message header.
(This is why there are
different mechanisms for DSNs and MDNs. DSN information is for
by MTAs so it's in the envelope, and MDN information is for
MUAs so it's in the header.) The IMAP server is a very borderline case
between MTA and MUA so it might not be immediately clear that your
wrong. However you might want to forward a message as an attachment with
IMAP flags, in which case there's no envelope in which to stash them.
Yes, a way to encode metadata in headers would be needed as well.
The problem is with MTA-MTA data to be passed separately from the
message data. There's no way to do that at the moment without every MTA
on a message's route understanding the specific extension the data is
for. So, essentially what I'm suggesting is a way to do the same as for
header data, but for MTA relevant data, so MTAs which understand the
data can use it, but other MTAs will just pass it on to the next MTA
VPOP3 - POP3/SMTP/IMAP4/Webmail Email server for Windows