Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

It's great to be smart 'cause then you know stuff.

computers / alt.privacy.anon-server / yamn-0.2.5 testing

SubjectAuthor
* yamn-0.2.5 testingZax
+* Re: yamn-0.2.5 testingStefan Claas
|`- Re: yamn-0.2.5 testingStefan Claas
`* Re: yamn-0.2.5 testingZax
 `* Re: yamn-0.2.5 testingSEC3
  `- Re: yamn-0.2.5 testingZax

1
yamn-0.2.5 testing

<slrnsvaidj.e3v.admin@fleegle.mixmin.net>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=11437&group=alt.privacy.anon-server#11437

  copy link   Newsgroups: alt.privacy.anon-server
Path: i2pn2.org!i2pn.org!aioe.org!news.mixmin.net!.POSTED!not-for-mail
From: adm...@mixmin.net (Zax)
Newsgroups: alt.privacy.anon-server
Subject: yamn-0.2.5 testing
Date: Sat, 29 Jan 2022 14:05:39 -0000 (UTC)
Organization: Mixmin
Message-ID: <slrnsvaidj.e3v.admin@fleegle.mixmin.net>
Injection-Date: Sat, 29 Jan 2022 14:05:39 -0000 (UTC)
Injection-Info: news.mixmin.net; posting-host="c4af4a3027e8317d29ea238d8aa6bb2f616aa3fc";
logging-data="4119175"; mail-complaints-to="abuse@mixmin.net"
User-Agent: slrn/pre1.0.4-2 (Linux)
 by: Zax - Sat, 29 Jan 2022 14:05 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

I've been doing some work on the config/flag handling in yamn. Since it
was released there have been credible moves to standardise config file
formats. I've consequently decided to convert it to use a YAML format
config file. Some key points to note:-

* v0.2.5 is not compatible with the config file from older versions. It
needs to be re-coded into YAML format.
* Running "yamn --debug" will print the configuration in YAML format.
If no config file is found (see below) the defaults will be output.
* yamn config is now a Go package with unit tests. This has no impact
on usage but helps with development and debugging.

Config file location
- --------------------
yamn will try quite hard to find a configuration file. In order of
precedence (highest first):-

* If the --config flag points to a file that exists, it will be used.
* If the YAMNCFG environment variable points to an existing file, use
that file.
* If there is a yamn.yml in the current directory, use it.
* If the --dir flag was specified, look for a yamn.yml in the directory
specified.
* If a yamn.yml file exists in the user's homedir, use it.
* Lastly, use /etc/yamn.yml if it exists.
* If all attempts fail, issue a warning and go with defaults

The output from "yaml --debug" will include:-
files:
config: <path-to-config>
This will indicate what config file will be read. Consider that it
might vary depending on what directory you run it from (if there is a
yamn.yml in the current directory).

Testing
- -------
If you'd like to test the new version, please switch to a branch called
"config" on Github and compile from there. I'll merge this into the
master branch once I'm confident it hasn't broken anything. My remailer
"yamn4" is currently running it.

remailer-wallet
- ---------------
I've seen the proposal to get yamn to respond to a remailer-wallet
request. It's not included in this branch but, once it's been merged,
I'm happy to add that functionality.

Thanks and enjoy!

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEJHudPu4ysYQcZBcigyyPTc2QQmMFAmH1SbIACgkQgyyPTc2Q
QmN9QQ/9HOUeC8R/clB3P3EyRSp8Z34CynfOthLVTRTWQEWYbvztCse5td5fYhWv
TZ43ETZa9DgXylVZGaaloB/Yeh0OvlU67534icFGGYUeh4lrzw5S7B0IMtzepmsw
vgxBI6+FUyhoE6DUMR00hqkZv8nX5vGLGXXWselht+1ikNrNDujkQC/2u3axS0QV
jmnbn6brNXLRwJxpIg5Bv+Z70fl9xCy7giu/Z/I8W0xktqFgRsOL4eKNd/O4hujL
uPvFvq6/vSr82fFnJauqhPw+sgLqr+1gmZRsWLn0cQX3BO0SnPyVcsZAz/Z/E3S2
tG826Dm2kUGIzwzyjrRysxSXhEtPMfbl1AIvlWC+Qw2a2rbg5CHNHrl0EDu5AEeM
maUixDHT19KoArrCxzxo9YAIyFYO8ezow3KDPyf9pnzfkNX9e9D+lfd5qsp+pTvO
Fj4Jdo2KvgF3kIX+oYF9MDYUDfDyhuFOCgJtttmwFyPFgU5teB+dvA502xixzMzp
ekkPJwyDe/AnwL7xD7B8jRb1gAnsVhFTdTogQViqwOVWMOTgNMcM3x5OpO3OGXRS
cGxXtMkj3qiBX1CAoXQbMKXLZniwD/xM8HzSReXnxFP17/lmRreVxBAgFX5BN8iv
u2jGJmFxc8pzX5b3OwcYYFdACuOlFmqj5/4N6HRfyi0f4F4Y8ac=
=PKhV
-----END PGP SIGNATURE-----

