Subj : newsutil.js - content-typ
To   : Ash-Fox
From : Digital Man
Date : Mon Nov 19 2007 05:40 pm

  Re: newsutil.js - content-type and binary usenet groups.
  By: Ash-Fox to DOVE-Net.Synchronet_JavaScript on Mon Nov 19 2007 01:00 pm

 > Greetings,
 > 
 > I've noticed that Synchronet's NNTP server has 'weird' issues when mirroring
 > binary groups. Upon further investigation I found that the 'default'
 > content-type which was being inserted by newsutil.js was causing binary
 > attachments in the messages to appear as text.
 > 
 > writeln("Content-Type: text/plain; charset=IBM437");

The line is only inserted (from newsutil.js) if the original message does not
contain a specified Content-Type header field. If you're mirroring between NNTP
servers, then I would expect the original messages to have this Content-Type
header field.

 > If I comment this line out, news readers suddenly don't have a issue
 > figuring out there is a attachment in the message. I know this line is
 > important as it assumes the messages are in the old IBM437 charset which is
 > more compatible with BBS messages.
 > 
 > I have read through RFC 2049 (http://www.ietf.org/rfc/rfc2049.txt) and try
 > as might. No matter what content-type I specified, the messages did not
 > display correctly.
 > 
 > For this reason I'm trying to figure out a workaround that would work. Such
 > as, somehow marking the messages that newslink imports
 > as 'non-charsettable' or such. Unfortunately this isn't going too well and
 > wondered if anyone had any ideas on this issue.

Can you check if the original messages (on USENET?) have the Content-Type
header field or not?

                                       digital man (xbox-live: digitlman)

Snapple "Real Fact" #39:
An ant's smell is stronger then a dog's.
Norco, CA WX: ---.-øF, --% humidity, NaN mph --- wind, --.-- inches rain/24hrs

.