I am currently testing the new YAMN version at Sinless remailer. It is
working okay with the new yamn.yml config file. But the problem I am having
is the Systemd service I used to start YAMN fails with these errors.

Jan 31 12:26:31 onus.sinless.space systemd[1]: Started YAMN Anonymous Remailer.

Jan 31 12:26:31 onus.sinless.space yamn[29606]: Warn: 2022/01/31 12:26:31 yamn.go:189:
No config file was found. Resorting to defaults

Jan 31 12:26:32 onus.sinless.space yamn[29606]: Warn: 2022/01/31 12:26:32 client.go:323:
open pubring.mix: permission denied

Jan 31 12:26:32 onus.sinless.space yamn[29606]: Warn: 2022/01/31 12:26:32 client.go:323:
open mlist2.txt: permission denied

Jan 31 12:26:32 onus.sinless.space yamn[29606]: Error: 2022/01/31 12:26:32 server.go:276:
Failed to create idlog. mkdir idlog: permission denied

Jan 31 12:26:32 onus.sinless.space systemd[1]: yamn.service: Main process exited,
code=exited, status=1/FAILURE

Jan 31 12:26:32 onus.sinless.space systemd[1]: yamn.service: Failed with result 'exit-code'.

I am using the Systemd service from the sec3 tutorial page. This one.
<https://www.sec3.net/yamnhelp/debian/remailer/create-yamn-service.txt>

Cheers,
Sinless Operator
remop@sinless.space

On 2022-01-31 19:32, Sinless Remop wrote:
> I am currently testing the new YAMN version at Sinless remailer. It is
> working okay with the new yamn.yml config file. But the problem I am having
> is the Systemd service I used to start YAMN fails with these errors.
>
> Jan 31 12:26:31 onus.sinless.space systemd[1]: Started YAMN Anonymous Remailer.
>
> Jan 31 12:26:31 onus.sinless.space yamn[29606]: Warn: 2022/01/31 12:26:31 yamn.go:189:
> No config file was found. Resorting to defaults
>
> Jan 31 12:26:32 onus.sinless.space yamn[29606]: Warn: 2022/01/31 12:26:32 client.go:323:
> open pubring.mix: permission denied
>
> Jan 31 12:26:32 onus.sinless.space yamn[29606]: Warn: 2022/01/31 12:26:32 client.go:323:
> open mlist2.txt: permission denied
>
> Jan 31 12:26:32 onus.sinless.space yamn[29606]: Error: 2022/01/31 12:26:32 server.go:276:
> Failed to create idlog. mkdir idlog: permission denied
>
> Jan 31 12:26:32 onus.sinless.space systemd[1]: yamn.service: Main process exited,
> code=exited, status=1/FAILURE
>
> Jan 31 12:26:32 onus.sinless.space systemd[1]: yamn.service: Failed with result 'exit-code'.
>

If Systemd isn't working for you you might try starting YAMN via the
Daemon program instead. A while back Zax posted how to do it. I kept
these notes:

====
If you want to run Yamn as a detached process, I'd suggest using the
daemon package. It does it properly and takes out all the pain.

On Debian, you can "apt install daemon". After downloading the package,
create a config file called .daemonrc in the homedir of the user who
will run the daemon.

There are loads of config options but all you'll probably need is this:

yamn \
chdir=/home/yamn/yamn,\
stdout=/home/yamn/yamn/yamn.log,\
stderr=/home/yamn/yamn/yamn.log,\
pidfiles=/home/yamn/yamn,\
command=/home/yamn/go/bin/yamn --dir=/home/yamn/yamn --remailer

The process can then be started with:
daemon --name=yamn
And stopped with:
daemon yamn --name=yamn --stop

====

--
SEC3

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

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

On Tue, 1 Feb 2022 01:32:12 +0100, Sinless Remop wrote in
Message-Id: <20220201.013212.1a12a003@mix2.remailer.xyz>:

> I am currently testing the new YAMN version at Sinless remailer. It is
> working okay with the new yamn.yml config file. But the problem I am having
> is the Systemd service I used to start YAMN fails with these errors.
>
> Jan 31 12:26:31 onus.sinless.space systemd[1]: Started YAMN Anonymous Remailer.
>
> Jan 31 12:26:31 onus.sinless.space yamn[29606]: Warn: 2022/01/31 12:26:31 yamn.go:189:
> No config file was found. Resorting to defaults

Hi,

In this age, systemd is probably the best west way to start a remailer.
I used Daemon way back when sysvinit was the normal but I'd go with
systemd now.

Please can you try modifying your unit file to:
ExecStart=/home/yamn/yamn/yamn -M -D --dir /home/yamn/yamn

The above assumes your yamn.yml file is located at /home/yamn/yamn/yamn.yml.

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

