2. There are - to my mind - a quite limited number of calls available. For example I see no way of being able to "get" a list of Mailinglist names & IDs, or Mailings & their IDs or return a subscriber search of more than one entry.

This will make creating an "interesting" extension quite hard... Are there any examples where others have used direct database access rather than SOAP to build extensions and how much effort is there in maintaining this as and when upgrades to the db schema occur?

2. We started developing a new webservice interface based on Spring WS (instead of Axis) and covering 80% of OpenEMM's functionality. However, this will take some time, so do not expect it before October/November.

2. We started developing a new webservice interface based on Spring WS (instead of Axis) and covering 80% of OpenEMM's functionality. However, this will take some time, so do not expect it before October/November.

Oooh - That sounds very interesting. So, if we start on something now using the functionality available today, it should be relatively easy to migrate that work to the new interface?

Is there any documentation or design specs that could help us in the interim period? (I'd be happy to sign an NDA if you need us to).

To use targetgroups there has to be a field "tx_teopenemmnewsletter_targetgroups" in the fe_users table. This field should be created when you install the extension. In this field the targetgroup a recipient selected will be stored. Also there must be a field "targetgroups" in the OpenEMM database. How to create customs fields in OpenEMM is described in the OpenEMM documentation. When you synchronize your users the values from the field tx_teopenemmnewsletter_targetgroups in the TYPO3 database will be stored in the field targetgroups in the OpenEMM database. Then you have to create targetgroups in OpenEMM like it is described in the OpenEMM dokumentation. After that you can select a targetgroup when you create a newsletter in TYPO3.