<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I'd rather not add RFC-breaking settings. But there's IMAP4rev2 discussion going on in <a href="https://www.ietf.org/mailman/listinfo/extra" class="">https://www.ietf.org/mailman/listinfo/extra</a>. Someone motivated enough could perhaps try to suggest changing this behavior in there.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 23 May 2018, at 23.13, Rupert Gallagher <<a href="mailto:ruga@protonmail.com" class="">ruga@protonmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Sorry for top posting, my client is still broken. </div>
<div class="">
    <br class="">
</div>
<div class="">I have never seen the ghost of a "<span style="background-color: rgba(255, 255, 255, 0);" class="">system-alerts" or similar "well-known" mail folder in the past 30 years. </span>
</div>
<div class=""><span style="background-color: rgba(255, 255, 255, 0);" class=""><br class=""></span>
</div>
<div class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">Compliance with an RFC obscure feature is compellong us all to </span><span style="background-color: rgba(255, 255, 255, 0);" class="">clear </span><span style="background-color: rgba(255, 255, 255, 0);" class="">subscriptions fol</span>
    <span style="background-color: rgba(255, 255, 255, 0);" class="">ders by hand. </span>
</div>
<div class=""><span style="background-color: rgba(255, 255, 255, 0);" class=""><br class=""></span>
</div>
<div class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">As we meet the problem over and over again, a non-RFC configuration option could solve the problem, and it would be very much appreciated...</span>
</div>
<div class="">
    <br class="">
</div>
<div class="">
    <br class="">
</div>
<div class="">
    <div class="">On Wed, May 23, 2018 at 11:57, Aki Tuomi <<a href="mailto:aki.tuomi@dovecot.fi" class="">aki.tuomi@dovecot.fi</a>> wrote:</div>
    <div class="">
        <br class="">
    </div>
    <div class="">> On 23.05.2018 12:31, Rupert Gallagher wrote:
    </div>
    <blockquote class="protonmail_quote" type="cite">
        <blockquote type="cite" cite="mid:zQtYpyAyiDeYzri3miX1VsgsTmaWrXEG5FmsqSgAPZAH9zQXIWG7MeUnDprshLaPTwJAMyuqoGz4aFzGiQLq63mK7McIgpFWsTXlooGtArw=@protonmail.com" class="">
            <div class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">Dovecot
          does not clear the subscription file from non-existent
          folders. </span>
            </div>
        </blockquote>
        <br class="">Hi!
        <br class="">
        <br class="">Thank you for your bug report. Unfortunately this is not a BUG, but mandated behavior by RFC3501, see last two paragraphs in the excerpt.
        <br class="">
        <br class="">Aki Tuomi
        <br class="">
        <br class="">6.3.6.  SUBSCRIBE Command
        <br class="">
        <br class="">   Arguments:  mailbox
        <br class="">
        <br class="">   Responses:  no specific responses for this command
        <br class="">
        <br class="">   Result:     OK - subscribe completed
        <br class="">               NO - subscribe failure: can't subscribe to that name
        <br class="">               BAD - command unknown or arguments invalid
        <br class="">
        <br class="">      The SUBSCRIBE command adds the specified mailbox name to the
        <br class="">      server's set of "active" or "subscribed" mailboxes as returned by
        <br class="">      the LSUB command.  This command returns a tagged OK response only
        <br class="">      if the subscription is successful.
        <br class="">
        <br class="">      A server MAY validate the mailbox argument to SUBSCRIBE to verify
        <br class="">      that it exists.  However, it MUST NOT unilaterally remove an
        <br class="">      existing mailbox name from the subscription list even if a mailbox
        <br class="">      by that name no longer exists.
        <br class="">
        <br class="">           Note: This requirement is because a server site can
        <br class="">           choose to routinely remove a mailbox with a well-known
        <br class="">           name (e.g., "system-alerts") after its contents expire,
        <br class="">           with the intention of recreating it when new contents
        <br class="">           are appropriate.
        <br class="">


    </blockquote>
</div></div></blockquote></div><br class=""></body></html>