Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. bad_messageid (Chris Knipe)
2. Re: bad_messageid (Chris Knipe)
3. Re: bad_messageid (Julien ?LIE)
4. Re: bad_messageid (Russ Allbery)
----------------------------------------------------------------------
Message: 1
Date: Wed, 17 Feb 2016 17:27:33 +0200
From: Chris Knipe <[email protected]>
To: [email protected]
Subject: bad_messageid
Message-ID:
<CA+4TWFu5hvHGygS6r=bjcc-sd4o0abdtojpf+ocae4v3ooc...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Guys,
Is there a way to disable these checks in incoming messages, or to relax it?
I'm getting thousands of these, just as an example
bad_messageid <part1553of1353.kbi$KFf0LMR4$3&IW1wy@[email protected]>
Whilst I understand that, technically yes, the message-id is bad (I receive
mostly double @'s or double .'s), Diablo, and a lot of other usenet servers
accept these messages. They are freely available on all of usenet, not
running INN it seems...
--
Regards,
Chris Knipe
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20160217/f9092ec5/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 17 Feb 2016 18:06:27 +0200
From: Chris Knipe <[email protected]>
To: [email protected]
Subject: Re: bad_messageid
Message-ID:
<ca+4twfvd4+y60dxfeznkvudvq94tf0anm3rpuwa95numttz...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
Actually came to realize after I've hit sent, there's no point in hiding
the message-ids... But oh well,
bad_messageid <part197of219.2VCPu4v4BzKrvM9AIwEW@[email protected]>
bad_messageid <part203of219.9$2Z5eoUYMT&HHfk83tU@[email protected]>
bad_messageid <part170of219.aztwXxLu3edYXTaQJTC2@[email protected]>
bad_messageid <part114of219.LlSblPRBqQMeV5gQnqkm@[email protected]>
bad_messageid <part82of219.LlSblPRBqQMeV5gQnqkm@[email protected]>
bad_messageid <part138of219.vA&O8bnz7R2cYJHFZUuS@[email protected]>
Just a few (GMT+2) . This is the latest version of INN (2.6.4 I believe)
Have rejected over 300K of these from one feed already out of some 380K
offers.
On Wed, Feb 17, 2016 at 5:27 PM, Chris Knipe <[email protected]> wrote:
> Hi Guys,
>
> Is there a way to disable these checks in incoming messages, or to relax
> it?
>
> I'm getting thousands of these, just as an example
>
> bad_messageid <part1553of1353.kbi$KFf0LMR4$3&IW1wy@[email protected]>
>
> Whilst I understand that, technically yes, the message-id is bad (I
> receive mostly double @'s or double .'s), Diablo, and a lot of other usenet
> servers accept these messages. They are freely available on all of usenet,
> not running INN it seems...
>
>
> --
>
> Regards,
> Chris Knipe
>
--
Regards,
Chris Knipe
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20160217/567dbf9b/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 17 Feb 2016 22:47:53 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: bad_messageid
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Hi Chris,
> Is there a way to disable these checks in incoming messages, or to
> relax it?
It is currently impossible to disable these checks.
As they have been present for more than 20 years (INN 1.5.1 was already
checking the syntax of message-IDs), I am not very appealed to the idea
of relaxing them now.
> bad_messageid
> <part1553of1353.kbi$KFf0LMR4$3&IW1wy@[email protected]>
>
> Whilst I understand that, technically yes, the message-id is bad (I
> receive mostly double @'s or double .'s), Diablo, and a lot of other
> usenet servers accept these messages. They are freely available on
> all of usenet, not running INN it seems...
Do you know the name(s) of the newsreader(s) that posted these articles?
I believe it would be better to contact their authors so that they fix
the syntax of the message-IDs they generate).
We should not encourage them to go on creating articles that generate
interoperability issues. (I bet other news servers than INN also reject
such articles.)
--
Julien ?LIE
? The most effective way to remember your wife's birthday is to forget
it once? ? (Nash)
------------------------------
Message: 4
Date: Wed, 17 Feb 2016 17:09:30 -0800
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: bad_messageid
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Julien ?LIE <[email protected]> writes:
> It is currently impossible to disable these checks.
> As they have been present for more than 20 years (INN 1.5.1 was already
> checking the syntax of message-IDs), I am not very appealed to the idea of
> relaxing them now.
Yeah, I've resisted relaxing that check for as long as I've been involved
in INN. The posters that are generating those message IDs are completely
broken, and they're only being propagated by servers that don't make any
attempts to enforce standards compliance.
It's one thing if syntax errors affect fields that are primarily for human
consumption, but since the message ID is the unique database key for
netnews, I don't think it's a good idea to allow blatant syntax errors.
It's usually always the same thing: double @-signs, by something posting
YEnc binary crap. My guess is that there's some binary autoposter that
doesn't produce syntactically valid articles.
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
End of inn-workers Digest, Vol 81, Issue 3
******************************************
