User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 In Thunderbird when receiving a mail message that has characters in ISO-8859-7 (Greek) it displays OK but when forwarding this message (inline mode) all Greek characters turn into garbage (Chinese...) and no matter what encoding I try they do not reappear correctly. Only the Subject field though displays OK. Reproducible: Always Actual Results: Sent: Friday, December 10, 2010 9:51 AM Subject: TO NEO MNHMONIO ============================================================================================================== Ìå ôçí åðéöýëáîç ðáíôüò íïìßìïõ äéêáéþìáôüò ìáò. ÊÜèå ìÞíõìá çëåêôñïíéêïý ôá÷õäñïìåßïõ áðü ôçí ÔñÜðåæá ôçò ÅëëÜäïò (ÔôÅ) áðïóôÝëëåôáé êáëüðéóôá áëëÜ äåí ôç äåóìåýåé ïýôå åñìçíåýåôáé ùò íá óõíéóôïýóå Þ åðçñÝáæå óõìâáôéêÞ Þ Üëëç äÝóìåõóç ôçò ÔôÅ. Ôï ìÞíõìá çëåêôñïíéêïý ôá÷õäñïìåßïõ ðñïïñßæåôáé ðñïò áðïêëåéóôéêÞ ÷ñÞóç ôïõ ðñïóþðïõ, ôïõ ïðïßïõ ç äéåýèõíóç áíáãñÜöåôáé óôçí åðéêåöáëßäá ôïõ ìçíýìáôïò. Ï áðïóôïëÝáò êáé ç ÔôÅ äåí áíáëáìâÜíïõí êáììßá åõèýíç ãéá áíáêñéâåéåò, ðáñáâßáóç ôçò áêåñáéüôçôáò, áðþëåéá Þ êáèõóôåñçìÝíç äéáâßâáóç ôïõ ìçíýìáôïò, ãéá áóôï÷ßá, äéáêïðÞ Þ õðïâÜèìéóç ôçò õðçñåóßáò Þ ôïõ ìçíýìáôïò êáèþò êáé ãéá êÜèå åî áõôïý ôïõ ëüãïõ áðþëåéá Þ æçìßá êáèüëç ôçí õðü ôïõ íüìïõ ðñïâëåðüìåíç Ýêôáóç. ÅÜí ëÜâáôå êáôÜ ëÜèïò ôï ðáñüí ìÞíõìá çëåêôñïíéêïý ôá÷õäñïìåßïõ, ðáñáêáëïýìå íá åéäïðïéÞóåôå áìÝóùò ìÝóù çëåêôñïíéêïý ôá÷õäñïìåßïõ ôïí áðïóôïëÝá êáé íá äéáãñÜøåôå ôï ìÞíõìá. ÏðïéáäÞðïôå áíáêïßíùóç, äéÜäïóç Þ ÷ñÞóç ìÝñïõò Þ ïëüêëçñïõ ôïõ ìçíýìáôïò ÷ùñßò Üäåéá áðáãïñåýåôáé áõóôçñÜ êáé ìðïñåß íá åðéöÝñåé ðïéíéêÞ êáé áóôéêÞ åõèýíç. Any e-mail message from the Bank of Greece (BoG) is sent in good faith but shall neither be binding nor construed as constituting or affecting a contractual arrangement or other commitment by the BoG. The e-mail is intended for the exclusive use of the person whose e-mail address appears in caption as recipient. The sender and the BoG decline liability for inaccuracy, breach of integrity, loss or delayed delivery of the message, for any failure in, interruption to or degradation of either the service or the message, as well as for any loss or damage sustained thereof to the fullest extent provided by law. If you have received this e-mail in error, please notify the sender immediately via e-mail and delete it at once. Any unauthorized disclosure, dissemination or use, either in whole or in part is strictly prohibited and may give rise to both criminal and civil liability. All rights reserved. ============================================================================================================== Expected Results: ============================================================================================================== Με την επιφύλαξη παντός νομίμου δικαιώματός μας. Κάθε μήνυμα ηλεκτρονικού ταχυδρομείου από την Τράπεζα της Ελλάδος (ΤτΕ) αποστέλλεται καλόπιστα αλλά δεν τη δεσμεύει ούτε ερμηνεύεται ως να συνιστούσε ή επηρέαζε συμβατική ή άλλη δέσμευση της ΤτΕ. Το μήνυμα ηλεκτρονικού ταχυδρομείου προορίζεται προς αποκλειστική χρήση του προσώπου, του οποίου η διεύθυνση αναγράφεται στην επικεφαλίδα του μηνύματος. Ο αποστολέας και η ΤτΕ δεν αναλαμβάνουν καμμία ευθύνη για ανακριβειες, παραβίαση της ακεραιότητας, απώλεια ή καθυστερημένη διαβίβαση του μηνύματος, για αστοχία, διακοπή ή υποβάθμιση της υπηρεσίας ή του μηνύματος καθώς και για κάθε εξ αυτού του λόγου απώλεια ή ζημία καθόλη την υπό του νόμου προβλεπόμενη έκταση. Εάν λάβατε κατά λάθος το παρόν μήνυμα ηλεκτρονικού ταχυδρομείου, παρακαλούμε να ειδοποιήσετε αμέσως μέσω ηλεκτρονικού ταχυδρομείου τον αποστολέα και να διαγράψετε το μήνυμα. Οποιαδήποτε ανακοίνωση, διάδοση ή χρήση μέρους ή ολόκληρου του μηνύματος χωρίς άδεια απαγορεύεται αυστηρά και μπορεί να επιφέρει ποινική και αστική ευθύνη. Any e-mail message from the Bank of Greece (BoG) is sent in good faith but shall neither be binding nor construed as constituting or affecting a contractual arrangement or other commitment by the BoG. The e-mail is intended for the exclusive use of the person whose e-mail address appears in caption as recipient. The sender and the BoG decline liability for inaccuracy, breach of integrity, loss or delayed delivery of the message, for any failure in, interruption to or degradation of either the service or the message, as well as for any loss or damage sustained thereof to the fullest extent provided by law. If you have received this e-mail in error, please notify the sender immediately via e-mail and delete it at once. Any unauthorized disclosure, dissemination or use, either in whole or in part is strictly prohibited and may give rise to both criminal and civil liability. All rights reserved. ==============================================================================================================