iQIzBAEBCAAdFiEEJHudPu4ysYQcZBcigyyPTc2QQmMFAmH8TFYACgkQgyyPTc2Q
QmOY9xAAnU4RYvv+gXj3FQqDmOGgQhwlY3/X8V//dAeUb9M6VyfKXWzPmwvcFJmX
6QoVz97IncKi3TtALRVY2+lwhfaO4AXkxqS8KV5f8lylGxL7N4dxIAbk9cZ2GfMU
NNZT7fpGPWkHqYxKiRFFFJyEdFvo6QLwIpNQhPPsK7Trj7a6gzkXY3HqVUd/Ge/H
D9xL1MBk1OG5hJRhhVrOM80bEu6h+ROwQzHusCzKIRZFUOWcQjmnD3acIHGQdjhC
/sKlD2RMCAd+AHsJmboHWt9dKlIxzpnSy2T7OWjnWrNWjNH5QIoQMrMpkoLBzYP9
tB7UCmyOZpEAmBMwkpOuuDNV4Hh0Ru+k0vMokrdxfgKi1BCo8t2ai4x+OxOT5Ox7
I4rn9GpiByZF+IEsVJNQDef/xY8hSzEETdU3MbXRKOcqOxJA6MpRx4UfcpSX9WtY
FLx1/Q8Ik/XmJefZNBGTzYSK0oYMyOLB93HeCGigsBJiJYIxoS17MRgh5VO0rT0i
i97M4U9XF1mjI3/IpnI2vbWCbtJN/2eFIiDZU7jB8SYI+WJEZgmGPsGUCACltV9G
wwLAUCvD9PJAcKFEvtVYTmBy8GBu01ex/PLX3S1lCvWVPg6K+6+UtLgPefxyJIEJ
TRjN6SNDY0LKgxdWonNEwD814h3Roh/r6M4tCX1QPDasCMxlggw=
=3P/+
-----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

On 2022-02-03 16:42, Zax wrote:

>> I am currently testing the new YAMN version at Sinless remailer. It is
>> working okay with the new yamn.yml config file. But the problem I am having
>> is the Systemd service I used to start YAMN fails with these errors.
>
>> Jan 31 12:26:31 onus.sinless.space systemd[1]: Started YAMN Anonymous Remailer.
>
>> Jan 31 12:26:31 onus.sinless.space yamn[29606]: Warn: 2022/01/31 12:26:31 yamn.go:189:
>> No config file was found. Resorting to defaults
>
> Hi,
>
> In this age, systemd is probably the best west way to start a remailer.
> I used Daemon way back when sysvinit was the normal but I'd go with
> systemd now.
>
> Please can you try modifying your unit file to:
> ExecStart=/home/yamn/yamn/yamn -M -D --dir /home/yamn/yamn
>
> The above assumes your yamn.yml file is located at /home/yamn/yamn/yamn.yml.

Yes. That is my yamn.yml's location.
I tried the modification to yamn.service that you suggested, but the service still failed as before:

