-
Beiträge
-
-
I installed OTOBO in Docker. Everything works, but there’s one problem. I keep getting error messages, about once a minute. The error log looks like this:
[Wed Feb 25 14:37:19 2026][Error][Kernel::System::Daemon::DaemonModules::BaseTaskWorker::_HandleError][60] There was an error executing Execute() in Kernel::System::Console::Command::Maint::Email::MailQueue: The CRAM-MD5 SASL mechanism is effectively deprecated by RFC8314 and should no longer be used at (eval 510) line 1.
How can I fix this? -
-
Log by link
Yes, valid addresses have been assigned. Mail arrives and departs normally. The only problem is the email sent every minute to the administrator, which, as far as I understand, is generated by the system. -
Hi Dmitry,
just an idea, but as it looks a bit like admin notifications are sent once a minute per email – maybe check setting
Daemon::SchedulerTaskWorker::NotificationRecipientEmailIn case the email sender address is not valid, that could cause trouble?
Otherwise, since there is this warning about CRAM-MD5 SASL in your logs: Is your email server configured to support CRAM-MD5 as authentication method?
Otobo itself does not use CRAM-MD5 per se, for talking SMTP to the email server Otobo delegates to Net::SMTP which will cycle through the available authentication mechanism advertised by the server, until it can successfully authenticate with one of these. In case that leads to an attempt via CRAM-MD5, it is that Net::SMTP does issue a warning, which you see bubbling up. The warning itself is legit – CRAM-MD5 is deprecated. You might want to check if the email server actually does offer CRAM-MD5?
In case you cannot re-configure your email server, disabling above setting would probably silence all warnings, if that is an option.
kind regards,
-mike
-
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.