OpenEMM Technical Support Forum

You have to get rid of the clone version of Java (from FSF) first with

yum remove java*

before you install the "real" Java from SUN.

We have not tried yet, but OpenEMM should run with Java 6. Why don't you check it and report the result back here for everybody?

This is a bug which will be fixed with version 5.1.1 (planned for release next week). Workaround: create a target group of your choice (you do not have to use it).

Thanks for your feedback so far! Although, we are still at the beginning with OpenEMM (the RC1 came out just 1 year ago), I think we (the developers and the community) have already achieved a lot: - a small but growing and compared to its size very supportive community - all verified bug reports fro...

According to our experience 10,000 mails per hour is a decent (i.e. above-average) performance for a state-of-the-art server with one dual-core-CPU in a real world environment (with real world providers at the other end of the line).

Yes, but there is a Linux and a Windows version.

Your basic configuration looks just fine. I will move this thread to the bugs forum to make it easier to find other users who are affected by this problem

We tried to confirm this behaviour with OpenEMM 5.1- but could not. What OpenEMM version do you use?

We closed this thread because we just released the final version of OpenEMM 5.1 for Windows.

Any language except for Latin and Klingon is welcome!

OK, we will add the mysql/bin directory to the search path for those users who do not use the standard paths suggested by MySQL in the next bugfix release.

We just confirmed this as a bug and will fix it in release 5.1.1.

I just checked with our demo account of OpenEMM 5.1 (see http://demo.openemm.org:8081/logon.do?action=0) and it worked. Do you use 5.1?

OpenEMM never removes addresses, but if an e-mail address generates a hard bounce the address is deactivated, and if an e-mail address generates the n.th soft bounce (don't know the exact number right now) it is also deactivated. Perhaps ud can provide more details here.

In the meantime we confirmed this bug. It only occurs when no target group is defined. As a workaround please define an arbitrary target group.

Thank you for finding this bug!

Sorry, we could not reproduce this issue. Could you please provide the OpenEMM version you are working with and exactly which button in which screen of the wizard you hit before the error showed up?

Thank you!