<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="">So, I changed the <font face="Menlo" class=""><span style="font-size: 11px;" class="">$config['managesieve_host'] = '<a href="tls://mail.mydomain.com’" class="">tls://mail.mydomain.com’</a>; to the fqdn of my mail server instead of the internal IP address and now it works!</span></font><div class=""><font face="Menlo" class=""><span style="font-size: 11px;" class=""><br class=""></span></font></div><div class=""><font face="Menlo" class=""><span style="font-size: 11px;" class="">Why would using the fqdn work, but not the internal LAN IP address?</span></font></div><div class=""><font face="Menlo" class=""><span style="font-size: 11px;" class=""><br class=""></span></font></div><div class=""><font face="Menlo" class=""><span style="font-size: 11px;" class="">As a side note, I am now remembering that in my main Roundcube config, I had to use the fqdn for the imap and smtp server instead of the internal LAN IP address. Is it because it needs to connect to a host with the same hostname that the certificate returns? Would it work to add an entry in my hosts file that says "10.116.0.2 </span><a href="http://mail.mydomain.com" style="font-size: 11px;" class="">mail.mydomain.com</a><span style="font-size: 11px;" class="">”? I should be able to use the internal IP addresses, right? Are there downsides to using the fqdn?</span></font></div><div class=""><font face="Menlo" class=""><span style="font-size: 11px;" class=""><br class=""></span></font></div><div class=""><font face="Menlo" class=""><span style="font-size: 11px;" class="">I may have some questions about configuring sieve rules later, but I can start a new thread for that.</span></font></div><div class=""><div class="">
<meta charset="UTF-8" class=""><div dir="auto" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none; caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); 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><br class="Apple-interchange-newline">Austin Witmer</div></div></div></div><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 11, 2022, at 1:06 PM, Christian Kivalo <<a href="mailto:ml+dovecot@valo.at" class="">ml+dovecot@valo.at</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">I added “login” to my auth_mechanisms line in<br class="">/etc/dovecot/conf.d/10-auth.conf. That line already looked like<br class="">auth_mechanisms = plain<br class="">This is what the line looks like now: auth_mechanisms = plain login<br class="">I restarted dovecot and it still is not advertising anything after<br class="">“SASL” in the sieve log file. See below:<br class="">[10-Jul-2022 16:33:27 -0600]: <4d9b66la> S: "NOTIFY" "mailto"<br class="">[10-Jul-2022 16:33:27 -0600]: <4d9b66la> S: "SASL" ""<br class="">[10-Jul-2022 16:33:27 -0600]: <4d9b66la> S: "STARTTLS"<br class="">[10-Jul-2022 16:33:27 -0600]: <4d9b66la> S: "VERSION" "1.0"<br class="">[10-Jul-2022 16:33:27 -0600]: <4d9b66la> S: OK "Dovecot (Ubuntu) ready."<br class="">[10-Jul-2022 16:33:27 -0600]: <4d9b66la> C: STARTTLS<br class="">[10-Jul-2022 16:33:27 -0600]: <4d9b66la> S: OK "Begin TLS negotiation now."<br class="">[10-Jul-2022 16:33:30 -0600]: <4d9b66la> C: LOGOUT<br class="">[10-Jul-2022 16:33:30 -0600]: <4d9b66la> S:<br class="">????Y8h#u??Lu?u?V2??N[?˴?+)u?????F?'{ֺ?G?r?iS??pݥ??D}?????<br class="">[10-Jul-2022 16:33:30 -0600]: <4d9b66la> S: ?>??0??SxfXC%]c?|?y?"w???K_ޕ???N<br class="">?.?c? ??_D?r???ǿ?r??w??#?/j?l/Wu?=.I^????~??y??(-n?6]!a??;?E?l??qn?j<br class="">[10-Jul-2022 16:33:30 -0600]: <4d9b66la> S:<br class="">?.e???i8p?{Ur"???3GZ?C??7??U)s?;,c?6????HY??B?ڑB.g=TtAk?dq???nV?i<br class=""> ?BG2D???7?hܖQTl?)G??9??W?????M^??<br class="">??D&?䢀rQ???2E?pn?Ez?????䉉i? @1??փiC???=???W?M\<br class="">`?]?}?D$`?:???^?/K???5?aB?c??ar)?l@C??X?ٹ?!J???k??"/1?r???w?_??@?p??w<br class="">)R?d??o????k*?*?????<br class=""> i?O?i%S?l^?o2?H<br class="">[10-Jul-2022 16:33:30 -0600]: <4d9b66la> S:<br class="">5?7?x??w?z"??hu4?E??:?/?F(d?;??i??"??5??G,5????E?C?MS????<br class="">L???*??*???LO?D?? J?l???ځ?<br class="">??IN??v?fR?5t?:???SG?>{mY??D?˱????t?Rj?w?#<br class=""> ??n??[?S?<br class=""> V4O?z?=.ܰې??uA?ھ????9?τ???c??oE?;LBOg??Ql'w?=<br class="">[10-Jul-2022 16:33:30 -0600]: <4d9b66la> S: ?&???C/_??*??????|.??$O?~?<br class="">??5?"????縉??<br class="">?r??0~?+~????B<br class=""> ??5)]cZ?Z?t??D??????-?dZ??M?z??2TɉOp?q?o?T?3?`'????g??6<br class="">[10-Jul-2022 16:33:30 -0600]: <4d9b66la> S: m??]~5???<br class="">[10-Jul-2022 16:33:30 -0600]: <4d9b66la> S:<br class="">And once again the line from my mail.log file.<br class="">Jul 10 22:33:27 mail dovecot: managesieve-login: Disconnected (no auth<br class="">attempts in 0 secs): user=<>, rip=10.116.0.3, lip=10.116.0.2, TLS,<br class="">session=<7VswBnvjXuIKdAAD><br class="">Any further suggestions? Why do you suppose that the auth mechanisms<br class="">are not being advertised?<br class=""></blockquote>The auth mechanisms are not shown because you access from a remote host, have STARTTLS available and "disable_plaintext_auth = yes" set. The auth mechanisms will be shown after STARTTLS.<br class="">This is described here <a href="https://wiki.dovecot.org/Pigeonhole/ManageSieve/Troubleshooting" class="">https://wiki.dovecot.org/Pigeonhole/ManageSieve/Troubleshooting</a><br class=""><br class=""><br class=""><br class="">One more thing comes to mind regarding the ssl options in the managesieve plugin config. Do you use a self signed cert in dovecot?<br class=""><br class="">One more thing you could try, in your managesieve plugin config.inc.php<br class=""><br class="">remove this section:<br class="">$config['managesieve_conn_options'] = array(<br class=""> 'ssl' => array(<br class=""> 'verify_peer' => false,<br class=""> 'allow_self_signed' => true,<br class=""> ),<br class=""> );<br class=""><br class="">add this section:<br class="">$config['managesieve_conn_options'] = [<br class=""> 'ssl' => [<br class=""> 'verify_peer' => false,<br class=""> 'peer_name' => 'change to the hostname from dovecots ssl certificate',<br class=""> ],<br class="">];<br class=""><br class="">add in there, when using self-signed cert<br class=""> 'allow_self_signed' => true,<br class=""><br class="">-- <br class=""> Christian Kivalo</div></div></blockquote></div><br class=""></div></body></html>