reply to saved messages not stored in ~/sent

[Tom Fowle]

Hello,
Using mutt v1.42 under Debian wheezy
I often save important received emails in seperately named files in my home
directory. If I save such a message, then return to it in the same mutt
session and reply, it appears my reply message is not saved in ~/sent

This may also happen if I save the message, close mutt, open it again with
mutt -f "saved messagename"
and reply again, it appears the reply is sent, but does not appear in
~/sent

Apparrently replies on messages I havn't saved in seperate files are all
saved in ~/sent

I have not changed directories doing all this.

Any help much appreciated
Thanks in advance
Tom Fowle WA6IVG

[Tom Fowle]

goofed, using V1.52
T.F.

Post by Tom Fowle
Hello,
Using mutt v1.42 under Debian wheezy
I often save important received emails in seperately named files in my home
directory. If I save such a message, then return to it in the same mutt
session and reply, it appears my reply message is not saved in ~/sent
This may also happen if I save the message, close mutt, open it again with
mutt -f "saved messagename"
and reply again, it appears the reply is sent, but does not appear in
~/sent
Apparrently replies on messages I havn't saved in seperate files are all
saved in ~/sent
I have not changed directories doing all this.
Any help much appreciated
Thanks in advance
Tom Fowle WA6IVG

[Nathan Stratton Treadway]

Post by Tom Fowle
Hello,
Using mutt v1.42 under Debian wheezy
I often save important received emails in seperately named files in my home
directory. If I save such a message, then return to it in the same mutt
session and reply, it appears my reply message is not saved in ~/sent

Check carefully to see if the messages are being saved somewhere else.
(For example, look at the Fcc: line on the Compose menu just before
sending the message.)

If the outgoing messages are ending up in those separately-name files
for the recipient, for example, then check the setting for the
$save_name configuration variable.

Or, you may have some fcc-(save-)hook commands in effect somewhere...


Nathan