--
pub 1024D/228761E7 2003-06-04 Steven Crook <steve@mixmin.net>
Key fingerprint = 1CD9 95E1 E9CE 80D6 C885 B7EB B471 80D5 2287 61E7
ssb rsa4096/832C8F4DCD904263 created: 2019-05-04 expires: 2024-05-02 usage: S

Re: yamn-0.2.5 testing

<st413i$g2$1@gioia.aioe.org>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=11440&group=alt.privacy.anon-server#11440

  copy link   Newsgroups: alt.privacy.anon-server
Path: i2pn2.org!i2pn.org!aioe.org!DNi+fko7fOvnXQCyLm0H/g.user.46.165.242.91.POSTED!not-for-mail
From: ste...@ctemplar.com (Stefan Claas)
Newsgroups: alt.privacy.anon-server
Subject: Re: yamn-0.2.5 testing
Date: Sun, 30 Jan 2022 02:30:10 +0800
Organization: Aioe.org NNTP Server
Message-ID: <st413i$g2$1@gioia.aioe.org>
References: <slrnsvaidj.e3v.admin@fleegle.mixmin.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Injection-Info: gioia.aioe.org; logging-data="514"; posting-host="DNi+fko7fOvnXQCyLm0H/g.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
X-Notice: Filtered by postfilter v. 0.9.2
X-HTTP-Posting-Host: 92.78.27.123
X-Newsreader: newsgroupstats.hk
 by: Stefan Claas - Sat, 29 Jan 2022 18:30 UTC

Zax <admin@mixmin.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> Hi,
> I've been doing some work on the config/flag handling in yamn. Since it
> was released there have been credible moves to standardise config file
> formats. I've consequently decided to convert it to use a YAML format
> config file. Some key points to note:-
> * v0.2.5 is not compatible with the config file from older versions. It
> needs to be re-coded into YAML format.
> * Running "yamn --debug" will print the configuration in YAML format.
> If no config file is found (see below) the defaults will be output.
> * yamn config is now a Go package with unit tests. This has no impact
> on usage but helps with development and debugging.
> Config file location
> - --------------------
> yamn will try quite hard to find a configuration file. In order of
> precedence (highest first):-
> * If the --config flag points to a file that exists, it will be used.
> * If the YAMNCFG environment variable points to an existing file, use
> that file.
> * If there is a yamn.yml in the current directory, use it.
> * If the --dir flag was specified, look for a yamn.yml in the directory
> specified.
> * If a yamn.yml file exists in the user's homedir, use it.
> * Lastly, use /etc/yamn.yml if it exists.
> * If all attempts fail, issue a warning and go with defaults
> The output from "yaml --debug" will include:-
> files:
> config: <path-to-config>
> This will indicate what config file will be read. Consider that it
> might vary depending on what directory you run it from (if there is a
> yamn.yml in the current directory).
> Testing
> - -------
> If you'd like to test the new version, please switch to a branch called
> "config" on Github and compile from there. I'll merge this into the
> master branch once I'm confident it hasn't broken anything. My remailer
> "yamn4" is currently running it.
> remailer-wallet
> - ---------------
> I've seen the proposal to get yamn to respond to a remailer-wallet
> request. It's not included in this branch but, once it's been merged,
> I'm happy to add that functionality.
> Thanks and enjoy!

Hi Steve,

I tested yamn-config client today under Windows 10 and here is my
info for that, so that people can also try a binary if they like.

https://gateway.pinata.cloud/ipfs/QmUeeFs88Vm8R2kPKRt3MnrwTbJFD37FKe8JDgRAW5hnEz

