bjd-pfq

Here's a weird observation: I have a mailbox with 9481 messages. I am exporting 'all files in this folder to EML format'. When I have the custom date for filenames...

Somebody please look into this and give me some feedback here -- this is a severe bug that may cost people their emails.

When I choose HTML instead of EML all symptoms as described above remain.

Thanks for responding. I am getting: myInbox exportTools.js:359:10 NS_ERROR_FILE_NAME_TOO_LONG: Component returned failure code: 0x80520011 (NS_ERROR_FILE_NAME_TOO_LONG) [nsIFile.createUnique] exportTools.js:1147 onStopRequest68 chrome://mboximport/content/mboximport/exportTools.js:1147 This is with my custom date format as described above (only...

When I limit the Subject to 50 characters 7193 out of 9483 are exported. You see the trouble with silently failing? (Oh, and the red indicator persists).

When I uncheck "Customized format for filenames" AND "cut subject at 50 chars" it exports all messages and creates an index.html file (I had never seen that, nor did I...

Also, I have set charset for filenames to 'utf-8'; doesn't that place an extra limit on filenames??

Different issue, but can we have a more European date (or ISO) in the index.html? The American style date is non-standard imho, ambiguous and generally ugly as hell. But first...

My /tmp is located on an unencrypted drive, and when I use my custom date (see above) and do NOT limit the subject to 50 characters, all messages are exported...

Actually I misspoke. The ecryptfs limit seems to be 143, see: https://unix.stackexchange.com/questions/32795/what-is-the-maximum-allowed-filename-and-folder-size-with-ecryptfs/32834#32834 But also see the important comment on UTF-8 encoded filenames.