From Newsgroup: alt.privacy

Any average Usenet user can use QSL. There's no way the average non-
tech user can begin to figure out all that supposedly anon stuff
posted by others in a.p.a-s.

Template used for this post:

Fcc: anon
Host: sec3
From: anonymous@anonymous.com
From: QSLUser
Chain: middleman,*,frell; copies=3;
To: mail2news@dizum.com, mail2news@neodome.net
Newsgroups: alt.privacy.anon-server, alt.privacy
Subject: QSL Still WORKS!

SMTP Server: mailrelay.sec3.net
Port: 587
TLS
No Authentivation

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy

Fritz Wuehler wrote:

Any average Usenet user can use QSL. There's no way the average non-
tech user can begin to figure out all that supposedly anon stuff
posted by others in a.p.a-s.

Template used for this post:

Fcc: anon
Host: sec3
From: anonymous@anonymous.com
From: QSLUser
Chain: middleman,*,frell; copies=3;
To: mail2news@dizum.com, mail2news@neodome.net
Newsgroups: alt.privacy.anon-server, alt.privacy
Subject: QSL Still WORKS!

SMTP Server: mailrelay.sec3.net
Port: 587
TLS
No Authentivation

Only <5 users are using QSL in the United States...

Can QSL MIME base64 encode the Subject: content, in
case UTF-8 characters are used? Mixmaster 3.1 can't
handle properly folded MIME base64 Subject: content
and removes half of the Subject line... Has Richard
fixed this, from Elvis's Mixmaster 3.1?
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy

On Tue, 03 Feb 2026 21:08:56 +0100, you wrote:

Fritz Wuehler wrote:

Any average Usenet user can use QSL. There's no way the average non-
tech user can begin to figure out all that supposedly anon stuff
posted by others in a.p.a-s.

Template used for this post:

Fcc: anon
Host: sec3
From: anonymous@anonymous.com
From: QSLUser
Chain: middleman,*,frell; copies=3;
To: mail2news@dizum.com, mail2news@neodome.net
Newsgroups: alt.privacy.anon-server, alt.privacy
Subject: QSL Still WORKS!

SMTP Server: mailrelay.sec3.net
Port: 587
TLS
No Authentivation

Only <5 users are using QSL in the United States...

He shows immediately in the above what a lying suck he is.

Can QSL MIME base64 encode the Subject

Who cares about the Subject? Do you actually think some crook is
going to use a Subject such as: "I've decided to rob McDonalds
tomorrow night..."

case UTF-8 characters are used?

An average user of QSL doesn't need to know what the F'k a UTF
character is. Only pretentious tekkies discuss stuff like "UTF-8
characters".

Mixmaster 3.1 can't
handle properly folded MIME base64 Subject: content
and removes half of the Subject line... Has Richard
fixed this, from Elvis's Mixmaster 3.1?

