Sujet : Re: inn, cleanfeed and ipv6
De : deletethis (at) *nospam* invalid.lan (nb)
Groupes : news.software.nntpDate : 10. Apr 2025, 12:48:27
Autres entêtes
Organisation : Ausics - https://newsgroups.ausics.net
Message-ID : <q4o6917-432q-50q0-rro-o019rnsprpr3@vainyvq.yna>
References : 1 2 3 4
greetings from Basse Terre
On Wed, 9 Apr 2025, Ray Banana wrote:
* nb wrote:
>
>
On Tue, 8 Apr 2025, Nigel Reed wrote:
I know I was shown inns cleanfeed few years back and its totally
different from dnews's cleanfeed which dnews has had internally since
day dot, I'm suspecting since the peers who accepted it, do binaries,
it might be in the detection of such messages, and is misclassifying
ipv6 addresses - but as not an inn operator, I'm only guessing.
>
JFTR: Cleanfeed is not part of INN (INN provides just provides a Perl hook
I'm aware, but everyone who runs inn seems to use, AFAIK, Steve's version, I might be wrong tho.
Do you mean the IPv6 protocol or just string representations of bare
IPv6 addresses contained somewhere in the article's headers?
In article body, not headers. our news server does not use "6"
I know I've put a "6" address in posts before and no issues, perhaps it just didn't like that one, or the localhost version, together in same post /shrugs/
I have a test script I wrote years ago to disprove to others our server
was eating their posts, it comes in handy for uses like this too, it
checks 10 or 11 open servers and only ours had the article, as I'm away
for 10 days I can really run it and paste the outputs.
>
Does your script print the error code and reason it receives from the
misbehaving servers in response to the TAKETHIS command? That might indeed
shed some light on this issue.
no, the script only tests in reader mode, the takethis errors I get from dnews' logs.
The peers that reject your articles should have entries in their logs
showing the reason for rejecting the article (e.g. "439 Misplaced binary").
I was planning when I get back to email one of the text inn peers I know responds to email, and ask what inn logs say for the MID
anyways, off trekking out of range for a few days, good to see Gabx seems to have fixed his problem now by what he's posted, does inn really not
default to listen to "6", and that you have to quote the address specifically,
I find that strange, when we were looking at inn to replace dnews I don't
recall that, anyway, until we can convert the backend to an inn cnfs format,
that transition wont be happening :)
cheers