[horde] whups-mail-filter driver issue

[Alonzo Shivers]

On Mon, Apr 16, 2018, 6:52 AM Carsten <horde-groupware at familie-lahme.de>
wrote:

>
>
> Am 14.04.2018 um 00:22 schrieb Alonzo Shivers:
> > I'm trying to use whups-mail-driver, and I'm getting a driver error that
> > I'm not sure how to fix.
> >
> > /usr/bin/whups-mail-filter --mail-user [email redacted] --mail-pass
> > [password redacted] --queue-id 1 --mail-host [host redacted]
> >
> > Broadcast message from systemd-journald at lxubns01 (Fri 2018-04-13
> 17:48:32
> > EDT):
> >
> > HORDE[7619]: No such backend "" found [pid 7619 on line 1679 of
> > "/usr/share/php/Horde/Registry.php"]
>
> Hi,
>
> You are using the whups/horde system on a remote system relative to your
> mail system?
> If not: try without "--mail-host".
> If yes: Have You configured the mail backend correct?
>
> Additional Question: is whups working on the web interface including
> "watch"-notifications and other mail stuff?
>
> br
> Carsten
>
> >
>
> >
> >
> >    Fatal
> > Error:
> >    No such backend ""
> > found
> >    In /var/www/horde/whups/lib/Factory/Driver.php on line
> > 46
> >
> >
> >    1. Horde_Registry::appInit()
> > /usr/bin/whups-mail-filter:74
> >    2. Horde_Registry->pushApp()
> > /usr/share/php/Horde/Registry.php:298
> >    3. Horde_Registry->_pushAppError()
> > /usr/share/php/Horde/Registry.php:1640
> >    4. Horde_Registry::appInit()
> > /usr/bin/whups-mail-filter:74
> >    5. Horde_Registry->pushApp()
> > /usr/share/php/Horde/Registry.php:298
> >    6. Horde_Registry->callAppMethod()
> > /usr/share/php/Horde/Registry.php:1635
> >    7.
> > Horde_Registry_Application->init()
> >
> > /usr/share/php/Horde/Registry.php:1197
> >    8.
> > Whups_Application->_init()
> >
> > /usr/share/php/Horde/Registry/Application.php:117
> >    9.
> > Whups_Factory_Driver->create()
> >       /var/www/horde/whups/lib/Application.php:49
> >
> --
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org


Apologies for the delaying responding. The issue was that while I was
manually running the script from the command line, I wasn't running it with
appropriate privileges to access the libraries. Running under sudo for
testing, and then as root via cron, have resolved the issues.