YAMN chain transit time

[Yamn Remailer]

Does a yamn message sent through a chain, go immediately through the
chain to the exit remailer - where it is retained for a random time
before delivery to the destination, or does the message stop at each
remailer and wait for a random time before delivery to the next remailer
in the chain?

[Stefan Claas]

Post by Yamn Remailer
Does a yamn message sent through a chain, go immediately through the
chain to the exit remailer - where it is retained for a random time
before delivery to the destination, or does the message stop at each
remailer and wait for a random time before delivery to the next remailer
in the chain?

It sits in the pool until it is randomly picked, to have a high latency
Network, compared to the Onion Courier Network, which is low latency and
does *not* store message and can *not* log message,s like MTAs for YAMN
can possibly do.

[Nomen Nescio]

Post by Stefan Claas

Post by Yamn Remailer
Does a yamn message sent through a chain, go immediately through the
chain to the exit remailer - where it is retained for a random time
before delivery to the destination, or does the message stop at each
remailer and wait for a random time before delivery to the next
remailer in the chain?

It sits in the pool until it is randomly picked, to have a high
latency Network, compared to the Onion Courier Network, which is low
latency and does *not* store message and can *not* log message,s like
MTAs for YAMN can possibly do.

Pool or queue? Just some observations.

Pool is where newly encrypted messages sit until transmitted to an SMTP
server. The receiving SMTP servers hold the messages in a queue where
they become "randomized" in a swell of other inbound traffic before
leaving.

Queues can have thousands of messages waiting to move so delays can be
helpfully unpredictable. In addition, we can limit the number of outbound
connections to mailservers or domains, so we don't overconsume destination
resources hindering other inbound traffic.

[Yamn2 Remailer]

Post by Yamn Remailer
Does a yamn message sent through a chain, go immediately through the
chain to the exit remailer - where it is retained for a random time
before delivery to the destination, or does the message stop at each
remailer and wait for a random time before delivery to the next remailer
in the chain?

The latter to hide the correlation of in- and outgoing messages
at every stage of transmission.

[D]

Post by Yamn Remailer
Does a yamn message sent through a chain, go immediately through the
chain to the exit remailer - where it is retained for a random time
before delivery to the destination, or does the message stop at each
remailer and wait for a random time before delivery to the next remailer
in the chain?

as a casual user of remailers with no vital expectation of anonymity, if
remailer latency was more predictable, minutes instead of hours, or even
days in some cases, then timing articles to arrive within a certain time-
frame could be useful . . . but remailers cater also to users in serious
need or expectation of de facto namelessness (nonexistent to big brother)
thus the more sporadic and unpredictable any otherwise reliable remailer
can be made to function, the better the odds it might blend into traffic

as a result, posted articles may sometimes arrive surprisingly early, or
fashionably late, which is status quo behavior for remailers, especially
if using longer mixmaster or yamn remailer chains (e.g., * * * * * exit),
but considering the overall reliability of remailers, it's a small price
to pay (free) for waiting and watching for new posted articles to appear

i would never post to newsgroups without using remailers, and beware the
storefront operatives posing as "nice guys" in this and other newsgroups
that have been promoting their duplicitous entrapment schemes ad nauseam