From: noel <deletethis@invalid.lan>
Subject: inn, cleanfeed and ipv6
Newsgroups: news.software.nntp
User-Agent: Pan/0.141 (Tarzan's Death; 168b179 git.gnome.org/pan2)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
NNTP-Posting-Host: news.ausics.net
Message-ID: <67f47ca5$1@news.ausics.net>
Date: 8 Apr 2025 11:32:21 +1000
Organization: Ausics - https://newsgroups.ausics.net
Lines: 24
X-Complaints: abuse@ausics.net
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.bbs.nz!news.ausics.net!not-for-mail
Bytes: 1985

I've had a few reports of select users posts not getting out to all 
servers, and experienced it myself in a group last night, running one of 
my scripts that checks open servers, verified my suspicions, there seems 
to be something in the cleanfead script inn servers not liking (all?) 
ipv6 addresses.

I resent my message 3 times, and inn servers declined the takethis every 
time, I removed only the ipv6 address in it, and the message was taken by 
the peers who operate inn, I asked 2 of who complained about this I know 
are not dummies to try it, same exact message, resend, wait an hour then 
resend removing only ipv6 address, they reported back to me this morning 
there ipv6-less messages can be seen on the inn based servers. 

all the ipv6 addresses -mine and the examples they sent me, were all 
different, nowhere near each other entirely. Now I know I've seen some in 
the past, I've sent some in the past that have propogated, perhaps its 
not all address es that trigger this.

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.