I have a strange sense of deja vu. Jen's articles'
Message-IDs include characters that, when transferred
to the References: header by pan, leave an article that
can't be read by pan.
This very article is an example, responding to:
Message-ID: <$g63dRgft$@checkmate.orgy.????>
(Isn't that just adorable? Jen can fuzz newsreaders -- the
world is their oyster!)
The potential for abuse can't be understated. They are
constructing articles for which naive responses,
using pan, aren't _readable_ by pan.
It's an active attack against people who
use pan2 as their newsreader.
I have a strange sense of deja vu. Jen's articles'
Message-IDs include characters that, when transferred
to the References: header by pan, leave an article that
can't be read by pan.
This very article is an example, responding to:
Message-ID: <$g63dRgft$@checkmate.orgy.????>
(Isn't that just adorable? Jen can fuzz newsreaders -- the
world is their oyster!)
The potential for abuse can't be understated. They are
constructing articles for which naive responses,
using pan, aren't _readable_ by pan.
It's an active attack against people who
use pan2 as their newsreader.
vallor wrote:
I have a strange sense of deja vu. Jen's articles' Message-IDs include
characters that, when transferred to the References: header by pan,
leave an article that can't be read by pan.
This very article is an example, responding to:
Message-ID: <$g63dRgft$@checkmate.orgy.????>
(Isn't that just adorable? Jen can fuzz newsreaders -- the world is
their oyster!)
The potential for abuse can't be understated. They are constructing
articles for which naive responses,
using pan, aren't _readable_ by pan.
It's an active attack against people who use pan2 as their newsreader.
You could just killfile the knucklehead. I don't see any of its crap
unless someone replies to it.
vallor wrote:
I have a strange sense of deja vu. Jen's articles'
Message-IDs include characters that, when transferred
to the References: header by pan, leave an article that
can't be read by pan.
This very article is an example, responding to:
Message-ID: <$g63dRgft$@checkmate.orgy.????>
(Isn't that just adorable? Jen can fuzz newsreaders -- the
world is their oyster!)
The potential for abuse can't be understated. They are
constructing articles for which naive responses,
using pan, aren't _readable_ by pan.
It's an active attack against people who
use pan2 as their newsreader.
You could just killfile the knucklehead. I don't
see any of its crap unless someone replies to it.
Steve <lammasland@gmail.com> wrote:
vallor wrote:
I have a strange sense of deja vu. Jen's articles' Message-IDs
include characters that, when transferred to the References: header
by pan, leave an article that can't be read by pan.
This very article is an example, responding to:
Message-ID: <$g63dRgft$@checkmate.orgy.????>
(Isn't that just adorable? Jen can fuzz newsreaders -- the world is
their oyster!)
The potential for abuse can't be understated. They are constructing
articles for which naive responses,
using pan, aren't _readable_ by pan.
It's an active attack against people who use pan2 as their
newsreader.
You could just killfile the knucklehead. I don't see any of its crap
unless someone replies to it.
Ditto. IMO he should be under Formosa Protection,
no good purpose is served by trying to engage him.
Steve <lammasland@gmail.com> wrote:
vallor wrote:
I have a strange sense of deja vu. Jen's articles' Message-IDs
include characters that, when transferred to the References: header
by pan, leave an article that can't be read by pan.
This very article is an example, responding to:
Message-ID: <$g63dRgft$@checkmate.orgy.????>
(Isn't that just adorable? Jen can fuzz newsreaders -- the world is
their oyster!)
The potential for abuse can't be understated. They are constructing
articles for which naive responses,
using pan, aren't _readable_ by pan.
It's an active attack against people who use pan2 as their
newsreader.
You could just killfile the knucklehead. I don't see any of its crap
unless someone replies to it.
Ditto. IMO he should be under Formosa Protection,
no good purpose is served by trying to engage him.
I have a strange sense of deja vu. Jen's articles'
Message-IDs include characters that, when transferred
to the References: header by pan, leave an article that
can't be read by pan.
This very article is an example [...]
cloakn3kcia4pnos.onion port 6697 sslgh0stAnon <<+++
cloakn3kcia4pnos.onion port 6697 sslgh0stAnon <<+++
On Thu, 14 Oct 2021 14:06:27 +0100, Sn!pe wrote:
Steve <lammasland@gmail.com> wrote:
vallor wrote:
I have a strange sense of deja vu. Jen's articles' Message-IDs
include characters that, when transferred to the References: header
by pan, leave an article that can't be read by pan.
This very article is an example, responding to:
Message-ID: <$g63dRgft$@checkmate.orgy.????>
(Isn't that just adorable? Jen can fuzz newsreaders -- the world is
their oyster!)
The potential for abuse can't be understated. They are constructing
articles for which naive responses,
using pan, aren't _readable_ by pan.
It's an active attack against people who use pan2 as their
newsreader.
You could just killfile the knucklehead. I don't see any of its crap
unless someone replies to it.
Ditto. IMO he should be under Formosa Protection,
no good purpose is served by trying to engage him.
I concur. I don't read him/her anymore.
cloakn3kcia4pnos.onion port 6697 sslgh0stAnon <<+++
vallor <vallor@cultnix.org> wrote:
I have a strange sense of deja vu. Jen's articles'
Message-IDs include characters that, when transferred
to the References: header by pan, leave an article that
can't be read by pan.
This very article is an example [...]
I don't use pan, but I can comment. The References header should not
include non-ASCII characters. Your message and this one has References containing only ASCII characters, although it contains a "=?UTF-8?Q"
sequence representing non-ASCII characters. An implementation might
replace the sequence with the Unicode characters it represents, which
I think is a bad idea (in the Subject header it can perhaps be useful,
but it should not be done in the References header). Some of the other follow-up messages just have question marks there instead, meaning that
the References header no longer matches. Let's see what happens with
this message; I am posting it with a intact References header.
Those who do use Pan perhaps should file a bug report (and/or fix it
if you know how).
I don't use non-ASCII characters or "=?UTF-8?Q" sequences in my message
IDs, and I would hope that nobody does, but apparently some people do. Although if you want to provide testing, you could perhaps use the
newsgroup defined for testing this things instead. In addition to testing clients, there is also the case of server testing, in case server software reads the Message-ID and/or References header and what it does with it if
it contains such things. (My own server software does not check for ASCII sequences representing non-ASCII characters, but does reject any non-ASCII characters entered directly in the message ID, and will refuse to post the message in that case.)
Here is a copy of the References header of this message (hopefully won't
get mangled), in case this helps anyone (due to the actual References:
header being mangled):
References: <$g63dRgft$@checkmate.orgy.=?UTF-8?Q?=F0=9F=8F=B3=EF=B8=8F=E2=80=8D=F0=9F=8C=88?=> <isqf6uF9ch0U2@mid.individual.net>
(Note that it contains a space followed by a tab, since it is a copy of
the original References header with the original Message-ID appended.)
The problem could become even worse if it contains a "=?UTF-8?Q?" sequence which represents ASCII characters, I suppose? (Even if so, I am not going
to post such a message, except possibly to a testing-only newsgroup.)
cloakn3kcia4pnos.onion port 6697 sslgh0stAnon <<+++
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 225:07:54 |
Calls: | 6,623 |
Calls today: | 5 |
Files: | 12,171 |
Messages: | 5,318,597 |