Date: Thu, 11 Jun 2020 08:13:01 +0200 From: Polytropon <freebsd@edvax.de> To: Warren Hua <warren@boxsci.com> Cc: freebsd-questions@freebsd.org Subject: Re: tools for building mailserver on freebsd Message-ID: <20200611081301.f05ea3d0.freebsd@edvax.de> In-Reply-To: <a200e395-dd73-1acc-2cbd-63b759cb1829@boxsci.com> References: <7f0656fc-f3f9-4058-8382-c3dab4c4cc88@kicp.uchicago.edu> <E31E1861-9909-42AE-AA55-B3334EC4C787@boosten.org> <832e1c23-28bb-affd-8d5d-4f8d66cda93f@boxsci.com> <a200e395-dd73-1acc-2cbd-63b759cb1829@boxsci.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Jun 2020 13:37:34 +0800, Warren Hua wrote: > And, this guide is even better than those smart scripts (mailinabox > etc). Following it step by step, we know how it works exactly. If you're running a "full stack mail server", and you are responsible for its operation, you probably _should_ know how it works exactly. > I think this is also the difference in principle for freebsd and linux. It's the difference between a "turnkey system" or "appliance container" compared to a system you have full control of, in all of its parts. If "just for fun and experiments" is your primary goal, a pre-configured "all in one" is definitely nothing wrong to use. But if you plan to build a long-term system that is exposed to the public, you're probably better of with something you actually understand. And imagine the common case where security updates are needed. On a system you control, you can update and maybe reconfigure the parts that _need_ those actions, while leaving the other parts untouched. You can do this on your own, very quickly, without having to wait for a 3rd party to update their "magic script" and hope it doesn't break anything. Being able to understand the different components, how they interact with each other, is (in my opinion) essential if you want to be a responsible (!) mail system admin, as this is _not_ a "install & forget" thing today. Sidenote: You can create a meta-port of your "full stack mail server", and if you install that, all required components will be installed. This approach also works, in a different manner, if you separate components into jails. Summary: You never know what's _really_ in the tin can. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200611081301.f05ea3d0.freebsd>