@aescling You should do it anyway, if it does something cool with your e-mail setup

@vaporeon_ maybe i’m just a hardass or something but to me it’s kit’s play lol, at least under the conditions that

1. i know exactly what i am trying to do, and
2. the configuration file layout feels reasonable and motivated

@aescling I think for me the annoying parts would be:
a. Remembering where all those config files are located (unless it's just in the same directory for the same program, but in that case, why are there multiple config files at all?)
b. Remembering (or looking up in the manpages) what the option that I need to change is called and what the allowed arguments are
c. 4 files is a lot to keep in my short-term memory...

Though we might be assuming different scenarios? My scenario is something like "Apache httpd has a lot of config files in /etc/httpd/ and the task is making it host a second directory or configuring a module or something", or "I need to configure my SSH client to accept the hopelessly obsolete encryption algorithms for this particular ancient server that I want to SSH into"

If the tutorial tells you exactly which lines to change and what to change them to, for sure it's easier

@wallhackio there is much joy and satisfaction to be found in finding ways to take ownership of your computer, and it does not always require that you write code to do so

@aescling i can understand that but i really just like writing code, my computer is just a vessel for that activity

@wallhackio thing is, those Damned Configuration Files are how you turn a compiled codebase into a compiled codebase that Does Things

@aescling but I could just hire an aescling to do that part for me :)

@wallhackio anyway you would hate running a mail server

@aescling yes