Description: Architecture, privacy, and operation of the YAMN Web interface.

← Back to the interface

# YAMN Web architecture and operation

YAMN Web is a send-only interface for preparing messages for delivery through the YAMN remailer network. The same composer handles email delivery and Usenet publication. The application is available through HTTPS and the existing Onion service.

## Complete route

    Browser
      ↓ HTTPS or Onion
    PHP YAMN Web
      ↓ local request, without a temporary message file
    YAMN encoder
      ↓ encrypted YAMN envelope
    Rust Nym sender
      ↓ Nym mixnet
    Nym ingress on kvara
      ↓ Tor, forwards only the envelope to the selected Entry
    Selected YAMN Entry
      ↓ YAMN packet layers
    Selected YAMN Middle
      ↓ YAMN packet layers
    Selected YAMN Exit
      ↓ SMTP delivery
    mail2news@mail2news.tcpreset.net
      ↓ Mail2News conversion
    news.tcpreset.net → misc.test

The Nym sender does not receive the body, subject, or final recipient as separate parameters. It receives only the encrypted envelope produced by the YAMN encoder.

## HTTPS and Onion service

The public HTTPS address remains `https://yamnweb.virebent.art`. The existing Onion address remains `http://ai63yqfo2wu2j3ey7nmatyel52jjvcmfg4e4kkxp2y7x3bc6nue6czyd.onion:4343/`, including its configured port. This interface neither generates nor changes the Onion address. Both access points serve the same application directory.

The HTTPS virtual host does not retain access logs. The application may emit technical PHP or service errors, but it does not intentionally log message contents.

## The YAMN chain

The chain selected in the form has three roles:

- Entry: receives the YAMN packet from the transport route and removes the first layer.
- Middle: processes the intermediate hop and forwards the packet.
- Exit: removes the final layer and delivers the message through SMTP. For Usenet articles, the SMTP recipient is the service-configured Mail-to-News gateway.

The `*` option randomly selects an available remailer from the local list. This is intentional because remailer availability and reliability change over time.

## Destinations

The composer uses the sender, optional Reply-To address, subject, and body for every message. Enter an email recipient for email delivery. To publish on Usenet, leave the email recipient empty and enter a Newsgroup; the application then adds the configured Mail-to-News recipient that converts the message leaving the remailer chain into an NNTP article.

Acceptance by the Nym transport confirms only that the route has started. Each remailer holds the packet in a queue for a variable delay, so delivery or Usenet publication may take several hours. This send-only interface does not read the final destination and cannot confirm publication itself.

References is optional and contains one or more Message-IDs used to link a new article to an existing thread. It does not enable reply retrieval or message fetching.

## What is stored

- The public YAMN keyring and remailer list are stored as technical service data.
- The Nym client stores only the technical state required for its transport identity.
- The message text and encrypted envelope are not written to temporary files by the submission route.
- The web session stores the CSRF token and the minimum state required for the POST flow.
- The browser may retain cookies or typed data according to its own settings.

## Important limitations

YAMN Web provides no inbox, fetch, message viewing, AEC, or reply retrieval. A message is accepted when the Nym sender accepts its transmission, but this is not a final delivery receipt.

During maintenance, the Nym ingress may operate in dry-run mode. In that mode it validates received packets without forwarding them to the SMTP remailer.

## Responsible use

Check the recipient or newsgroup, chain, and References before submission. Do not include passwords, private keys, or information you do not want to transmit through the remailer network. Anonymity also depends on message content, timing, and sender behavior.

Back to message composition