David :Bienvenu Assignee
	Description • 25 years ago

We need to munge msf file names for folders on a per-platform basis so that the
msf file name is legal. 4.5 did this with _'s. <\......\> is an example of a
bogus name that should be munged.

	John G. Myers
	Comment 1 • 25 years ago

Problematic NT characters: "/" "." ":" "\\" "~" "<" ">" "\""
NT filesystems are also case-independent, so uppercase characters need to be
munged in order to disambiguate them from lowercase characters.
The filenames "aux", "nul", etc. can be problematic, my server always puts a "="
character after every "/" in order to avoid this potential problem.

You can probably make the munging be platform-independent, since platforms which
don't need munging won't be hurt by it.

	John G. Myers
	Comment 2 • 25 years ago

The "|" character is also problematic on NT.

	David :Bienvenu Assignee
	Comment 3 • 25 years ago

fixed to replace illegal characters with '_'

	Karen Huang
	Comment 4 • 25 years ago

David, could you provide more information..so I can verify this bug?

	David :Bienvenu Assignee
	Comment 5 • 25 years ago

<\......\> is an example of a bogus name that should be munged. try creating an 
imap folder with that name, and see if you can open it.

	Karen Huang
	Comment 6 • 25 years ago

Used 02-28-08-M15 Win32 commercial build:

*Copy David's code for Win32 as following:
#elif defined(XP_WIN32)
        nsCAutoString illegalChars = "\"/\\[]:;=,|?<>*$";


*The Test results are as following:
1)Created/opened folders & copied messages successfully on 5.0 were as
following:
"\" "[]" ":" ";" "=" "," "|" "<" "$" "\\" characters, uppercase characters and
"aux", "nul" file names 

2) Created folders unsuccessfully and displayed warning message "The current
command did not succeed, the mail server responded: Invalid mailbox name" on 5.0
were as following:
 "/" "//" "?" "~" ">" "*" characters.

3) Created "." folder:
  "." folders displayed successfully on the 4.x & IMAP server but did not
display on the 5.0.

4) List the IMAP servers folders' list as following:
* LIST (\HasNoChildren) "/" $
* LIST (\HasNoChildren) "/" ,
* LIST (\HasNoChildren) "/" .  --> server displayed "." folder but not on 5.0
* LIST (\HasNoChildren) "/" :
* LIST (\HasNoChildren) "/" ;
* LIST (\HasNoChildren) "/" <
* LIST (\HasNoChildren) "/" =
* LIST (\HasNoChildren) "/" []
* LIST (\HasNoChildren) "/" aux
* LIST (\HasNoChildren) "/" nul
* LIST (\HasNoChildren) "/" | 
* LIST (\HasNoChildren) "/" {1} \
* LIST (\HasNoChildren) "/" {2} \\
* LIST (\HasNoChildren) "/" {9} <\......\  --> see existing bug#22474 

So, David, how do you think for above results?

	David :Bienvenu Assignee
	Comment 7 • 25 years ago

I think you're rolling several bugs into one, but if that helps you keep track 
of things, that's fine. This bug is about munging the .msf file name on disk.

	Karen Huang
	Comment 8 • 25 years ago

If above verification rolls several bugs, I will log those bugs separately....
But, I am not quite sure what the exactly I need to verify for this bug?
Can you describe more? Thanks.
I think I need to Cc: John for this bug since he mentioned many issues for this 
bug... Cc:jgmyers

	John G. Myers
	Comment 9 • 25 years ago

You should be able to create ">" on Netscape Messaging Server.  That should be 
filed as a separate bug.

Netscape Messaging Server will allow you to create a folder containing "~" only 
if it is not the first character.  So you should create "a~b" or somesuch.

	Karen Huang
	Comment 10 • 25 years ago

Thanks for the response, I will log those bugs. 

	Karen Huang
	Comment 11 • 25 years ago

Bug#29581 & bug#29599 have been logged....

	Karen Huang
	Comment 12 • 25 years ago

Logged other bug#29890 & bug#29926.
Don't know whether I can mark as verified for this bug or not since bug#29599 
">" problem & bug#29926 "/" problem need to be solved in order to close this 
bug......adding depends bugs here!!

	Karen Huang
	Comment 13 • 25 years ago

Sorry, should be bug#29581 instead of bug#29599!! Changing depends from 
bug#29599 to bug#29581.

	Karen Huang
	Comment 14 • 25 years ago

I put David's code here for including other platforms in case we may need to 
check other platforms:

  #if defined(XP_MAC) 
        nsCAutoString illegalChars = ":"; 
  #elif defined(XP_OS2) 
        nsCAutoString illegalChars = "\"/\\[]:;=,|?<>*$. "; 
  #elif defined(XP_WIN32) 
        nsCAutoString illegalChars = "\"/\\[]:;=,|?<>*$"; 

	Karen Huang
	Comment 15 • 25 years ago

*** Bug 14231 has been marked as a duplicate of this bug. ***

	(not reading, please use seth@sspitzer.org instead)
	Comment 16 • 23 years ago

heads up, this code is getting tweaked.

instead of replacing, I'll be hashing foldernames will "illegal chars".

(note, foldernames that are too long for the OS's filesytem also get hashed, 
but the initial part of the name is preserved.)  

see #82821

this code got moved into nsMsgUtils.cpp, NS_MsgHashIfNecessary()

	Karen Huang
	Comment 17 • 23 years ago

Change the OS from WindowsNT to ALL.
Adding bug 84004 for this bug's dependence.

I will use this bug for the main bug to track .msf file names for all the 
platforms....

David, hope you don't mind that I am reopening this bug since there are some  
bugs existing (bug 29581 & bug 29926 for WinNT, bug 84004 for Mac)

#if defined(XP_MAC) 
        nsCAutoString illegalChars = ":"; 

John & David,
Any idea about the illegalChars for Mac?
Also, how about Linux platform?
I need to investigate more from this bug and log other bugs per platform 
basis...

	Karen Huang
	Comment 18 • 23 years ago

Oops! I mean bug 84008 for Mac

	David :Bienvenu Assignee
	Comment 19 • 16 years ago

I'm closing this bug - we can deal with the other issues separately, instead of making this bug into a tracking bug (since we already munge the .msf file names, and that's not the issue with the other bugs)