[dev] How to keep IMP from blocking other apps

[Sebastian Birnbach]

Sure, and anonymization is not even required as SMTP server credentials are
configured in the console.
Here is my backends.local.php:


// IMAP server
$servers['imap'] = array(
    // ENABLED by default; will connect to IMAP port on local server
    'disabled' => false,
    'name' => '2B IMAP Server',
    'hostspec' => 'localhost',
    'hordeauth' => true,
    'protocol' => 'imap',
    'port' => 143,
    'smtp' => array(
        'horde_auth' => true, // use the global settings from
Settings->Horde->Mailer
    ),
    'secure' => 'tls',
);



I have not yet figured out when exactly IMP will talk to the mail server. I
observe that I cannot use the user preferences or the admin console without
waiting for every click.
Oh, except for logging in, that is unaffected.

There has been some unfortunate discussion in the bug tracking system, so
please let me clarify again:
my question is not about authentication. Both Horde and mail server
authentication are fine. No problem here, not even related to it.
My issue is about Horde operation when the mail server fails or responds
very slowly. In this case IMP is very slow and seems to drag other Horde
apps down.

Kind regards

  Seb.






Am Mi., 9. Jan. 2019 um 16:10 Uhr schrieb Ralf Lang <lang at b1-systems.de>:

> Hi, can you please post an anonymized imp config? (backends.local.php,
> conf.php)
>
> imp should not try to authenticate just because of a pushApp() during
> init of unrelated pages
>
> portal might be trickier as some portal blocks depend on imp
>
>
>
> Am 09.01.19 um 16:04 schrieb Sebastian Birnbach:
> > In my Horde installation, authentication is done against Horde's prefs
> > container, i.e. an SQL server. IMP is configured to create its mail
> server
> > session on passed-through user login credentials
> > (imp/config/backends.ocal.php: 'hordeauth' => true).
> >
> > The mail server is a local dovecot installation. It checks the passed
> user
> > credentials against the same SQL server (SQL table 'horde_users';
> password
> > scheme: SHA-512 for both Horde and dovecot).
> >
> > Please note that the mail server is NOT used for Horde authentication.
> >
> > Idea of the configuration was to make sure a Horde session can always be
> > created (except if the SQL server dies, in which case Horde won't run
> > anyways) and users can conveniently be administered through the Horde
> > console.
> >
> > This all worked out and functions as intended. But.
> >
> >
> >
> > If the mail server dies or, as I recently experienced , takes ~30 seconds
> > for a response (my misconfiguration), a page request to *any* Horde app
> > will not be served until IMP has spoken to the mail server. This can be
> > observed even with most unrelated pages like the user prefs.
> >
> > That is, once the mail server dies or responds slowly, the rest of Horde
> is
> > quite unusable.
> >
> >
> >
> > I opened RFE #14885, asking for adding an IMP timeout, only to be told
> that
> > my problem was a configuration issue.
> >
> > So, can anybody think of a configuration that keeps IMP from blocking
> other
> > apps? I imagine a system configuration where mail is not the only
> > application of importance should be quite common.
> >
> > Kind regards
> >
> >   Seb.
>