[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Schema for Postfix



Hello,

You will need to create your own. I found that this is not an easy task.
You will need to replace the XXXXX with your own Enterprise Number. The
Openldap FAQ has info on how to get your own number- it is free.

(BTW, any input on this schema design is MOST welcome. This was my first
attempt and works well for me.)

Here is what I created and I use this for all the lookup tables for PF.

Hope it helps!


###################################################
#
# Mail server lookup tables
#
# Created from book "Postfix" by Richard Blum
# and other sources

# Attribute Type Definitions

attributetype (1.3.6.1.4.1.XXXXX.21.0.0
        NAME ( 'ltv' 'lookupTableValue' )
        DESC 'Pattern To Match'
        EQUALITY caseIgnoreIA5Match
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.26)

attributetype (1.3.6.1.4.1.XXXXX.21.0.1
        NAME ( 'ltr' 'lookupTableReturn' )
        DESC 'Value Returned'
        EQUALITY caseIgnoreIA5Match
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.26)

attributetype (1.3.6.1.4.1.XXXXX.21.0.2
        NAME ( 'pn' 'profileName' )
        DESC 'type of scenario- like LVS, CORE, GLOBAL'
        EQUALITY caseIgnoreIA5Match
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.26)

attributetype (1.3.6.1.4.1.XXXXX.21.0.3
        NAME 'pDescription'
        DESC 'Profile Description'
        EQUALITY caseIgnoreIA5Match
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.26)

attributetype (1.3.6.1.4.1.XXXXX.21.0.4
        NAME ( 'lTT' 'lookupTableType' )
        DESC 'alias, virtual, relocated, access, canonical, transport'
        EQUALITY caseIgnoreIA5Match
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.26)

###################################################

#
# mailServer Object - represents one server's settings
#

objectclass ( 1.3.6.1.4.1.XXXXX.21.1
        NAME 'mailProfile'
        SUP top STRUCTURAL
        DESC 'Mail Profile'
        MUST pn
        MAY pDescription  )

#
# lookupTable Object - one container for each flavor
# of table type: alias, access, canonical, relocated, transport, virtual
#

objectclass ( 1.3.6.1.4.1.XXXXX.21.2
        NAME 'mailTable'
        SUP top STRUCTURAL
        DESC 'Lookup Table'
        MUST  lTT
        MAY pDescription  )

#
# looupTable Table Entry- generic object for storing a table
# entry

objectclass ( 1.3.6.1.4.1.XXXXX.21.3
        NAME 'lookupTableEntry'
        SUP top STRUCTURAL
        DESC 'Lookup Table Entry'
        MUST ( lTV $ lTR )
        MAY pDescription  )


Hope it helps!
-- 
Dave Augustus
Network Operations Center
Kenneth Copeland Ministries