A forum is good for searches. Social media is good for blind repost and "me me me" posting.
That's life
So sad we abandoned the forum approach.
Shimitar
joined 1 month ago
After 20+ years of hosting my email in a similar way (postfix...) I decoded to explore the "all in ones" like stalwart and mailcow.
Stalwart looks promising because its a new approach, supposedly more streamlined and efficient. Will post back in a few months.
I am not worried about stalwart dual license, the overall feeling seems to be of trust.
I have started testing out stalwart, seems pretty nice, bit way too early to give you reasonable feedback.
If you are looking for an innovative approach to email server stalwart is the new boss in town.
If you want proven and stable, mailcow might be your easy choice.
Both can be deployed with containers, I did with podman.
I don't see anything wrong here. Ram is supposed to be always as full as possible.
What is not needed by running programs should be full of disk pages cached. A system with lots of free ram is oversized or abnormal.
Also, today's kernels require swap space. On disk is a must for a server, and maybe consider even zram.
Having swap will allow the kernel to organize it's memory usage even better.
Don't over think ram as that is a field in which you will be wrong and the kernel will be right 99%.
Interesting enough...
tcpdump -i wg0
21:49:49.604220 IP 10.70.0.1 > dns.google: ICMP echo request, id 5337, seq 1, length 64
21:49:49.638242 IP dns.google > 10.70.0.1: ICMP echo reply, id 5337, seq 1, length 64
21:49:50.615200 IP 10.70.0.1 > dns.google: ICMP echo request, id 5337, seq 2, length 64
21:49:50.648361 IP dns.google > 10.70.0.1: ICMP echo reply, id 5337, seq 2, length 64
21:49:51.628391 IP 10.70.0.1 > dns.google: ICMP echo request, id 5337, seq 3, length 64
21:49:51.673502 IP dns.google > 10.70.0.1: ICMP echo reply, id 5337, seq 3, length 64
21:49:52.641711 IP 10.70.0.1 > dns.google: ICMP echo request, id 5337, seq 4, length 64
21:49:52.673321 IP dns.google > 10.70.0.1: ICMP echo reply, id 5337, seq 4, length 64
21:49:53.655076 IP 10.70.0.1 > dns.google: ICMP echo request, id 5337, seq 5, length 64
21:49:53.695391 IP dns.google > 10.70.0.1: ICMP echo reply, id 5337, seq 5, length 64
while on the other console, as user 1070:
ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
just gets stuck there...
This is baffling!
(stopping the ping also stop the prints in the tcpdump)
Thanks for the fun read! You made my day.
And in a lifetime on linux I never noticed the Ctrl+y stuff.