Using 19990923 build on win98 (still checking mac and linux) Replying to a plain text messsage while in Plain text format, there is no quoting for the original text. This is regression, I've scanned the bug data base and I don't see an opened bug for this. 1. Change your preference for html compose = false 2. Launch Messenger 3. Open a folder and select a plain text message 4. Click Reply from toolbar (notice no quoting for the original text) 5. Reply to the message and retrieve the message (no quoting for the original text)

It's because the function that convert HTML to plaintext failed. Maybe because it doesn't know what to do with BlockQuote

Move milestone stoppers to M10

Does this happen on Linux or Mac?

What do you mean by "no quoting for the original text" ? On both my Mac and windows with a debug build from 2 days ago, I get the full body of the original message thanslated from HTML to plain text. The only problem I see is that I don't have the '>' at the beginning of each line. That's your problem too or it's worst like the all message body is missing?

Considering that the quoted message is visible, just without the '>', I don't think this is an M10 stopper. Moving to M11. Akkana, can you help JF decide where the right place to plug in the '>' is?

The plaintext output sink doesn't have any code to handle blockquote type=cite (currently, it treats it as a normal blockquote, and just indents it a few spaces). There clearly should be code to handle this, which I should be able to do this fairly early in M11. I suggest you reassign this bug to me when you're done with any M10 portions of it, and I'll make cites work for M11. Or file a new bug if this one has other issues you still want to address.

Reassign to Akkana for M11

Just a answer ducarroz comment on 9/24. I do see the text, however I don't see the ">" before each line like we did in 4.x when we replied to a quoted message in plain text mode. Akkana's (per your comment) I'm not seeing the original message indented. If I read your comment correctly currently it's suppose to indent the original text.

Thanks, Esther. You're right -- replies in plaintext aren't going through the normal output encoder at all, so it makes no difference whether I add the "> " or not, the reply text is being generated somewhere else. (It has other problems, too -- it sometimes inserts <s> strikeover tags on part of the text for no obvious reason.) I'm guessing it's libmime -- reassigning to rhp. Meanwhile, I've filed bug 15293 to me to implement the blockquote type=cite conversion.

Bulk change to assigned. - rhp

changing QA assigned to pmock

Now that HTML - Plain Text conversion works, this should be fixed. - rhp

Linux (1999-11-09-11 M11) Win Nt 4.0 (1999-11-09-11 M11) Mac (1999-11-09-11 M11) POP/IMAP: Reply in plain text doesn't quote the original text problem still exists. Re-open the bug

I'm going to mark this as a duplicate of the most current Plain text compose bug that is currently being worked on (17983). This scenario fits the description of that bug. I will verify it again too. *** This bug has been marked as a duplicate of 17983 ***

Update bug 17983 was verified for M12, this scenario is fixed too.