Domain alias



  • hi all

    are there any information about the domain alias in a ldap enviroment ?

    a main entry like this, doesn’t work for domain2

    dn: ou=domain1,dc=server,dc=com
    kopanocompanyserver: domain1.com
    kopanoviewprivilege: server.com
    objectclass: organizationalUnit
    objectclass: top
    objectclass: kopano-company
    ou: domain1.com
    ou: domain2.com
    

    thanks


  • Kopano

    Hi @noise,

    Kopano does not care for a domain that is assigned to a tenant. So I guess you are asking, because you are missing configuration in your MTA?

    Since this is a hosting system you may want to get in contact with our support.



  • @fbartels said in Domain alias:

    So I guess you are asking, because you are missing configuration in your MTA?

    I’ve always wondered why that is, since its pretty easy to implement it.
    All you need is already in kopano.

    and your “thinking” this is a hosting system, like you did with me.
    but most probly he has multiple domains, like me…

    Multi-tenancy configurations is one of the great features of kopano, its just not used as it should, but thats my personal opinion, this is because for example, if you add a new “company” and you use the domainname. ( per example: add the company name as : domain.tld )
    in mysql all you need is this querie: for example in postfix :
    query = select value from objectproperty where propname=‘companyname’ and value=’%s’

    And if you add a new domain, postfix directly knows.
    I find this part a great feature.

    And you can do exactly the same with ldap.


  • Kopano

    @thctlo said in Domain alias:

    And you can do exactly the same with ldap.

    Yes of course you can do exactly the same with LDAP. But the key point is that the mail domain is not relevant to Kopano at all. The only relevant piece of information is the primary email address of the user.

    Everything else is resolved in the MTA (and therefore Kopano gives you the best flexibility instead of limiting you in what you can do).



  • @fbartels said in Domain alias:

    The only relevant piece of information is the primary email address of the user.

    That flexibility is exactly why i like kopano. :-)



  • Hmmh ok that means this is not possible either with ldap or database to receive emails to the same user with two different domains :-( on all systems i have domain alias like plesk etc. or i need a license for this ?


  • Kopano

    @noise said in Domain alias:

    or i need a license for this

    If it helps warranting the purchase for you, then yes ;-)

    But as said before this is possible, your mta just needs to resolve your aliases for you (Plesk is doing nothing different).



  • ok thanks, i try. at the moment i not want a license, but perhaps later if i kill my kerio.

    edit:
    i do the following query…

    ## (associatedDomain = aliasDomain) (kopanocompanyserver = Domain)
    server_host = localhost
    search_base = dc=test,dc=local
    bind_dn = cn=admin,dc=test,dc=local
    bind_pw = xxxxxx
    scope = sub
    query_filter = (&(objectclass=kopano-company)(|(objectclass=associatedDomain)(|(kopanoCompanyServer=%s)(associatedDomain=%s)$
    result_attribute = kopanoCompanyServer, associatedDomain
    recursion_limit = 9
    expansion_limit = 100
    version = 3
    

    all local tests seems to working, but to work it properly, the complete email address of the second domain must be deposited as an email alias.



  • just setup a new query as alias, look how its done with mysql.
    i have in postfix 5 of these searches/files


  • Kopano

    @noise when you edit your post then this does not get marked as unread on this forum and can therefore easily be missed.

    See this post on StackExchange for some strategies https://serverfault.com/questions/415274/postfix-what-exactly-are-alias-domains



  • @fbartels said in Domain alias:

    https://serverfault.com/questions/415274/postfix-what-exactly-are-alias-domains

    ok tanks, i notice with doing edits ;-)
    i think my queries are working, but now have other things to resolve it.