Bug 189441 - Backup kmail/mail-dir mails to fat/vfat filesystem on usb stick not possible
Summary: Backup kmail/mail-dir mails to fat/vfat filesystem on usb stick not possible
Status: RESOLVED DUPLICATE of bug 55339
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.9
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-12 11:40 UTC by Toni
Modified: 2009-08-17 00:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Toni 2009-04-12 11:40:26 UTC
Version:           1.9.9 (using KDE 3.5.10)
OS:                Linux
Installed from:    Debian stable Packages

Situation: 
----------
- Mails stored kmail in maildir format use special characters (at least comma and colon). E.g. "1120923112.4769.TEuXE:2,R"

- Current usb sticks are mostly formatted with fat/vfat file system

Problem: 
--------
fat/vfat isn't able to store files with at least the colon character, so you aren't able to backup kmail mails on usb stick out of the box.

Fix:
----

I know that problem (or at least the restriction) concerns to the old Windows (v)fat format, there would be no problem if usb sticks would use a better file system. I know also that one can work around it (pack mails into tar file, ...).

But apart from the fact that the above mentioned restriction means also compatibility (least common denominator regarding the charset): Is it really necessary to use these special chars in the file names? User don't have to deal with these files directly, so readability isn't necessary. On the other side software doesn't (at least in principle) matter wether there's a colon or an "x", "y" or "z".

Or is it a requirement of the maildir format?

Suggestion: Avoid special chars in filenames if it isn't necessary
Comment 1 Martin Koller 2009-08-17 00:29:46 UTC

*** This bug has been marked as a duplicate of bug 55339 ***