Adrien de Croy <[email protected]> wrote: > > > With XSEND, you upload the message to IMAP first, then you say: > > > > TAG XSEND UID > > how do you provide the SMTP forward path? Is that scraped from the headers?
That's the right thing to do. You also need to do BCC: processing. (sendmail -t does the right thing.) The rationale for BURL is that there is more to the SMTP envelope than just the sender and recipient addresses - in particular there are the DSN attributes. There's a somewhat ugly and ill-defined split between information for MTA processing (in the envelope) and information for MUA processing (in the headers - see MDN for example). But in fact MTAs do header processing too, so there no practical advantage to ESMTP envelope extensions and a lot of complexity disadvantage. There are a few envelope extensions: DSN, future release, message tracking, CONNEG and CONPERM facsimile media conversion, and 8BITMIME + BINARYMIME. If you want to eliminate BURL you need to either define a mapping from headers to the extension parameters that you want to support, or embed ESMTP inside IMAP. Tony. -- f.anthony.n.finch <[email protected]> http://dotat.at/ Fair Isle: West or northwest, backing southwest, 5 to 7. Rough or very rough. Squally wintry showers. Good, occasionally poor. _______________________________________________ imap5 mailing list [email protected] https://www.ietf.org/mailman/listinfo/imap5