Dup of bug 597821? See also bug 604628.

Yes similar problem... There is no problem though when I use Outlook Express for the same messages. You should probably see how Outlook overcomes this problem and apply the same solution in TB. Best Regards Yiannis Loukopoulos

I may have the same problem. I receive a normal text ant in the sent email this appears: Anyone 

and everyone should thoroughly appreciate and 

absolutely enjoy this...

A 

Celtic (pronounced Keltic) Amazing Grace - 

from the Andre 

Rieu orchestra
 (about 

three minutes in length - and you will wish it 

were way longer!)

it begins with the 

leading notes being played on a pennywhistle (an 

instrument which comes to us 

from Ireland)
 

...then, the lead is taken over by a single 

bagpiper...
 

...thereafter followed by an entire array of 

bagpipers!

I'm hoping you have external 

speakers and that you'll really crank them up 

for this be blessed as you watch and 

listen http://www.youtube.com/watch?v=TY8J35OXVxg&feature=related

(In reply to comment #2) > Yes similar problem... (In reply to comment #3) > I may have the same problem. Same as bug 597821 or not is very easily known, as phenomenon of bug 597821 is apparent and why bug 597821 happens is simple. If mail structure of bug 597821 comment #10, a) each part is properly shown using correct charset, b) View/Character Encoding shows charset of text part in second multipart/alternative instead of charset of text part in first multipart/alternative. Upon forward, used text(mail body) is data in first multipart/alternative, but used charset at composition window becomes charset shown at View/Character Encoding(charset of text in second multipart/alternative). In that bug, not-so-well-formed second multipart/alternative was inserted by AVG and such behavior is not so good, but it's Tb's bug. Garbled display depends on charset specified for text part in each multipart/alternative part. So, garbled text data itself is useless. Check of mail data via View/Message Source or content of .eml file saved by "Save As" is sufficient. Same mail structure generated by AVG? If similar mail structure to bug 597821 comment #10, who generated such mail structure?

When bug 597821 is fixed, if your problem is not gone please reopen this bug Question for Yiannis? > Same mail structure generated by AVG?

Root cause of "charset is pcked up from last attachment" was resolved by bug 1026989 at last. Some valuable bug reports from users were hidden/lost/ignored by "duping to bug 716983, then duping bug 716983 to other bug". Unfortunately, or fotunately, only "garbled display in Forward Inline case" was resolved by unknown bug while the other bug was being processed, so nothing was resolved by the other bug. Duping this bug to bug 1026989, for ease of tracking, search, understanding current status of problem.

FYI. Patch of bug 1026989, one liner patch, was proposed in the other bug to which bug 716983(and bug 701818 too) had been duped to. The patch was dig out from the other bug by bug 1026989, and long lived "charset is picked up from last attachment" issue has been resolved by bug 1026989. Why such "digging out hidden important patch from the other bug" should be needed in B.M.O?