So I'm new to Omnimix.

I don't undestand the procedure/steps to send a message via Yamn.

I'm getting the following error message in the Mailer:

"Error sending the Mailer message. Sending error (anon) Yamn encryption
failed.
Yamn returned no files."

How do I fix this please?

In article <666cb6bb5c236033de10668f5d8482d2@dizum.com> Nomen Nescio
<nobody@dizum.com> wrote:

>So I'm new to Omnimix.
>
>I don't undestand the procedure/steps to send a message via Yamn.
>
>I'm getting the following error message in the Mailer:
>
>"Error sending the Mailer message. Sending error (anon) Yamn encryption
>failed.
>Yamn returned no files."
>
>How do I fix this please?

Are remailer status data downloaded correctly?
Does Mixmaster work and send data?
What's listed at the MixData tab on the right?

You may try the following - the hard way:

Add a "0.mxt" file to OM's "mix\om" folder containing

----------------------------------------
To: mailbox@domain.invalid
Subject: Dummy Message

This is a dummy message.
----------------------------------------

then launch a CLI and from within OM's mix folder execute

"yamn.exe -m -c 5 -l *,*,*,*,* om\0.mxt".

With Zax's 64-bit yamn (lacking a 32-bit version) running on Win32 for
example I got

| c:\Program Files\OmniMix\mix>yamn.exe -m -c 5 -l *,*,*,*,* om\0.mxt
| This version of o:\OmniMix_IDE\Projects\OmniMix\mix\yamn.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher.
|
| c:\Program Files\OmniMix\mix>

without any output at the mix\pool folder, whereas OM's obviously 32-bit
version should give you

| c:\Program Files\OmniMix\mix>yamn.exe -m -c 5 -l *,*,*,*,* om\0.mxt
| Info: 2021/09/12 16:43:02 chain.go:36: Stats updated and reimported
| Info: 2021/09/12 16:43:02 client.go:172: Chain: yamn@tnetconsulting.net,yamn@mix1.remailer.xyz,yamn@middleman.remailer.online,yamn@virebent.art,yamn@yamn.paranoici.org
| Trace: 2021/09/12 16:43:02 client.go:228: Encrypting Final Hop: Hop=yamn@yamn.paranoici.org, KeyID=6a46a517e3366e3e136f26b876454de0
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@virebent.art, KeyID=a2025fd73027e8955783d02b989b532c
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@middleman.remailer.online, KeyID=a46cebe5f0aab5d86a588332d4d66a2d
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@mix1.remailer.xyz, KeyID=e3dd4bd7f418334dc46b28492849c6c8
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@tnetconsulting.net, KeyID=865d0957811ea97f5703760a2f0e248f
| Info: 2021/09/12 16:43:02 client.go:172: Chain: yamn@mixharbor.xyz,yamn@mix1.remailer.xyz,yamn@middleman.remailer.online,yamn@virebent.art,yamn@yamn.paranoici.org
| Trace: 2021/09/12 16:43:02 client.go:228: Encrypting Final Hop: Hop=yamn@yamn.paranoici.org, KeyID=6a46a517e3366e3e136f26b876454de0
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@virebent.art, KeyID=a2025fd73027e8955783d02b989b532c
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@middleman.remailer.online, KeyID=a46cebe5f0aab5d86a588332d4d66a2d
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@mix1.remailer.xyz, KeyID=e3dd4bd7f418334dc46b28492849c6c8
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@mixharbor.xyz, KeyID=983ef6363a57fda440cbefcfa0376f33
| Info: 2021/09/12 16:43:02 client.go:172: Chain: yamn@remailer.privacy.at,yamn@mix1.remailer.xyz,yamn@middleman.remailer.online,yamn@virebent.art,yamn@yamn.paranoici.org
| Trace: 2021/09/12 16:43:02 client.go:228: Encrypting Final Hop: Hop=yamn@yamn.paranoici.org, KeyID=6a46a517e3366e3e136f26b876454de0
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@virebent.art, KeyID=a2025fd73027e8955783d02b989b532c
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@middleman.remailer.online, KeyID=a46cebe5f0aab5d86a588332d4d66a2d
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@mix1.remailer.xyz, KeyID=e3dd4bd7f418334dc46b28492849c6c8
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@remailer.privacy.at, KeyID=f1d19d9f9c7924545ae20cfa4c0b5e7f
| Info: 2021/09/12 16:43:02 client.go:172: Chain: yamn@remailer.privacy.at,yamn@mix1.remailer.xyz,yamn@middleman.remailer.online,yamn@virebent.art,yamn@yamn.paranoici.org
| Trace: 2021/09/12 16:43:02 client.go:228: Encrypting Final Hop: Hop=yamn@yamn.paranoici.org, KeyID=6a46a517e3366e3e136f26b876454de0
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@virebent.art, KeyID=a2025fd73027e8955783d02b989b532c
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@middleman.remailer.online, KeyID=a46cebe5f0aab5d86a588332d4d66a2d
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@mix1.remailer.xyz, KeyID=e3dd4bd7f418334dc46b28492849c6c8
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@remailer.privacy.at, KeyID=f1d19d9f9c7924545ae20cfa4c0b5e7f
| Info: 2021/09/12 16:43:02 client.go:172: Chain: yamn@tnetconsulting.net,yamn@mix1.remailer.xyz,yamn@middleman.remailer.online,yamn@virebent.art,yamn@yamn.paranoici.org
| Trace: 2021/09/12 16:43:02 client.go:228: Encrypting Final Hop: Hop=yamn@yamn.paranoici.org, KeyID=6a46a517e3366e3e136f26b876454de0
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@virebent.art, KeyID=a2025fd73027e8955783d02b989b532c
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@middleman.remailer.online, KeyID=a46cebe5f0aab5d86a588332d4d66a2d
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@mix1.remailer.xyz, KeyID=e3dd4bd7f418334dc46b28492849c6c8
| Trace: 2021/09/12 16:43:02 client.go:281: Encrypting: Hop=yamn@tnetconsulting.net, KeyID=865d0957811ea97f5703760a2f0e248f
|
| c:\Program Files\OmniMix\mix>

