[Fabio Macchia]

ello,

My Otobo installation cannot send outgoing emails. The system log shows Can’t connect to smtp.gmail.com: !, but the server itself can connect to Google’s SMTP without any issues.

 

Summary of Tests:

Here is what we have confirmed is working correctly on the server:

telnet smtp.gmail.com 587 -> Connects successfully.
openssl s_client … -> Handshake completes successfully (Verify return code: 0 (ok)). The server trusts the certificate.
sudo -u otobo dig smtp.gmail.com -> DNS resolves correctly for the otobo application user.
otobo.CheckModules.pl –all -> All required Perl modules for mail (Net::SMTP, IO::Socket::SSL, etc.) are installed and ok.
SELinux/AppArmor -> Checked and confirmed they are not blocking the connection.
The Core Problem: Even though all underlying system and dependency checks pass, the Otobo application log still shows a Can’t connect error.

We also noticed that a single otobo.Daemon.pl start command launches 6-7 separate daemon processes at once, which seems abnormal.

Question: Why would the Otobo Perl environment fail to connect when all system-level tools work perfectly? What could be the cause of the multiple daemon processes?

Any ideas for deeper debugging would be greatly appreciated. Thank you.

[Autor]

Beiträge