autogenerated fields



  • Thank you, it's works)
    And then for example i add new field "description" and want this field to generate some Id
    for example this "python -c 'import uuid; print str(uuid.uuid4()).upper();'"
    i could add this field , then choose "Generated", then write private function.
    is new privat function in this php file enough for this?



  • And could you please tell me , what kolab do to create user? Add info to 389DS , what else? I need this info , because i want to migrate existing ldap users to kolab, but seems i need not only ldap copy.


  • Global Moderator

    @Constin The Kolab Web Administration Panel does nothing but address LDAP (389 Directory Server to be precise). It does not configure your system to use LDAP, or for the system to create a home directory for the user (see man pam_mkhomedir, though).



  • @kanarip said:

    @Constin The Kolab Web Administration Panel does nothing but address LDAP (389 Directory Server to be precise). It does not configure your system to use LDAP, or for the system to create a home directory for the user (see man pam_mkhomedir, though).

    i don't want kolab-webadmin to create home dir or something else, except ldap user . But i want it to create ldap user i want, with fields i want.

    I think that kolab-webadmin not only create ldap user, but also do something with cyrus.Isn't it? When i copy/paste kolab-user with another name/mail/etc i could login to roundcoube , but have an error that this user haven't mailbox.



  • For Cyrus IMAP Murder deployments, the Kolab daemon is normally configured to initially communicate with a Cyrus IMAP frontend server.
    Unless the target mailbox server had already been supplied by LDAP, the Kolab daemon would create the mailbox using the connection to a Cyrus IMAP frontend , and await the mailbox entry to re-occur on said frontend.

    Can i do it manually? Which command?



  • seems it

    kolab create-mailbox "user/john.doe/New@example.org"
    

    but this no help , still have error for copied user in roundcoube "Mailbox does not exist"



  • @Constin
    wow nice toy kolab.py
    i'll play with it)


  • Global Moderator

    @Constin said:

    I think that kolab-webadmin not only create ldap user, but also do something with cyrus.Isn't it? When i copy/paste kolab-user with another name/mail/etc i could login to roundcoube , but have an error that this user haven't mailbox.

    It's the kolabd service that listens to changes in LDAP, and applies the corresponding changes to IMAP -- such as when you create a new user, with all the email attributes in place, kolabd will create a mailbox.



  • Was a bug with cyrus.
    Changing policy_uid and primary_mail -ok
    Changing $homedirectory_base - ok

    But changing both at same time with kolabd restarting and cyrus start to spam errors. It cannot handle with new primary_mail python template and fall completely down. restart cyrus don't help.



  • [example.com]
    primary_mail = '%(givenname)s'[0:1].%(surname)s@%(domain)s

    in webadmin panel all good
    James Bond = j.bond@example.com

    But in ldap and cyrus

    Feb 22 13:52:40 mail imaps[5133]: ptload(): bad response from ptloader server: ptsmodule_canonifyid() failed
    Feb 22 13:52:40 mail imaps[5133]: ptload completely failed: unable to canonify identifier: 'James'[0:1].bond@example.com


  • Global Moderator

    This is a typical case of running off in to a corner where you expect all things to just magically work.

    While maybe, arguably, this should work -- the way you expect it to -- it may just not and that's what you're finding is either a bug (this forum is not the correct place to report those) or is in fact an unanticipated use-case and therefore a feature enhancement request in the making (this forum is not the correct place to put those in either).

    The routines for primary_mail, secondary_mail and policy_uid do not use the same parsing routines; what you have listed as configured for the primary_mail configuration setting seems to originate from the secondary_mail defaults, but is not in fact supported.

    To verify what does and what may and what will not work, see step 4 in the process transcript at:

    https://docs.kolab.org/administrator-guide/configuring-the-kolab-server.html#application-of-the-default-recipient-policy-example



  • I don't want magic. I want understandable algorithms and documentation.
    link you gave me use string "domain" with "preferredlanguage": "de_DE" and shoudn't work by default. But ok ,
    when i use really python string format that passed this test , your php function return ' '. Null.

    When i use '%(givenname)s'[0:1].%(surname)s@%(domain)s it makes 2 things:

    1. Write primary email in webadmin panel correct. It means, that my mask is ok.

    2. But. Then starts your second function "apply_formats" in kolab_recipient_policy.php and change this correct mail to crap. and store it to ldap. and cyrus fall down.

    It's ok to say RTFM than you have good documentation. But you don't . I have read all PHP code in kolab, but i'm not php coder..

    i deleted second topic , sorry for double.

    But second question is how to clear cyrus cache and stop that crap?

    Feb 22 13:13:04 mail imaps[3754]: starttls: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits reused) no authentication
    Feb 22 13:13:04 mail imaps[3754]: ptload(): bad response from ptloader server: ptsmodule_canonifyid() failed
    Feb 22 13:13:04 mail imaps[3754]: ptload completely failed: unable to canonify identifier: 't1'[0:1].t1@domain.com
    Feb 22 13:13:04 mail imaps[3754]: SASL bad userid authenticated
    Feb 22 13:13:04 mail imaps[3754]: badlogin: localhost [127.0.0.1] PLAIN [SASL(-13): authentication failure: bad userid authenticated]
    Feb 22 13:13:06 mail imaps[3763]: idle for too long, closing connection
    Feb 22 13:13:07 mail imaps[3755]: starttls: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits reused) no authentication
    Feb 22 13:13:07 mail imaps[3755]: ptload(): bad response from ptloader server: ptsmodule_canonifyid() failed
    Feb 22 13:13:07 mail imaps[3755]: ptload completely failed: unable to canonify identifier: 't1'[0:1].t1@domain.com
    Feb 22 13:13:07 mail imaps[3755]: SASL bad userid authenticated
    Feb 22 13:13:07 mail imaps[3755]: badlogin: localhost [127.0.0.1] PLAIN [SASL(-13): authentication failure: bad userid authenticated]
    Feb 22 13:13:10 mail imaps[3764]: idle for too long, closing connection
    Feb 22 13:13:11 mail imaps[3749]: starttls: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits reused) no authentication
    Feb 22 13:13:11 mail imaps[3749]: ptload(): bad response from ptloader server: ptsmodule_canonifyid() failed
    Feb 22 13:13:11 mail imaps[3749]: ptload completely failed: unable to canonify identifier: 't1'[0:1].t1@domain.com
    Feb 22 13:13:11 mail imaps[3749]: SASL bad userid authenticated
    Feb 22 13:13:11 mail imaps[3749]: badlogin: localhost [127.0.0.1] PLAIN [SASL(-13): authentication failure: bad userid authenticated]
    Feb 22 13:13:13 mail imaps[3765]: idle for too long, closing connection
    Feb 22 13:13:15 mail imaps[3756]: starttls: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits reused) no authentication
    Feb 22 13:13:15 mail imaps[3756]: ptload(): bad response from ptloader server: ptsmodule_canonifyid() failed
    Feb 22 13:13:15 mail imaps[3756]: ptload completely failed: unable to canonify identifier: 't1'[0:1].t1@domain.com
    Feb 22 13:13:15 mail imaps[3756]: SASL bad userid authenticated
    Feb 22 13:13:15 mail imaps[3756]: badlogin: localhost [127.0.0.1] PLAIN [SASL(-13): authentication failure: bad userid authenticated]
    Feb 22 13:13:17 mail imaps[3759]: idle for too long, closing connection
    Feb 22 13:13:18 mail imaps[3757]: starttls: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits reused) no authentication
    Feb 22 13:13:18 mail imaps[3757]: ptload(): bad response from ptloader server: ptsmodule_canonifyid() failed
    Feb 22 13:13:18 mail imaps[3757]: ptload completely failed: unable to canonify identifier: 't1'[0:1].t1@domain.com
    Feb 22 13:13:18 mail imaps[3757]: SASL bad userid authenticated
    Feb 22 13:13:18 mail imaps[3757]: badlogin: localhost [127.0.0.1] PLAIN [SASL(-13): authentication failure: bad userid authenticated]
    Feb 22 13:13:20 mail imaps[3766]: idle for too long, closing connection
    [root@mail frank]# 
    

  • Global Moderator

    I recognize a tone in your message and choose to abandon further participation in the subject.



  • but 5 hours early i give my apologies for emotions in IRC. And you said "no problem"
    Keep it simple. Your product have problems we can discuss about it or not, but better discuss, isn't it?

    One sidestep away from default installation and you ignore questions.


Log in to reply