OpenEMM Support

At the end of every e-mail, we have a link that allows the user to update his or her profile. Lately, that link hasn't been working. The form below will load the profile information correctly, but when we try to submit it via the Subscribe action, it will error out every single time. Is there a log ...

For example, lets say that our largest list has 48,687 subscribers. When I go to send the mailing, OpenEMM will tell me that there are:
16966 Text-E-Mails
50053 HTML-E-Mails

Which makes me think there are 67,019 subscribers. However, when I do the final send, it tells me that there have been 48,687 ...

OpenEmm shows the wrong count just before you send. However, shows the correct count when sent. Why is this? Can it be fixed?

Nevermind! I just got it. I had to go into semu.py and explicitly define the location of the smart-relay file, changing:

SMART_RELAY = agn.mkpath (agn.base, 'conf', 'smart-relay')
fd = open (SMART_RELAY)

to:

fd = open ('/home/openemm/conf/smart-relay')

after that, the Sendmail queue ...

I'm running into the same problem on CentOS 5.5 with OpenEMM 6.0.1. I have my smart-relay set to 127.0.0.1, but it continues to send as though the relay weren't set. I modified my semu.py as:


def getRelay (self, domain):
if self.checkForSmartRelay:
self.checkForSmartRelay = False
try:
SMART ...

This could be an indication that I need new glasses, but, where can I find the RPM for install on CentOS?

I checked http://sourceforge.net/projects/openemm/files/, and while they have the zip, bin.tar.gz et. al, I cant see the RPM.

I got similar errors until I installed the newest version of JDK. Also remember to delete the link to the old JDK when you install.

We just had a PCI scan and the version of Resin that OpenEMM uses is officially out of date and (apparently) susceptible to a lot of exploits. Since OpenEMM runs as a singular package, is there a way that I can update just Resin?

Thanks!

Our company is scanned regularly for PCI compliance. Recently the log-in for OpenEMM has been identified as an issue as the information is not encrypted on login. I'm using RHEL 5. Does anyone know what I can do to appease the PCI gods?

I'm trying to create a new form/scripted action for referring a friend to our mailings. I've read chapter 11, but there is little useful information for advanced action management. Are there any good sources of help out there?