633217 - All e-mails that I forward have unknown characters included for spaces and line breaks.

Status: RESOLVED DUPLICATE of bug 1026989

(Thunderbird :: General, defect)

Description

[mwalsh]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7

I have tried everything that I know of. Attached is an e-mail to be forwarded. (

        Polish  sausage

  Everyone  seems to be in such a hurry to scream 'racism'  these  days.

   A  customer asked, "In what aisle could I find the  Polish  sausage?"

   The  clerk asks, "Are you  Polish?"

   The  guy, clearly offended, says, "Yes I am. But let  me ask you something. If I had asked for  Italian sausage , would you ask me if I was Italian?

   Or  if I had asked for German Bratwurst, would you  ask me if I was German?

   "Or  if I asked for a kosher hot dog would you ask me  if I was  Jewish?

   Or  if I had asked for a Taco, would you ask if I  was  Mexican?

  Or  if I asked for some Irish whiskey, would you ask  if I was  Irish?"

   The  clerk says, "No, I probably  wouldn't."

   The  guy says, "Well then, because I asked for Polish  sausage, why did you ask me if I'm  Polish?"

   The  clerk replied, "Because you're in Home  Depot.."

I am really tired of this and unless resolved, I will discontinue Mozilla products.

Reproducible: Always

Steps to Reproduce:
1.Just forward an e mail. 
2.
3.
Actual Results:  
click forward. 

forwarded e-mail is corrupted.

Expected Results:  
People who receive a forward are looking to shoot me. 

Reproduce the original.

Comment 1

[Daniel Veditz [:dveditz]]

Might be a configuration setting that conflicts with your system? You'll have better luck going through support at http://www.mozillamessaging.com/ -- there's not enough information here to know what's wrong in order to fix it


Where do these emails come from in the first place? I've seen odd characters come into mail when they're originally from word processing documents that use special characters internally to mark soft breaks and the like. If you type these into the compose window yourself then I have no explanation.

What would _really_ help is a copy of the raw mail, including headers. View the source of such a mail (before and after corruption, if you can), select all, copy, then paste into notepad. Save the file and then attach to the bug.

Comment 2

[mwalsh]

See attached. 
forwarded then raw..



-------- Original Message --------
Subject: 	Fwd: FW: Think about it!
Date: 	Thu, 10 Feb 2011 09:46:42 -0600
From: 	mike cavanaugh <[e-mail]>




 

 

 

 



--- On Fri, <j
Date: Friday, February 4, 2011, 2:04 AM

 

Suzanne


To:
Date: Wednesday, February 2, 2011, 7:51 PM






        Polish  sausage

  Everyone  seems to be in such a hurry to scream 'racism'  these  days.

   A  customer asked, "In what aisle could I find the  Polish  sausage?"

   The  clerk asks, "Are you  Polish?"

   The  guy, clearly offended, says, "Yes I am. But let  me ask you something. If I had asked for  Italian sausage , would you ask me if I was Italian?

   Or  if I had asked for German Bratwurst, would you  ask me if I was German?

   "Or  if I asked for a kosher hot dog would you ask me  if I was  Jewish?

   Or  if I had asked for a Taco, would you ask if I  was  Mexican?

  Or  if I asked for some Irish whiskey, would you ask  if I was  Irish?"

   The  clerk says, "No, I probably  wouldn't."

   The  guy says, "Well then, because I asked for Polish  sausage, why did you ask me if I'm  Polish?"

   The  clerk replied, "Because you're in Home  Depot.."

 
Subject: Fwd: FW: Think about it!
From: mike cavanaugh <[e-mail]>
Date: Thu, 10 Feb 2011 09:46:42 -0600



 

 

 

 



--- On Fri, <j
Date: Friday, February 4, 2011, 2:04 AM

 

Suzanne


To:
Date: Wednesday, February 2, 2011, 7:51 PM






        Polish  sausage

  Everyone  seems to be in such a hurry to scream 'racism'  these  days.

   A  customer asked, "In what aisle could I find the  Polish  sausage?"

   The  clerk asks, "Are you  Polish?"

   The  guy, clearly offended, says, "Yes I am. But let  me ask you something. If I had asked for  Italian sausage , would you ask me if I was Italian?

   Or  if I had asked for German Bratwurst, would you  ask me if I was German?

   "Or  if I asked for a kosher hot dog would you ask me  if I was  Jewish?

   Or  if I had asked for a Taco, would you ask if I  was  Mexican?

  Or  if I asked for some Irish whiskey, would you ask  if I was  Irish?"

   The  clerk says, "No, I probably  wouldn't."

   The  guy says, "Well then, because I asked for Polish  sausage, why did you ask me if I'm  Polish?"

   The  clerk replied, "Because you're in Home  Depot.."

Comment 3

[Ludovic Hirlimann [:Usul]]

(In reply to comment #1)

> What would _really_ help is a copy of the raw mail, including headers. View the
> source of such a mail (before and after corruption, if you can), select all,
> copy, then paste into notepad. Save the file and then attach to the bug.

THe best way to do that is to sve the email using File -> save (choose .eml format) and add it here using the add an attachment.

Can you try to rebuild your index on the folders where you have the issue ?

Comment 4

[mwalsh]

Attachment: This is a raw e-mail.

Comment 5

[mwalsh]

Attachment: This is the same e mail after clicking forward.

Comment 6

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #4)
> This is a raw e-mail.

Next is added by AVG. Dup of bug 597821.

> --=======AVGMAIL-165C00F6=======
Content-Type: multipart/alternative; boundary="=======AVGMAIL-0227052B======="
> 
> --=======AVGMAIL-0227052B=======
> Content-Type: text/plain; x-avg=cert; charset=us-ascii
>(snip)

Comment 7

[WADA:World Anti-bad-Duping Agency]

Closing as dup of bug 597821. If not dup, re-open please.

Comment 9

[WADA:World Anti-bad-Duping Agency]

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.

Comment 10

[WADA:World Anti-bad-Duping Agency]

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?