* yamn.service - YAMN Anonymous Remailer
Loaded: loaded (/etc/systemd/system/yamn.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2022-02-03 17:07:32 EST; 1min 29s ago
Process: 797 ExecStart=/home/yamn/yamn/yamn -M -D --dir /home/yamn/yamn (code=exited, status=1/FAILURE)
Main PID: 797 (code=exited, status=1/FAILURE)

Feb 03 17:07:31 onus.sinless.space systemd[1]: Started YAMN Anonymous Remailer.
Feb 03 17:07:31 onus.sinless.space yamn[797]: Info: 2022/02/03 17:07:31 yamn.go:187: Using config file: yamn.yml
Feb 03 17:07:31 onus.sinless.space yamn[797]: Info: 2022/02/03 17:07:31 client.go:320: Fetching https://www.tincture.ws/pinger/yamn/pubring.mix and storing in pubring.mix
Feb 03 17:07:32 onus.sinless.space yamn[797]: Warn: 2022/02/03 17:07:32 client.go:323: open pubring.mix: permission denied
Feb 03 17:07:32 onus.sinless.space yamn[797]: Info: 2022/02/03 17:07:32 client.go:320: Fetching https://www.tincture.ws/pinger/yamn/mlist2.txt and storing in mlist2.txt
Feb 03 17:07:32 onus.sinless.space yamn[797]: Warn: 2022/02/03 17:07:32 client.go:323: open mlist2.txt: permission denied
Feb 03 17:07:32 onus.sinless.space yamn[797]: Error: 2022/02/03 17:07:32 server.go:276: Failed to create idlog. mkdir idlog: permission denied
Feb 03 17:07:32 onus.sinless.space systemd[1]: yamn.service: Main process exited, code=exited, status=1/FAILURE
Feb 03 17:07:32 onus.sinless.space systemd[1]: yamn.service: Failed with result 'exit-code'.

When I start the YAMN daemon using Daemon it starts up. Email moves through the remailer.
So I'm assuming that the content of my yamn.yml is good.
Sinless Remop
remop at sinless.space

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

On Fri, 4 Feb 2022 04:40:32 +0000, Sinless Remop wrote in
Message-Id: <20220204.044032.ef114205@mixmin.net>:

> Yes. That is my yamn.yml's location.
> I tried the modification to yamn.service that you suggested, but the service still failed as before:
>
> * yamn.service - YAMN Anonymous Remailer
> Loaded: loaded (/etc/systemd/system/yamn.service; enabled; vendor preset: enabled)
> Active: failed (Result: exit-code) since Thu 2022-02-03 17:07:32 EST; 1min 29s ago
> Process: 797 ExecStart=/home/yamn/yamn/yamn -M -D --dir /home/yamn/yamn (code=exited, status=1/FAILURE)
> Main PID: 797 (code=exited, status=1/FAILURE)
>
> Feb 03 17:07:31 onus.sinless.space systemd[1]: Started YAMN Anonymous Remailer.
> Feb 03 17:07:31 onus.sinless.space yamn[797]: Info: 2022/02/03 17:07:31 yamn.go:187: Using config file: yamn.yml
> Feb 03 17:07:31 onus.sinless.space yamn[797]: Info: 2022/02/03 17:07:31 client.go:320: Fetching https://www.tincture.ws/pinger/yamn/pubring.mix and storing in pubring.mix
> Feb 03 17:07:32 onus.sinless.space yamn[797]: Warn: 2022/02/03 17:07:32 client.go:323: open pubring.mix: permission denied
> Feb 03 17:07:32 onus.sinless.space yamn[797]: Info: 2022/02/03 17:07:32 client.go:320: Fetching https://www.tincture.ws/pinger/yamn/mlist2.txt and storing in mlist2.txt
> Feb 03 17:07:32 onus.sinless.space yamn[797]: Warn: 2022/02/03 17:07:32 client.go:323: open mlist2.txt: permission denied
> Feb 03 17:07:32 onus.sinless.space yamn[797]: Error: 2022/02/03 17:07:32 server.go:276: Failed to create idlog. mkdir idlog: permission denied
> Feb 03 17:07:32 onus.sinless.space systemd[1]: yamn.service: Main process exited, code=exited, status=1/FAILURE
> Feb 03 17:07:32 onus.sinless.space systemd[1]: yamn.service: Failed with result 'exit-code'.
>
> When I start the YAMN daemon using Daemon it starts up. Email moves through the remailer.
> So I'm assuming that the content of my yamn.yml is good.

That's odd. I've just created a yamn.service file and it starts without
any problems. The principle different is this:

2022/02/04 19:26:13 [INFO] Using config file: /home/crooks/yamn5/yamn.yml

When my remailer starts, it reports the full path to the config file but
yours doesn't. The lack of path explains the permission denied errors.
It's probably trying to create files in /.

I've created a new branch called config_debug. It's identical to what
you're running but will print a message stating where it's finding the
yamn.yml file. Would you mind giving it a try?

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

iQIzBAEBCAAdFiEEJHudPu4ysYQcZBcigyyPTc2QQmMFAmH9hBEACgkQgyyPTc2Q
QmMGDA//UGaRNZFjkg9AlEO89IDecqPIRre+PYQBF3fjqcdz4vhsXN9qUkbZXu7r
/1S/hBw3YbDBKqAyTusC+utr9qOKZetiMThxS3Lg8VWUAduaxQ+O9FoK3ZmZFWTS
/hLatWjk0iLpqujVlhqpiliezdGDScD/dR16+ds12ZKP5Bh/XiL+bvTMPsQZy++a
2mBX7zjfAiqj6H0/8kQqJMSwpRz5mZMC4+6HjznUYU7Uza19jtX0AanC9dLIiykx
rRsGKGLIJrJ96DOTVnh0iMpFCD/WKuTq1FZa3f8KqHQ5O5DZB1g6Ycihu2RClJuM
GgNq/VIDSrSjZfhUYJOInZmSNOpXhikstWHgQTDqaNNZeN7akb/UEyla1XeI7iNt
pQiZ9mUCuKRr3ysxKeXSyNQ9nEOZr/Xnxj6QVi9QkNY5WrqxJ7ok1Omo20v0KURw
8qDkrp6URZOTfJUYXjK2gscNJy4h7/8DzN8SirPdb+Dw+3fCP9HtTYiXsRENhein
UiSaJNpJX4JJ3pJRplTMMMNcvhnLwJjUv3Z919TZXYz/Vv383NREWGVsa2jCo+XF
28cee7RhzkObjujRAi2gF1U98WjThQZuR0ktBeACSrF12zHbB28bPN3/N96c/hEa
YjSQIkUBpgCQwtUhuzJ5Ivd+mYN2LfQ9lsneXKt49HLt8gtOXRY=
=yZUE
-----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

On 2022-02-04 14:52, Zax wrote:
>On Fri, 4 Feb 2022 04:40:32 +0000, Sinless Remop wrote in
> Message-Id: <20220204.044032.ef114205@mixmin.net>:
>
>> Yes. That is my yamn.yml's location.
>> I tried the modification to yamn.service that you suggested, but the service still failed as before:
>
>> * yamn.service - YAMN Anonymous Remailer
>> Loaded: loaded (/etc/systemd/system/yamn.service; enabled; vendor preset: enabled)
>> Active: failed (Result: exit-code) since Thu 2022-02-03 17:07:32 EST; 1min 29s ago
>> Process: 797 ExecStart=/home/yamn/yamn/yamn -M -D --dir /home/yamn/yamn (code=exited, status=1/FAILURE)
>> Main PID: 797 (code=exited, status=1/FAILURE)
>
>> Feb 03 17:07:31 onus.sinless.space systemd[1]: Started YAMN Anonymous Remailer.
>> Feb 03 17:07:31 onus.sinless.space yamn[797]: Info: 2022/02/03 17:07:31 yamn.go:187: Using config file: yamn.yml
>> Feb 03 17:07:31 onus.sinless.space yamn[797]: Info: 2022/02/03 17:07:31 client.go:320: Fetching https://www.tincture.ws/pinger/yamn/pubring.mix and storing in pubring.mix
>> Feb 03 17:07:32 onus.sinless.space yamn[797]: Warn: 2022/02/03 17:07:32 client.go:323: open pubring.mix: permission denied
>> Feb 03 17:07:32 onus.sinless.space yamn[797]: Info: 2022/02/03 17:07:32 client.go:320: Fetching https://www.tincture.ws/pinger/yamn/mlist2.txt and storing in mlist2.txt
>> Feb 03 17:07:32 onus.sinless.space yamn[797]: Warn: 2022/02/03 17:07:32 client.go:323: open mlist2.txt: permission denied
>> Feb 03 17:07:32 onus.sinless.space yamn[797]: Error: 2022/02/03 17:07:32 server.go:276: Failed to create idlog. mkdir idlog: permission denied
>> Feb 03 17:07:32 onus.sinless.space systemd[1]: yamn.service: Main process exited, code=exited, status=1/FAILURE
>> Feb 03 17:07:32 onus.sinless.space systemd[1]: yamn.service: Failed with result 'exit-code'.
>
>> When I start the YAMN daemon using Daemon it starts up. Email moves through the remailer.
>> So I'm assuming that the content of my yamn.yml is good.
>
> That's odd. I've just created a yamn.service file and it starts without
> any problems. The principle different is this:
>
> 2022/02/04 19:26:13 [INFO] Using config file: /home/crooks/yamn5/yamn.yml
>
> When my remailer starts, it reports the full path to the config file but
> yours doesn't. The lack of path explains the permission denied errors.
> It's probably trying to create files in /.
>
> I've created a new branch called config_debug. It's identical to what
> you're running but will print a message stating where it's finding the
> yamn.yml file. Would you mind giving it a try?

I just tried your YAMN version called config_debug. Unfortunately, I get the same failed response
from Systemd.

* yamn.service - YAMN Anonymous Remailer
Loaded: loaded (/etc/systemd/system/yamn.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2022-02-04 15:45:49 EST; 16s ago
Process: 10253 ExecStart=/home/yamn/yamn/yamn -M -D --dir /home/yamn/yamn (code=exited, status=1/FAILURE)
Main PID: 10253 (code=exited, status=1/FAILURE)

Feb 04 15:45:48 onus.sinless.space systemd[1]: Started YAMN Anonymous Remailer.
Feb 04 15:45:48 onus.sinless.space yamn[10253]: Using config via --dir: /home/yamn/yamn/yamn.yml
Feb 04 15:45:48 onus.sinless.space yamn[10253]: Info: 2022/02/04 15:45:48 yamn.go:187: Using config file: yamn.yml
Feb 04 15:45:48 onus.sinless.space yamn[10253]: Info: 2022/02/04 15:45:48 client.go:320: Fetching https://www.tincture.ws/pinger/yamn/pubring.mix and storing in pubring.mix
Feb 04 15:45:49 onus.sinless.space yamn[10253]: Warn: 2022/02/04 15:45:49 client.go:323: open pubring.mix: permission denied
Feb 04 15:45:49 onus.sinless.space yamn[10253]: Info: 2022/02/04 15:45:49 client.go:320: Fetching https://www.tincture.ws/pinger/yamn/mlist2.txt and storing in mlist2.txt
Feb 04 15:45:49 onus.sinless.space yamn[10253]: Warn: 2022/02/04 15:45:49 client.go:323: open mlist2.txt: permission denied
Feb 04 15:45:49 onus.sinless.space yamn[10253]: Error: 2022/02/04 15:45:49 server.go:276: Failed to create idlog. mkdir idlog: permission denied
Feb 04 15:45:49 onus.sinless.space systemd[1]: yamn.service: Main process exited, code=exited, status=1/FAILURE
Feb 04 15:45:49 onus.sinless.space systemd[1]: yamn.service: Failed with result 'exit-code'.

I am not using absolute paths in my yamn.yml file. Maybe that is where things are going wrong.
Here is what I have been using:

- - - - -
general:
loglevel: info
logtofile: false
files:
config: yamn.yml
pubring: pubring.mix
mlist2: mlist2.txt
pubkey: key.txt
secring: secring.mix
adminkey: adminkey.txt
help: help.txt
pooldir: pool
maildir: Maildir
idlog: idlog
chunkdb: chunkdb
logfile: yamn.log
urls:
fetch: true
pubring: https://www.tincture.ws/pinger/yamn/pubring.mix
mlist2: https://www.tincture.ws/pinger/yamn/mlist2.txt
mail:
sendmail: false
pipe: "/usr/sbin/sendmail -t"
outfile: false
usetls: true
smtp_relay: onus.sinless.space
smtp_port: 25
mx_relay: true
onion_relay: false
sender: ""
username: ""
password: ""
outbound_name: Anonymous
outbound_addy: nobody@sinless.space
custom_from: false
stats:
minlat: 3
maxlat: 360
minrel: 90
rel_final: 99
chain: '*,*,*'
num_copies: 1
distance: 2
stale_hours: 24
use_expired: false
pool:
size: 5
rate: 70
min_send: 5
loop: 300
max_age: 28
remailer:
name: sinless
address: yamn@sinless.space
exit: false
max_size: 12
id_expire: 14
chunk_expire: 60
max_age: 14
key_life: 14
key_grace: 28
daemon: true

- - - - -

Sinless Remop
remop at sinless.space

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

On Fri, 4 Feb 2022 21:11:10 +0000, Sinless Remop wrote in
Message-Id: <20220204.211110.1d7d025a@mixmin.net>:

[snip]

> I am not using absolute paths in my yamn.yml file. Maybe that is where things are going wrong.
> Here is what I have been using:
>
> - - - - -
> general:
> loglevel: info
> logtofile: false
> files:
> config: yamn.yml
> pubring: pubring.mix
> mlist2: mlist2.txt
> pubkey: key.txt
> secring: secring.mix
> adminkey: adminkey.txt
> help: help.txt
> pooldir: pool
> maildir: Maildir
> idlog: idlog
> chunkdb: chunkdb
> logfile: yamn.log

This is your problem. When you're running under systemd, without a working
directory defined in your unit file, it's treating these as absolute paths. If
you remove the entire files: section, then they will default to the --dir path
you specify in your unit. You can prove this by removing them and then
running:

yamn --debug

You should see all of the entires in the files section defined as
absolute within the --dir path. I should have been clearer in my
earlier posting: The debug flag isn't returning what you should define
in your yml config file. It's returning the entire config, including
all the defaults. You only need to define the things your want to
adjust from default. My yamn.yml contains:

- ---
general:
loglevel: trace
logtofile: true

mail:
smtp_relay: fleegle.mixmin.net
pipe: "/usr/sbin/sendmail -t"

stats:
maxlat: 60
minlat: 2
minrel: 95.0
relfinal: 99.0

urls:
fetch: false

files:
maildir: /home/crooks/Maildir/yamn5
pubring: /home/echolot-yamn/echolot/results/pubring.mix
mlist2: /home/echolot-yamn/echolot/results/mlist2.txt

remailer:
name: yamn5
address: yamn5@mixmin.net
exit: false
daemon: true

Apologies for not being clearer about it.

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

iQIzBAEBCAAdFiEEJHudPu4ysYQcZBcigyyPTc2QQmMFAmH9qocACgkQgyyPTc2Q
QmOQlw/6Aoku9St89xW/ZN/qi5JwYYDQKq6xmIxKhW/5dYLJUiS7o0bSg1L0HQav
r4kbg1by71UVQJT3MijwOb4TCkXrnygFRn+rklz3aTsQf9tyGk8scjfeY5+EXYTk
vLtC0uIpK+6Wf7XQ4fxaKdDF0AY7DYZjnZ7RlqJGO09bn6cHoTrqqX5UiDYKJq+U
D11n6z0qa+jBrz1Q8AdxVXi7qqwCqafmcjy5VOxVeJHSoejoiVrT/HQ17qGKdSvZ
qze/RVeTpfla9VDcmMR39tScRTKbtjMude/M+qpsq6GEDeiRwWL68wWkTzX0b5Cn
GIhQys258TkBYw+r8R1tyz77pwfJRN732GyCajuyFy0nBxY2u8peSLgYW1jwEZr5
yGbZSGQJxFVGHGe5p+Gu5tq3u/a/fMaR8qg9SiwRvWYcRS7g+4aGWCnP0OZRwHnI
efKm9qUSDJQF4ZYzVASicEtMzZYCeSof3DRYd62lpt9e09gqMX78zl+LPdA1yp9d
XlVmlvgM9Os+xllyI4jni/cwDG7OguLtdCk7Hs5XYNb9L2y6kaJxdD6SPiDYH5/R
NBAXXSLIqUdsZXfOrRdpJSBe3o/VZTUqWXG360pZzRGQCdueOSm9PzRsGsW/cZZm
RegB2BFXkytdSl2a6u1rl5PTpL2wfk2PWy4AfYMkMUAgJIXaOoY=
=z+im
-----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

On 2022-02-04 17:36, Zax wrote:
> On Fri, 4 Feb 2022 21:11:10 +0000, Sinless Remop wrote in
> Message-Id: <20220204.211110.1d7d025a@mixmin.net>:
>
> [snip]
>
>> I am not using absolute paths in my yamn.yml file. Maybe that is where things are going wrong.
>> Here is what I have been using:
>
>> - - - - -
>> general:
>> loglevel: info
>> logtofile: false
>> files:
>> config: yamn.yml
>> pubring: pubring.mix
>> mlist2: mlist2.txt
>> pubkey: key.txt
>> secring: secring.mix
>> adminkey: adminkey.txt
>> help: help.txt
>> pooldir: pool
>> maildir: Maildir
>> idlog: idlog
>> chunkdb: chunkdb
>> logfile: yamn.log
>
> This is your problem. When you're running under systemd, without a working
> directory defined in your unit file, it's treating these as absolute paths. If
> you remove the entire files: section, then they will default to the --dir path
> you specify in your unit. You can prove this by removing them and then
> running:
>
> yamn --debug
>
> You should see all of the entires in the files section defined as
> absolute within the --dir path. I should have been clearer in my
> earlier posting: The debug flag isn't returning what you should define
> in your yml config file. It's returning the entire config, including
> all the defaults. You only need to define the things your want to
> adjust from default. My yamn.yml contains:

Thanks for the clarification. I changed my yamn.yml. All is well now
with my systemd unit.

Cheers!

Sinless Remop
remop at sinless.space

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

On Sat, 5 Feb 2022 00:36:17 +0000, Sinless Remop wrote in
Message-Id: <20220205.003617.a287ca01@mixmin.net>:

>> You should see all of the entires in the files section defined as
>> absolute within the --dir path. I should have been clearer in my
>> earlier posting: The debug flag isn't returning what you should define
>> in your yml config file. It's returning the entire config, including
>> all the defaults. You only need to define the things your want to
>> adjust from default. My yamn.yml contains:
>
> Thanks for the clarification. I changed my yamn.yml. All is well now
> with my systemd unit.

Great! I'll press on with the next update which will revise the logging
functionality. After that I'm hoping to rework the chain selection
process to make it more robust and testable.

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

iQIzBAEBCAAdFiEEJHudPu4ysYQcZBcigyyPTc2QQmMFAmH+OgYACgkQgyyPTc2Q
QmN1zg/8DCu/yc+olPdEYsf4iVmnR/mqqCkqCL5ppnUM/3HW7Z6KqYGXENLhii5U
VJEDn2SBJ9PIFmmC8CXqIX//zRe8T51yOJgGDpgJrXTD8vSDqJZZyFS3IZ1E9D0k
5T0/XuAhI94A91Y6i1Au4jn/KOEK48g8Zz8ZrMo1G6/SIiVFr0tyCPwfWxYJANoG
CPriuFUF/UL6ulI4M+k5ziYUicQCpb+TXTuTTZkMqztsKtqcNL2VM5VAG94AdyyO
xRxdTI9R1Nxe6ToW7r6qvrbuSWKeyeXm//2O8G7d11t0J9AB1Jvp/Cqn3komjcKn
hijzbJzRGad1h4NdfWMyGact/AglTCHL7yXFYhHFz2UbX1mp6UyRofw63jeFKJLP
vg3pJ6xLuUxnVXT37cUCA+nZMSG3vCnWamaLuFL5ShUlTZLge2NG1WrjcWcmvczy
TirRv0L213dm0YzcaJoydYS6zfw4WZMFqXb+hPS2F9ZEyTGB6QAOUsCAAwjInoum
sK7EcmR41/VXZXdfmCSsEbTTfxL9D3jVhv5qYatZr97a9mho8B5rGARlhWXEgPwH
5NbB9euY/tkZhGZyMJa6XaICXCip5Mv6tK0OZQVhiixGXVlLym/NW9i+7/JFwIq1
HXCwT4bkS2t9COvZrYeAQPW/kbBOF/+4l0rHKwqm/5u6sKDRJkw=
=3zxy
-----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

On Saturday, February 5, 2022 at 9:49:11 AM UTC+1, Zax wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> On Sat, 5 Feb 2022 00:36:17 +0000, Sinless Remop wrote in
> Message-Id: <20220205.003...@mixmin.net>:
> >> You should see all of the entires in the files section defined as
> >> absolute within the --dir path. I should have been clearer in my
> >> earlier posting: The debug flag isn't returning what you should define
> >> in your yml config file. It's returning the entire config, including
> >> all the defaults. You only need to define the things your want to
> >> adjust from default. My yamn.yml contains:
> >
> > Thanks for the clarification. I changed my yamn.yml. All is well now
> > with my systemd unit.
> Great! I'll press on with the next update which will revise the logging
> functionality. After that I'm hoping to rework the chain selection
> process to make it more robust and testable.

Hi Steve,

just wanted to update Len with your lastest release, but I get build
errors for various platforms. Here is the compiler output, encrypted
with your pub key.

Hope encryption is correct, because I no longer use PGP and last
time I used it is long ago.

Best regards
Stefan

-----BEGIN PGP MESSAGE-----

hQIMA3YDvjoVGxbBARAApcBoWPyC9Qj5ekPJRR9P/cQrQBTp349O6cNkIPu1g0ba
NwNXjO+14ghhp+m0uE1XJh44q/iO7s8BF77hKFfhm/ITgQ6oQ5Q1AHbFjL3q7+op
XhkMyTOxxPYWCyZ56CNZipHhpqpztpp71IzpgQVzhGFkyEghF/s7xtSLh7CE+mrk
mLxQOtA+ma1wNVqvM0IWgYTqZmZ5HNKA/b64xCAkkvG+0KxTfB1kPkpwelaqnbY3
t2fSYcMItJD+7GrDz6PQtuFnKZ5iWszF55WRrpkTGW7Ylcr6s+jovL76k3wFxb5o
mLJgicSMd47z+XR+GZslt5xraDcTP0JW8nMn2ytBTxAPySe1Cf8RGKUZlsCAlMwZ
Xvasf4unDDFoHT5fpZHJ0r+WMtqn2/TkKWvRIyuYKsTshBjsuAp7PDZfxIxa57lm
Gv638twkerZTmeN4QZhqJS8usIKVHSjceLpcsYlrZ1cZ0vDWYHKvucXwUBl0skdI
+zBB774wElIrYNoPB6JmV0LFRPAvhgWkU8jKbBt++b/+VvMB2t9L4noPv+H0yc/N
MI1cmbORGmgYb/GD31VBhjXyyuYE/6ddoGLqiwdSxbzAFn4n3k8GI7KjwQuhG57H
6mwLQGcYIVwE2iCPj9GryXQqUr5VY0SpCiJKLQvMsIpq0Ogd7B815jlcDlMGqurS
6QFOujDI68nqZM0s2lU0/t9TZe81iCTgIFExULs+2G31zzoareNNsIHEV2GFzUOX
qQBMRUw2aes/YIoYENH5Si4wlPK4d7auKZGr53cVcHCcgoVq9MoCHcu+j4sTbCWO
q+vhw8zAP1wnPP78+f3Lnyo8CCzH25KmiXqbCe5XA0QRbL9cqaVVuiwfwZHCN0yU
Dj5109RjsWP+bt6ohfdk0HJ9P5uX8rAFBjENSanFwV/B/LpSybPhbEPM6K1yJDvK
zHz4jyRVxILNsKhiIrlrMSo52we41lfkT2fUGbPPuvQ/7bjzmg0KZoRORSOZT4ae
Lf9uEXDxJ0rwS4/JIuenO9A88WKwbbRNGZgElwaXmeujqTDv2tpxLtcb2WVkLZtN
P8j0S5sl6gsiWaN9RB3tK8PMi9PJktPCIKWWprWQgKdtzXN3Hgkl1/kWwu2eAoNQ
gQS5WDyGAnEX4kr/DnqylkAv0pwLXF+mvnMURWjpNOYdtGuMaAIX8cnZl00jQ2oD
Mavk6bU8yS2z+POpGzZFy/g3QzGnR3S/i3RK4/k0JC3NEA0C8tx+fQOefDjtVSaN
tGEtNrrTWjmHisMUWw4q9KcnPU0Y5BNrA+AZbY2053oUwKmZqu46rpc6kk8WM+tR
y6Reh0H1SQh485GzqODHloxMG5aLC4rz8UgeRFtZsyCdex4RJVk4hm3PeIP1T83k
OVuypezf8ckU088sCwIIp1qswGcyVRsdmPe4LthgthXDk5xakWxPk6qvrWvDZb0A
6YpoHlFSuMlhZI87RY6m7m2nysJXZ/PH3DXAjwKjm0zXUdUsn/mxss9+LKDX81n7
h7vRnQHyDnVGusYg2Q==
=bx2A
-----END PGP MESSAGE-----

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

On Mon, 7 Feb 2022 10:24:41 -0800 (PST), Stefan Claas wrote in
Message-Id: <724eef40-107e-44fb-85bf-058489238b5en@googlegroups.com>:

> just wanted to update Len with your lastest release, but I get build
> errors for various platforms. Here is the compiler output, encrypted
> with your pub key.
>
> Hope encryption is correct, because I no longer use PGP and last
> time I used it is long ago.

Hi Stefan,

Unfortunately I can't decrypt it. It's entirely possible that's my
fault as I haven't used it in a long time either! I don't appear to
have the secret key it's encrypted to. Feel free to send it to my email
address if there's nothing too sensitive in it.

Steve

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

iQIzBAEBCAAdFiEEJHudPu4ysYQcZBcigyyPTc2QQmMFAmICzwAACgkQgyyPTc2Q
QmNy7Q/8CMzqWR068LQ9GT9O5W0kw3933szg2UBUf5qJNtedQpkuboPwH8SDNaio
6uMb4Hwd4PKz7MjyD/HaZTpcFMgfZxiGtQuW7bWuU5J3yc9Jhd2GNRQTTD8pVPw/
3rIyR828WgabOffYnZZGDQcIvW8zda+r6IPERyogh+rLn3c4ICpekWn3c6bfJ7EB
XLy+L9QnrTcZDrkQ7Y90B8bVY3PZdOXDn82Yyjru/Djif2d9AZSn6qLhOLTPzcGP
XeCsVUVs3Wv4qRWw+RGiI9k+8sWb2lZouZg5HLU9yPlXqRC1TqwSW1utpoykOTcd
1kkHqNLf47WMtDJSRhQpxfTHXQNhAGxkYlWuGnDkv2AgUduPFD/b32ZMt73bed9k
9LGyK9LdrEWmI0zwP1izEoiAMpZ1/HkRB0p56/nzzmKDwGL/fwGEoH1Sd+GCIDcP
IXmWwmE8SMp+lFoOAIetA9RNRs4M8zE+X6tkcbVlibMzqp1qs9tbYIyPBy1s/5Ik
O7OaM3bkquYOfS1z/HnMFXcjdS2PaO0N495yKit0GIbT/vLES+f88eUXua+wEiF/
lv76Rzw5uRGTgaijcNAymbnImXFFizMRrDWzGQ05Vm7tCWjIIOIcwpd1V6GpCuFJ
QDw1D63CK34vZZb97t5NysJUy+vDvWrNaY8YW9TNda/Bsi/xcfQ=
=ZoIn
-----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

On Tue, 8 Feb 2022 20:13:53 -0000 (UTC), Zax <admin@mixmin.net> wrote:
>Ste

"white eyes" speak with forked tongue

On Tuesday, February 8, 2022 at 9:13:54 PM UTC+1, Zax wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> On Mon, 7 Feb 2022 10:24:41 -0800 (PST), Stefan Claas wrote in
> Message-Id: <724eef40-107e-44fb...@googlegroups.com>:
> > just wanted to update Len with your lastest release, but I get build
> > errors for various platforms. Here is the compiler output, encrypted
> > with your pub key.
> >
> > Hope encryption is correct, because I no longer use PGP and last
> > time I used it is long ago.
> Hi Stefan,
>
> Unfortunately I can't decrypt it. It's entirely possible that's my
> fault as I haven't used it in a long time either! I don't appear to
> have the secret key it's encrypted to. Feel free to send it to my email
> address if there's nothing too sensitive in it.

Hi Steve,

I just send you an email, with a text file, as attachment, from my
ctemplar address.

Best regards
Stefan