Closed Bug 147075 Opened 22 years ago Closed 15 years ago

Mozilla fails to encode special characters (e.g., slashes, accented letters) in attachment filenames

Categories

(MailNews Core :: Attachments, defect)

Product:
MailNews Core
Component:
Attachments
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME
Milestone:
mozilla1.2beta

People

(Reporter: csmith, Unassigned)

References

Details

(Whiteboard: needinfo)

Attachments

(1 file)

Appearance of file name small letter e+acute accent (U00E9) in FizzillaMach/2003020603's attachment pane
641 bytes, image/png
Details 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0rc3)
Gecko/20020523
BuildID:    2002052305

Summary: I cannot seem to send attachments (in any format) when they have names
with extensions (after the .) of more than 3 characters.

Running Mozilla Mail w/ IMAP, standard SMTP server config.  Open new message
(Compose), put "imatest" in subject and body, attached text file "test.txt", and
hit Send.  No problem.

NOW changed filename to test.txtt, attach to a new message as above, and I get
an error message

"Sending of message failed.
Please verify that your Mail & Newsgroups account settings are correct and try
again.     
                           (  OK  )


Reproducible: Always
Steps to Reproduce:
1.open mailer
2.hit compose
3.put text in subject and body
4.attach a file with >3 char extension, like test.txtt
5.hit "Send" button

Actual Results:  Error message
"Sending of message failed.
Please verify that your Mail & Newsgroups account settings are correct and try
again. 

Expected Results:  Send message!

Had same response under rc1 (which drove me to upgrade to rc3, but wasn't fixed
yet).
WorksForMe using FizzillaCFM/2002052305 (RC3). I saved a text file named
"test.txtt" from BBEdit and Mozilla successfully sent an e-mail it was attached to.

This does sound somewhat similar to my bug 131910, however.
Change reproducible to: Not always!

I just confirmed Greg K's test, done after a restart Mozilla.  The difference I
see is that now when I attach a file, the name is test.txtt (or whatever the
original name is).  Before when I was attaching a file, the attachment window
was reporting the attachment as 
file:///diskname/path/path/path/filename

I can now reproduce the above behavior ONLY when I have a folder with a "/" in
the name (like "Stuff/Misc"), which seems to force the attachment to be put in
the file:/// format.  But I'm pretty sure that my previous tests were not only
in such a badly named folder.  Will continue to test.



I have now confirmed a problem using FizzillaCFM/2002052305 (RC3), but it's
different than what Chris reported.

Mozilla fails to encode slashes in attachment paths. Slashes in either file or
directory names aren't encoded, so message send fails.

Revising Summary and nominating for Mozilla 1.0, nsbeta1, and nsmac1.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: mozilla1.0, nsbeta1, nsmac1
Summary: attachments w/ >3 char extensions can't be sent → Mozilla fails to encode slashes in attachment paths resulting in message send failure
It appears MailNews may not be doing any character escaping in attachment paths.
It probably needs to do so.
Keywords: adt1.0.0
Blocks: 143047
Keywords: nsbeta1 → nsbeta1+
Whiteboard: [adt1 RTM]
Removing adt1.0.0 nomination until there is a patch with reviews, and it has
been verified on the trunk. Pls renominate as adt1.0.1, when this has been
verified on the trunk as fixed.
Keywords: adt1.0.0
reassigning to ducarroz.  JF or Trix, can you reproduce this?
Assignee: mscott → ducarroz
Keywords: nsbeta1+ → nsbeta1
Whiteboard: [adt1 RTM]
Discussed in mail news bug meeting.  need info how do you get the slash in the
filename?
Whiteboard: needinfo
It's easy. For example, in the Finder, create a new folder. You can simply type
"foo/bar".

Although TextEdit doesn't let you save filenames containing slashes directly,
you can add one in the Finder post-save.
On a Mac, just create a file (any file) and rename it in the Finder, including a
slash in the filename, since MacOS doesn't use the slash as the directory
deliminater. (Well, I guess with MacOS X this is only half true, since the
underlying Darwin uses slashes, but the Carbon and other MacOS APIs use the
"old" Mac conventions.)

It looks like the standard Mac Carbon "Save As" boxes prevent you from entering
a slash as the filename, but the Finder still allows it.
Keywords: nsbeta1 → nsbeta1-
*** Bug 158912 has been marked as a duplicate of this bug. ***
*** Bug 155408 has been marked as a duplicate of this bug. ***
Setting OS to Mac System 9.x per bug 155408.
OS: MacOS X → Mac System 9.x
*** Bug 159637 has been marked as a duplicate of this bug. ***
*** Bug 166201 has been marked as a duplicate of this bug. ***
This problem ( not being able to handle a "/" in the file path has been around
for a while? Anyone working on it?
If I recall correctly, this is a problem in our implementation of the file
manager. It has been written for MacOS 9 and it's currently rewritten for MacOS
X. Simon, is it correct?
Target Milestone: --- → mozilla1.2beta
JFD: i don't think that's the issue. How are you getting the file path?
I don't remember if I am using nsFileSpec or nsILocalFile, I'll have to take
look... The problem I remember was when the volume name contains a slash, we
weren't able to load a file in the browser window too.
*** Bug 177448 has been marked as a duplicate of this bug. ***
QA Contact: trix → yulian
QA Contact: yulian → stephend
This is another example of Mozilla (I am now using Mozilla 1.2.1) being much
more intolerant than Netscape 4. Please could someone explain why this has to be
so? If Netscape 4 can handle file-names that don't quite accord with approved
practice, why can't Mozilla be made as tolerant as that, too?
Setting OS to Mac OS X since OS 9 is no longer supported.

Testing using FizzillaMach/2003020603, a slash character in an attachment
filename is converted to a colon. Mozilla is incorrectly considering the slash
to be part of the path. However, message send no longer fails.

FWIW, FizzillaMach/2003020603 is also failing to encode non-ASCII characters
such as é or ü in attachment filenames.
OS: Mac System 9.x → MacOS X
Summary: Mozilla fails to encode slashes in attachment paths resulting in message send failure → Mozilla fails to encode special characters (e.g., slashes, accented letters) in attachment filenames
For example, a file named with a single letter e+acute accent (U00E9) is
encoded by FizzillaMach/2003020603 as "=?UTF-8?B?ZcODw4U=?=" and displayed in
the attachments pane as shown in this attachment.
*** Bug 193155 has been marked as a duplicate of this bug. ***
*** Bug 118411 has been marked as a duplicate of this bug. ***
Product: MailNews → Core
This seems WFM now... Can someone confirm?
Assignee: ducarroz → nobody
QA Contact: stephend → attachments
Product: Core → MailNews Core
(In reply to comment #25)
> This seems WFM now... Can someone confirm?
 Works for me too with acentuated charaters. -> WFM. Feel Initial commenters/reporters feel free to reopen if you still have issues with recent TB builds (http://stage.mozillamessaging.com/en-US/thunderbird/early_releases/downloads/)
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: