OpenEMM Technical Support Forum

We plan to setup a SVN repository with read access for everybody (and write access for committers) after the release of OpenEMM 5.5 in May.

Yes, I will update the webservice doc and post a hint to the SourceForge bugtracker. Thanks for your patience!

This is the fix regarding the path:

change the second line in EmmCreateWSDL.sh to

DEPLOY=/home/openemm/webapps/core

Does it work now?

Have you noticed that with 5.4.0 the path has changed from /home/openemm/webapps/openemm/htdocs to /home/openemm ?

Apparently, OpenEMM does not find the Axis libs. Please copy libs axis.jar, jaxrpc.jar, saar,jar, wsdl4j.jar and xercesImpl.jar from /home/openemm/webapps/core/WEB-INF/lib to home/openemm/lib. Does this help?

abmm, have you set up the redirect service properly so that link clicks are visible in the statistic view? If not, see install guide for explanation.

OK, that looks alright. Could you provide me with test data by PM so that we can try to reproduce the problem and see if it is a bug we have to fix?

Have you tried out column names without a blank like AgentName and AgencyName?

Please see http://www.agnitas.de/openemmservice-de.shtml

In case you use the Windows version plase see here:

http://sourceforge.net/tracker/index.ph ... tid=848488

For updates of OpenEMM please follow the install guide (we uploaded the latest version yesterday).

Our specialist (ud) for this script is on vacation until Eastern. Since this seems to be no case of urgency I will not call him back to the office.

slrtscn.py is our "syslog realtime scanner" which analyzes log files for sent mails and bounces and writes information to files to be processed by update.py. If slrtscan.py is very busy this could mean that is has to handle a lot of bounces.

We (the developers) have no experience with exim. Maybe someone else can help?

However, it is a pity that OpenEMM causes problems with OpenSuse. Since we only use Red Hat and CentOS it would be great if someone from the Suse camp could offer some insights. (I guess it is a problem with Suse's special sendmail configuration.)