In the original code, a for-else is used with wrong logic, so that if there was
a response ('no blank line between quoted message and response') in the section,
the loop would break and not execute the else[1]. Unfortunately, the code that
checks whether to include the quoted text verbatim is inside the else clause.

Attached patch fixes this and reorganizes the code a bit.

[1] http://docs.python.org/reference/compound_stmts.html#the-for-statement

This patch fixes the symptom, I'll try to find the cause and fix it. This will
probably lead to a lot more noise reaching the tracker if committed as-is.

Antoine Pitrou reported the issue that Roundup borks email responses containing
lines stating with '>' [1][2][3]. I've tracked it down to mailgw.parseContent
wrongly discarding sections bits.

Attached script shows this behavior.

[1] http://bugs.python.org/msg82084
[2] http://bugs.python.org/msg85439
[3] http://bugs.python.org/msg70718

Antoine Pitrou wrote:
The problem I'm having often is that quoted text, or snippets of interpreter
sessions, are lost. Basically, everything which begins with one or more '>'
signs is threatened.