with 5 files ending up in the "mix\pool" folder.

What do you get?

Anonymous wrote:

> With Zax's 64-bit yamn (lacking a 32-bit version) running on Win32 for
> example I got

I'm also interested in official Windows binaries of the latest Yamn
version signed by its maintainer Zax, but they aren't anywhere to be
found. Need a URL, please!

On 2021-09-14 9:02 a.m., Nomen Nescio wrote:
> Anonymous wrote:
>
>> With Zax's 64-bit yamn (lacking a 32-bit version) running on Win32 for
>> example I got
>
> I'm also interested in official Windows binaries of the latest Yamn
> version signed by its maintainer Zax, but they aren't anywhere to be
> found. Need a URL, please!
>

Zax's latest yamn.exe (jul 3 2021) can be found on his website, unsigned
though.

<https://www.mixmin.net>

--
SEC3

YAMN Tutorials - https://sec3.net/yamnhelp

On Tue, 14 Sep 2021 10:38:58 -0400, SEC3 <admin@sec3.net> wrote:

>On 2021-09-14 9:02 a.m., Nomen Nescio wrote:
>> Anonymous wrote:
>>
>>> With Zax's 64-bit yamn (lacking a 32-bit version) running on Win32 for
>>> example I got
>>
>> I'm also interested in official Windows binaries of the latest Yamn
>> version signed by its maintainer Zax, but they aren't anywhere to be
>> found. Need a URL, please!
>>
>
>Zax's latest yamn.exe (jul 3 2021) can be found on his website, unsigned
>though.
>
><https://www.mixmin.net>

Many thanks!