Like the average Usenet poster needs to know what the hell a "folded
MIME base64" whatever is. Keep a QSL Subject line a max of 80
characters and it won't screw up the Subject line. Who needs more
than that? It's the Subject line, fool, It's not intended to be the
same length as the body message, nor the length of a 5,000 word short
story. (But then you modern feebs don't know what a "story" is if it
doesn't come attached with a Youtube URL.)

Elvis or no Elvis, there is no valid mention anywhere as to QSL being
hacked. Outside of the pgp/MIME e-fail problem, which can be
avoided by typing and encrypting your e-mail message outside of your
e-mail program, QSL pgp is safe.

Of course, if you are a professional criminal or terrorists, you
aren't going to fully trust any anon program. But as far as the
average QSL user's fear of troublemakers using their id from posts to
cause more problems, QSL is TOTALLY safe.

And to say again, Time is the true arbiter of software security. The
new crap you and others proclaim to be invincible for anon security
can only be proven over time, as has QSL and pgp.

In closing, STFU!

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy

Fritz Wuehler wrote:

Like the average Usenet poster needs to know what the hell a "folded
MIME base64" whatever is. Keep a QSL Subject line a max of 80
characters and it won't screw up the Subject line. Who needs more
than that? It's the Subject line, fool, It's not intended to be the
same length as the body message, nor the length of a 5,000 word short
story. (But then you modern feebs don't know what a "story" is if it
doesn't come attached with a Youtube URL.)

Why are you so stupid? Ok, you are a U.S. citizen, which explains a lot!

FYI: Subject: lines made outside the United States can become longer
and are automatically MIME base64 encoded (and maybe folded) if the
line contains umlauts, accents, etc. But you don't know that, because
your little world revolves only around the United States! Ask a native
American how this works, because he can explain RFC 2047 to you!


--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy

Radio Eriwan wrote:

Fritz Wuehler wrote:

Like the average Usenet poster needs to know what the hell a "folded
MIME base64" whatever is. Keep a QSL Subject line a max of 80
characters and it won't screw up the Subject line. Who needs more
than that? It's the Subject line, fool, It's not intended to be the
same length as the body message, nor the length of a 5,000 word short
story. (But then you modern feebs don't know what a "story" is if it
doesn't come attached with a Youtube URL.)

Why are you so stupid? Ok, you are a U.S. citizen, which explains a lot!

FYI: Subject: lines made outside the United States can become longer
and are automatically MIME base64 encoded (and maybe folded) if the
line contains umlauts, accents, etc. But you don't know that, because
your little world revolves only around the United States! Ask a native American how this works, because he can explain RFC 2047 to you!

It's also the fault of the university and colleges closures.
Now in America, once they finish elementary school, they already start
working at Ford or Coca cola , right?
Lol
This news reaches Europe.
Do you think these are distorted news?
antifas ?
The aliens ?
ICE?
--
https://yamn.virebent.art
https://news.tcpreset.net http://lsbvtvxe2sfws3rmg2i3y3jqow3bwoicjwlwe5cxvxsyhrlll5q4ejyd.onion/ http://e2mjj44t3eauxra2rmrlpn7vbd6whziypccfehlrlgnnvgr6xwp5lrad.onion/ gemini://n5ry24fweklbn562o7fnyefanygtwxlgi7aevn26huuxqlsftxy5ljqd.onion/
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy

On Wed, 04 Feb 2026 18:37:34 +0300, you wrote:

Fritz Wuehler wrote:

Like the average Usenet poster needs to know what the hell a "folded
MIME base64" whatever is. Keep a QSL Subject line a max of 80
characters and it won't screw up the Subject line. Who needs more
than that? It's the Subject line, fool, It's not intended to be the
same length as the body message, nor the length of a 5,000 word short story. (But then you modern feebs don't know what a "story" is if it doesn't come attached with a Youtube URL.)

Why are you so stupid? Ok, you are a U.S. citizen, which explains a lot!

FYI: Subject: lines made outside the United States can become longer
and are automatically MIME base64 encoded (and maybe folded) if the
line contains umlauts, accents, etc. But you don't know that, because
your little world revolves only around the United States! Ask a native American how this works, because he can explain RFC 2047 to you!

All the bullshit aside about header length, etc., nowhere did you
prove QSL is not secure enough for Usenet anon posting;

As I pretty much stated earlier, the average QSL user doesn't have to
know a damn thing about RFC or MIME or much of anything else except
how to download remailer updates to keep QSL working. There isn't an
iota of proof otherwise. (Let's not cover the efail problem again.
That's a PGP/Mime problem, not a QSL problem. Besides, I did show the
"cure" for that.)

A properly used QSL STILL WORKS! No sicko Usenet troublemaker has a
chance to uncover your id and try to ruin your online or private life
with lies or threats. Of course, if a QSL user has previously told
much about his life pre their QSL usage, then repeats some of that
info while using QSL, it could enable a stalker to tack those pieces
of info together and come to a conclusion as to the anon posters'
identity. Also, one's online personal - peculiar - way of conversing
could give one's id away to a sicko stalker. However,, that is NOT a
QSL fault. It's a human fault.

So, quit your bullcrap about line length, MIME, 64 bit, etc. No
piece of software is made to please all by doing everything for
everybody.* QSL's prime function is anonymity. It STILL does that.

*(Except Microsoft shit. That's why it's all a pain in the ass for
the average user.)

--- Synchronet 3.21b-Linux NewsLink 1.2