Comments received via incoming mail aren't triggering notifications

avatar BrianJCohen Pro May 1. 2010. 12:03 pm
The incoming mail module is no longer functioning correctly for us. This is a rather critical issue. The symptoms are:

- Anything you do via the web that triggers an email notification (eg, post a comment to a ticket that has subscribers) will successfully dispatch that email notification and all valid recipients will receive it. This is working fine.

- However, if you reply to a notification from your email client, that message will be successfully delivered to the incoming mail account's mailbox and activeCollab's script in cron will successfully pick it up, parse it, and place the comment in the right ticket or discussion. But, unlike if you had posted this via the web, the system isn't dispatching an email to the other subscribers to the ticket/discussion. Until recently, this was working correctly.

I poked around, and it looks like the incoming mails that it fails on are sitting in the table `acx_incoming_mails`.
avatar Dušan Marić Staff May 3. 2010. 5:03 am
Hi Brian,

As we have checked your activeCollab setup, it turns out that the system does successfully sent email notifications regardless an action being triggered via the web or by Incoming Mail module.

The most possible reason for not receiving notifications any more is users' email client spam filters or any sort of script that blocks certain email addresses.
activeCollab team member
avatar BrianJCohen Pro May 3. 2010. 11:10 am
Dusan,

I replied to your support request response. Clearly you either did not understand the problem as described or you did not fully investigate the matter. The problem persists and can be readily and easily duplicated on any ticket or discussion. This issue has nothing to do with spam filters, as I can verify that activeCollab is never attempting to send the emails in the first place.
avatar Ilija Studen Staff May 4. 2010. 8:39 am
Hello,

Thanks Brian for digging into this and figuring out what the problem was.

Problem was that scheduled tasks triggered through command line interface consumed more memory than when they were triggered via URL. When we tested your setup, we manually triggered scheduled task events by visiting event URL and they worked well.

Simple increase of memory_limit resolved the problem. Also, swhiching from CLI to triggering via curl that pings task URL would also resolve the problem.
avatar BrianJCohen Pro May 4. 2010. 9:57 am
Ilija,

As I recommended to Dusan when I explained the memory exhaustion issue, I recommend you add a sanity check to the activeCollab installation script that ensures the memory_limit of the CLI PHP is sufficiently high.
avatar Ilija Studen Staff May 4. 2010. 11:42 am
Yes, definitely. We'll update installer to check memory_limit and warn you when it's lower than recommended.

Try activeCollab free for 30 days, No credit card required!

Instant access to activeCollab, no installation needed.

.tryactivecollab.com

If you are already a user of activeCollab, you can log in here.