Closed
Bug 100609
Opened 24 years ago
Closed 24 years ago
Attachment filename corruption on send (and receive)
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: frankfurter, Assigned: bugzilla)
References
()
Details
It appears that attachments exceeding 8.3 are getting corrupted filenames (this
could be an OSX problem?).
See url for screen shot (unless I can figure out how to attach the image).
Filename locally is:
"A Perfect Circle - Diary Of A Madman (Live).mp3"
Upon attaching it to the mail it becomes:
"A Perfect Circle - Di#2467C.mp3"
End recipient receives file with corrupted filename as well.
| Reporter | ||
Comment 1•24 years ago
|
||
Sorry, browser wouldn't let me attach screen shot, says:
You must provide a description of your attachment.
in a big red box (yes, I provided a description.)
See the URL above for a screenshot.
Thanks!
Comment 2•24 years ago
|
||
over to ducarroz, our mac os x person.
I think you'll want to take a look at nsMsgUtils.cpp, NS_MsgHashIfNecessary().
we currently have code (#ifdef XP_MAC) that decides to hash if the file name is
longer than the Mac OS 8.x / 9.x limit of 32 chars.
that code is set at compile time. I believe our mac os x binaries are built on
9.1, where XP_MAC is set, so this may not get fixed.
Assignee: sspitzer → ducarroz
Comment 3•24 years ago
|
||
Our file code on Mac os X still can't deal with file names > 31 chars. If the
attachment is still sent correctly, and received, then this should be a WFM.
Confirming using Fizzilla/2001091313 (0.9.4). The attachment is not saved with the original
filename after being received.
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Comment 5•24 years ago
|
||
does this problem append with file name < 32 characters?
| Assignee | ||
Comment 6•24 years ago
|
||
I did a test with an attachment with a short file name and it works fine. We
have the same limitation with MacOS 9.x
We have planed to rewrite the way we manage attachment in nsMsgCompFields which
should resolve this issue as well others.
WFM.
Severity: major → minor
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•