Tickets :: Comment on [#3381] "forward" handles multipart/alternative incorrectly

* Your Email Address
* Spam protection	Enter the letters below: .___. ..__. __..___ [__ \| \|\| \|(__ [__ [___\|/\\|\|__\|.__)[___
Comment	>> I have implemented > >> (sort of) #2 with the addition that we still put the text of the > >> first viewable text part into the message body window. > > > > Hi, > > > > Thanks for looking at this! > > > > I have one fear about your proposed solution: is the text that you > put in the message body window editable? Please make that text not > editable! If the text is editable, then two version of the text will > still be sent -- the edited text (in the message body), plus the > original text (in the attachment). My goal is to make sure that only > one version of text is sent. > > > > If you'd like to compare to another mail program, I can say how the > Pine mail reader does it: > > 1. By default, forward only the text/plain part. During the sending > process, insert the text/plain into the editing buffer, so that the > user can edit it. > > 2. If the user choose an optional forwarding command, pine will > attach the forwarded message as a message/rfc822 attachment, and will > not let the user edit the text of the attachment. (The user can > still type a preamble, that will be put in to the first part of the > message, before the attachment.) > > > > This algorithm simplifies down to something like: > > 1. If the user edits the text of the forwarded message, make sure > that ONLY that text is sent, and that no other text from the original > message is sent. Send only the edited text. > > 2. If the user user does not edit the text of the forwarded message, > then it is safe to forward anything that was in the original message. > > > > > > Thank you, > > > > -Jacob Morzinski
Attachment
Watch this ticket

Saved Queries