OpenEMM Support

Successfully used the manual? No.

Got it working? Yes.

sturmey wrote:The documentation for this product is abysmal. The people who created the user manual should be ashamed of how inadequate it is.

Has anyone successfully used the "manual" to get openemm working?

The format uses regular expressions. Putting each possibliity on a seperate line seems to work better.

I had to add a bunch of stuff to get mine to work properly. The base file barely got anything. Here is my [hard] section:

[hard]
#
unknown user|user unknown|user not found
550 No such recipient ...

I had to add the following to bav.rule under [hard]:

550 No such recipient


I would suggest to others to look at var/spool/filter/unspec-1, look at the bounce messages there, and look for a tell tail line that can be put in bav.rule.

I spent about two hours putting debug messages in bavd.py and ...

Note: Gave up - installed the VMX version.

Note: Gave up, installed the VMX version.

Okay, so man 5 procmailrc has bavrc documented.

I understand that file. But I still cannot find any docs on the format of bav.rule, and I think this is where my problem lies.

I have a bounce message coming back, shows up in var/spool/filter, but doesn't make it to my bounce filter, or ...

That's what I did - working fine now, so obviously the VM is bad.

I agree with you completely - this seems like a good system but documentation and support are very inadequate. If I don't get it working today, we may go the same route...

...and the xmlback file in that VMX install is broken.

Links you want to be tracked or links that you want an action to take place must be trackable, and will/must be modified by the system to point back to the openemm server in order to function.

Links that you don't need to track and don't want converted, make untrackable.

The openemm system must be ...

On the Trackable Links tab, select each link, edit, and set it to not trackable.

I'm getting the error "Unable to get database cursor" in the pickdist.log, the bav-update.log and the update.log

test and admin messages go out, but not regular messages.

Running on SLES 9 SP 3

Any ideas?

Tried like heck to get it working on SuSE Linux Enterprise Server 9 SP 3.

Gave up, went to running the VMX version, although I had to work like heck to get that one working too, which one should not have to do.

That's where mine's running, so the answer is yes.

I didn't do anything special to get it there. I think the install figured out 8080 was in use and used the next available.

~openemm/conf/console.conf has the port number in it. That's the only place in my tree where 8081 appears.

Hope this helps.

Same deal here! What's the solution???

I have python-mysql installed, so that's not it.