: c:\test>yamn-0.2b.exe -h
: Unable to determine Yamn's basedir. Continuing with a slight sense of trepidation.
: Usage of yamn-0.2b.exe:
: -D Start remailer as a daemon. (Requires -M
: -M Perform routine remailer actions
: -R Read a message from stdin
: -S Force pool send
: -V Print version string
: -c int
: Number of copies
: -chain string
: Remailer chain
: -config string
: Config file
: -copies int
: Number of copies
: -d Inject a dummy message
: -daemon
: Start remailer as a daemon. (Requires -M
: -debug
: Print detailed config
: -dir string
: Base directory (default "/etc/yamn")
: -dummy
: Inject a dummy message
: -l string
: Remailer chain
: -m Function as a client
: -mail
: Function as a client
: -meminfo
: Print memory info
: -nodummy
: Don't send dummies
: -read-mail
: Read a message from stdin
: -refresh
: Refresh remailer stats files
: -remailer
: Perform routine remailer actions
: -s string
: Subject header
: -send
: Force pool send
: -stdout
: Write message to stdout
: -subject string
: Subject header
: -t string
: Recipient email address
: -to string
: Recipient email address
: -version
: Print version string
:
: c:\test>yamn-0.2b.exe -version
: Unable to determine Yamn's basedir. Continuing with a slight sense of trepidation.
: Error: Unable to read config: open /etc/yamn/yamn.cfg: The system cannot find the path specified.
: c:\test>

:-(

On 2021-09-14 3:30 p.m., Anonymous wrote:
> On Tue, 14 Sep 2021 10:38:58 -0400, SEC3 <admin@sec3.net> wrote:
>
>> On 2021-09-14 9:02 a.m., Nomen Nescio wrote:
>>> Anonymous wrote:
>>>
>>>> With Zax's 64-bit yamn (lacking a 32-bit version) running on Win32 for
>>>> example I got
>>>
>>> I'm also interested in official Windows binaries of the latest Yamn
>>> version signed by its maintainer Zax, but they aren't anywhere to be
>>> found. Need a URL, please!
>>>
>>
>> Zax's latest yamn.exe (jul 3 2021) can be found on his website, unsigned
>> though.
>>
>> <https://www.mixmin.net>
>
> Many thanks!
>
> : c:\test>yamn-0.2b.exe -h
> : Unable to determine Yamn's basedir. Continuing with a slight sense of trepidation.
> : Usage of yamn-0.2b.exe:
> : -D Start remailer as a daemon. (Requires -M
> : -M Perform routine remailer actions
> : -R Read a message from stdin
> : -S Force pool send
> : -V Print version string
> : -c int
> : Number of copies
> : -chain string
> : Remailer chain
> : -config string
> : Config file
> : -copies int
> : Number of copies
> : -d Inject a dummy message
> : -daemon
> : Start remailer as a daemon. (Requires -M
> : -debug
> : Print detailed config
> : -dir string
> : Base directory (default "/etc/yamn")
> : -dummy
> : Inject a dummy message
> : -l string
> : Remailer chain
> : -m Function as a client
> : -mail
> : Function as a client
> : -meminfo
> : Print memory info
> : -nodummy
> : Don't send dummies
> : -read-mail
> : Read a message from stdin
> : -refresh
> : Refresh remailer stats files
> : -remailer
> : Perform routine remailer actions
> : -s string
> : Subject header
> : -send
> : Force pool send
> : -stdout
> : Write message to stdout
> : -subject string
> : Subject header
> : -t string
> : Recipient email address
> : -to string
> : Recipient email address
> : -version
> : Print version string
> :
> : c:\test>yamn-0.2b.exe -version
> : Unable to determine Yamn's basedir. Continuing with a slight sense of trepidation.
> : Error: Unable to read config: open /etc/yamn/yamn.cfg: The system cannot find the path specified.
> : c:\test>
>
> :-(
>

For the Yamn binary to work properly it needs a mix.cfg file in the same
directory. Here is one that you can use.

<https://www.sec3.net/yamnhelp/windows10/yamn.cfg>

--
SEC3

YAMN Tutorials - https://sec3.net/yamnhelp

On 2021-09-14 5:31 p.m., SEC3 wrote:

> For the Yamn binary to work properly it needs a mix.cfg file in the same
> directory. Here is one that you can use.

CORRECTION: It needs a yamn.cfg file:

> <https://www.sec3.net/yamnhelp/windows10/yamn.cfg>

--
SEC3

YAMN Tutorials - https://sec3.net/yamnhelp

SEC3 <admin@sec3.net> wrote:

>On 2021-09-14 5:31 p.m., SEC3 wrote:
>
>> For the Yamn binary to work properly it needs a mix.cfg file in the same
>> directory. Here is one that you can use.
>
>CORRECTION: It needs a yamn.cfg file:
>
>> <https://www.sec3.net/yamnhelp/windows10/yamn.cfg>

It needs to be configured to put out its version? That's weird.