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 Rem...
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 testi...
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 unsubscribes t...
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...
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 p...