Hi there, up to today I had just one signature file in the plain old place ~/.signature which I edited on the system I used mutt. For my other mail clients I have a bunch of different signature files in a VCS to use the same files with different clients (actually several instances of Mozilla Thunderbird). I recently took my old mutt config from an ancient server to a Debian squeeze with recent mutt 1.5.20. Everything works fine so far, my kudos to the mutt developers and Debian package maintainers.
Today I wanted to integrate the above mentioned signature files in mutt and switch between them with folder-hooks. It took quite some time to find out the right strings to match the folders, but I could solve that. Now the following problem occurs. The signature files start with the UTF-8 byte order mark, which is no problem for current editors (Vim, Notepad++) and Thunderbird itself. My mutt calls Vim as mail editor and now Vim shows me this BOM character as follows (I'm actually just typing this in Vim): 24 <feff>Alexander Dahl, Staff Engineer This is the same signature you should see below and you should also find this special character in it. To cut a long story short: which part in my toolchain causes this? I suppose mutt should strip this BOM character before adding the signature file to the empty mail before opening this with Vim, but I'm not entirely sure if this is right. If yes, should I file a bug? Greets Alex -- Alexander Dahl, Staff Engineer NTNU Nanolab -- http://www.ntnu.no/nanolab Norwegian University of Science and Technology (NTNU)
pgpinjUkgxQHo.pgp
Description: PGP signature
