Notification error

[exctble]

Infos:

• Used Zammad version: 6.3.1
• Used Zammad installation type: source
• Operating system: Ubuntu 22.04

Expected behavior:

• Notifications work correctly

Actual behavior:

• Notifiction doesn’t work right now

Logs of problem in monitoring section: * Channel: Email::Notification out Net::SMTPFatalError

Logs from production.log:

E, [2024-08-31T10:42:07.361457#551175-149160] ERROR -- : Can't use Channel::Driver::Smtp: #<Net::SMTPFatalError: Net::SMTPFatalError>
E, [2024-08-31T10:42:07.361534#551175-149160] ERROR -- : 550 non-local recipient verification failed
 (Net::SMTPFatalError)
app/models/channel/driver/smtp.rb:98:in `deliver'
app/models/channel.rb:263:in `deliver'
lib/notification_factory/mailer.rb:172:in `deliver'
lib/notification_factory/mailer.rb:226:in `notification'
app/models/transaction/notification.rb:217:in `block in perform'
app/models/transaction/notification.rb:106:in `each'
app/models/transaction/notification.rb:106:in `perform'
lib/transaction_dispatcher.rb:61:in `execute_single_backend'
app/jobs/transaction_job.rb:25:in `block in perform'
app/jobs/transaction_job.rb:21:in `perform'
lib/background_services/service/process_delayed_jobs.rb:25:in `block (2 levels) in launch'
lib/background_services/service/process_delayed_jobs.rb:23:in `block in launch'
lib/background_services/service/process_delayed_jobs.rb:20:in `loop'
lib/background_services/service/process_delayed_jobs.rb:20:in `launch'
lib/background_services/service.rb:27:in `block in run'
lib/application_handle_info.rb:19:in `use'
lib/background_services/service.rb:33:in `block in run_in_service_context'
lib/background_services/service.rb:32:in `run_in_service_context'
lib/background_services/service.rb:26:in `run'
lib/background_services.rb:67:in `block in start_as_thread'

E, [2024-08-31T10:42:07.368217#551175-149160] ERROR -- : Can't use Channel::Driver::Smtp: #<Net::SMTPFatalError: Net::SMTPFatalError> (Channel::DeliveryError)>
app/models/channel.rb:289:in `handle_delivery_error!'
app/models/channel.rb:270:in `rescue in deliver'
app/models/channel.rb:251:in `deliver'
lib/notification_factory/mailer.rb:172:in `deliver'
lib/notification_factory/mailer.rb:226:in `notification'
app/models/transaction/notification.rb:217:in `block in perform'
app/models/transaction/notification.rb:106:in `each'
app/models/transaction/notification.rb:106:in `perform'
lib/transaction_dispatcher.rb:61:in `execute_single_backend'
app/jobs/transaction_job.rb:25:in `block in perform'
app/jobs/transaction_job.rb:21:in `perform'
lib/background_services/service/process_delayed_jobs.rb:25:in `block (2 levels) in launch'
lib/background_services/service/process_delayed_jobs.rb:23:in `block in launch'
lib/background_services/service/process_delayed_jobs.rb:20:in `loop'
lib/background_services/service/process_delayed_jobs.rb:20:in `launch'
lib/background_services/service.rb:27:in `block in run'
lib/application_handle_info.rb:19:in `use'
lib/background_services/service.rb:33:in `block in run_in_service_context'
lib/background_services/service.rb:32:in `run_in_service_context'
lib/background_services/service.rb:26:in `run'
lib/background_services.rb:67:in `block in start_as_thread'

What can i do with this problem? The credentials in settings correct.

[MrGeneration]

550 non-local recipient verification failed

Ask your configured mail server I’d say. That’s what Zammad gets in return of trying to send out the notification.

[exctble]

Yes, I read about this problem that it is most likely on the mail server side, but i use a 5-10 minutes ago a old Zammad with old version, where the same settings and creds. Now i’m asking about fresh zammad and try to configure email notifications. Interesting, that send and receive emails working good, but it’s problem only with notifications.

Any ideas about that? Mail server is public, not private.

[exctble]

Guys, i found the solution, you must assign an email on your agent, which will be accept the notification. Without that, he sort the agent in ascending order and check the e-mail for notification, when he found user without e-mail - this is broke him. For me it was the 2 first users, which have a e-mail, and the 3-rd was without e-mail.