Closed
Bug 398967
Opened 18 years ago
Closed 17 years ago
Problem extracting attachments sent from Apple Mail
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 378729
People
(Reporter: pajek, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sl; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7
Build Identifier: 20070728
If I extract attachments sent from Apple Mail the files are corrupted. It looks like resource and data fork from are "glued" together (first resource and then data fork) in a single file. If I forward the same mail to another e-mail address, and open it on Windows computer it works as expected.
Reproducible: Always
Steps to Reproduce:
1. Send an email with attachment using Apple Mail application
2. Receive and open sent mail in Thunderbird
3. Extract attachment
Actual Results:
It looks like resource and data forks of the attached file are "glued" together in a single file.
Expected Results:
There should be only one file with only data fork in it.
I couldn't find anything on the subject so I am posting a bug here. I hope I didn't miss an already posted bug/solution.
Trouble extracting this PDF attachment (11342_31.5x90.pdf):
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: multipart/alternative; boundary=Apple-Mail-4-251306562
X-Mailer: Apple Mail (2.752.2)
--Apple-Mail-4-251306562
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=UTF-8;
delsp=yes;
format=flowed
Thanks!
Attached is a PDF
[snip]
Thank you
=EF=BF=BC
--Apple-Mail-4-251306562
Content-Type: multipart/mixed;
boundary=Apple-Mail-5-251306562
--Apple-Mail-5-251306562
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=ISO-8859-1
<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
[snip]
class=3D"khtml-block-placeholder"></DIV></DIV></BODY></HTML>=
--Apple-Mail-5-251306562
Content-Transfer-Encoding: base64
Content-Type: application/pdf;
x-mac-type=50444620;
x-unix-mode=0644;
x-mac-creator=4341524F;
name=11342_31.5x90.pdf
Content-Disposition: inline;
filename=11342_31.5x90.pdf
JVBERi0xLjQNJeLjz9MNCjQgMCBvYmoNPDwvTGluZWFyaXplZCAxL0wgNzUzMjMzL08gNi9FIDY4
NzgyOC9OIDEvVCA3NTMxMTIvSCBbIDg1NiAxOTVdPj4NZW5kb2JqDSAgICAgICAgICAgICAgICAg
[snip]
MjggMDAwMDAgbg0KMDAwMDY4Nzg3OSAwMDAwMCBuDQowMDAwNzUyOTYzIDAwMDAwIG4NCnRyYWls
ZXINPDwvU2l6ZSA0Pj4Nc3RhcnR4cmVmDTExNg0lJUVPRg0=
--Apple-Mail-5-251306562
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
charset=US-ASCII
<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><BR></DIV></BODY></HTML>
--Apple-Mail-5-251306562--
--Apple-Mail-4-251306562--
Comment 2•17 years ago
|
||
I remember seeing this problem a lot with attachments on Apple Mail-created e-mails. More recently, I notice that in many cases the "delete" or "detach" functions simply do not do anything at all. (Using TB 2.0.0.14 on Linux here)
In some respects, that's actually worse. I prefer an attachment that I can get rid of (to archive the e-mail without it), even if there are a few messed up characters at the end. Now, I am stuck with the attachment!
Any idea what can be done, anyone?
Comment 3•17 years ago
|
||
I can confirm this bug on Thunderbird 2.0.0.0.16 on *Intel* Macs. It does not happen on *PPC's*
Comment 4•17 years ago
|
||
I wonder why this longstanding and IMHO serious bug is still unconfirmed. It seriously compromises the usability of Thunderbird on the Macintosh Platform: Attachments sent from Apple Mail are a daily occurrence in the graphics business and every new Mac has an Intel processor.
I am responsible for 10+ Mac workstations and decided to equip them with Thunderbird instead of Apple Mail. I don't know how long I can justify my decision as long as this bug is not fixed.
Comment 5•17 years ago
|
||
see also Bug 378729 and attachment/comment <https://bugzilla.mozilla.org/show_bug.cgi?id=378729#c8>
Updated•17 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Version: unspecified → 2.0
You need to log in
before you can comment on or make changes to this bug.
Description
•