26cb67a0921c954671bc262c73f2420919ee6c6bc0cde60abaeae1c52d97d5f6 yamn-config-darwin-amd64
8fec744d65304b3c98f7201c932ef09331577fab690d2905674bd1eaceac15fc yamn-config-dragonfly-amd64
695f6231aa15a245706acfe90c7d009d695d04201b06ceb9a8eca5955e9792d1 yamn-config-freebsd-amd64
ee1e7f8a55d1d8a42643d6150f64715d8a7a5a0d84150e6d483044c3489f89a9 yamn-config-freebsd-arm5
60f51806749552552d06f58accc4b08aa341cdd241c9515f60ead22ac6b79ae0 yamn-config-freebsd-arm6
90a42beb6e499aaef1a8edd2c954a714c770b4843e3b7e79c6574c8ae774b93d yamn-config-freebsd-arm7
898e00649e2bf5e058c7e9ade226e6656ef707b8173a564a58c95c0ab99830ca yamn-config-linux-386
5e2a2b56b1dfc44ab507e5879ff711db57d16bc30cbe3827602681380fdf7e00 yamn-config-linux-amd64
afbd766fc9ca5992869814db5ff3145e83ff26bc0d63e6bcf4d303de40817b27 yamn-config-linux-arm5
b0ab1920750bff905b648e9958c3c057deec8b83d84d02586c9d481813532d0e yamn-config-linux-arm6
d17ab0104c495c1f3b5d7238de95864f43670c2c9082448e3a9c604876597538 yamn-config-linux-arm64
d12de5d8ae9c60f7b65c2b376c389fda69bee6da428364ed061fa31df6f88f45 yamn-config-linux-arm7
bddb67a5caa48e0c16c2026b164bc6f5b07094ba7c24bfe098e15991ae6a9b13 yamn-config-linux-mips64
a623bfbd25b75f4c11e26bedb417a947dc0a3fb882475dbb69db46d87eb40d39 yamn-config-linux-mips64le
fa165e8a9891871fb0dd9bcce3f4713de7ecba865752d3ff04cec4c67ff1c156 yamn-config-linux-ppc64
b5bf6b0847994b2e21d2820cafbca2aa0fa728c9803ffcea75e36e3b57139dce yamn-config-linux-ppc64le
dca5fc3ec9b55186f1820f4a650f86280e9b51c4931438dd6765aacd2fd86fcb yamn-config-netbsd-amd64
089b492e027c85b776256d75ee6f852ebbed6b4890b0d227b02196f15370ee89 yamn-config-netbsd-arm5
7459f7497669f05c0180e7e47f3bb3943dd630488e97274b71b9c19c4032dd6e yamn-config-netbsd-arm6
76996557295acef0446fdfbeb142839124f9dff0a974d08cd8394fd0e97883f9 yamn-config-netbsd-arm7
a3e227f5577fb549a704642bbfd714756d37579cab0d1857515c31c63f7bdd68 yamn-config-openbsd-amd64
4531050d5b0567464046dbf0d9aea36063abef313701bd03ea29f698fb51ab3e yamn-config-plan9-386
edc524fba8a9d4e9ac0dfd6d775002f9cec76deae78a5f983cda4ce78f4fb506 yamn-config-plan9-amd64
5550dfefdab8759ce493611d67c72aabebc64dae71d544613ea2c195af4f8f5d yamn-config-solaris-amd64
7ee56f72bd919749f230321648b2431e37a8861889307678ff618e2577a01889 yamn-config-windows-386.exe
ac5cc8ae6384bd4a6e1f56b823aaaab29a2f2b0d3a340c4e74348aef68fb6f32 yamn-config-windows-amd64.exe

Here is the log file created with yamn-config:

Info: 2022/01/29 19:09:47 yamn.go:187: Using config file: C:\Users\xxxxxxxxxxxx\Desktop\yamn/yamn.yml
Info: 2022/01/29 19:09:47 chain.go:36: Stats updated and reimported
Info: 2022/01/29 19:09:47 client.go:172: Chain: yamn4@mixmin.net,yamn@mix2.remailer.xyz
Trace: 2022/01/29 19:09:47 client.go:228: Encrypting Final Hop: Hop=yamn@mix2.remailer.xyz, KeyID=f5228bfe7223a6bb92f653604445ba54
Trace: 2022/01/29 19:09:47 client.go:281: Encrypting: Hop=yamn4@mixmin.net, KeyID=12998ad8f6934b4b7587c5687f02329c
Trace: 2022/01/29 19:09:47 mail.go:231: Message recipients are: yamn4@mixmin.net
Trace: 2022/01/29 19:09:48 pool.go:179: Deleted m8907418de3f91c from Pool

