George Holbert wrote:
I'm attempting to add a mail-routing draft schema
(draft-lachman-laser-ldap-mail-routing-02.txt) to FDS.
The schema can be found here (among other places):
In an unusual and unfortunate coincidence, the mailRoutingAddress OID
defined by the schema is the same as the OID for 'ntGroupType', which is
defined in FDS' 50ns-directory.ldif schema.
DESC 'Netscape defined attribute type'
X-ORIGIN 'Netscape NT Synchronization'
The OID arc belongs to Netscape Directory server, and was submitted to
alvestrand on Feb 11 1999:
DESC 'RFC 822 address to use when routing messages to
the SMTP MTA of this recipient'
This expired draft was first written in May 1999 by H. Lachman at
He was correct to use the Netscape ARC, and I don't see a more
I can't say which came first, the draft, or the Netscape Messaging
Server 4, which brought that schema, (as far as I can tell).
The most obvious solution is to change the OID of one of these. But
which one should be changed, and to what?
There's probably not really a single right answer, but if anyone else
has happened to run into this, I'd be interested to hear how you
I would say that the OID from the mail routing draft should be changed
and you should file an "ITS" (bug report) at the OpenLDAP site. The
conflicting OID is a company private OID, and is from an expired draft.