Closed Bug 113862 Opened 24 years ago Closed 23 years ago

Attachments forwarded from AOL client do not come through

Categories

(SeaMonkey :: MailNews: Backend, defect, P1)

Product:
SeaMonkey
Component:
MailNews: Backend
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME
Milestone:
mozilla1.0

People

(Reporter: kmurray1115, Assigned: mscott)

Details

If an AOL client user receives an email with an attachment and forwards that email to this client, the attachment does not come through, specifically, MS excel files. They come through as "Part 1.2" but are not the file that it should be. Tried this on build 2001-12-06-03. The specific scenario: 1. Original email composed in Netscape 6.2 2. Sent to AOL client user 3. AOL client user forwards that email to user of this build: 2001-12-06-03 (and prior) Result: Attached file comes through unusable, as "Part 1.2" Expected Result: Attachment should come through intact Huge dogfood issue for Netscape/AOL employees.
Keywords: nsbeta1
From origianl message source: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="part1_d8.10095180.2941216b_boundary" X-Mailer: AOL 6.0 for Windows US sub 10535
are you sure this isn't a dup of the bug we respun 094 for this week? It sure sounds like it. Is your inbox configured for offline use?
could be - if it is, didn't that fix go into the 2001-12-06-03 build?
I'm pretty sure this is a dup of 110067 which was one of the reasons the 094+ branch was respun this month.
Bug 110067 says the fix was checked into the trunk. I was using a trunk build when this happened.
QA Contact: huang → esther
Component: Networking - IMAP → Offline
QA Contact: esther → gchan
Maybe I can help clear this up. I think there might be some confusion here. For bug 110067, it is checked into the trunk. If you currently are using 6.2, have folders selected for offline, and have messages (w/attachments) downloaded already: they will stay 'corrupted' even if you use a new trunk build. The fix prevents mesgs from being corrupt but does not fix a mesg that has been corrupted. The solution to fix your corrupted mesgs is from Scott's comment number 43: http://bugzilla.mozilla.org/show_bug.cgi?id=110067#c43 "To make the current messages work you would have to delete the .msf file of the affected folder" The 'part 1.2' is always attached when sending mail (W/attach) from aol. It contains headers and looks like attachment in ascii format. Everytime I fowarded a mesg (that had attach) and sent it to the trunk build, there was always the attachment and 'part 1.2' attachment. When I composed a mesg from AOL and added an attachemnt and sent it to my trunk build, only the attachment was there. No 'part 1.2'. I tried 3 test cases using your steps to reproduce: Test1 1.Composed a message using 'respin 094', attached an excel file 2.sent it to my aol act and opend it with aol 6.0 3.downloaded attach and opened it (no problem) 4.Forwarded to myself 5.opened it with 2001-12-06-09-trunk/ build 6.I saw both the 'part 1.2' and my excel attach. 7.I was able to open/save the excel file with no problem Test2 1.Used 6.2, composed a mesg and attached excel file. 2.sent it to my aol act and opend it with aol 6.0 3.downloaded attach and opened it (no problem) 4.Forwarded to myself 5.opened it with 2001-12-06-09-trunk/ build 6.I saw both the 'part 1.2' and my excel attach. 7.I was able to open/save the excel file with no problem Test 3 1.Used 6.2, selected a folder for offline use 2.clicked on a mesg, in the folder selected for offline use, that had an excel attach 3.tried opening attach and it's corrupted. 4.Forwarded it to my aol act and opend it with aol 6.0 3.downloaded attach and opened it (corrupted file) 4.Forwarded to myself 5.opened it with 2001-12-06-09-trunk/ build 6.I saw both the 'part 1.2' and my excel attach. 7.Saving the file no problem. But if I opened it from mail mesg or from after downloading it to my hard drive, the file was corrupted. I couldn't really replicate your problem Kevin. Hope this helps.
Thanks for all your testing Gary. Kevin can you give us more steps on how to reproduce this that might help us narrow it down? Your sure you aren't using a 6.2 build that corrupted the message to begin with and not a 6.2.1 or a trunk build?
Kevin, If you follow Gary's steps, does the bug go away? I did see this on Kevin's machine. One thing about the other bug was that I thought it had least displayed the attachment, you just couldn't download it completely. I don't think Kevin's message was displaying the attachment. If you still have the message and Gary's steps don't help out, we can see if one of us can duplicate this.
Status: NEW → ASSIGNED
Keywords: nsbeta1 → nsbeta1+
Priority: -- → P1
Is this really a nsbeta1+, P1? If yes, then we need to try and targeted to a milestone M1.0 or earlier to make the beta.
Yes should be nsbeta1,P1, tried to add nsenterprise but not enough privs.
Kevin, do you still have the message that causes this? If so, can you Edit it as New (Ctrl-E) and send it to me? I'm working on a time warner issue that could be similar to this one. When you run into this problem, does the busy cursor never go away when you click on the message?
I don't have the original message, but if the aol client user in the scenario above is on mac, IIRC, it seems to bre much more prevalent. I will look through my mail and see if I can find it for sure though.
Target Milestone: --- → mozilla0.9.9
If this bug is really Mac specific, we have several problems receiving messages with images that are sent from the mac via the AOL client. Esther can probably dig up the bug numbers but we are already working hard on those. Since we don't have a test case yet, not a .9.9 stopper.
Target Milestone: mozilla0.9.9 → mozilla1.0
I am pretty sure the fix for bug 93439 will solve this case as well...
Kevin, I followed your steps in original scenario using 20020301 builds. I sent an email using NS6 commercial trunk, Mac G3 OS9.1, with xls attachment. I opened it in AOL 7.0 client and forwarded it to myself using my @aol and @netscape.com addresses. I opened this forwarded message in my AOL account in NS6 Client= message and attachment OK I opened this forwarded message in my dredd account using NS6 client = Message and attachment OK. What is a mac, IIRC? As Scott mentioned, this probably was fixed with one of the Mac specific bugs regarding attachments. Have you seen any problems with this type of mail message in the last month?
I have not seen this recently. However, I haven't been seeing many messages from this source. I'll believe JF when he says this one is likely fixed with bug 93439. And Esther - "IIRC" means: "If I Remember Correctly," and is not specific to the mac. ;-)
marking worksforme then.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.