OpenEMM Support

Sorry to report that we have decided to go with a commercial product. The documentation and support here are just not adequate. I tried like the dickens to get this system running for about 2 months now and feel like all I got was bruises...

I could really use some help with this. The documentation, as I read it, is either very incomplete or wrong, and I am admittedly a noobie with forms and OpenEMM.

I follow the manual to create a subscribe form and the accompanying actions and all that gets returned is the error.

For one thing, the ...

Here's pretty much everything I did...
1. checked for zombie processes, if found reboot

2. edit bin/mailer.sh to apply the fix for sendmail pid files: remove $BASE from the two lines referencing sendmail PID files (only if sendmail is complaining, which it was)

BEFORE:

$sm -q1m -NNEVER ...

I discovered a zombie java process... after a reboot, we now see the error form when clicking on archive or fullview link in mailing. There is no longer an error logged in jvm_redirection.log or jvm_console.log.

Any thoughts?

- Andrew

After getting 5.3.2 installed and working so I can send test mailing, neither the fullview nor archive is working. I followed the user manual for creating the actions and forms, at first I found that the ##AGNUID## string in the link was not being interpreted. I found this thread: http://www.openemm ...

Just as matter of housekeeping, the following was posted in another thread, answering the question regarding the differing file sizes...

Simple solution: the TAR file is the original build source for the RPM where the binary is not stripped. During the build process of the RPM the binary is ...

OK, I got it working this time using xmlback from the tar file. The only strange thing I encountered is that running the rpm upgrade as root caused my /tmp directory to be chown'ed to the openemm user. Once I returned the permissions and ownership on /tmp, everything works properly... so far ...

I had the same problem with the RPM (on Fedora 6) which I downloaded and installed after january 7.
I followed the hint and I pulled the xmlback from the OpenEMM-5.3.2-bin.tar.gz file and now I can send testmails.

Can you elaborate at all... I tried this once and I got a version mis-match error ...

CentOS 5.0
java version "1.5.0_14"
mysql-5.0.22-2.2.el5_1.1

Looks like you have a problem with the xmlback binary. Unfortunately this is not the first case, but we cannot reproduce the error here. One reported solution : fetch the .tar.gz file and use the xmlback found in this package. If this still does not solve the problem, you can compile the binary ...

I re-installed with the fresh rpm and have the same problem...

/var/log/*mailgun.log:
[07.01.2008 11:48:22] DEBUG/write/meta/(1/1/1/3): Try to execute /home/openemm/bin/xmlback -vql -E /tmp/error53148.tmp -o generate:temporary=true;syslog=false;account-logfile=/home/openemm/var/spool/log/account ...

I am having identical problem on CentOS 5 after update to 5.3.2. On sending a test mailing, no mail is sent and mailgun.log shows:


[04.01.2008 09:04:19] ERROR/writer/meta/(1/1/2/30): command /home/openemm/bin/xmlback -vql -E /tmp/error3159.tmp -o generate:temporary=true;syslog=false;account ...

MA says it's not "real" config because you don't have iptables set up yet (If it's running, you're in deep doodoo, as your default actions for all chains is accept). The file you quoted is just the default config before any rules are added or initialized. Try googling on "iptables howto". You can ...

along, did you find out something that is worth to share with the community? If so, please post. Thank you!

Briefly, I had a great deal of trouble getting this install to work. Finally, I decided to try putting the host in our DMZ (using iptables rather than our PIX for firewall) and giving it a ...