User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2007122205 Minefield/3.0b3pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2007122204 Thunderbird/3.0a1pre ID:2007122204 Once you've sent or saved a message and want to re-edit it (Ctrl-E) the signature gets broken. Originally looking like: ++++++++++++++++++++++ text body -- sig line 1 sig line 2 ++++++++++++++++++++++ after Ctrl-E (Edit message as new) it reads: ++++++++++++++++++++++ text body -- sig line 1 sig line 2 -- sig line 1 sig line 2 ++++++++++++++++++++++ Reproducible: Always Steps to Reproduce: 1. Have a mail / news account with signature 2. Compose a mail / posting and send or save and close 3. Re-edit (Ctrl-E) Actual Results: The formerly properly placed signature is now corrupted, first line being placed in the line behind the signature delimiter. If any a second signature is displayed, behind a new signature delimiter. Expected Results: Original signature stays at the right place (new line after signature delimiter). This is also reported for current Seamonkey trunk on Linux.

(In reply to comment #0) > This is also reported for current Seamonkey trunk on Linux. Yes, that's me. I have now checked the archive of my private builds and can tell, that the last good build ist 200709291908 CEST and the first bad one is 200709301247 CEST. But someone has to convert the timezone. *g*

Well, I can confirm this issue with the current SeaMonkey-Nightly: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9b3pre) Gecko/2007122203 Mnenhy/0.7.5.20005 SeaMonkey/2.0a1pre HaFi has cut down the Regression-Window with his Linux-Builds to: 2007-09-29 10:09:00 - 2007-09-30 03:47:00 PST, so the Bonsai-Query was: http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2007-09-29+10%3A00%3A00&maxdate=2007-09-30+03%3A47%3A00&cvsroot=%2Fcvsroot After a quick look at the Checkins, I suspect Reeds checkin for Bug 155622. Additional, I do not use format=flowed, have disabled this with the usual Settings in user.js

And a quick look into Bug 155622 shows, that this Report looks like an Duplicate to the reported Regression with pending patch. :( Sorry for my too fast confirmation. I will mark this as an Duplicate to Bug 155622, sure it was only a Dupe for the allready reported Regression, not the complete Bug.