Cron to execute Channel::EmailParser.process_unprocessable_mails

Infos:

  • Used Zammad version: 6.2.0
  • Used Zammad installation type: (source, package, docker-compose, …) source
  • Operating system: Debian 12
  • Browser + version:

Expected behavior:

  • Process all tickets from email sources.

Actual behavior:

  • Sometimes a mail was a unprocessable mails.

Steps to reproduce the behavior:

  • We are having some problems with our mail server running out of resources.

When that happens, sometimes support emails from our customers are left unprocessed and we have to do it manually from the Zammad console with:
Channel::EmailParser.process_unprocessable_mails

The problem is that if we don’t check the monitoring option, our customers’ support requests are left in limbo.

While we solve the real problem with our mail server… could we generate a daily cron to run Channel::EmailParser.process_unprocessable_mails? how should we do it?

Why would you do that?
Failing mails usually have a reason. It happens like 1% of the time that “just something hit the fan and you can reimport without issues”.

Running it automatically will most likely only end in errors being thrown on a regular basis and you still don’t solve the issue.

Implement a proper monitoring solution that monitors Zammads endpoint and “alerts you” if healthy: false is present.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.