On Thu, Apr 11, 2013 at 12:10 PM, Timo Sirainen <tss(_at_)iki(_dot_)fi> wrote:
On Thu, 2013-04-11 at 11:07 -0400, John C Klensin wrote:
Remember that, for an IMAP user, APPEND offers the choice of
determining what folder the outgoing message going into. That
determination could be made manually or based on the outgoing
address(es), etc. Google's "save automatically" cannot
reasonably support that unless you take your command sequence a
step further and send "and when you store it, put it in folder
XYZ" (or, in Gmail's case, "attach label XYZ"). If you build
an automatic "if the server is saving automatically, don't save
locally" capability, you deprive at least some users of that
folder-selection capability.
I don't think there are many users who want to save the message anywhere
else than the default Sent mailbox (which is configured by IMAP
SPECIAL-USE extension). Those few who want something different are most
likely able to also disable this feature (or more likely haven't enabled
it in the first place).
Isn't this sort of advice already passed around by a number of email
clients as the Fcc: (file carbon copy) header?
Yes, that header is typically removed by the client before message
submission, but perhaps a reasonable approach here is for the server to
advertise at EHLO that it supports an Fcc extension. The client can then
choose to (a) include the Fcc to ask the server to store the mail, or (b)
store the mail itself (locally or by IMAP) and omit the Fcc, or even (c)
store the mail itself and also assert something like Fcc: /dev/null to
force the server to discard its copy.
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp