Discussion:
mail2news bug: 10,11,12, 13,14,15, 16,17,18, 19,20,21
Add Reply
Nomen Nescio
2017-06-23 00:42:47 UTC
Reply
Permalink
Raw Message
Mail2News software developers,

within at least the Subject: header argument after each comma directly
followed by any printable character the m2n unit inserts a separating
whitespace.

This posting was sent by OmniMix 2.4.6 (exit dizum =>
***@m2n.mixmin.net) including the headers

| Subject: mail2news bug: 10,11,12, 13,14,15, 16,17,18, 19,20,21
| X-Test: 10,11,12, 13,14,15, 16,17,18, 19,20,21

With QSL 1.1.2 I got similar results.

Mail delivery works as expected, it's only about Usenet postings. AFAICS
***@dizum.com and ***@m2n.mixmin.net 'normalize' comma
separation, whereas frell and frell2, which may have their own m2n
strategy, get it right by not altering the original text.

TIA for fixing that bug
Anonymous
2017-06-23 09:48:35 UTC
Reply
Permalink
Raw Message
Post by Nomen Nescio
Mail2News software developers,
within at least the Subject: header argument after each comma directly
followed by any printable character the m2n unit inserts a separating
whitespace.
This posting was sent by OmniMix 2.4.6 (exit dizum =>
| Subject: mail2news bug: 10,11,12, 13,14,15, 16,17,18, 19,20,21
| X-Test: 10,11,12, 13,14,15, 16,17,18, 19,20,21
With QSL 1.1.2 I got similar results.
Mail delivery works as expected, it's only about Usenet postings. AFAICS
separation, whereas frell and frell2, which may have their own m2n
strategy, get it right by not altering the original text.
TIA for fixing that bug
Now it's working correctly, interesting!

I had a series of tests at alt.test with different results, like
Message-ID: <***@dizum.com>.

Wait and see.
Fakey's Puppy Whistle Holder Emeritus 🐶笛
2017-06-23 19:01:20 UTC
Reply
Permalink
Raw Message
On Fri, 23 Jun 2017 09:48:35 +0000 (UTC), LO AND BEHOLD; "Anonymous
<***@remailer.paranoici.org>" determined that the following was of
great importance and subsequently decided to freely share it with us in
Post by Anonymous
Mail2News software developers, within at least the Subject: header
argument after each comma directly followed by any printable character
the m2n unit inserts a separating whitespace. This posting was sent by
headers | Subject: mail2news bug: 10,11,12, 13,14,15, 16,17,18,
19,20,21 | X-Test: 10,11,12, 13,14,15, 16,17,18, 19,20,21 With QSL
1.1.2 I got similar results. Mail delivery works as expected, it's only
and frell2, which may have their own m2n strategy, get it right by not
altering the original text. TIA for fixing that bug
Now it's working correctly, interesting!
perhaps it has something to do with that cobbled-together broken newsreader of yours.
--
THIS SPACE FOR RENT


-

"You just made puppy whistle's sig line longer." - Janithor

-

"If I have a complaint about the (Southern Poverty) Law Center's description (of the alt-right movement), it is the phrase "heavy use of social media," which implies the alt-right is a real-world movement which uses a lot of social media. This is backwards: it is an online movement which occasionally appears in the real world. Where it gets punched." - Jason Rhode

-

"I think we should destroy every last fucking mosque in America." - "Checkmate, DoW #1" <***@The.Edge> proves for us that white males are violent in Message-ID: <***@news.altopia.com>

-

Golden Killfile, June 2005
KOTM, November 2006
Bob Allisat Memorial Hook, Line & Sinker, November 2006
Special Ops Cody Memorial Purple Heart, November 2006
Special Ops Cody Memorial Purple Heart, September 2007
Tony Sidaway Memorial "Drama Queen" Award, November 2006
Busted Urinal Award, April 2007
Order of the Holey Sockpuppet, September 2007
Barbara Woodhouse Memorial Dog Whistle, September 2006
Barbara Woodhouse Memorial Dog Whistle, April 2008
Tinfoil Sombrero, February 2007
AUK Mascot, September 2007
Putting the Awards Out of Order to Screw With the OCD Fuckheads, March 2016
Nomen Nescio
2017-06-24 00:29:00 UTC
Reply
Permalink
Raw Message
Post by Nomen Nescio
Mail2News software developers,
within at least the Subject: header argument after each comma directly
followed by any printable character the m2n unit inserts a separating
whitespace.
This posting was sent by OmniMix 2.4.6 (exit dizum =>
| Subject: mail2news bug: 10,11,12, 13,14,15, 16,17,18, 19,20,21
| X-Test: 10,11,12, 13,14,15, 16,17,18, 19,20,21
With QSL 1.1.2 I got similar results.
Mail delivery works as expected, it's only about Usenet postings. AFAICS
separation, whereas frell and frell2, which may have their own m2n
strategy, get it right by not altering the original text.
TIA for fixing that bug
Does it only happen with longer, folded header entries?

| Subject: Re: mail2news bug: 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21 ...
| X-Test: Numbers to follow ... 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21 ...

And, I know, this isn't a test group. ;)
Anonymous
2017-06-24 21:16:44 UTC
Reply
Permalink
Raw Message
Post by Nomen Nescio
Post by Nomen Nescio
Mail2News software developers,
within at least the Subject: header argument after each comma directly
followed by any printable character the m2n unit inserts a separating
whitespace.
This posting was sent by OmniMix 2.4.6 (exit dizum =>
| Subject: mail2news bug: 10,11,12, 13,14,15, 16,17,18, 19,20,21
| X-Test: 10,11,12, 13,14,15, 16,17,18, 19,20,21
With QSL 1.1.2 I got similar results.
Mail delivery works as expected, it's only about Usenet postings. AFAICS
separation, whereas frell and frell2, which may have their own m2n
strategy, get it right by not altering the original text.
TIA for fixing that bug
Does it only happen with longer, folded header entries?
| Subject: Re: mail2news bug: 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21 ...
| X-Test: Numbers to follow ... 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21 ...
Obviously is does. To sum it up, the m2n gateways ***@dizum.com
and ***@m2n.mixmin.net corrupt header entries containing commas
while folding them.

It would be great if that could be fixed.

Zax, any thoughts?
Zax
2017-06-26 09:34:42 UTC
Reply
Permalink
Raw Message
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sat, 24 Jun 2017 21:16:44 +0000 (UTC), Anonymous wrote in
Post by Anonymous
Post by Nomen Nescio
Post by Nomen Nescio
Mail2News software developers,
within at least the Subject: header argument after each comma directly
followed by any printable character the m2n unit inserts a separating
whitespace.
This posting was sent by OmniMix 2.4.6 (exit dizum =>
| Subject: mail2news bug: 10,11,12, 13,14,15, 16,17,18, 19,20,21
| X-Test: 10,11,12, 13,14,15, 16,17,18, 19,20,21
With QSL 1.1.2 I got similar results.
Mail delivery works as expected, it's only about Usenet postings. AFAICS
separation, whereas frell and frell2, which may have their own m2n
strategy, get it right by not altering the original text.
TIA for fixing that bug
Does it only happen with longer, folded header entries?
| Subject: Re: mail2news bug: 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21 ...
| X-Test: Numbers to follow ... 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21 ...
while folding them.
It would be great if that could be fixed.
Zax, any thoughts?
I'm struggling to reproduce the behaviour you describe. In fact, in my
tests, no folding at all takes place. Check out the short test thread
beginning with
<***@mixmin.net> in alt.testing.testing.

The mail2news gateway software doesn't perform any deliberate header
folding, it's handled by the email library. Specifically,
email.as_string(). When I use this directly in Python, it seems to wrap
at a whitespace close to the max line length.
... Subject: Testing header folding
... Foldit: This is a long header, complete with a comma, some spaces,
and a number or two; 1,2,3.
...
... Payload space"""
Post by Anonymous
Post by Nomen Nescio
Post by Nomen Nescio
m.as_string()
'From: Steve Crook <***@mixmin.net>\nSubject: Testing header
folding\nFoldit: This is a long header, complete with a comma, some
spaces, and a\n number or two; 1,2,3.\n\nPayload space'

As you can see in the above test, a \n has been inserted between "a" and
" number".

Can you post an example to a test group and let me know the Message-ID?

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEYtRzDvCkhhVOX3JsJqfI5MW644EFAllQ1ScACgkQJqfI5MW6
44GOVQ//Zt2gp3qBVFDGVUTrBYwMqqE9W7+blmN1LWEgpioQkvZsm6AHo0BU25WY
gCSUr2hv+IYuN5pIlk99bTDS48NhMow4o0t3ajssg1+LS02t6s6RVINjcykQMrsV
+iULuyBOHxmXAMpSgj8NZ0V5gf372CW/u2mPX7pVKqIfsU11jqSJ0SYp0qU57k5Y
3f/ZQ6U51l7XWqvKzNogWSMGseehf0NNFEAxCOaZvMZL5kg9kwuZlf3wc/05oZ3h
ocgiX5nZyW1iFYrO5XNbMuqH+C6Zm4Etqyv6ODMK+aNiEIEJkxn+2sW7Y1vJsx1g
5wdvQgdA3aLqPWub6McXwND7mWZZXlgBMU5ABcbvTEwVAP2jf2KWdhJbAxS9z2vo
W1UIsxP81z8Kdec56oHMTknPpY1l1FCx3OusfPLo4MUmoVpv9SlYioOAvXgIjH5Z
MgeeceRvsbBkpftvbz+EWrft0VLHKuAp6WZdL4toAdPrjHH1qxlUAokgRgZlBYEI
n6Bqr8hrWXBktpJgI2YmapkRkbzARYdNvYDnOxfZDxEZZZ+tWMbT0RH9cI5V8LSX
0lJq13KN+qo5N9DtGhz8wGJm0fk4NEkUECJGt/Sxy5xM9AwGEKkqq6ujX9U3CYmD
kC0Avt+ax+ihhS2LOqiXzRvO95JXlXUJN+1vJVBWEJP5I/JRnnU=
=HQzo
-----END PGP SIGNATURE-----
--
pub 1024D/228761E7 2003-06-04 Steven Crook <***@mixmin.net>
Key fingerprint = 1CD9 95E1 E9CE 80D6 C885 B7EB B471 80D5 2287 61E7
sub 4096R/BE3EFAA7 created: 2014-11-14 expires: 2016-11-13 usage: S
Anonymous
2017-06-26 17:33:10 UTC
Reply
Permalink
Raw Message
Post by Zax
On Sat, 24 Jun 2017 21:16:44 +0000 (UTC), Anonymous wrote in
Post by Anonymous
Post by Nomen Nescio
Post by Nomen Nescio
Mail2News software developers,
within at least the Subject: header argument after each comma directly
followed by any printable character the m2n unit inserts a separating
whitespace.
This posting was sent by OmniMix 2.4.6 (exit dizum =>
| Subject: mail2news bug: 10,11,12, 13,14,15, 16,17,18, 19,20,21
| X-Test: 10,11,12, 13,14,15, 16,17,18, 19,20,21
With QSL 1.1.2 I got similar results.
Mail delivery works as expected, it's only about Usenet postings. AFAICS
separation, whereas frell and frell2, which may have their own m2n
strategy, get it right by not altering the original text.
TIA for fixing that bug
Does it only happen with longer, folded header entries?
| Subject: Re: mail2news bug: 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21 ...
| X-Test: Numbers to follow ... 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21 ...
while folding them.
It would be great if that could be fixed.
Zax, any thoughts?
I'm struggling to reproduce the behaviour you describe. In fact, in my
tests, no folding at all takes place. Check out the short test thread
beginning with
The mail2news gateway software doesn't perform any deliberate header
folding, it's handled by the email library. Specifically,
email.as_string(). When I use this directly in Python, it seems to wrap
at a whitespace close to the max line length.
... Subject: Testing header folding
... Foldit: This is a long header, complete with a comma, some spaces,
and a number or two; 1,2,3.
...
... Payload space"""
Post by Anonymous
Post by Nomen Nescio
Post by Nomen Nescio
m.as_string()
folding\nFoldit: This is a long header, complete with a comma, some
spaces, and a\n number or two; 1,2,3.\n\nPayload space'
As you can see in the above test, a \n has been inserted between "a" and
" number".
Was the folding done by your mail client or by the m2n gateway?

Here MM encodes unfolded header lines, which I expect to be sent still
unfolded from the exit remailer to the m2n gateway.
Post by Zax
Can you post an example to a test group and let me know the Message-ID?
I sent a few self-explaining test postings to alt.testing.testing.

Thanks
Anonymous
2017-06-28 21:51:50 UTC
Reply
Permalink
Raw Message
Post by Anonymous
I sent a few self-explaining test postings to alt.testing.testing.
Did you have a look at message
<***@remailer.paranoici.org>?

With "Mixmaster input (exit banana):" the banana remailer, which is
a middle only remailer, must have remailed the message to paranoia.
In the course of that transmission both headers even get truncated.

From

| Subject: Mail2news bug: 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21, 22,23,24, 25,26,27 ...
| X-Test: Mail2news bug: 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21, 22,23,24, 25,26,27 ...

to

| Subject: Mail2news bug: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
| 17, 18, ...
| X-Test: Mail2news bug: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
| 17, 18, 1 ...

Mixmaster remailers are seriously broken and nobody cares - at least
as long as they suffice for sending threats and slander.
Fritz Wuehler
2017-07-01 16:07:01 UTC
Reply
Permalink
Raw Message
Post by Anonymous
Post by Anonymous
I sent a few self-explaining test postings to alt.testing.testing.
Did you have a look at message
With "Mixmaster input (exit banana):" the banana remailer, which is
a middle only remailer, must have remailed the message to paranoia.
In the course of that transmission both headers even get truncated.
From
| Subject: Mail2news bug: 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21, 22,23,24, 25,26,27 ...
| X-Test: Mail2news bug: 1,2,3, 4,5,6, 7,8,9, 10,11,12, 13,14,15, 16,17,18, 19,20,21, 22,23,24, 25,26,27 ...
to
| Subject: Mail2news bug: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
| 17, 18, ...
| X-Test: Mail2news bug: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
| 17, 18, 1 ...
Mixmaster remailers are seriously broken and nobody cares - at least
as long as they suffice for sending threats and slander.
Yesterday the German parliament passed the Netzwerkdurchsetzungsgesetz.

https://www.thelocal.de/20170630/germany-imposes

It's a law that supports social media platforms in removing user
contributions which they think might be offending in any way. That
governmental legitimation of corporate mind control creates an enormous
extralegal force seriously undermining our democracy.

In Germany free speech now is at Facebook's and Google's mercy.

With the censorship-resistant Usenet becoming more and more important
it's really time to bring the remailer system up to scratch. Please fix
all these bugs. The future is yours, we need your services!

Loading...