Infos:
Used Zammad Version:
- 6.4.1-173684
7225.e899e544.noble
Environment:
-
Installation method: package -
Operating system (if you're unsure: cat /etc/os-release ): ubuntu 24.04 -
Database + version: postgresql 16.6 -
Elasticsearch version: 8.17 -
Browser + version: firefox 134, edge 131
Expected behavior:
What should happen is that the email server is re-checked at a proper interval (let’s say every minute) and it should come back to life by itself, without human intervention.
Actual behavior:
If the email server for notification is temporarily unavailable for some reasons (i.e. I had to shut down the mail server for some minutes), the outbound notification email get stuck and never recover.
I see these errors in the log:
E, [2025-01-15T07:15:55.458843#54149-183620] ERROR -- : Can't use Channel::Driver::Smtp: #<Net::SMTPServerBusy: Net::SMTPServerBusy>
E, [2025-01-15T07:15:55.458960#54149-183620] ERROR -- : 450 4.7.1 Error: too much mail from X.X.X.X
Then I need to edit the outbound notification email, click continue and it comes back to life again.
Steps to reproduce the behavior:
Make the notification email server unavailable and send an email as a customer