DataMuseum.dk

top - metrics - download

    Length: 3706 (0xe7a)
    Types: TextFile
    Names: »READ-ME«

└─⟦2d1937cfd⟧ Bits:30007241 EUUGD22: P.P 5.0
    └─⟦dc59850a2⟧ »EurOpenD22/pp5.0/pp-5.tar.Z« 
        └─⟦e5a54fb17⟧ 
            └─⟦this⟧ »pp-5.0/Chans/dirlist/READ-ME« 

TextFile

This directory contains code for an X.500 Directory based list channel.

It is only a test channel at the moment, not quite ready to be 
called a beta-test.
I would not suggest you use in 'in service'.

For those who can't resist playing...

You will need the Quipu-6.1 extensions to ISODE-6.0.
Do NOT try the code against Quipu-6.0 - it will kill your DSA.

The definitions in 'oid.extra.{gec,at,oc}' should be appended 
to the installed oidtables (the best way to do this is add them 
to <ISODE>/dsap/oidtable.*.local and re-install them).

The binaries made by default are:

dirlist		- the list channel itself.
dl		- a Directory based replacement to mlist.
lsd		- a version of Dish that knows about mail lists, and
		  the various X.400 attribute syntaxes.

The dl user interface uses the concept of User Friendly Naming (ufn).
That is instead of using DN's you can enter strings such as
	Robbins, UCL
	Onions, Nottingham
	Rose, Nyser, USA
and the 'ufn' code will try to establish the correct DN.
Initial experience shows the hit rate to be very high.
You need to tailor the 'ufnrc' file to your local needs.
UFN is described in full by an Steve Kille paper.

The structure of the DIT:

A Mail list needs 2 entries in the DIT, an example is given using the
list 'quipu-support' - which is held in the Quipu DIT under
c=GB@o=University College London@ou=Computer Science.

There is the 'cn=quipu-support entry itself.
This has the objectclass 'ppDistributionList'.
Attributes:

	mhsDLMembers	-  The members to send the mail to !
		Syntax is:  ORName ::= <DN> $ <ORAddress>
		If you use the 'dl' interface, you don't need to specify the
		ORaddress component as it is lokked up in the DIT !

	dl-policy	-  The list delivery policy
		Syntax is : <expansion> $ <conversion> $ <priority>
		<expansion> ::= 'TRUE' | 'FALSE'  
			-- If TRUE sub lists are allowed.
		<conversion> ::= 'ORIGINAL' | 'TRUE' | 'FALSE'
			-- Is message content conversion allowed.
			-- ORIGINAL implies use parameter fro original message
		<priority> ::= 'ORIGINAL' | 'HIGH' | 'LOW' | 'NORMAL'
			-- The priority to use when delivering the message

	mhsDLSubmitPermissions - Defines who can send to the list.
		Syntax is : <group> | <individual> | <member> | <pattern>
		<group> ::= 'GROUP #' <DN>
			-- Memeber of the X.500 group <DN> can send to the list
		<individual> ::= 'INDIVIDUAL #' <ORName>
			-- The individual defined by ORName may send.
		<member> ::= 'MEMBER #' <ORName>
			-- A Member of the named list may send.
			-- Only works if the named list is also directory based.
		<pattern> ::= 'PATTERN #' <ORName>
			-- Anybody who's ORName Matches the <ORName> pattern can send.
			-- E.g if <ORName> was 'c=GB', then only people in 'GB" could send
			-- The special token 'ALL' define a pattern which permits anybody to send to the list.

	owner		-	The manager of the list.
		This should be a Role entry, in the Quipu-support
		example it is the DN of Quipu-support-request


The 'cn=Quipu-support-request' entry, which is an OrganisationalRole.
The role ocuppant is the person who manages the list.
In the 'Quipu-Support' example this point to 'cn=Colin Robbins'.
(You don't have to have this entry, the 'Owner' can point directly to the
Manager).

For each local list, you will need an entry in 
isoaliases, to map between the list name and the DN e.g.,
quipu-support: "c=GB@o=University College London@ou=Computer Science@cn=Quipu-support"

In the pp-tailor file you will need someting like...

chan     dirlist        prog=dirlist,
                        show="via Directory List Channel",type=both
                        adr=x400,table=list,
                        bptout="ia5,hdr.822",chanout=dr2rfc,




Colin