Mail::IMAPClient::_imap_command_do(Mail::IMAPClient=HASH(0x5573e6f6ba90), "CLOSE") called at /usr/share/perl5/Mail/IMAPClient.pm line 1238 When you log into the mail system, davmail will pop up a window to allow you to do Duo 2-factor authentication: Note that the password dialog might show you two. Mail::IMAPClient::_get_response(Mail::IMAPClient=HASH(0x5573e6f6ba90), 3, undef) called at /usr/share/perl5/Mail/IMAPClient.pm line 1340 14 at /usr/share/perl5/Mail/IMAPClient.pm line 1429. Kernel::System::Console::InterfaceConsole::Run(Kernel::System::Console::InterfaceConsole=HASH(0x5573e2cac530), "Maint::PostMaster::MailAccountFetch", "-debug", "-mail-account-id", 1) called at bin/ line 37ĮRROR: * BYE Connection closed. Kernel::System::Console::BaseCommand::Execute(Kernel::System::Console::Command::Maint::PostMaster::MailAccountFetch=HASH(0x5573e2cad338), "-debug", "-mail-account-id", 1) called at /opt/znuny-6.3.1/Kernel/System/Console/InterfaceConsole.pm line 81 Mail::IMAPClient::_ANON_("2 BAD User is authenticated but not connected.\x called at /opt/znuny-6.3.1/Kernel/System/Console/BaseCommand.pm line 454 at /usr/share/perl5/Mail/IMAPClient.pm line 1378. Read: 2 BAD User is authenticated but not connected.ĮRROR: 2 BAD User is authenticated but not connected. Answering whether Geary/Gnome Accounts accepts self-signed certificates is probably a good first step to solving this, especially speaking I have noticed the easiest way to mess up this configuration process in other mail clients and get similar garbled BAD REQUEST messages in the DavMail log is by playing with the SSL/TLS settings. Read: * OK The Microsoft Exchange IMAP4 service is ready.
Using Mail::IMAPClient version 3.42 on perl 5.030000Ĭonnecting with IO::Socket::SSL PeerAddr PeerPort 993 Proto tcp Timeout 600 Debug 1 SSL_verify_mode 0 Code: Select all Spawning child process to fetch incoming messages from mail accounts.
0 kommentar(er)
