Dumb(?) schema problem

["Keith T. Garner" <kgarner@kgarner.com>]

I'm writing an application that uses its own schema to store some
data.  With OpenLDAP 2.0.x everything was smooth sailing.  With
OpenLDAP 2.1.x, I'm getting an error with the one structural object
I've created.  Looking in gq it appears to be structural as far as
openldap is concerned, but once I try to add something to do, it
fails.

>From my attempts:

Dec  4 17:52:47 zorak slapd[1821]: conn=13 op=12 ADD dn="jvd=domain1.test,o=hosting,dc=jamm,dc=test" 
Dec  4 17:52:47 zorak slapd[1821]: conn=13 op=12 RESULT tag=105 err=0 text= 
Dec  4 17:52:47 zorak slapd[1820]: conn=13 op=13 ADD dn="mail=acct1@domain1.test,jvd=domain1.test,o=hosting,dc=jamm,dc=test" 
Dec  4 17:52:47 zorak slapd[1820]: conn=13 op=13 RESULT tag=105 err=65 text=no structural object classes provided 

Here's what JVM/JammVirualDomain looks like:
    objectclass ( 1.3.6.1.4.1.12461.1.2.3 NAME 'JammVirtualDomain'
            SUP top STRUCTURAL
            DESC 'Virtual Domain entry to be used with postfix transport maps'
            MUST ( jvd $ accountActive $ lastChange $ delete $ editAccounts $ 
                   editPostmasters )
            MAY ( postfixTransport $ description  ) )

Here's what the JammMailAccount object (that is trying to be added)
looks like:
   objectclass ( 1.3.6.1.4.1.12461.1.2.2 NAME 'JammMailAlias' SUP top AUXILIARY
            DESC 'Mail aliasing/forwarding entry'
            MUST ( mail $ maildrop $ accountActive $ lastChange )
            MAY ( mailsource $ cn $ description $ userPassword ) )

Is there anything really obvious that I'm missing?

Keith

-- 
   Keith T. Garner                                        kgarner@kgarner.com
   The whole problem with the world is that fools and fanatics are always so
 certain of themselves, and wiser people so full of doubts.  --Bertrand Russell