[SOLVED] I think I found what the problem is and I believe it 's a bug, but I haven't checked mutt source files.
I believe that when mutt fires up the editor for composing a reply, it gives the $ iconv -f <Content-type's charset> -t $charset to the editor, so in my case, it forces vim to sense fenc=utf-8, after editing the reply tries to iconv -f $charset -t <one of $send_charset> and everything goes smoothly. However, mutt doesn't do the same with the message headers like subject and probably from and to, when $edit_headers=yes, giving vim the original subject line with iso-8859-7 encoding and forcing it to fenc=iso-8859-7, after editing the reply it tries to iconv $charset -t <one of $send_charset> but the file encoding is != $charset, so the unreadable output. If the above assumptions are correct, I think that mutt should iconv not only the message body, but also the headers when $edit_headers=yes. D. -- PGP key 39A40276 at wwwkeys.eu.pgp.net key fingeprint: 9A0B 61C6 B826 4B73 69BB 972B C5E7 A153 39A4 0276
