727324 - Forward/Reply/Edit As New/Edit draft message fails to show image, save, send, when image is embed in html mail, if IMAP Mbox name contains "[", "]", "^", and if "#", "?" is also used in Mbox name

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking: IMAP, defect)

Description

[ubuntumuntu]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.46 Safari/535.11

Steps to reproduce:

Forward or Reply to message; possibly containing "inline attachments"

Platform: OS/X 10.6.8
TB: 10.0.1


Actual results:

When I try saving (to drafts), forwarding or reply to a message that contains a logo in the signature (including my own) - imbedded by reference & not as a attached image, it fails with a message: "Sending of message failed. Attachment error." 

When I remove all embedded images is seems to work most of the time.
In a few messages there are actual attached documents (txt, pdf, png, etc) and I can keep those attached fine (but not the signature images)

I've tried this with multiple accounts - gmail & in-house IMAP server.
Those servers own clients work fine, but not TB 


Expected results:

Should be sending and/or saving messages

Comment 2

[Hashem Masoud]

(In reply to ubuntumuntu from comment #0)
See bug 696580 for more info. Try starting Thunderbird in safe-mode (add-ons disabled) and check.

Comment 3

[ubuntumuntu]

Issue is still present when restarting in Safe Mode (extensions disabled).

The bug referenced seems somewhat similar, but I don't think it's exactly the same - I can compose a new message with my logo attached by reference (as opposed to as an attachment), and add attachments if I like (txt's, pdf's, etc).
The newly-composed message saves to drafts fine & sends OK. 

The issue presents when forwarding or replying to some messages that contain certain embedded objects - not sure if it's just images.

This is not a new installation - I've had this app on this OS for a while now (year to 2), and this is only a recent development.
I've tried removing & reloading all passwords for all accounts, but the issue remains.

Comment 4

[WADA:World Anti-bad-Duping Agency]

Can you reproduce your problem with local mail folder? (POP3 or Local Folders)
Can you attach your signature file to this bug?
Remove/replace personal information from file. Please don't paste long data to bug.

Comment 5

[ubuntumuntu]

Seems OK from a POP account.

Unfortunately the sig is all personal info - I use an HTML file as my sig with an <img src="http://domain.com/image.png" /> for my logo

Comment 6

[WADA:World Anti-bad-Duping Agency]

Checked with file url.
> <img src="file:///C:/PICTURE/foo.gif">

In draft mail, image in signature is embed in mail.
>  <img src="cid:[e-mail]" alt="sig" title="Signature">
> --------------060508010309010800040401
> Content-Type: image/gif; name="foo.gif"
> Content-ID: <[e-mail]>

In Edit window of this draft mail, if local mail folder, image's property is following, and is shown in inline, and draft is saved normally.
> mailbox:///C:/wada/@@@/Mail0/Drafts?number=769&part=1.2&filename=foo.gif

If IMAP, image's property is following, and the image is broken.
> imap://userName@hostname:993/fetch%3EUID%3E%5E%5BGmail%5D%5EDrafts%3E190?part=1.2&filename=foo.gif
>(unescape string)
> imap://userName@hostname:993/fetch>UID>^[Gmail]^Drafts>190?part=1.2&filename=foo.gif
And following error occurs upon save.
> Unable to save your message as draft.
> There was an error attaching fetch>UID>^[Gmail]^Drafts>190.
> Please check if you have access to the file.
This error was observed in both Tb 10.0.1 and Tb trunk(Tb13.0a1,2012/02/10 build)
Confirming.

Perhaps mismatch between URL creation for image and URL interpreting/processing.
IIRC, this issue is already reported.

Comment 7

[ubuntumuntu]

Thanks for the follow-up, WADA.
That seems fairly consistent with what I'm experiencing.

Based on your notes the issue seems more widespread than just my Mac instance? (I have a Linux desktop too, but haven't run TB on it for a while)

Just a note: the issue's present not just when my own logo/signature is present in the IMAP message composition, but also when another party/sender's signature logo is present. 
These images will show up fine in the composition (below/above the response), but will cause the message to fail saving on the IMAP server.

Comment 8

[WADA:World Anti-bad-Duping Agency]

Not signature only issue. Problem occurs on any <img> with cid: url in html, with image data embed in multipart/related with Content-ID:, if IMAP folder.

Comment 9

[WADA:World Anti-bad-Duping Agency]

Problem is observed in Tb 9.0.1 on Win.
When did problem start to occur in your environment?

Comment 10

[ubuntumuntu]

This problem has been a real issue since v.10 on Mac.
On an earlier version on this macine (could be between 9 & 10) the *was* another issue that was a real annoyance, but I can't recall what it was right now.

Comment 11

[WADA:World Anti-bad-Duping Agency]

Folder name seems relevant. 
Following is image's property in composition window.
(1) Edit draft
(1-A) Drafts : no problem occurs
> imap://[e-mail]:993/fetch%3EUID%3E/Drafts%3E10?part=1.2
(1-B) [Gmail]/Drafts : problem occurs
> imap://[e-mail]:993/fetch%3EUID%3E%5E%5BGmail%5D%5EDrafts%3E207?part=1.2
(2) Edit As New, Forward
(2-A) Inbox : no problem occurs
> imap://[e-mail]:993/fetch%3EUID%3E/INBOX%3E12121?part=1.2
(2-B) Inbox/[Inbox99] : problem occurs
> imap://[e-mail]:993/fetch%3EUID%3E%5EINBOX%5E%5E%255BInbox99%255D%3E5?part=1.2

In (2-B), escaping of "%" of "%5B" by "%25" is also seen.
Above is observed in Tb 7.0a2(2011/08/16 build, final Tb 7.0a2 build) too, so, no-so-new problem.

Comment 12

[WADA:World Anti-bad-Duping Agency]

(2-C) Inbox/Inbox0 : no problem occurs.
> imap://[e-mail]:993/fetch%3EUID%3E/INBOX/Inbox0%3E1?part=1.2

Difference between (1-B) and (2-B) is perhaps due to that "[Gmail]" is same as folder of \Noselect(can't hold mail, can hold sunfolder only.)

Comment 13

[WADA:World Anti-bad-Duping Agency]

(3) Tb version 3 alpha 1 (20060302), first trunk Tb 3.0a1 build.
(3-1) Inbox/[Inbox99], Forward,Edit As New : problem occurs
> imap://[e-mail]:993/fetch%3EUID%3E%5EINBOX%5E%5E%5BInbox99%5D%3E5?part=1.2
(3-2) [Gmail]/Drafts, Edit draft : problem occurs.
> imap://[e-mail]:993/fetch%3EUID%3E%5E%255BGmail%255D%5EDrafts%3E207?part=1.2

Incorrect escaping and/or over escaping looks to exist since initial of Tb 3.0.

Comment 15

[WADA:World Anti-bad-Duping Agency]

Problem observed with "[", "]", "#", "?". 
(4) "[", "]", "#" in Mbox name
(4-1) mail in [ABC]/#P1/P1, Edit As New
      "/#P1/P1" is omitted in URL for image part.
> imap://[e-mail]:993/fetch%3EUID%3E/%5BABC%5D%3E2?part=1.2&filename=ButaJ.gif
(4-2) mail in [ABC]/X#P2/P2, Edit As New
      Double "5E"("^") is seen. Escape of "%" by "%25" is seen.
      Further, creation of X.msf was observed(file accessed after cut at "#"). 
> imap://[e-mail]:993/fetch%3EUID%3E%5E%255BABC%255D%5E%5EX%23P2%5E%5EP2%3E3?part=1.2&filename=ButaJ.gif
(5) "[", "]", "?" in Mbox name
Same phenomenon as "#" case was observed.

- "/" = 0x2F is path delimiter in URL, so Tb looks to replace "/" in Tb's request
  by "^", if Tb considers "it's not URL path delimiter".
- "^" = 0x5E, "\" = 0x5C, "[" = 0x5B, "]" = 0x5D are continuous 0x5. chars.
- "#" = 0x23, "?" = 0x26 is hash, search delimiter in URL.
  String in URL after "#" and/or "?" may be omitted from IMAP Mbox name.
- "%" = 0x25 is used for escape, so "%" is changed to "%25" by escaping, and
  "%25" is changed to "%" by unescaping. So, Mbox with "%25" in name is dangerous.
- ">" = 0x3E is used as delimiter in Tb's request, so Tb is currently impossible
  to access Mbox with ">" in name(known bug).
- When following special chars is used in Gmail IMAP Mbox name, Tb hashes file name(when Period, ending period only). This hashed name may produce error such as "folder file not found" in special situation, and it may cause wrong/over escaping.
>   --------------------- ----- ----  ------------------------------   ---------------
>   Character name        glyph hex   Gmail Label                      .msf file in Tb
>   --------------------- ----- ----  ------------------------------   ---------------
>   Double-Quote            "   0x22          Special/Double-Quote/"   6f9712b5.msf
>   Pound-Sign              #   0x23            Special/Pound-Sign/#   d35d4f8e.msf
>   Asterisk                *   0x2A              Special/Asterisk/*   8dc8f97d.msf
>   Period                  .   0x2E                Special/Period/.   1ce1ece1.msf
>   Colon                   :   0x3A                 Special/Colon/:   ca2cc70d.msf
>   Less-than               <   0x3C             Special/Less-than/<   91b940bf.msf
>   Greater-than            >   0x3E          Special/Greater-than/>   5945ba71.msf
>   Question-Mark           ?   0x3F         Special/Question-Mark/?   bd0bf74a.msf
>   Back-Slash              \   0x5C            Special/Back-Slash/\   0a80dbdf.msf
>   Virtical-Bar            |   0x7C          Special/Virtical-Bar/|   834876ff.msf
>   --------------------- ----- ----  ------------------------------   ---------------

What special character is used in your case?

Comment 16

[WADA:World Anti-bad-Duping Agency]

Because I tested "#" case, and because bug 720911 can occur if Mbox name has # in folder name, I deleted all files/directories under imap.gmail.com directory, imap.gmail.com.msf, panacea.dat in profile and forced re-sych, to clean up garbage by that bug. All folders is offline-use=off.
After it, I couldn't see problem in Tb 10.0.1 on Inbox/[Inbox99] nor [Gmail]/Drafts any more. I couldn't see problem with [ABC]/[DEF], [ABC]/XX, [ABC]/YY etc. any more.
I could observe problem of (4)/(5) only on [ABC]/#..., [ABC]/X#...., [ABC]/X which is relevant to created X.msf by [ABC]/X#, [ABC]/?..., [ABC]/Y?..., [ABC]/Y which is relevant to created Y.msf by [ABC]/Y#.

Before clean up of files/directories, .msf/.sbd for Inbox was Inbox-M.msf / Inbox-M.sbd(suffixed) and .msf/.sbd for [Gmail] was [Gmail]-N.msf / [Gmail]-N.sbd(suffixed) in my environment due to bug 520437.
As seen in X.msf file creation when [ABC]/X#P1/P1 of case (4-2), file access from URL(/[Gmail]/Drafts => [Gmail].sbd\Drafts.msf) may occur. If "folder not found" occurs in such "access from URL", it may cause double escaping and/or over escaping.

What .msf file/.sbd directory is used for mail folder in which problem occurred?
Is special character used in mail folder name?

Comment 17

[marc.massart]

In my case it is #.

Comment 18

[WADA:World Anti-bad-Duping Agency]

Other case was found.

(6) Check result with "^P^./&P,Q&"(no quote) using Yahoo! IMAP.
    Because Gmail IMAP doesn't allow Mbox name with "^", Yahoo! IMAP is used.
(6-1) image URL by Edit As New 
> imap://[e-mail]:993/fetch%3EUID%3E%5E%255EP%255E.%5E%5E%26-P%2CQ%26-%3E126?part=1.2&filename=ButaJ.gif
Folder Location.
> imap://[e-mail]/%5EP%5E.
> imap://[e-mail]/%5EP%5E./%26-P%2CQ%26-
Created .msf/.sbd by Tb on Win-XP.
> ^P^38ea2173.msf
> ^P^38ea2173.sbd
> ^P^38ea2173.sbd\&-P,Q&-.msf    <= 0 byte file, not used
> ^P^38ea2173.sbd\&-P,Q&--1.msf  <= actually used .msf file, suffixed
(a) Because of "ending period" in "^P^.", filename is hashed.
(b) Because of "modified utf-7" is used, "&" is sent as "&-", and Tb uses
    the "&-" for file name.
(c) Because I renamed parent's folder name sometimes, suffixed name of
    "&-P,Q&-" + "-1" was used for .msf/.sbd of "&P,Q&".
    This is phenomenon of bug 520437.
    Rename of parent folder => Unsubscribe/re-subscribe occurs on "^P^./&P,Q&"
    => Suffix is added to .msf name.

I couln't observe problem with newly created "^PQ^./&P,Q&"(no quote).
  ^PQ^1f9a197e.msf
  ^PQ^1f9a197e.sbd
  ^PQ^1f9a197e.sbd\&-P,Q&-.msf <= No suffix is added
So, suffixed .msf name is aparently a causes of problem in this case.
I'm not sure "^" in Mbox name or hashed file name is mandatory condition. Because Tb doesn't correctly delete file upon rename sometimes if hashed name is used, it's convenient to generate garbage file :-)

Comment 19

[WADA:World Anti-bad-Duping Agency]

Hashed name was irrelevant to case (6). Only special "^"(0x5E, which is used by Tb for escape of "/" in Mbox name string) and suffixed file name was relevant to case (6).

Yahoo! IMAP allows "^" in Mbox name and supports case sensitive Mbox name, and MS Win uses case insensitive file system with keeping case sensitive file name.
Tb adds suffix to .msf file name if .msf file name is already used in such case.
So any combination can occur.
  Mbox name   File name in Tb on Win
    ABC       xxx.msf    xxx.msf    xxx-1.msf  xxx-1.msf  xxx-2.msf  xxx-2.msf
    Abc       xxx-1.msf  xxx-2.msf  xxx.msf    xxx-2.msf  xxx.msf    xxx-1.msf
    abc       xxx-2.msf  xxx-1.msf  xxx-2.msf  xxx.msf    xxx-1.msf  xxx.msf
  Where xxx is any of ABC, Abc, abc.
  Which is initially used as xxx depends on order of creation at Tb.
  When parent folder is renamed, Mbox name and file name is re-synch'ed.
  Which of ABC, Abc, abc is used for xxx part of file name depends on
  order of Mbox in LIST response or LSUB response.
In any case, if these folders are subfolder of folder named "^", Location of Folder Properties is always as folllows.
  Mbox name   Location of Folder Properties
    ^/ABC     imap://userName@hostname/%5E/ABC 
    ^/Abc     imap://userName@hostname/%5E/Abc
    ^/abc     imap://userName@hostname/%5E/abc
Corresponding .msf is one of xxx.msf, xxx-1.msf, xxx-2.msf where xxx is one of ABC, Abc, abc. Because of order of ascii binary, file for "Abc" is usually ...\^\xxx-1.msf.
Assume simplest next case.
  Mbox name   Used .msf file   Location of Folder Properties
    ^/ABC     ...\^\ABC.msf    imap://userName@hostname/%5E/ABC
    ^/Abc     ...\^\Abc-1.msf  imap://userName@hostname/%5E/Abc
    ^/abc     ...\^\abc-2.msf  imap://userName@hostname/%5E/abc
If Mbox of "^/Abc" is accessed via this URL without checking of actually associated .msf file, ...\^\Abc.msf is searched, and ...\^\ABC.msf is returned from MS Win, because MS Win's file system is case insensitive.

(7) "^/Abc" when "^/ABC" and "^/abc" also exists.
(7-1) "^/Abc" : Edit As New, Forward. image's URL.
> imap://[e-mail]:993/fetch%3EUID%3E%5E%5E%5E%5EABC%3E142?part=1.2&filename=ButaJ.gif
Multiple escaping of "/" by "^" is seen.
It looks next;
  /^  + /ABC => ^^ + ^ABC => %5E%5E + %5EABC
  => %5E%5E/%5EABC => %5E%5E^%5EABC => %5E%5E%5E%5EABC
Location of this folder is "/%5E/Abc". "ABC" in the image's URL is perhaps file name part of ...\^\ABC.msf.

Comment 20

[WADA:World Anti-bad-Duping Agency]

I could reproduce problem with Inbox/[Inbox99] and [Gmail]/Drafts which I saw before clean up of files/directories.

(1) Create IMAP folder "X" for test, creae subfolder X/X and delete X/X to create ...\X.sbd directory.

(2) X/A/[B], with suffix of A-1.msf for "A"
    Manually create A.msf in ...\X.sbd to emulate suffix by bug 520437.
    Create folder of "X/A" by Tb => ...\X.sbd.\A-1.msf is used for "X/A".
    Create "X/A/[B]" by Tb => ...\X.sbd.\A-1.sbd\[B].msf is used for "X/A/[B]".
    Location = imap://[e-mail]/X/A/%5BB%5D
    Copy mail contains embed image in HTML.
    Image's URL by Eit As New/Forward.
> imap://[e-mail]:993/fetch%3EUID%3E%5EX%5E%5EA%5E%5E%255BB%255D%3E1?part=1.2&filename=ButaJ.gif

...\X.sbd\A.sbd, ...\X.sbd\A.sbd\[B].msf of size=0, were also created. 

(3) X/[A]/B, with suffix of [A]-1.msf for "[A]"
    Manually create [A].msf in ...\X.sbd to emulate suffix by bug 520437.
    Create folder of "X/[A]" by Tb => ...\X.sbd.\[A]-1.msf is used for "X/[A]".
    Create "X/[A]/B" by Tb => ...\X.sbd.\[A]-1.sbd\B.msf is used for "X/[A]/B".
    Location = imap://[e-mail]/X/%5BA%5D/B
    Copy mail contains embed image in HTML.
    Image's URL by Eit As New/Forward.
> imap://[e-mail]:993/fetch%3EUID%3E%5EX%5E%5E%255BA%255D%5E%5EB%3E1?part=1.2&filename=ButaJ.gif

...\X.sbd\[A].sbd, ...\X.sbd\[A].sbd\B.msf of size=0, were also created.

It seems several kinds of issues involved.
(a) Cut of URL at "#" and/or "?". ".msf file not found" due to it.
    Incorrect addition of "/" to URL due ".msf file not found".
(b) Problem in "[" and/or "]" processing when suffix is added to .msf file.
    It seems to produce "/" before "[" and/or after "]".
(c) Problem in "^" processing when suffix is added to .msf file.
    It seems to produce "/" before "^".
(d) Escaping of "/" which is generated due to (a), (b), (c), in URL by "^".

Comment 21

[WADA:World Anti-bad-Duping Agency]

Quick Summary of currently known cases by quick tests.

Problem was observed in following cases with Tb 10.0.1 on Win-XP.

(Case-A) "[" or "]" or "^" in folder name, .msf file name is suffixed 
> ------ Parent folder -----------------   ------ Child folder ------------------
> "[" or "]" or "^"    File name is        "[" or "]" or "^"    File name is
>   in name              suffixed            in name             suffixed
> -----------------    -----------------   -----------------    -----------------
>   Yes                  Yes                 Yes/No               Yes/No
>   Yes                  No                  Yes/No               Yes
>   No                   Yes                 Yes                  Yes/No
>   No                   No                  Yes                  Yes
> -----------------    -----------------   -----------------    -----------------

(Case-B) "[" or "]" in parent folder name, ."#" or "?" in child folder name
> ------ Parent folder -----------------   ------ Child folder ------------------
> "[" or "]"           File name is        "#" or "?"       
>   in name              suffixed            in name        
> -----------------    -----------------   -----------------
>   Yes                  Yes/No              Yes            
> -----------------    -----------------   -----------------

It looks:
- Suffixed .msf file causes ".msf file not found" condition.
- "cut of URL at #/?" occurs by #/? then produces ".msf file not found" condition.
- The ".msf file not found" condition causes bad "/" insertion in URL format
  folder path, and escaping of the inserted "/" by "^" in the URL occurs.

Comment 22

[WADA:World Anti-bad-Duping Agency]

(In addition to comment #21)
- Bad insertion of "/" followed by "replacing by ^" occurs only when folder name has special character of "]", "[", "^".

Comment 23

[WADA:World Anti-bad-Duping Agency]

Condition was simple.
(i)  Mbox name contains "[" or "]" or "^",
     and suffix is used for .msf file name at any hierarchy of folder structure.
(ii) Mbox name contains "[" or "]" or "^",
     and "#" or "?" is used after the "[" or "]" or "^".
So, problem can be observed by (i) Mbox = [ with [-1.msf (ii) Mbox = [#  

(In reply to marc.massart from comment #17)
> In my case it is #.

I couldn't observe problem with "#" only. In my environment, "[" or "]" or "^" was needed in addition to "#" or "?" to see problem.
What other special character is used at where in Mbox name in your case? "." is mbox hiearchy delimiter? namespace="Inbox." case? Or "#" in namespace?

Comment 24

[marc.massart]

Believe it or not, but since I upgraded to 10.0.02 the problem has gone. I tried all kind of things and I could not reproduce. Sorry.

Comment 25

[WADA:World Anti-bad-Duping Agency]

(In reply to marc.massart from comment #24)
> Believe it or not, but since I upgraded to 10.0.02 the problem has gone.

As I wrote in comment #16, I also couldn't see problem of comment #11 which actually occurred in my environment after some actions on my Tb.
Because problem is relevant to "suffix in .msf file name"(Inbox-3.msf is used instead of normal Inbox.msf), if resynchronization of mail folder name occurs and normal/non-suffixed .msf file is used, problems related to "suffixed .msf file name" disappears. Because Mbox named xxx-N doesn't exist at server, xxx-N.msf is deleted by resynchronization, and normal xxx.msf is used.
So, "this bug's problem disappeared after some events" is very normal phenomenon if "suffixed .msf file name" was relevant to problem.

Comment 26

[WADA:World Anti-bad-Duping Agency]

[e-mail](bug opener), is "special character in Mbox name" relevant to your problem? 
If Yes, which character? Is "suffixed .msf file name" used in your environment?
If No & No, did your problem occur with what mail folder name? Is "folder delimiter", namespace, "IMAP Server Directory:" relevant in your case?

Comment 27

[WADA:World Anti-bad-Duping Agency]

FYI.
How to show and send broken image in Forward window due to this bug(written in bug 547956 comment #10).
(1) At Forward widow, open image property by double click of the broken image. 
(2) Correct corrupted path. (mail in Mbox named /XX/[# example)
> imap://userName@hostname:993/fetch%3EUID%3E%5EXX%5E%5E%255B%23%3E1?part=1.2&filename=foo.jpg
=> Change to following (> can be used for ease of viewing)
> imap://userName@hostname:993/fetch>UID>/XX/%5B%23>1?part=1.2&filename=foo.jpg
=> ">" is escaped by Tb
> imap://userName@hostname:993/fetch%3EUID%3E/XX/%5B%23%3E1?part=1.2&filename=foo.jpg

Problem with ">" in folder name is perhaps caused by this automatic over escaping of ">" as parameter separater.
  Mbox name = /A/B/X>Y  UID = 12345
  final request, folder name is already escaped
    fetch>UID>/A/B/X%3EY>12345
  over escape of ">" in request
    fetch%3EUID%3E/A/B/X%3EY%3E12345
  over unescape upon process of this request due to previous over escape
    fetch>UID>/A/B/X>Y>12345   
    ">" after X is delimiter so eaten, UID=Y, 12345=excess parameter value

Comment 28

[ubuntumuntu]

@WADA - sorry , but I'm not sure I understand the question.
I've (automatically) upgraded to v.10.0.2, & the problem persists, but not universal anymore.

One of the mailboxes where the problem is still present, is named "IMAP - local", for my local, in-house IMAP server.
In another, the only non-alphanumerical character is a space

In some cases (such as some Gmail accounts) the problem has seemed to be resolved.

This client-setup has not changed in over a year (maybe 2), with the exception that I've updated authentication passwords as the need arises. If it was making use of .msf now, it would've done so before.

I'll add more cases as I find them throughout the day.

Comment 29

[WADA:World Anti-bad-Duping Agency]

(In reply to ubuntumuntu from comment #28)
> One of the mailboxes where the problem is still present, is named "IMAP -
> local", for my local, in-house IMAP server.
> In another, the only non-alphanumerical character is a space

Mbox = "/XX/WithSuffix/A - B"(no quote) 
Location: of Folder Properties.
> imap://[e-mail]/XX/WithSuffix/A%20-%20B
.msf file for "WithSuffix" = WithSuffix-1.msf.
So, file path=...\XX.sbd\\WithSuffix-1.sbd\A - B.msf.
Image's URL in Forward.
> imap://[e-mail]:993/fetch%3EUID%3E%5EXX%5E%5EWithSuffix%5E%5EA%2520-%2520B%3E1?part=1.2&filename=ButaJ.gif

Additional observation.
- ...\XX\WithSuffix-1.msf, ...\XX\WithSuffix-1.sbd exists and is used.
- ...\XX\WithSuffix.msf,   ...\XX\WithSuffix.sbd   doesn't exist.
- When Forward was executed on above mail in ...\XX\WithSuffix-1.sbd\A - B.msf,
  ...\XX\WithSuffix.sbd and ...\XX\WithSuffix.sbd\A - B.msf(size=0) was created. 
- ...\XX\WithSuffix.sbd\A - B.msf was not deletable until termination of Tb.

I couldn't see problem with folder name="A - B" when parent folder's .msf file name doesn't have suffix in file name and there is no special chars such as "[".
Check full file path of .msf file for the "IMAP - local" folder, please.
For "suffix in .msf file name", see Bug 520437.

Comment 30

[ubuntumuntu]

I've found a "ghetto" quick-fix for some issues:

In an earlier version (think it was around v.9, or thereabouts), when I attached my HTML signature that references an image via a URL (i.e. not attached), it would insert the sig, but the image would not show (before this is wall all a-OK). 
If I sent it, it would get through OK to the recipient, but would not show correctly in the composition. I would have to double-click the image to ensure that the reference was OK & click OK & it would then show correctly.

This was the case on both (Ubuntu) Linux (32 & 64 bit) & OS/X (10.6 atm).

Now what I'm seeing, in conjunction with this bug, is that I can either delete the images referenced elsewhere in the message-thread so that the message can save/send, or if I double-click the image to inspect it, I can see that the messages are now attached (even my own logo that's been replied back to me, which should be referenced & not attached), and if I disable the "attach this image to this message" checkbox, the image (in some cases) then still shows correctly & can be sent/saved.

If I were to guess, I would think that maybe this attachement reference could have something to do with it?

Comment 31

[Bryce]

Any date for a quick patch ? Or we must change of mailing software for a long temporary time ? (Gmail webmail for exemple)

Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2

Comment 32

[ubuntumuntu]

Hi guys,

Is this an acknowledged issue that's actively being worked on, or is this simply something that's going to be ignored in the hope "that it will simply go away"?

Comment 33

[WADA:World Anti-bad-Duping Agency]

"Assigned To: No Body;" indicates that developer is not working for this bug yet.
Workaround is simple - remove conditions found in this bug analysis(conditions are already writen in bug summary).
(A) Stop using special char such as [ ] ^ # in Mbox name.
(B) If (A) is impossible(if Gmail IMAP, [ and ] is used by Gmail), remove suffix from file for IMAP folder including file for parent folder(see Bug 520437 which is already pointed in comment #30 for "suffix in .msf file name").
(B-1) If suffix is caused by same case-insensitive Mbox name due to case-sensitive Mbox name at server:
Don't use same case-insensitive Mbox name due to case-sensitive Mbox name at server.
(B-2) If suffix is caused by Bug 520437:
(B-2-1) If rename of Mbox is possible. (example when ABC-n.msf is used).
Rename ABC to XYZ, delete file named ABC-n.msf, ABC-n, delete directory named ABC-n.sbd. Restart Tb to avoid unwanted phenomenon. Open ABC folder, and rename XYZ to ABC.
(B-2-2) If rename of Mbox is impossible (e.g. Gmail's [Gmail]).
Terminate Tb. Delete file of [Gmail]-n.msf, [Gmail], rename directory of [Gmail]-n.sbd to [Gmail].sbd. Restart Tb.
If fails to recover from suffixed file name, try after stop using [Gmail]/All Mail, [Gmail]/Drafts, [Gmail]/Sent Mail, [Gmail]/Trash as special folder of Tb(Copies&Folders, Junk Settings, Server Settings).

Comment 34

[WADA:World Anti-bad-Duping Agency]

Typo. "Open ABC folder," -> "Open XYZ folder,"

Comment 35

[ubuntumuntu]

Just got an update for TB on OS/X - now running  11.0

I'm cautiously optimistic, but the issue seems resolved.

Will check back if issue re-occurs

Comment 36

[ubuntumuntu]

(In reply to ubuntumuntu from comment #35)
> Just got an update for TB on OS/X - now running  11.0
> 
> I'm cautiously optimistic, but the issue seems resolved.
> 
> Will check back if issue re-occurs

Could this bug possibly be a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=351109 ?

Comment 37

[WADA:World Anti-bad-Duping Agency]

(In reply to ubuntumuntu from comment #35)
> Just got an update for TB on OS/X - now running  11.0
> I'm cautiously optimistic, but the issue seems resolved.

If your case was resolved by Tb 11.0, and if special charcter is not used in IMAP Mbox name and suffix is not used for .msf file name/.sbd directory name at any folder path hiearchy for the IMAP folder, your case may be bug 351109, because bug 351109 is fixed by Tb 11(and trunk too).
However, problem I found by duplication test of this bug, with special char, with suffix in .msf file name/.sbd directory name, still occurs in Tb 11 and recent trunk builds.

"Which problem" can be identified by checkig image properties/location: of broken image in composed mail by Edit As New, Forward etc.
What image properties/location: was shown in your case?

Comment 38

[WADA:World Anti-bad-Duping Agency]

I observed following four different phenomena which depends on Mbox name.
(tested mail)
  IMAP folder : Offline-Use=Off folder
  multipart/mixed
    text/html : <img src="cid:img01"> 
    image/gif : Content-Id: <img01">, filename/name=img01.gif

(Observed phenomnon)
    At mail viewing                    At Forward/Edit As New
     embed image is broken or not       embed image is broken or not
(1) Shown always                       Shown always     
(2) Shown always                       Broken always
(3) Depends on Display Attachments Inline=On/Off and/or Offline-Use=On/Off
(3-a) If Display Attachments Inline=Off(Offline-Use=Off),
    Broken                             Broken
(3-b) When Display Attachments Inline is changed to On(Offline-Use=Off),
      or if Offline-Use=On(mail is saved in offline-store file by auto-sync), 
    Shown                              Shown
(3-c) When Display Attachments Inline is changed back to Off(Offline-Use=Off),
    Broken                             Broken
(4) Even if shown by Display Attachments Inline=On or Offline-Use=On,
    embed image is broken when Forward/Edit As New
    Shown                              Broken
Note: "always" in above context is;
      Regardless of Offline-Use = On/Off,
      Regardless of Display Attachments Inline = On/Off(Enabled/Disabled) 

It looks that two different issues are involved in phenomena I saw.
(Issue-A) Even though image is correctly fetched and shown at mail viewing,
          image is broken in Forward.
  Cause is broken image location(wrong interpretation/over escaping). 
  It looks relevant to combination of following.
  - .msf name/.sbd name != Mbox name, then fails to find file/dir for Mbox 
  - special character in Mbox name
    "^" as first char of Mbox name :
        Tb looks to escape "/" in Mbox name by "^"
    "[" "]" :
        Tb looks to replace them by "/", then replace by "^"
    "#" "?" :
        Hash/Search delimiter in URL
        Cut at "#" or "?" is observed in image location
(Issue-B) Image is not fetched at mail viewing, thus image is broken in Forward.
  Embed image is shown only with ;
    Display Attachments Inline = On(Offline-Use=Off),
    or Offline-Use=On
  It looks relevant to ".msf name/.sbd name != Mbox name" only.
    - Suffix in .msf file name due to;
      - unsubscribe/re-subscribe
      - case-sensitive Mbox name at IMAP server,
        and case-insensitive file syste at PC 
    - Hashed file name due to spcial character in Mbox name (see comment #15)
    - "&" in Mbox name.
      "&" is represented as "&-" in modified utf-7.
      Tb uses the "&-" as file name for "&" in Mbox name.

Issue-B is different problem from this bug. I'll rule out Issue-B from this bug will open separate ug for it, and focus on above (2) only in this bug.

Comment 39

[WADA:World Anti-bad-Duping Agency]

(Issue-B) in comment #38 was phenomenon when no CRLF is placed at close boundary of multipart mail, and it's absolutely different problem from this bug.
I perhaps tested with crafted mail data used for testing of such cases.
Sorry for my confusion.

Comment 40

[WADA:World Anti-bad-Duping Agency]

Following was characteristics of bug 287674, same phenomenon/problem as this bug when "space in Mbox name". 
> Over escaping by "%25" on "%" for "escaped character"
> Wrong "%5E" for "/" in Mbox name(delimiter) and doubled "%5E"
Setting dependency.

Comment 41

[WADA:World Anti-bad-Duping Agency]

Bug 287674 is report for Tb 1.0.2 opened on 2005-03-25.
Problem perhaps exists since initial of Tb. Problem may be inherited from Mozilla Mail&News, or Netscape Messenger.

Comment 42

[WADA:World Anti-bad-Duping Agency]

Close as dup of Bug 287674 because;
- original bug reporter says "problem disappeared after upgrade".
- phenomenon I observed with special chars in this bug is same as Bug 287674,
  except funny phenomenon with #/?(cut of URL at #/?).
- sufficiently messy due to many my comments about test results to analyze problem.
- phenomena of different problem with sufficed .msf file name is also involved
  in my comments.
I'll open new bug after sort out [ ] ^ cases and # ? cases.

Comment 43

[WADA:World Anti-bad-Duping Agency]

Problem of bug 287674(space in Mbox name) is not observed in Tb 17.0.1, but problem with #/? still seen in Tb 17.0.1.
Because I don't sort out phenomenon with #/? yet, re-open this bug in order to avoid loss of report on #/? case found in this bug.

Comment 44

[WADA:World Anti-bad-Duping Agency]

I couldn't see problem of bug 287674(space in Mbox name) in Tb 17, if newly defined Gmail account(suffixed .msf file name is never used.)
So I checked "suffixed parent's .mbox file name" case with several special characters in Mbox name. 

[An example of "Steps to reproduce" in Tb 17]

(1) Create a mail folder(call XYZ, XYZ.msf/XYZ.sbd is used)
(2) Unsubscribe XYZ
(3) Subscribe XYZ again => XYZ-1.msf/XYZ-1.sbd is used
(4) Create following sub folders under XYZ.
    "A B" (no quote, one space or several spaces is used)
    [
    ]
    {
    }A   (Gmail IMAP rejected } with reason of "Already exists", so }A is used.)
(5) Copy an HTML mail with embed image to each sub folder.
(6) Forward the mail (in HTML mode) => image is broken. 
    Broken pattern of Image Locaton: is same in any above Mbox name.
    (same patern as "space in Mbox name" case of bug 287674)

If two in "space [ ] # ?" is used at same in Mbox name(excluding "# and ?" case), problem was observed without suffixed .msf file name of parent folder".

Problem may occur when two of "suffixed-msf space [ ] { } # ?" exists at same time.

Comment 45

[Arthur K. (he/him)]

This one doesn't repro for me. I was able to forward and send a message from an IMAP mailbox named "[", "]" which arrived fine to my regular Inbox. This seems to be WFM now. Tested with 78.9.1 Portable and 88.0b3.