Infos:
- Used Zammad version: 6.0.0
- Used Zammad installation type: docker-compose
- Operating system: Linux
- Browser + version: Not applicable
Actual question
We have multiple Zammad instances which were not able to send mails for some hours due to a network outage and we see the “unable to send email” notification box at a lot of tickets in the UI.
Delayed::Job.count is 0 for all instances so we assume Zammad has given up forever on retrying to send these emails?
Are there ways (presumably in the rails console) to:
a) find all tickets where email was not sent
b) re-create the jobs to send these emails?
(although not really meaningful i filled out the given points)
Expected behavior:
- There is a clear way to determine and possibly re-send emails which did not leave Zammad due to a mail server outage. Possibly using the rails console.
Actual behavior:
- Information in the documentation, forum and in github issues is unclear and offers no advice how to really examine the state or re-create jobs if that might be required
Steps to reproduce the behavior:
- Let the outgoing mail server fail for a couple of hours
- See the delivery failure messages at the tickets in the UI
- Try to know:
- a) if Zammad will re-send them if the mail server is available again after a longer down time
- b) if not (a): if there is a way to find all tickets/articles in the system having a delivery failure
- c) if (b) trigger the re-creation of the delivery job for all tickets