Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

When using maildir, can I set the extension on each message file (.eml)?

  • 3 Antworten
  • 1 hat dieses Problem
  • 12 Aufrufe
  • Letzte Antwort von Onno Ekker

more options

I switched to using maildir for message storage (one file per message). These files are stored with no extension, so Windows doesn't know which app to use to open them. Plus, the description (title) field is blank in Explorer. Adding ".eml" to the file fixes both of these problems. Is there a way to add ".eml" to each message file when they are written? Thanks.

I switched to using maildir for message storage (one file per message). These files are stored with no extension, so Windows doesn't know which app to use to open them. Plus, the description (title) field is blank in Explorer. Adding ".eml" to the file fixes both of these problems. Is there a way to add ".eml" to each message file when they are written? Thanks.

Alle Antworten (3)

more options

Hmm, this isn't promising. In "Maildir in Thunderbird", it says:

Maildir is disabled by default because there are still many bugs. It is not 100% ready for users.

WARNING: We suggest you leave Maildir disabled unless you are an advanced user, willing to risk your data, and know how to back up your email before turning on Maildir and how to restore it if you run into problems.

So unlike many other questions, I won't be personally experimenting with this feature...

more options

I understand the risks and I appreciate the warning. I used BulkRenameUtility to add the extension to the existing files and got the desired result, but that's not practical on an ongoing basis. If I choose to be reckless and use maildir, can I set the extension? If so, how? Thanks.

more options

At the moment this can't be done, see bug 1144478.