Re: yEnc-encoded articles in newsgroups

Thus spake Julien ÉLIE <iulius@nom-de-mon-site.com.invalid>
[...]

Sounds great with a one-line list of newsgroups, separated with a
space, thanks.

Done now.

FYI, it will be useful with the perl-nocem program shipped with the
next release of INN (2.7.2) as I have added the possibility to only
process a subset of Message-IDs within a notice, according to specific
rules by the news admin (sort of a local function called like in
cleanfeed.local).  Having the whole list of newsgroups will permit for
instance to process Message-IDs of articles posted to a newsgroup
actually carried by the server.  Or more complex cases like processing
NoCeM notices for only a subset of newsgroups (if someone does not
want to cancel anything in some newsgroups) or not taking into account
notices from "john" or of a given type, except for a subset of
newsgroups.

Is that the -i option in perl-nocem (I'm using INN 2.8 snapshots)?

I think some newsgroups should be marked as allowing binaries or HTML.
<CAOLa=ZSo7ngBUxkfR+EEojhr4a-mM+3=f-P1H36hnhJukEqGVA@mail.gmail.com>
in linux.kernel.git was caught in the Bot-misplaced_binary filter but
looks like a valid article.

My filter makes use of the is_binary () function in Cleanfeed, which in
turn relies on some configuration variables.  The problem in the case of
the linux.kernel.git messages is that some of them have a Content-Type
of multipart/mixed with the PGP signature included as a Base64 encoded
attachment.

Is it an issue to open upstream to Cleanfeed, to fix the is_binary()
function?

Cleanfeed from Github does not handle Content-Type: multipart/mixed
except for HTML, so it was my own fault, obviously. Quick fix applied
now, is_binary() still misses lots of binary attachments encapsulated in
separate entities.
I think I will make Cleanfeed more Mime-aware (MIME::Parser) and add
local config variables for allowed/disallowed mime types when I find the time.

--
Пу́тін — хуйло́
https://www.eternal-september.org