Used 01-31-14-Mtest build Cannot read/open .xls attach files for Cyrus IMAP account 1) Login to a Cyrus IMAP mail account 2) Send a 345kb.xls attachment file: 3) Actual Results: The 345kb.xls attachment file: can be send, but cannot read/open this attachment file locally. Expected results: Should open/read this xls attachment after attaching and downloading this attach file locally for Cyrus IMAP account
Adding nsbeta1 & interop for the keywords since without this fix, Cyrus IMAP account users won't be able to open & read those attached file locally.
can you attach a log?
The .xls file (1st attachment) seems cannot be displayed here. I can send email and attach that file to you if you need it....
marking nsbeta1+ and moving to mozilla0.9
Priority: -- → P2
Target Milestone: --- → mozilla0.9
*** This bug has been marked as a duplicate of 63189 ***
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE
Retest on 05-01-06 trunk build Reopen this bug since it's not dup of bug 63189. This is specific for Cyrus account
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Karen can you save the attachment to disk and then open it in excel? Does that work?
It works if I save the attachment to disk and then open it in excel. But it seems it's also working after I try many times afterwords. Don't know why the first few times are not working....
moving to 0.9.1
Target Milestone: mozilla0.9 → mozilla0.9.1
I fixed some problems with imap and the memory cache yesterday which effected opening of attachments. Can you retest this with a build from today or later....thanks.
Karen, could you try this out when you get a chance?
It seems that I can open this .xls attach file now, but there is crash after I open this .xls attach file....another bug? I probably need to verify this bug later....
marking fixed then. the crash after opening was a smoketest blocker in yesterday's builds that was fixed by valeski with a respin build last night.
Status: REOPENED → RESOLVED
Last Resolved: 17 years ago → 17 years ago
Resolution: --- → FIXED
OK. Based on my verification & Scott's comments -- that is another problem. Then Marking as verified on 05-07-06-trunk build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.