Roundcube Community Forum
Release Support => Requests => Topic started by: getrati on April 27, 2022, 03:41:29 AM
-
Hi.. I am getting issue with my newly created roundcube email setup. Unable to send message with it. Some error logs shared below. Please check and suggest how to resolve the issue.
----------------
[26-Apr-2022 16:35:07 +0530]: <82uhjq4q> IMAP Error: Login failed for mailtest against 127.0.0.1 from 49.206.30.101. Empty startup greeting (127.0.0.1:993) in /var/www/html/roundcube/program/lib/Roundcube/rcube_imap.php on line 200 (POST /?_task=login&_action=login)
[27-Apr-2022 10:30:02 +0530]: <8mv05nmj> IMAP Error: Login failed for webmaster@mynewsdash.com against 127.0.0.1 from 49.206.30.101. Empty startup greeting (127.0.0.1:993) in /var/www/html/roundcube/program/lib/Roundcube/rcube_imap.php on line 200 (POST /?_task=login&_action=login)
[27-Apr-2022 10:44:38 +0530]: <8mv05nmj> IMAP Error: Login failed for webmaster@mynewsdash.com against 127.0.0.1 from 49.206.30.101. Empty startup greeting (127.0.0.1:993) in /var/www/html/roundcube/program/lib/Roundcube/rcube_imap.php on line 200 (POST /?_task=login&_action=login)
[27-Apr-2022 10:45:25 +0530]: <8mv05nmj> IMAP Error: Login failed for webmaster@mynewsdash.com against 127.0.0.1 from 49.206.30.101. Empty startup greeting (127.0.0.1:993) in /var/www/html/roundcube/program/lib/Roundcube/rcube_imap.php on line 200 (POST /?_task=login&_action=login)
[27-Apr-2022 11:13:31 +0530]: <8mv05nmj> IMAP Error: Login failed for webmaster@mynewsdash.com against 127.0.0.1 from 49.206.30.101. Empty startup greeting (127.0.0.1:993) in /var/www/html/roundcube/program/lib/Roundcube/rcube_imap.php on line 200 (POST /?_task=login&_action=login)
"errors.log" 145L, 17313C
-
I am at stuck with that issue. Eagerly waiting for your support to resolve the issue. Thanks in advance..
-
You say SMTP issues but then you show errors from 127.0.0.1:993 and 993 is an IMAP port. That does not make sense. Also in those errors there is no protocol specified, it should start with ssl:// or tls://. Finally because you are using an IP and not and FQDN there is no way to verify the cert used in the connection so have you set the conn_options to disable all verification?