[prev in list] [next in list] [prev in thread] [next in thread] 

List:       inn-workers
Subject:    Re: Enforcing NNTP-Posting-Host
From:       Julien_ÉLIE <julien () trigofacile ! com>
Date:       2008-04-15 17:51:09
Message-ID: F60D7FF1A9B741F49B17B7425927CDC3 () Iulius
[Download RAW message or body]

Hi Marco,

>> Do you think it is a good idea to allow the setting of NNTP-Posting-Host?
>> Normally, it should be the IP of the client, even if it is private...
>
> I believe that using filter_nnrpd.pl is a reasonable solution.

That is also true (furthermore, it is very easy to do).
And it seems better than changing the addnntppostinghost variable from BOOL
to STRING whose values can also be "true" or "false".


I think we can take the opportunity to greatly improve the samples provided
with filter_nnrpd.pl (and also filter_innd.pl/py nnrpd_access/auth/*, etc.).
It can be useful for people.

For instance, specifying a couple of lines for NNTP-Posting-Host and
how $modify_headers works.
Samples for different return values ('DROP', 'SPOOL', '', 'article rejected')
could also be interesting.

-- 
Julien ÉLIE

« Ma parole... Vous êtes soûls ! Heu ! Sourds... » (Astérix) 


[prev in list] [next in list] [prev in thread] [next in thread]