Vicidial Inbound Email cannot connect through IMAPClient

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Vicidial Inbound Email cannot connect through IMAPClient

Postby bronson » Sat Jan 13, 2024 2:24 pm

Outbound email is working fine but inbound emails are not getting pulled in.

I'm on a vicibox10 install that has been updated to a recent SVN. The problem below has been an issue since before the upgrade.

System Specs:
Version: 2.14b0.5
SVN Version: 3796
DB Schema Version: 1704
DB Schema Update Date: 2024-01-13 10:29:25

I ran the debug /usr/share/astguiclient/AST_inbound_email_parser.pl --debugX

and got the following error:

Code: Select all
1 - sales - sales
Attempting to connect to IMAP server (mail.domain.tld)  -  1 - sales - sales

Started at Sat Jan 13 13:40:44 2024
Using Mail::IMAPClient version 3.43 on perl 5.026001
Connecting with IO::Socket::SSL PeerAddr mail.domain.tld PeerPort 993 Proto tcp Timeout 600 Debug 1
ERROR: Unable to connect to mail.domain.tld: Failed to set SSL cipher list error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no cipher match at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 377.
        Mail::IMAPClient::connect(Mail::IMAPClient=HASH(0x55c2236abfb0)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 315
        Mail::IMAPClient::new("Mail::IMAPClient", "Debug", 1, "Ignoresizeerrors", 1, "Port", 993, "User", ...) called at /usr/share/astguiclient/AST_inbound_email_parser.pl line 311
Cannot connect through IMAPClient: (sales|mail.domain.tld|sales@domain.tld|ssl-no-cert:0) Unable to connect to mail.domain.tld: Failed to set SSL cipher list error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no cipher match No such file or directory at /usr/share/astguiclient/AST_inbound_email_parser.pl line 311.
You have new mail in /var/spool/mail/root


I've followed the Vicidial Email doc at https://vicidial.org/docs/Email_user_manual.txt to the letter.

  • Installed All required CPAN modules
  • Ensured "E" Keepalive is enabled on astguiclient.conf
  • Verified postfix is installed, active, and running

Initially, I got the error:
SSL_verify_mode must be a number and not a string at /usr/lib/perl5/site_perl/5.12.1/IO/Socket/SSL.pm line 2251.


So I followed the troubleshooting advice in the doc:
- If you see the following error:

SSL_verify_mode must be a number and not a string at /usr/lib/perl5/site_perl/5.12.1/IO/Socket/SSL.pm line 2251.


Edit the "SSL.pm" file that is shown in the error you received:

Line 2251, change:

die "SSL_verify_mode must be a number and not a string";

To:

$verify_mode = '0';


Save it(since the file is most likely read-only, you might have to force save[in 'vi' that's ':w!'])

Then try running the email script again:

/usr/share/astguiclient/AST_inbound_email_parser.pl --ssl-no-cert --debugX --force-check

*Note The line is now at 2391 not, 2251

When I run /usr/share/astguiclient/AST_inbound_email_parser.pl --ssl-no-cert --debugX --force-check, I get:

Code: Select all
vicibox:~ # /usr/share/astguiclient/AST_inbound_email_parser.pl --debugX
vicibox:~ # /usr/share/astguiclient/AST_inbound_email_parser.pl --ssl-no-cert --debugX --force-check
1 - sales - sales
Attempting to connect to IMAP server (mail.domain.tld)  -  1 - sales - sales

Started at Sat Jan 13 14:16:34 2024
Using Mail::IMAPClient version 3.43 on perl 5.026001
Sending: 1 LOGOUT
ERROR: NO not connected at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1568.
        Mail::IMAPClient::_send_line(Mail::IMAPClient=HASH(0x563628e42800), "1 LOGOUT", 0) called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1344
        Mail::IMAPClient::_imap_command_do(Mail::IMAPClient=HASH(0x563628e42800), "LOGOUT", "BYE") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1248
        Mail::IMAPClient::_imap_command(Mail::IMAPClient=HASH(0x563628e42800), "LOGOUT", "BYE") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 2007
        Mail::IMAPClient::logout(Mail::IMAPClient=HASH(0x563628e42800)) called at /usr/share/astguiclient/AST_inbound_email_parser.pl line 685
Trying command when NOT connected! at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 123.
        Mail::IMAPClient::LastError(Mail::IMAPClient=HASH(0x563628e42800), "NO not connected") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1568
        Mail::IMAPClient::_send_line(Mail::IMAPClient=HASH(0x563628e42800), "1 LOGOUT", 0) called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1344
        Mail::IMAPClient::_imap_command_do(Mail::IMAPClient=HASH(0x563628e42800), "LOGOUT", "BYE") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1248
        Mail::IMAPClient::_imap_command(Mail::IMAPClient=HASH(0x563628e42800), "LOGOUT", "BYE") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 2007
        Mail::IMAPClient::logout(Mail::IMAPClient=HASH(0x563628e42800)) called at /usr/share/astguiclient/AST_inbound_email_parser.pl line 685
ERROR: Error sending '1 LOGOUT': NO not connected at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1345.
        Mail::IMAPClient::_imap_command_do(Mail::IMAPClient=HASH(0x563628e42800), "LOGOUT", "BYE") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1248
        Mail::IMAPClient::_imap_command(Mail::IMAPClient=HASH(0x563628e42800), "LOGOUT", "BYE") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 2007
        Mail::IMAPClient::logout(Mail::IMAPClient=HASH(0x563628e42800)) called at /usr/share/astguiclient/AST_inbound_email_parser.pl line 685
Trying command when NOT connected! LastError was: NO not connected at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 123.
        Mail::IMAPClient::LastError(Mail::IMAPClient=HASH(0x563628e42800), "Error sending '1 LOGOUT': NO not connected") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1345
        Mail::IMAPClient::_imap_command_do(Mail::IMAPClient=HASH(0x563628e42800), "LOGOUT", "BYE") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1248
        Mail::IMAPClient::_imap_command(Mail::IMAPClient=HASH(0x563628e42800), "LOGOUT", "BYE") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 2007
        Mail::IMAPClient::logout(Mail::IMAPClient=HASH(0x563628e42800)) called at /usr/share/astguiclient/AST_inbound_email_parser.pl line 685
ERROR: Error sending '1 LOGOUT': NO not connected at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1298.
        Mail::IMAPClient::_imap_command(Mail::IMAPClient=HASH(0x563628e42800), "LOGOUT", "BYE") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 2007
        Mail::IMAPClient::logout(Mail::IMAPClient=HASH(0x563628e42800)) called at /usr/share/astguiclient/AST_inbound_email_parser.pl line 685
Trying command when NOT connected! LastError was: Error sending '1 LOGOUT': NO not connected at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 123.
        Mail::IMAPClient::LastError(Mail::IMAPClient=HASH(0x563628e42800), "Error sending '1 LOGOUT': NO not connected") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 1298
        Mail::IMAPClient::_imap_command(Mail::IMAPClient=HASH(0x563628e42800), "LOGOUT", "BYE") called at /usr/lib/perl5/vendor_perl/5.26.1/Mail/IMAPClient.pm line 2007
        Mail::IMAPClient::logout(Mail::IMAPClient=HASH(0x563628e42800)) called at /usr/share/astguiclient/AST_inbound_email_parser.pl line 685
script execution time in seconds: 0     minutes: 0


I've been digging through the forums and I am at a loss as to how to investigate further.

Please help :?
bronson
 
Posts: 96
Joined: Thu Oct 14, 2021 10:34 am

Re: Vicidial Inbound Email cannot connect through IMAPClient

Postby williamconley » Sat Jun 29, 2024 1:44 pm

Consider that some mail systems require SSL for connection. So once you got all your code worked out to ignore the ssl requirement, you still may have hit that wall.

Have you tried it while hitting an email server YOU control? This would give you valuable insight into both ends of the request.

Also, you might consider posting the provider. I'm assuming you blocked out your domain name, but if you're hitting gmail or live.com or !! aol.com or some such, that might be valuable information for someone with experience to assist.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20253
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Vicidial Inbound Email cannot connect through IMAPClient

Postby mflorell » Sun Jun 30, 2024 7:08 am

Some email providers have been making their email client connections harder and harder to get working with them over recent years, like Gmail. But we've found that some others, like hotmail.com have no issues connecting with VICIdial recently. The sad fact is that email is a mess, and abusing email services is still too easy, which is one reason these services are making their 3rd-party connections more and more restrictive. Another reason is to try to get you to use their web email clients so they can more easily feed you ads, but that's not really unexpected for the free services out there.
mflorell
Site Admin
 
Posts: 18383
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: Vicidial Inbound Email cannot connect through IMAPClient

Postby bronson » Fri Sep 20, 2024 8:25 am

williamconley wrote:Consider that some mail systems require SSL for connection. So once you got all your code worked out to ignore the ssl requirement, you still may have hit that wall.

Have you tried it while hitting an email server YOU control? This would give you valuable insight into both ends of the request.

Also, you might consider posting the provider. I'm assuming you blocked out your domain name, but if you're hitting gmail or live.com or !! aol.com or some such, that might be valuable information for someone with experience to assist.


Yes, this is a self-hosted email server I built using redmail. I am able to send and receive emails through roundcube and thunderbird, but for some reason it does not work through vicidial. The thing is it was working previously but I can't figure out why it doesn't work anymore.
bronson
 
Posts: 96
Joined: Thu Oct 14, 2021 10:34 am

Re: Vicidial Inbound Email cannot connect through IMAPClient

Postby williamconley » Mon Sep 23, 2024 7:59 pm

Self-hosted redmail should allow troubleshooting with the logs of redmail to find out why the connection fails.

"was working previously" implies you don't think anything changed, but obviously something did. It'll either be connectivity (networking) or an updated package or credentials on one of the two servers.

Observing the email script with --debugX may give you a hint from the Vicidial side. If you succeed in connecting but get rejected, then the redmail logs should help find out Why.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20253
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)


Return to Support

Who is online

Users browsing this forum: Bing [Bot] and 92 guests