[ingo] driver said: exception 'Ingo_Exception' with message '"Authentication failed."'

Arjen de Korte arjen+horde at de-korte.org
Mon Feb 2 20:23:16 UTC 2015

Citeren lst_hoe02 at kwsoft.de:

> Zitat von django at nausch.org:
>> I'm running horde 5.2.3 with ingo 3.2.3 an a CentOS7 VM and nginx  
>> as webserver.
>> My configuration is like this one here:   
>> https://dokuwiki.nausch.org/doku.php/centos:mail_c7:horde_8
>> If I try to store a new filter-rule I receive following error:
>> Script not updated: exception 'Ingo_Exception' with message 'There  
>> was an error activating the script. The driver said: exception  
>> 'Ingo_Exception' with message '"Authentication failed."' in  
>> /usr/share/horde/ingo/lib/Transport/Timsieved.php:87 Stack trace:  
>> #0 /usr/share/horde/ingo/lib/Transport/Timsieved.php(120):  
>> Ingo_Transport_Timsieved->_connect() #1  
>> /usr/share/horde/ingo/lib/Script/Util.php(45):  
>> Ingo_Transport_Timsieved->setScriptActive(Array) #2  
>> /usr/share/horde/ingo/lib/Script/Util.php(81):  
>> Ingo_Script_Util::activate(Array) #3  
>> /usr/share/horde/ingo/lib/Basic/Rule.php(198):  
>> Ingo_Script_Util::update() #4  
>> /usr/share/horde/ingo/lib/Basic/Base.php(48):  
>> Ingo_Basic_Rule->_init() #5 /usr/share/horde/ingo/basic.php(30):  
>> Ingo_Basic_Base->__construct(Object(Horde_Variables)) #6 {main}' in  
>> /usr/share/horde/ingo/lib/Script/Util.php:50 Stack trace: #0  
>> /usr/share/horde/ingo/lib/Script/Util.php(81):  
>> Ingo_Script_Util::activate(Array) #1  
>> /usr/share/horde/ingo/lib/Basic/Rule.php(198):  
>> Ingo_Script_Util::update() #2  
>> /usr/share/horde/ingo/lib/Basic/Base.php(48):  
>> Ingo_Basic_Rule->_init() #3 /usr/share/horde/ingo/basic.php(30):  
>> Ingo_Basic_Base->__construct(Object(Horde_Variables)) #4 {main}
>> On my old installation horde 5.2.3 with ingo 3.2.3 an a CentOS6 VM  
>> and apache 2.2 as webserver everything works fine. But not on my  
>> new webserver. :/ Configurations is exactly the same.
>> Where's the bug?
> Looks like your trying to push then script with timsieved over  
> network. Have you check that actually a sieve script server is  
> running to accept the script at the given port and you are able to  
> authenticate?

I haven't touched the Ingo or Dovecot configuration in months and I  
see something similar here. The problem is probably that you're  
connecting to 'localhost' and that name is not listed in the Common  
Names of the certificate presented. The solution is to either switch  
of TLS when connecting to 'localhost' or to use the FQDN of the server  
by adding one of the following two lines to your  

$backends['sieve']['transport'][Ingo::RULE_ALL]['params']['usetls'] =  
= 'fqdn.example.com';

This message was sent from a mailinglist subscription address.
For off-list replies, you must remove the address extension.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 11647 bytes
Desc: S/MIME Signature
URL: <http://lists.horde.org/archives/ingo/attachments/20150202/e4ce8829/attachment.bin>

More information about the ingo mailing list