Closed Bug 252320 Opened 20 years ago Closed 19 years ago

Previewing attached forwarded message(message/rfc822 part) fails on IMAP server when in folder several levels deep.

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: tom, Assigned: mscott)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Build Identifier: Thunderbird 0.7.2

If you forward a message from an IMAP folder that is several levels deep (2 or
more in this case) AND one of the folder names contains a space, you cannot
double click the attachment in the new message and view it. You either get a
blank message or an IMAP select error.



Reproducible: Always
Steps to Reproduce:
1. Have an IMAP account. I am using UW-Imapd, server banner is:

"* OK [CAPABILITY IMAP4REV1 X-NETSCAPE LOGIN-REFERRALS STARTTLS AUTH=LOGIN]
jmcinet IMAP4rev1 2001.315 at Tue, 20 Jul 2004 14:17:39 -0500 (CDT)"

I have not tested this on another IMAP server, but this error shouldn't be
server related since the message is viewable from anywhere but a new message window.

2. Create a folder (that can contain other folders) with a space in the name of
it. Create a folder without. Then create message folders under these folders. I
have the resulting structure:

|--test folder
  |--test1
|--testfolder
  |--test2

3. Put a message (I've dragged many messages while reproducing, some with
attachments, others without) into the folder without spaces in its path. Open
the message to see that it is available, and click forward. In the forward,
click on the attached message and you can see that it is viewable.

4. Close the above messages (two previews + new message) and drag the message to
the path including a space (in my example "test folder/test1". Now open the
message and verify that it is viewable. Click forward to create a new message
with this one attached. Double click the attached message to view it.
Actual Results:  
You get a blank window when previewing an attached forwarded message that is
contained in an IMAP path that contains a space.. I was also getting a select
error that looked like "Cabinet^^JMC^^Folder S-K" on another machine, but I
can't reproduce this on my machine.

Expected Results:  
Thunderbird should show the attached email so that the user can know that the
attachment is included.

Maybe something to do with incorrectly escaping spaces in the new message window
for IMAP paths?
Thunderbird(Mozilla Mail&News also) has some(but not so small) problems on
message/rfc822 part handling, especially on nested message/rfc822 part.
See meta Bug 269826.
(Q1) Can you find already reported bug for your problem in it?
(Q2) Does your "2." have relation to your problem?
     Does your problem occur only when IMAP folder & folder name with spaces(s)?
     Does your problem occur also when "Local Folders"?

Anyway, add "message/rfc822" in summary for ease of search.
Summary: Previewing attached forwarded message fails on IMAP server when in folder several levels deep. → Previewing attached forwarded message(message/rfc822 part) fails on IMAP server when in folder several levels deep.
>(Q1) Can you find already reported bug for your problem in it?

I could not at the time it was entered.

>(Q2) Does your "2." have relation to your problem?

Absolutely, it cannot be reproduced otherwise.

>Does your problem occur only when IMAP folder & folder name with spaces(s)?

Only when a folder above the current folder contains spaces in the name.

>Does your problem occur also when "Local Folders"?

I did not attempt to do that. My assumption was that it was somehow an IMAP
issue - although folders with space in their names work in normal use (opening
messages, moving messages between folders, etc).
Blocks: 269826
No longer depends on: 269826
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.