Until this security announcement [0] a few days ago, I was running mutt_1.5.11+cvs20060126-2
After the announcement, I upgraded and got mutt_1.5.11+cvs20060403-1. With this upgrade, my Fcc field (which defaults to an empty field) suddenly started showing "~/sent" instead. Clearly something has changed in the defaults for Mutt, either upstream or Debian built, between those two versions. The manual claims[1] that Fcc defaults to "", as per and so I believe showing "~/sent" is either a bug or a change in behaviour. Checking the Mutt source for mutt_1.5.11+cvs20060403-1 and reviewing the ChangeLog: > * init.h: Set $record default to ~/sent (closes: #2068). The bug report for Mutt bug 2068 says "$record does not have a default. This can result in unwanted mail loss. Since $mbox for instance _does_ have a default. $record should have one too." This behaviour is probably sensible but against Mutt's normal policy of not changing defaults, thus it came as a surprise. It will only cause a problem if, for some reason, the folder ~/sent cannot be written to. Having a pre-existing directory called ~/sent might cause confusion, I suppose. [0] http://lists.debian.org/debian-security-announce/debian-security-announce-2006/msg00195.html [1] http://www.mutt.org/doc/devel/manual.html#record -- Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED] - freenode: davee All email from me is now digitally signed, key from http://www.sungate.co.uk/ Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92
signature.asc
Description: Digital signature