(m2n dizum, News Group: alt.test.test, Subject: yamn-config test, (send the message twice due to wrong yamn config file extension))

And this is my yamn.yml client configuration in base64

Z2VuZXJhbDoKICAgIGxvZ2xldmVsOiB0cmFjZQogICAgbG9ndG9maWxlOiB0cnVlCmZpbGVzOgog
ICAgY29uZmlnOiBDOlxVc2Vyc1x4eHh4eHh4eHh4eHhcRGVza3RvcFx5YW1uL3lhbW4ueW1sCiAg
ICBwdWJyaW5nOiBwdWJyaW5nLm1peAogICAgbWxpc3QyOiBtbGlzdDIudHh0CiAgICBwb29sZGly
OiBwb29sCiAgICBsb2dmaWxlOiB5YW1uLmxvZwp1cmxzOgogICAgZmV0Y2g6IHRydWUKICAgIHB1
YnJpbmc6IGh0dHA6Ly93d3cubWl4bWluLm5ldC95YW1uL3B1YnJpbmcubWl4CiAgICBtbGlzdDI6
IGh0dHA6Ly93d3cubWl4bWluLm5ldC95YW1uL21saXN0Mi50eHQKbWFpbDoKICAgIHNlbmRtYWls
OiBmYWxzZQogICAgb3V0ZmlsZTogZmFsc2UKICAgIHVzZXRsczogdHJ1ZQogICAgc210cF9yZWxh
eTogZmxlZWdsZS5taXhtaW4ubmV0CiAgICBzbXRwX3BvcnQ6IDU4NwogICAgbXhfcmVsYXk6IGZh
bHNlCiAK

I will test yamn-config with Hal tomorrow.

Best Regards
Stefan

Re: yamn-0.2.5 testing

<st41pt$ajp$1@gioia.aioe.org>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=11441&group=alt.privacy.anon-server#11441

  copy link   Newsgroups: alt.privacy.anon-server
Path: i2pn2.org!i2pn.org!news.nntp4.net!aioe.org!DNi+fko7fOvnXQCyLm0H/g.user.46.165.242.91.POSTED!not-for-mail
From: ste...@ctemplar.com (Stefan Claas)
Newsgroups: alt.privacy.anon-server
Subject: Re: yamn-0.2.5 testing
Date: Sun, 30 Jan 2022 02:42:06 +0800
Organization: Aioe.org NNTP Server
Message-ID: <st41pt$ajp$1@gioia.aioe.org>
References: <slrnsvaidj.e3v.admin@fleegle.mixmin.net> <st413i$g2$1@gioia.aioe.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Injection-Info: gioia.aioe.org; logging-data="10873"; posting-host="DNi+fko7fOvnXQCyLm0H/g.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
X-HTTP-Posting-Host: 92.78.27.123
X-Notice: Filtered by postfilter v. 0.9.2
X-Newsreader: newsgroupstats.hk
 by: Stefan Claas - Sat, 29 Jan 2022 18:42 UTC

"Stefan Claas" <stefan@ctemplar.com> wrote:
> Zax <admin@mixmin.net> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----

> > - ---------------
> > I've seen the proposal to get yamn to respond to a remailer-wallet
> > request. It's not included in this branch but, once it's been merged,
> > I'm happy to add that functionality.
> > Thanks and enjoy!

Sorry, forgot to say thank you for that!

Regards
Stefan

Re: yamn-0.2.5 testing

<slrnt002on.e3v.admin@fleegle.mixmin.net>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=11539&group=alt.privacy.anon-server#11539

  copy link   Newsgroups: alt.privacy.anon-server
