Hello, your bug is quite a little bit older. I think your described errors may be gone thruy the last versions from icedove. Can you give a feedback of your actual status? This problems are still exist? Or may the bug be closed?
Regards Carsten On Wed, May 28, 2008 at 01:28:00AM +0300, db...@sanevision.com wrote: > Package: iceweasel > Version: 2.0.0.12-1 > Severity: important > > The important bug is given by the subject, but there are several less > troublesome satellite bugs here. Here's the full story. > > I had an email message that contained some "bad" characters. I was > trying to reply to it. The message claimed to be of ISO-8859-1 > encoding, but it contained the UTF-8 char 0xc481 (and many others, > but this was the one causing the main problem). Getting rid of all > occurences of this char let me send the message, but this was an > unacceptably tedious and needless procedure, IMHO. Here's the list > of things I consider bugs: > > 1) Any characters following the 0xc481 (Ä) weren't shown. Not sure > how many weren't and after which char they began showing but quite > a bunch were invisible. I don't mean that they were garbled, that I'd > expect to be the normal behavior; they were plain invisible. > Underlined for being misspelled, though. :-) > > 2) Saving the msg as a draft saved it only until the 0xc481 char > (don't remember inclusive or not). The rest of the text was lost > w/o any warning. > > 3) Sending the reply stalled in the "Sending msg." dialog, until > finally Iceweasel gave up, closed the TCP connection and announced: > > "Sending of message failed. The message could not be sent because > connecting to SMTP server blah.blah.blah failed. The server may be > unavailable or is refusing SMTP connections. Please verify that your > SMTP server setting is correct and try again, or else contact your > network administrator." > > 4) This was, obviously, incorrect and misleading, as the server was > fine, it had been connected just fine, and data had been sent up > to the 0xc481 char (not inclusively), and then there had been some > more bytes sent (which seemed to change a bit from try to try, but > c3 84 2e 0d 0a > was one of the things I observed several times). > > 5) Iceweasel used to have encoding preferences that a normal person > could find---"apply this encoding by default to incoming msgs", "apply > this to outgoing", "override the original", etc., etc. Now I can't > seem to find them. > > If these preferences are now under the huge list that is supposed > to be tweaked with the config editor, well, they can't be found w/o > knowing what to look for. I.e., a "description" or "help" column would > actually make this thing usable. > > If this has to be done with the "Folder Properties"---isn't it crazy, > setting up your preferred encoding separately for each one? I presume > it's not the case. > > 6) View->Character_Encoding->UTF-8 doesn't help on this msg., probably > because it specifies iso-9959-1. Or perhaps because the text is > all within a mime-attachement, again with iso-8859-1 promised. > Anyway, there seems to be lacking a way to turn all the "displayable > text" to a different encoding, regardless of what the message or its > attachements claim. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
