On Sun, Feb 19, 2012 at 06:34:13PM +0000, Tony Finch wrote: > Bron Gondwana <[email protected]> wrote: > > > > And the copy that went "over the wire" up to the IMAP server is your > > record of what you did. That _should_ include the BCC, so you can go > > back later and check who you sent it to. Obviously, the BCC should > > be stripped as it gets handed over to the delivery agent. > > Right. That last bit (creating the message envelope from the > From/To/CC/BCC headers and stripping BCC) is explained in RFC 5321, > and it's what sendmail -t does.
I've seen the argument of "what if you want to forward a copy on to someone else for inspection, whatever" - without forming a new copy of the message. That's actually really hard to do in the current universe, because the headers will make it look extra spammy. You're much better off forming a new message. Also, storage space for "Sent Items" is almost always cheap. The record of who you sent it to is almost always useful. All that's really missing is a way to form a "new" message from an "old" message without necessarily downloading everything first - but that's what the Lemonade CATENATE stuff was for. Build a new message, potentially including the old one as a message/rfc822 attachment, and then send that. Again, I really think it's the rare case. I'd rather not complicate message sending (and knowing which recipients had the message sent to them) for this case. There will still be SMTP. Most clients don't provide it for good reason - it's weird, advanced, non-intuative stuff. Do Exchange or Facebook provide such interfaces? I get a feeling that protocol designers tend to be people who are paranoid about all the edge cases, which is good, but then wind up optimising rare edge cases at the expense of being able to do the normal operations easily - which is bad. I don't want to optimise for "I want to bounce this message untouched to a new recipient without changing the sender", which is almost always a spam scanning nightmare anyway, at the expense of "the \XSent flag means that it was sent to the recipients named in the message, nothing more, nothing less". Bron. _______________________________________________ imap5 mailing list [email protected] https://www.ietf.org/mailman/listinfo/imap5
