<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On 11 Jan 2020, at 22:08, Bill Cole <<a href="mailto:macportsusers-20171215@billmail.scconsult.com" class="">macportsusers-20171215@billmail.scconsult.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; 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; float: none; display: inline !important;" class="">That should not matter, because 10.14+ (Mojave & Catalina) are entirely unfit for and hostile to server duties. The best answer to the question "How do I make Postfix work well on modern macOS?" is simply: "You don't.”</span></div></blockquote><br class=""></div><div>Though I heartily agree with your sentiment in Apple’s direction v.a.v. decent software — they tend to focus on 'user experience' turning the Mac into some sort of Joe/Jane consumer ‘device’, not on fundamental correctness or decent design in a technical sense (the complete and utter mess with logging and with file sharing, the way they have mashed up apache icm Server for instance), they are unreliable in what they support (the dropping of services Server.app, promising and not delivering the migration path as a prime example) — it is possible to run postfix reasonably well on macOS Mojave at least using what comes with MacPorts. Especially when in a while postfix 3.5 comes with improved postlog support thanks to Wietse (which I am already running).</div><div class=""><br class=""></div><div class="">And again thank you for pointing me towards /etc/postfix to solve the issue I and others were having.</div><br class=""><div class="">G</div><div class=""><br class=""></div><div class="">PS. I am always reminded of NeXT, also a prime example of how the company never bothered to fix very fundamental bug (e.g. in the standard C library). Brilliant in many ways. Apple too is capable of insane attention to detail as well as insane levels of neglect (completely broken regex in apache configs stayed as long as WebDAV was supported for instance). And what has attention now may become neglected next year. And they are far too closed.</div><div class=""><br class=""></div><div class="">PPS. There are also good things in Apple land. My daughter informed me that her python model performed twice as fast on her 4-core 2.3GHz Core i5 than on her fellow student’s 6-core 3.2GHz Core i7. Most likely: hers was running on multiple cores, his wasn’t. He was on Windows 10 and the leap for the python maintainers from the basis (mostly Linux these days) to macOS <i class="">is</i> smaller than to Windows.</div></body></html>