Path: i2pn2.org!i2pn.org!aioe.org!news.mixmin.net!.POSTED!not-for-mail
From: adm...@mixmin.net (Zax)
Newsgroups: alt.privacy.anon-server
Subject: Re: yamn-0.2.5 testing
Date: Sun, 6 Feb 2022 17:53:27 -0000 (UTC)
Organization: Mixmin
Message-ID: <slrnt002on.e3v.admin@fleegle.mixmin.net>
References: <slrnsvaidj.e3v.admin@fleegle.mixmin.net>
Injection-Date: Sun, 6 Feb 2022 17:53:27 -0000 (UTC)
Injection-Info: news.mixmin.net; posting-host="c4af4a3027e8317d29ea238d8aa6bb2f616aa3fc";
logging-data="1758427"; mail-complaints-to="abuse@mixmin.net"
User-Agent: slrn/pre1.0.4-2 (Linux)
 by: Zax - Sun, 6 Feb 2022 17:53 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sat, 29 Jan 2022 14:05:39 -0000 (UTC), Zax wrote in
Message-Id: <slrnsvaidj.e3v.admin@fleegle.mixmin.net>:

> Hi,
>
> I've been doing some work on the config/flag handling in yamn. Since it
> was released there have been credible moves to standardise config file
> formats. I've consequently decided to convert it to use a YAML format
> config file. Some key points to note:-
>
> * v0.2.5 is not compatible with the config file from older versions. It
> needs to be re-coded into YAML format.
> * Running "yamn --debug" will print the configuration in YAML format.
> If no config file is found (see below) the defaults will be output.
> * yamn config is now a Go package with unit tests. This has no impact
> on usage but helps with development and debugging.
>
> Config file location
> - --------------------
> yamn will try quite hard to find a configuration file. In order of
> precedence (highest first):-
>
> * If the --config flag points to a file that exists, it will be used.
> * If the YAMNCFG environment variable points to an existing file, use
> that file.
> * If there is a yamn.yml in the current directory, use it.
> * If the --dir flag was specified, look for a yamn.yml in the directory
> specified.
> * If a yamn.yml file exists in the user's homedir, use it.
> * Lastly, use /etc/yamn.yml if it exists.
> * If all attempts fail, issue a warning and go with defaults
>
> The output from "yaml --debug" will include:-
> files:
> config: <path-to-config>
> This will indicate what config file will be read. Consider that it
> might vary depending on what directory you run it from (if there is a
> yamn.yml in the current directory).

Hi again,

yamn-0.2.6 is now available for downloading and compiling. This
incorporates the previous changes described above and also some changes
in the logging process. The format of log content will look very
slightly different but, under the covers, the handling is all new.

There are two logging options:-
* logtofile: yes/no (this is unchanged)
* logtojournal: yes/no (this is new)
Setting both options to "no" will result in logs being sent to stdout.

