efa-project.org

Recently upgraded from 3.0.1.6 to 3.0.2.1. Since the upgrade, users are no longer receiving the daily quarantine report I had configured.

Checked /var/www/html/mailscanner/conf.php and settings look valid for daily report still.

When running /uar/local/bin/mailwatch/tools/Cron_jobs/mailwatch_quarantine_report.php manually, it runs with no issue and sends the report.

/etc/cron.daily/mailwatch has the proper command as above, but I didn't receive the quarantine this morning like I usually do.

/var/log/cron doesn't show anything for that task, but looking back at the log before the upgrade, it seems it never has.

Not sure where else to look or what to do next. Any thoughts?

Oh, also another thing I've noticed since the upgrade- there seems to be a session timeout on the management web interface for mailwatch now- where can I set/change that? It seems to be relatively short (~10 minutes or less).

What happens if you try to run /etc/cron.daily/mailwatch directly? (just to verify that the file is syntactically correct)

shawniverson wrote: 13 Apr 2017 15:20 What happens if you try to run /etc/cron.daily/mailwatch directly? (just to verify that the file is syntactically correct)

Seems to run without any problem. No output at all- just takes about 10 seconds and returns to prompt. I received new quarantine reports after running it that way, so seems like it works.

Also, I added an edit about this- any thoughts:

Oh, also another thing I've noticed since the upgrade- there seems to be a session timeout on the management web interface for mailwatch now- where can I set/change that? It seems to be relatively short (~10 minutes or less).

Is the cron daemon actually running?

Session timeouts improvements coming, stay tuned.

Yep, crond appears to be running.

I tried a reboot and will report back tomorrow if it doesn't run in the morning.

Really appreciate the fast responses and love the project!

Thanks!

shawniverson wrote: 13 Apr 2017 15:38 Session timeouts improvements coming, stay tuned.

That'd be a useful improvement.

Waiting on one last pending PR in MailWatch before release of 3.0.2.2

Not to be a nag, but do you know where I can change the timeout manually? The brutally short timeout is starting to piss me off and I'll happily hardcode a fix until it is actually fixed.

What were they thinking?

near the top of functions.php, you'll see the timeout values.

I increased the numbers by a factor of 10 according to https://github.com/mailwatch/MailWatch/issues/730 but I still get timeouts in Chrome for MacOSX when the tab is not in the foreground.

It's super annoying.

Just fyi.

Working on 3.0.2.2 today