From Newsgroup: sci.crypt

Renewed interface for the YAMN anonymous remailer network is now available, providing easy access to post anonymously to Usenet newsgroups through the mixmaster network with Tor integration.

*Tor-native integration - Direct routing through onion services for enhanced anonymity

*No local setup required - Post to newsgroups directly from your Tor Browser, no command-line tools needed

*Multi-hop mixnet routing - Messages pass through YAMN mixmaster network (3+ hops) before delivery

*Pluto2 SMTP relay layer - Additional mixnet batching (30s windows), adaptive padding (8KB blocks), cover traffic generation, and randomized delays before entering YAMN network

*Zero metadata retention - No logs, no persistent data, complete unlinkability

*Browser-based interface - Simple web form replaces complex remailer clients

*Automatic chain selection - Smart remailer selection based on current stats and

https://yamnweb.virebent.art http://ai63yqfo2wu2j3ey7nmatyel52jjvcmfg4e4kkxp2y7x3bc6nue6czyd.onion:4343/

Victor

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: sci.crypt

In article <20251018.133017.2c0a4523@dirge.harmsk.com> Anonymous User wrote:

*Zero metadata retention - No logs, no persistent data, complete unlinkability

Can you please explain a little on how you archived this?

Like giving examples of how you archived that postfix is
absolutely not logging, nor in syslog and which Linux
distribution is used, so that YAMN and Mixmaster remops
can learn from it.

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: sci.crypt

Nomen Nescio wrote:

*Zero metadata retention - No logs, no persistent data, complete unlinkability

Can you please explain a little on how you archived this?

Like giving examples of how you archived that postfix is
absolutely not logging, nor in syslog and which Linux
distribution is used, so that YAMN and Mixmaster remops
can learn from it.

Good question, sorry if I elaborate a bit.

I don't use Postfix or traditional MTAs. My stack is:

-- Web Interface raA YAMN client raA Pluto2 raA Tor raA YAMN mixnet

YAMN Configuration

general:
loglevel: warn
logtofile: false
logtojournal: false
mail:
sendmail: no
mx_relay: false

This server runs debian12:

# /etc/rsyslog.d/99-yamn-nolog.conf
:programname, isequal, "yamn" stop
:programname, isequal, "pluto2" stop

# /etc/tor/torrc
Log notice file /dev/null
SafeLogging 1
IsolateDestAddr 1
IsolateDestPort 1

Pluto2 SMTP Relay
Pluto2 (https://github.com/gabrix73/pluto2) is for anonymous relay.
It logs operational events (connections, batches, relay status) but not:

Message content or headers
Email addresses
Message IDs beyond 24h in-memory replay cache
Timing correlation data

Data Persistence

Pluto2 message ID cache: RAM only, 24h expiry
YAMN pool: temporary files, shreded after send
No database, no persistent queues

Design Philosophy: Only log what's needed for system reliability, never message metadata.

Any advice for improvments is welcome.

Gabx


0745 074D FEAA 9CB7 62E9 D89D 3E54 F490 F2CC 5A82
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: sci.crypt

In article <10d0mfi$300de$1@news.tcpreset.net> Gabx wrote:

Nomen Nescio wrote:

*Zero metadata retention - No logs, no persistent data, complete unlinkability

Can you please explain a little on how you archived this?

Like giving examples of how you archived that postfix is
absolutely not logging, nor in syslog and which Linux
distribution is used, so that YAMN and Mixmaster remops
can learn from it.

Good question, sorry if I elaborate a bit.

I don't use Postfix or traditional MTAs. My stack is:

-- Web Interface raA YAMN client raA Pluto2 raA Tor raA YAMN mixnet

YAMN Configuration

general:
loglevel: warn
logtofile: false
logtojournal: false
mail:
sendmail: no
mx_relay: false

This server runs debian12:

# /etc/rsyslog.d/99-yamn-nolog.conf
:programname, isequal, "yamn" stop
:programname, isequal, "pluto2" stop

# /etc/tor/torrc
Log notice file /dev/null
SafeLogging 1
IsolateDestAddr 1
IsolateDestPort 1

Pluto2 SMTP Relay
Pluto2 (https://github.com/gabrix73/pluto2) is for anonymous relay.
It logs operational events (connections, batches, relay status) but not:

Message content or headers
Email addresses
Message IDs beyond 24h in-memory replay cache
Timing correlation data

Data Persistence

Pluto2 message ID cache: RAM only, 24h expiry
YAMN pool: temporary files, shreded after send
No database, no persistent queues

Design Philosophy: Only log what's needed for system reliability, never message metadata.

Any advice for improvments is welcome.

Thank you very much for the information.

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: sci.crypt

Nomen Nescio wrote:

In article <10d0mfi$300de$1@news.tcpreset.net> Gabx wrote:

Nomen Nescio wrote:

*Zero metadata retention - No logs, no persistent data, complete unlinkability

Can you please explain a little on how you archived this?

Like giving examples of how you archived that postfix is
absolutely not logging, nor in syslog and which Linux
distribution is used, so that YAMN and Mixmaster remops
can learn from it.

Good question, sorry if I elaborate a bit.

I don't use Postfix or traditional MTAs. My stack is:

-- Web Interface raA YAMN client raA Pluto2 raA Tor raA YAMN mixnet

YAMN Configuration

general:
loglevel: warn
logtofile: false
logtojournal: false
mail:
sendmail: no
mx_relay: false

This server runs debian12:

# /etc/rsyslog.d/99-yamn-nolog.conf
:programname, isequal, "yamn" stop
:programname, isequal, "pluto2" stop

# /etc/tor/torrc
Log notice file /dev/null
SafeLogging 1
IsolateDestAddr 1
IsolateDestPort 1

Pluto2 SMTP Relay
Pluto2 (https://github.com/gabrix73/pluto2) is for anonymous relay.
It logs operational events (connections, batches, relay status) but not:

Message content or headers
Email addresses
Message IDs beyond 24h in-memory replay cache
Timing correlation data

Data Persistence

Pluto2 message ID cache: RAM only, 24h expiry
YAMN pool: temporary files, shreded after send
No database, no persistent queues

Design Philosophy: Only log what's needed for system reliability, never
message metadata.

Any advice for improvments is welcome.

Thank you very much for the information.

You welcome !!!

Gabx
http://e2mjj44t3eauxra2rmrlpn7vbd6whziypccfehlrlgnnvgr6xwp5lrad.onion/

--- Digital Signature --- zJ8DqGjAnpdBck6CpoFaKCmqGTsvBjHrfE+0jUG9lIMAb1sZ55gNvB4Bx8hEFYq14GDTvtuJ7abXN7Las6AHCA==

--- Synchronet 3.21a-Linux NewsLink 1.2