From Newsgroup: alt.privacy.anon-server

The Gab loser wrote:

They are not all the duplicates there are.
I'll leave you the MIDs so you have fun drawing your conclusions.

Instead, this has nothing to do with the nature bombing from LDS Church
also called USA Mormon Church.
(it looks like being their style)

<20260911.234839.b3655646@msgid.frell.theremailer.net>
<20260911.224805.a13dae35@msgid.frell.theremailer.net>

<1789410771.430B546430D557FA@domain.invalid>
<20260914.203243.1b00c569@msgid.frell.theremailer.net>

<20260914.193756.7f39cb51@msgid.frell.theremailer.net>
<1789407885.D7C5322ABF13CA5D@domain.invalid>

<20260914.152734.cf317980@msgid.frell.theremailer.net>
<1789392520.9F2FAFD030CF1947@domain.invalid>

<1789464935.B88D1BEA9D42F46F@domain.invalid>
<20260915.113500.45a40fa4@msgid.frell.theremailer.net>


<1789376076.4FFE1D6C189CA692@domain.invalid>
<20260914.105333.4bd79c15@msgid.frell.theremailer.net>

<1789207362.783EF69E5B1605CB@domain.invalid>
<20260912.120232.a262dd38@msgid.frell.theremailer.net>

The strongest explanation for pairs 2-7 is delivery of the same logical >message to more than one Mail2News gateway, combined with a different >published Message-ID on the TCPReset path.

This is supported by an exact incoming Frell Message-ID match in our
SMTP logs and the Neodome spool copy, and by matching content, Date and >thread headers across the two published articles.

*Pair 1* is different: both articles were injected at Dizum, have
different Frell IDs and different Dates, and have identical bodies.
It is consistent with a repeated submission or re-emission before or at >Dizum. It provides no evidence that our local M2N caused that pair.

*Pair 3,4,5*
All four SMTP deliveries used the envelope sender >fritz-bounce@frell.theremailer.net. The incoming Frell Message-ID
exactly matches the corresponding Neodome articlerCOs ID.
TCPReset published its copy under a different @domain.invalid ID.
Within each pair, the content matches.

*Pair 3* also shows a temporary SMTP rejection followed by a successful >retry.
The rejected attempt does not establish a second local publication.
Retry or fallback behavior upstream is a plausible explanation, but it >remains unproven.

Overall, the evidence supports separate gateway injections and loss of a >shared published Message-ID, rather than a demonstrated double execution
by our M2N.

Howsoever, the reason for the duplicate postings is your shitty M2N
gateway, nothing else!

Best regards
Gabx

--- Digital Signature --- >Kmsk5D2J0iPpVnrIG58+J/Q1Jz3z3kMAhMJT+t57xsGsuZq9xgQaF+zYW++w/+GNU8IzzHyRkCIxPOCE7T8TDA==

And that's the one who dares to teach us about anonymous mailing?

OMG!
--- Synchronet 3.22a-Linux NewsLink 1.2