Subj : squirrel and M├╕├╕se
To   : mark lewis
From : Nicholas Boel
Date : Mon Jul 24 2017 15:22:54

Hello,

On Mon, 24 Jul 2017 10:46:56 -0400, Mark Lewis -> Nicholas Boel wrote:

 ml> that was more likely jamnntpd... it doesn't apply the message body
 ml> character set to the header data... nothing talks about doing that in
 ml> FTN stuffs... it was probably done by jamnntpd during the creation of
 ml> the article header... we won't mention that even on the 'net they don't
 ml> apply the body settings to the header... on the 'net, they do it, in
 ml> MIME, in the header field that's being special... we see it a lot in
 ml> spams with the name and/or subject fields being the main ""targets""...

Either way, it shouldn't happen. When a message arrives with a UTF-8 subject
line, it should not be translated. Especially when I have everything set here
to translate to - keep - and reply all with UTF-8 as well.

So what you're saying is the subject came in as UTF-8, but since the body was
us_ascii.. jamnntpd translated the subject to us_ascii as well? I have nothing
here in my configs that would tell it to do that.

To be more specific, his message arrived here with a readable subject line. I
could read the UTF-8 subject just fine. When I replied in Thunderbird, it still
 showed the subject as it was originally written. When I saved it, it was then
mangled.

I think remember seeing something in jamnntpd's code that when an ascii message
 comes in, not to translate it - even though it will change your CHRS kludge to
 whatever your charset is. Something's odd there, for sure.

Regards,
Nick

..... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
 * Origin: thePharcyde_ distribution system (1:154/10)

.