I'm using version 3.2.9 64-bit. When I use a UTF-8 or ANSI file for the subject (-sf parameter), I get garbled text. If the file is UTF-16 (with a little-endian BOM), the text looks correct.
Version 3.2.6 didn't have this issue. Could this be related to the recent file detection changes?
Yes, this issue was finally exposed with the most recent release. I had not tested the -sf option, shame on me. There was a line of code that used the size of an array which held the contents of the subject file, rather than using the string length of the content that was read. This caused problems downstream in the code when it came time to detect Unicode (not UTF-8) characters.
The particular line has been replaced with correct code, and I will be getting an update released in the next day or two.
That sounds great -- thanks!
3.2.10 has been uploaded. The garbled subject line has been fixed, and is not sent as quoted mime unless necessary. This latter is something that occurred with 3.2.9.
I've confirmed that 3.2.10 correctly handles files in UTF-8 or either flavor of UTF-16. Many thanks for the very quick version update!