<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="">On 23 Dec 2019, at 02:28, Steven Smith <<a href="mailto:steve.t.smith@gmail.com" class="">steve.t.smith@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class="">I suggest posting a question to the upstream dovecot mailing list too: <a href="https://www.dovecot.org/mailing-lists" class="">https://www.dovecot.org/mailing-lists</a></div></div></blockquote><div><br class=""></div><div>Yes, I already did that as well. The problem there of course is that it’s all Linux, almost nobody has macOS experience.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class="">I personally haven’t used doveadm for this task.</div></div></div></blockquote><div><br class=""></div><div>Too bad.</div><br class=""><blockquote type="cite" class=""><div dir="auto" class=""><div class="">Also, you’ll want to upgrade your MacPorts dovecot to the latest version. That version has a vulnerability with a reasonably serious CVE score.</div></div></blockquote><br class=""></div><div>Ha, thanks.</div><div><br class=""></div><div>It’s easy to miss this when you’re on your own git clone of macports-ports (as I want to be able to tinker with the recipes).</div><div><br class=""></div><div>G</div></body></html>