Avoid IMAP ACL Dovecot with Horde 5 Imp 6 Admin Warning

Abstract

If you have enabled IMAP ACL with Horde 5.15 IMP 6.1.5 with your Dovecot server you might get some warning like you didnt setup the Acl Admin in backends.local.php

If you have enabled IMAP ACL with Horde 5.15 IMP 6.1.5 with your Dovecot server you might get some warning. Something along the lines of "you did not setup the acl admin in backends.local.php".

This is related to cyrus servers, it should be ignored with no admin settings in backends.local.php, but it is not, also such admin is not needed with dovecot.

Your imp/config/backends.local.php may look like this

<?php
$servers['advanced'] = array(
   'disabled' => false,
   'name' => 'Advanced IMAP Server',
   'hostspec' => 'localhost',
   'hordeauth' => full,
   'protocol' => 'imap',
   'port' => 143,
   'secure' => 'tls',
   'maildomain' => '',
   'smtp' => array(
   //    'auth' => true,
   //    'debug' => false,
   //    'horde_auth' => false,
   //    'host' => 'smtp.example.com',
   //    'localhost' => 'localhost',
   //    'password' => null,
   //    /* Mail from a MUA SHOULD be sent via the mail submission port (587)
   //     * rather than the MTA port (25). Note that mail submission
   //     * REQUIRES some method of authentication (whether explicit
   //     * user/password credentials or configuring the mail submission
   //     * agent to automatically authenticate this host based on the
   //     * network location). */
   //    'port' => 587,
   //    'username' => null
   ),
   'spam' => array(
       // 'innocent' => array(
       //     'display' => true,
       //
       //     // Email reporting driver
       //     'email' => null,
       //     'email_format' => 'digest',
       //
       //     // Null reporting driver
       //     'null' => true,
       //
       //     // Program reporting driver
       //     'program' => null
       // ),
       // 'spam' => array(
       //     'display' => false,
       //
       //     // Email reporting driver
       //     'email' => null,
       //     'email_format' => 'digest',
       //
       //     // Null reporting driver
       //     'null' => true,
       //
       //     // Program reporting driver
       //     'program' => null
       // ),
       // // It is possible to directly define additional spam drivers.
       // // The 'drivers' array should contain a list of driver objects
       // // (these classes must implement the IMP_Spam_Base class).
       // 'drivers' => array(
       //     new IMP_Example_Spam_Driver()
       // )
   ),
   //    'admin' => array(
   //     'user' => 'cyrus',
   //     'password' => 'cyrus',
   //     'userhierarchy' => 'user.'
   //    ),
   'acl' => true,
   'cache' => false,
   'debug' => '/tmp/imp_imap.log',
   'debug_raw' => true,
   'quota' => array(
       'driver' => 'imap',
       'params' => array(
           'hide_when_unlimited' => true,
           'unit' => 'MB'
       )
   ),
   'special_mboxes' => array(
   //   IMP_Mailbox::MBOX_DRAFTS => 'Drafts',
   //     IMP_Mailbox::MBOX_SENT => 'Sent',
   //    IMP_Mailbox::MBOX_SPAM => 'Junk',
   //     IMP_Mailbox::MBOX_TEMPLATES => 'Templates',
   //     IMP_Mailbox::MBOX_TRASH => 'Trash',
   //     IMP_Mailbox::MBOX_USERSPECIAL => array(
   //         'Example' => _("Example Special Mailbox")
   //     )
   ),
   'autocreate_special' => false,
);

To avoid the warning, comment it out in imp/lib/Prefs/Special/Acl.php

       $view->new_user = $new_user;
    } catch (Horde_Auth_Exception $e) {
//        $notification->push('Could not authenticate as admin user to obtain ACLs. Perhaps your admin  configuration is incorrect in config/backends.local.php?', 'horde.warning');
    } catch (Horde_Exception $e) {
        if (!($e->getPrevious() instanceof IMP_Exception)) {
            $notification->push($e);
        }
    }

This is only a workaround, it should be fixed by the Horde team!

Update

Its reported as fixed in IMP 6.1.6

Robert Schetterer, 06. November 2013

   horde    imap    acl    imp