[mew-int 2576] Mew creating unusable folders

Gernot Heiser gernot at example.com
Tue Aug 12 18:02:35 JST 2008


I use
  (setq mew-fcc "+outCC")
to keep copies of outgoing mail.

I recently upgraded to Ubuntu Hardy and that upgraded mew to
5.2.52. Since than a lot of the copies end up in a directory " +outCC"
(note the leading blank character). Of course, this is not a
recognised folder name in mew, so I can't actually visit that folder
(I have to rename the directory in order to make the messages
accessible).

It seems that what happens is the following. If I don't explicitly
specify an Fcc folder (relying on the default +outCC) things work
correctly, the copy goes into the "outCC" directory. If I add another
FCC folder, say +foo (using a private keybinding that adds the folder
name to the Fcc: header) the Fcc: header looks like:
     Fcc: +foo, +outCC

This worked fine under previous versions of mew. In the present
version, this will file a copy in the "foo" and " +outCC"
directories. If I remove the space after the comma in the Fcc: header,
the message gets filed correctly.

Gernot





More information about the Mew-int mailing list