OpenEMM Technical Support Forum

The method findByColumn which is also used by the web service has a bug: When several recipients with the same email are registered the returned customer id will be always zero, the documentation of the method and the web service method state that the first match would be resulted though. I guess so...

Okay, as I see it one has to patch semu.py.

Can someone give me a hint how to make a hard bounce out of this please?

Calling exec from Java on some command will copy the whole memory of the application starting the command. If it's not possible, you will get the exception you have provided. For more information check http://stackoverflow.com/questions/209875/from-what-linux-kernel-libc-version-is-java-runtime-exec...

When browsing the mailing list, two SQL statements are fired. Both are very slow (around 80 second eachs on my development machine) and mysqld consumes 100% of one core. That's for just around 8500 mailings. 1. query: mysql> select count(*) from ( SELECT *, case when senddate is null then 0 else 1 e...

I've found how it's being dealt with.

The stuff is hard coded in the file semu.py and entries will be deleted from spool queue after 24h hours.

Thank you.

A restart only leads to the unpacking of the next chunk of 5,000 mails, so it does not help really. You have to investigate why Sendmail can not empty its queue: Are receiving SMTP servers blocking mails? Too many invalid addresses or softbounces? Thank you for your reply. We're not using sendmail ...

Is there a way to configure OpenEMM in a way so that the python based Sendmail emulation stops retrying to send a soft bounced entry after a certain retry count (let's say 20) and marks it as a hard bounce then and opts out the recipient from the mailing list/all mailing lists? I have seen "Rem...

The var/spool/QUEUE directory had over 10k files in it and didn't accept any new files: [26.07.2010 00:38:59] 3979 INFO/loop: Queue is already filled up Only after a restart of OpenEMM things went on normally and mails from the queue were proccessed and new were accepted to the queue with the queue ...

Hi, I know its not really a Bug but to some degree it is one nevertheless. With the current "toolings" like Apache CXF (and as I have read also the current AXIS versions), it is not possible to generate Java Code out of the provided WSDL as the RPC/Encoded style seems to be from an WS era...

Thank you.

Fresh 6.0.1 which got the schema from the file accompanying the release.

Should I be worried about this:
Is the table missing or is some code referencing a table which has a new name?

Anyone?