Undeliverable even though in LDAP

bshaw at vsvinc.com bshaw at vsvinc.com
Tue Jul 28 03:39:57 CEST 2015


Paul,
  You might need to add the "-c" flag to create the account in the first place.  Here is the help from the saslpassword2 app.:

[root ~]# saslpasswd2 -h

This product includes software developed by Computing Services
at Carnegie Mellon University (http://www.cmu.edu/computing/).

saslpasswd2: usage: saslpasswd2 [-v] [-c [-p] [-n]] [-d] [-a appname] [-f sasldb] [-u DOM] userid
        -p      pipe mode -- no prompt, password read on stdin
        -c      create -- ask mechs to create the account
        -d      disable -- ask mechs to disable/delete the account
        -n      no userPassword -- don't set plaintext userPassword property
                                   (only set mechanism-specific secrets)
        -f sasldb       use given file as sasldb
        -a appname      use appname as application name
        -u DOM  use DOM for user domain
        -v      print version numbers and exit

So, try: "saslpassword2 -c cyrus-admin".
Also, make sure postfix owns the file:

[root ~]# ls -l /etc/sasldb2
-rw-rw-rw-. 1 postfix root 12288 Apr 13 12:17 /etc/sasldb2

Brian


From: Paul Bronson <signaldeveloper at gmail.com>
Sent: Jul 27, 2015 9:22 PM
To: bshaw at vsvinc.com
Cc: Kolab Users List
Subject: Re: Undeliverable even though in LDAP

Brian = what do you mean when you started setting password?

Anyone else have an idea? This is killing me because it's a fresh install and already provides this error?

Here's the post that said to make a fake file:

http://permalink.gmane.org/gmane.comp.kde.devel.kroupware/19646



On Mon, Jul 27, 2015 at 8:37 PM, Paul Bronson <signaldeveloper at gmail.com> wrote:
>
> Hi Brian,
>
> Thanks for the input. I tried that, didn't help. You think this is the problem with the resources? I read somewhere else someone said to make a dummy sasldb2 file in the directory, tried that, didn't work either.
>
> On Mon, Jul 27, 2015 at 8:25 PM, <bshaw at vsvinc.com> wrote:
>>
>>   I think your SASL errors are red herrings.  I don't use shared resources and I had been getting those SASL errors until I set the password.  According to my notes you need to run "saslpasswd2 cyrus-admin" as root.
>>
>> Brian
>>
>>
>> From: Paul Bronson <signaldeveloper at gmail.com>
>> Sent: Jul 27, 2015 8:06 PM
>> To: users at lists.kolab.org
>> Subject: Undeliverable even though in LDAP
>>
>> Hi guys,
>>
>> I am back. I just tried this for the second time. Centos 6.5, kolab 3.4
>>
>> Fresh install. everything on latest version.
>>
>> I go into kolab web-admin.... add a resource. Call it conference room.
>>
>> Set no owner, set access rights to everyone (So everyone can use/see it I guess)
>>
>> Go go in as a regular user on roundcube.. book it. Immediately get an undeliverable. 
>>
>> unknown user:
>>     "resource-confroom-gbgconference1"
>>
>> So I go into logs.. I find:
>>
>> /var/log/kolab/pykolab
>>
>> 2015-07-27 18:52:52,895 pykolab.wallace ERROR Failed to parse iTip events from message: ValueError(u'Offset must be less than 24 hours, was -400',)
>> 2015-07-27 18:52:52,898 pykolab.wallace ERROR Failed to parse iTip objects from message: ValueError(u'Offset must be less than 24 hours, was -400',)
>>
>> /var/log/maillog
>>
>> Jul 27 18:50:19 mail1 imap[7557]: SASL unable to open Berkeley db /etc/sasldb2: No such file or directory
>> Jul 27 18:50:19 mail1 imap[7557]: SASL unable to open Berkeley db /etc/sasldb2: No such file or directory
>>
>> maillog shows that amavis finds the entry in LDAP:
>>
>>
>> Jul 27 18:49:08 mail1 amavis[6999]: (06999-01) ESMTP> 250 2.1.5 Recipient <resource-confroom-gbgconference1 at domain.com> OK
>>
>>
>>
>> Again - this is a new install - completely fresh. Nothing changed after running setup-kolab and I get this error right out of the box. There's no documentation stating how the resources should be handled and someone told me wallace is in charge of this...
>>
>> wallaced is running
>>
>> Do I need to do something special to make this work?
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20150727/49a207ac/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5843 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20150727/49a207ac/attachment-0001.bin>


More information about the users mailing list