<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Yes, I have considered VMs. Or move to containers. But as long as I can prevent having more than one OS to keep in control, I will do so.<div class=""><br class=""></div><div class="">The big issue for me apart from minimising what I need to be in carol of is that I need this to survive a reboot completely (e.g. if I’m away for 3 weeks and something happens, I must be certain it all runs again without my intervention). I even created a setup to do the docker stuff (start a virtual box docker machine at boot without any need to be logged in). See <a href="https://gitlab.com/gctwnl/rnadockermachineonmacmanager" class="">Gerben Wierda
/
macOS-manage-docker-machines</a> on GitLab.</div><div class=""><br class=""></div><div class="">But what I never got around to my time is limited) is making sure the docker stuff (or docker machines) were routed. And as long as my setup kept working there was not enough need.</div><div class=""><br class=""><div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><div class="">Gerben Wierda (<a href="https://www.linkedin.com/in/gerbenwierda" class="">LinkedIn</a>)</div><div class=""><a href="https://ea.rna.nl/" class="">R&A IT Strategy</a> (main site)<br class="">Book: <a href="https://ea.rna.nl/the-book/" class="">Chess and the Art of Enterprise Architecture</a><br class="">Book: <a href="https://ea.rna.nl/the-book-edition-iii/" class="">Mastering ArchiMate</a><br class=""></div></div></div></div></div></div></div></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 5 Mar 2022, at 14:56, Ralph Seichter via macports-users <<a href="mailto:macports-users@lists.macports.org" class="">macports-users@lists.macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">* Gerben Wierda via macports-users:<br class=""><br class=""><blockquote type="cite" class="">Apart from Steven Smith, are there other users here that run a mail<br class="">server setup via MacPorts? And is already someone else running on<br class="">Monterey?<br class=""></blockquote><br class="">While MacPorts provides the necessary ports for running a mail server on<br class="">macOS, I'd suggest an alternative approach if you are dead set on using<br class="">a Mac as the server machine. As mentioned here before, Apple is not<br class="">making it easy to use regular macOS for server use, and this seems to be<br class="">a deliberate decision on their end.<br class=""><br class="">Have you considered running the mail server components in virtual<br class="">machines (e.g. VirtualBox) or, even better, as a Docker/Containerd<br class="">service stack? This method isolates Postfix, Dovecot et al from the<br class="">underlying macOS, and the service Docker images can use Ubuntu, Debian,<br class="">or whichever Linux you fancy.<br class=""><br class="">I have introduced a Docker-based service infrastructure for a major mail<br class="">service provider in Germany, catering for hundreds of thousands of users<br class="">and millions of emails per day. While the production hardware is of<br class="">course beefy, I develop and run the very same Docker images on my<br class="">MacBook Pro.<br class=""><br class="">-Ralph<br class=""></div></div></blockquote></div><br class=""></div></body></html>