As the name suggests, logtojournal will cause yamn to write to the
systemd journal (if it's available). This is only of interest on Unix
systems with systemd.

Thanks to those who tested 0.2.5 and provided feedback.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEJHudPu4ysYQcZBcigyyPTc2QQmMFAmIACxcACgkQgyyPTc2Q
QmPVJg//Y5Sg73+86GuO1jJZgxBevdnqz0EEy6ONpYZesdN3imsJCtzP7ESGyFwD
rIvfH81Sy2sEExheVYrLlg/NZ4lrDiNkmJNDSoUd57AdJCaH5NEnCBIobXvBhATl
DnRi40OGVvCWFb/ndFMd0RfT/mGcCiEfpY699DRToTIwG9NwNzYqwIe3PvgJ8RDy
wsVAN0hlg7lJpjkogBmuBVjJNk5BCgV3jqVWAGywz/i+5bNHIEAT5c7BzhefE6z7
j9ij4IVqiF9N+1k+EgtMyZfEe+TzwV4+pdMLMyduTcaw4YQ49VwLR+qh6l3XKCHu
etUjYHh8/vojDrHYeWuo4zlzRjdDP4S11WTeD/oozFlZXT3YhiGFhFu+Dua+xui6
/HLhdwAkcOxl8qr8KQyV8IDcRk7ZqJe0JvOgrXpkqD0Eh37w1JKFDGFmEYLtQIOv
Fek1O4TbvF5aaBSMl8brEGGTbgBHBsuuxwHE5SjWTokRKdmcIeQvIQIAVuptgi/q
1ZNHhNKkAh4iopFxXpB5rKa2oZPRawrppDdzFI8fz9Fxm+SeQupApndrlC2O75sa
oynfX+pgA0fdcRPPQ7iNQzDEhr1Vy2btaL1RaZZ4sRJxyb/q77oCrNHkQZ8KQcZt
BnQgMYmfWlR9mC53HxzVyLl7uDH6QjpzWarUIrO5zG3kgpQApHg=
=fupk
-----END PGP SIGNATURE-----

--
pub 1024D/228761E7 2003-06-04 Steven Crook <steve@mixmin.net>
Key fingerprint = 1CD9 95E1 E9CE 80D6 C885 B7EB B471 80D5 2287 61E7
ssb rsa4096/832C8F4DCD904263 created: 2019-05-04 expires: 2024-05-02 usage: S

Re: yamn-0.2.5 testing

<fwULJ.14706$TXc5.9626@fx14.ams1>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=11541&group=alt.privacy.anon-server#11541

  copy link   Newsgroups: alt.privacy.anon-server
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!newsreader4.netcologne.de!news.netcologne.de!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!fx14.ams1.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.5.0
From: adm...@sec3.net (SEC3)
Subject: Re: yamn-0.2.5 testing
Newsgroups: alt.privacy.anon-server
References: <slrnsvaidj.e3v.admin@fleegle.mixmin.net>
<slrnt002on.e3v.admin@fleegle.mixmin.net>
Content-Language: en-US
In-Reply-To: <slrnt002on.e3v.admin@fleegle.mixmin.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 35
Message-ID: <fwULJ.14706$TXc5.9626@fx14.ams1>
X-Complaints-To: abuse@blocknews.net
NNTP-Posting-Date: Sun, 06 Feb 2022 18:33:47 UTC
Organization: blocknews - www.blocknews.net
Date: Sun, 6 Feb 2022 13:33:46 -0500
X-Received-Bytes: 2193
 by: SEC3 - Sun, 6 Feb 2022 18:33 UTC

> Hi again,
>
> yamn-0.2.6 is now available for downloading and compiling. This
> incorporates the previous changes described above and also some changes
> in the logging process.

Thanks for your time and efforts on improving YAMN!

I have one concern. YAMN's default settings for smtp_relay & smtp_port
are currently:

smtp_relay: fleegle.mixmin.net
smtp_port: 587

But as far as I can tell fleegle.mixmin.net does not allow relaying to
all Yamn remailer addresses. Yes, your local remailers yamn@, yamn2@,
yamn3@ and yamn4@ are permitted. I assume that's because they are local
addresses. But all the other YAMN remailers have not been given relay
permissions. Here is an example from my yamn.log when trying to deliver
to fleegle on port 587 using the chain "tncmm,middleman,yamn":

Info: 2022/02/06 13:18:13 chain.go:36: Stats updated and reimported
Info: 2022/02/06 13:18:14 yamn.go:187: Using config file: yamn.yml
Info: 2022/02/06 13:18:14 chain.go:36: Stats updated and reimported
Info: 2022/02/06 13:18:18 yamn.go:187: Using config file: yamn.yml
Warn: 2022/02/06 13:18:20 mail.go:386: Error: 554 5.7.1
<yamn@tnetconsulting.net>: Relay access denied
Warn: 2022/02/06 13:18:20 mail.go:262: SMTP relay failed
Warn: 2022/02/06 13:18:20 pool.go:78: Pool mailing failed: 554 5.7.1
<yamn@tnetconsulting.net>: Relay access denied

--
SEC3

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

Re: yamn-0.2.5 testing

<slrnt01qkp.e3v.admin@fleegle.mixmin.net>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=11548&group=alt.privacy.anon-server#11548

  copy link   Newsgroups: alt.privacy.anon-server
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.mixmin.net!.POSTED!not-for-mail
From: adm...@mixmin.net (Zax)
Newsgroups: alt.privacy.anon-server
Subject: Re: yamn-0.2.5 testing
Date: Mon, 7 Feb 2022 09:47:05 -0000 (UTC)
Organization: Mixmin
Message-ID: <slrnt01qkp.e3v.admin@fleegle.mixmin.net>
References: <slrnsvaidj.e3v.admin@fleegle.mixmin.net>
<slrnt002on.e3v.admin@fleegle.mixmin.net> <fwULJ.14706$TXc5.9626@fx14.ams1>
Injection-Date: Mon, 7 Feb 2022 09:47:05 -0000 (UTC)
Injection-Info: news.mixmin.net; posting-host="c4af4a3027e8317d29ea238d8aa6bb2f616aa3fc";
logging-data="1917774"; mail-complaints-to="abuse@mixmin.net"
User-Agent: slrn/pre1.0.4-2 (Linux)
 by: Zax - Mon, 7 Feb 2022 09:47 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, 6 Feb 2022 13:33:46 -0500, SEC3 wrote in
Message-Id: <fwULJ.14706$TXc5.9626@fx14.ams1>:

> I have one concern. YAMN's default settings for smtp_relay & smtp_port
> are currently:
>
> smtp_relay: fleegle.mixmin.net
> smtp_port: 587
>
> But as far as I can tell fleegle.mixmin.net does not allow relaying to
> all Yamn remailer addresses. Yes, your local remailers yamn@, yamn2@,
> yamn3@ and yamn4@ are permitted. I assume that's because they are local
> addresses. But all the other YAMN remailers have not been given relay
> permissions. Here is an example from my yamn.log when trying to deliver
> to fleegle on port 587 using the chain "tncmm,middleman,yamn":
>
> Info: 2022/02/06 13:18:13 chain.go:36: Stats updated and reimported
> Info: 2022/02/06 13:18:14 yamn.go:187: Using config file: yamn.yml
> Info: 2022/02/06 13:18:14 chain.go:36: Stats updated and reimported
> Info: 2022/02/06 13:18:18 yamn.go:187: Using config file: yamn.yml
> Warn: 2022/02/06 13:18:20 mail.go:386: Error: 554 5.7.1
><yamn@tnetconsulting.net>: Relay access denied
> Warn: 2022/02/06 13:18:20 mail.go:262: SMTP relay failed
> Warn: 2022/02/06 13:18:20 pool.go:78: Pool mailing failed: 554 5.7.1
><yamn@tnetconsulting.net>: Relay access denied

Hi,

I used to have a script that pulled remailer addresses out of Echolot
and whitelisted them as relays. It's many years since I've looked at
it! I'll check why it's no longer working.

Despite attempting to fix it (which, of course, I will), I'd prefer to
see users changing that setting to inject their messages to their
preferred MTA.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEJHudPu4ysYQcZBcigyyPTc2QQmMFAmIA6pkACgkQgyyPTc2Q
QmPqTg//RB6/4fG4nNQJFs/X13PXrLdyPbAM6bXQIOfgOqvXOqsmttyEsB094wjs
9nAap93lM0hr/+1LjDAJ8qNVPD0Rp7PcQyDtCSgHLGppsrMgz8I7BKMSekWU1vt+
c6q2tnatW5v/qi/1PD8AVMKVG8oY4+59rX85LSUo++QXFOqhWHaifMH7KoION/FQ
nV6WSoU/G9iSVicivOuU+VOalVrGxxIz4Dx2faYsezwBWn0mzP8it8B4J/QInM1x
rXjyQmFRFGqkX3dM9EWgPh3O3cUorYumIJnUo3hwNNRjdjx1eRLwCwbSEcLPjTkZ
Ntopu4SiGk9vGCFHx+4vPcnF2cdyH38dIrnRNb3hUdzsls1BViMn17PYnad+ioJN
8jMDJeWefUKsnaSBfCi+QXPUZyjkeHK+2o9w6iCMb/AGqZ+PNN1UjXpTctwVJDYF
368iFcNp0XxYp+FB5X81CO4+eM+YL/s4++CoAw7DWPGI6Y9vJbKGK4Ctj6/Qd+A1
ZBMXPKEa3THrMnbR8RefpuBGMZ4UDGcQfzqlUSoPirc1dZc6rYfk2x7N2x3yfgmp
WNKLxmchS6jrvueO+ISAmqIF5GALJSUldOGe7+RiLcoZGUyIJN0dDVk0iN0Ps7yO
BfPMyptcc4cvc/P6/ciLD+K+jYRNuJDrYoTMxIiJouvhlxKUDX0=
=/doS
-----END PGP SIGNATURE-----

--
pub 1024D/228761E7 2003-06-04 Steven Crook <steve@mixmin.net>
Key fingerprint = 1CD9 95E1 E9CE 80D6 C885 B7EB B471 80D5 2287 61E7
ssb rsa4096/832C8F4DCD904263 created: 2019-05-04 expires: 2024-05-02 usage: S

1
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor