[leafnode-list] Re: illegal headers

[Matthias Andree]

Am 10.08.2013 17:43, schrieb thufir:
> On Wed, 07 Nov 2012 19:04:05 +0000, Whiskers wrote:
> 
>> On Wed, 7 Nov 2012 06:28:17 +0000 (UTC) thufir
>> <hawat.thufir at gmail.com>
>> wrote:
>>
>>> when leafnode finds illegal headers:
>>>
>>>
>>> root at dur:~# article /var/spool/news/comp/os/linux/advocacy/6401
>>> contained illegal headers: non-printable characters in headers (relaxed
>>> check allows for iso-8859*)
>>>
>>>
>>>
>>> does it remove that article from the spool?
>>
>> What does that file look like?  Does it exist?  Is it mentioned in
>> /var/log/news.log (or whatever your news log file is)?  What does the
>> entry for that article number in
>> /var/spool/news/comp/os/linux/advocacy/.overview look like?
> 
> I see:
> 
> 
> root at dur:~# article /var/spool/news/comp/os/linux/advocacy/94 contained 
> illegal headers: non-printable characters in headers (relaxed check 
> allows for iso-8859*)
> 
> when running fetchnews
> 
> but can't see anything in any of the log files about illegal headers.
> 
> There's no article 94 in /var/spool/news/comp/os/linux/advocacy/.overview
> 
> 
> Clearly leafnode rejects the article because the header is bad, right?

Yup. This is the code that causes this assessment:

> if ((c != '\t' && c < ' ') || (c > 126 && c < 160)) {
>     *e = "non-printable characters in headers (relaxed check allows for iso-8859*)";
>     return 0;
> }

So there were control characters in the header. This is decided when the
XOVER information gets calculated, and causes the offending articles to
be removed from the spool, possibly also when running texpire should the
corruption happen later.

You need to set debugmode in the leafnode configuration, and enable your
syslogger to capture news facility messages with "debug" severity, to
see them in the log.

HTH
Matthias