-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix saving outgoing emails via IMAP #984
Comments
Anything in Manage > System? |
Post queue and jobs with errors are generated. And it doesn't change queue:work Functions are working And Logs > App Logs |
Any hanging background jobs in Manage > Status? |
Although the mail queue is cleared, it is rebuilt with attempts that exceed 100. We had to stop providing the service of the platform since each reply that is made arrives like 200 emails. |
It looks like somehow your mail server is accepting the email but returns an error. |
We use the Posfix and SES AWS. As I was telling you, you hadn't had any kind of problems, we have even acquired several modules, the problem has been presented to us when we update to the latest version. The Manage > Logs > App Logs : production.ERROR: imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled {"exception":"[object] (Webklex\IMAP\Exceptions\ConnectionFailedException(code: 0): imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled at /www/html/overrides/Webklex/IMAP/Client.php:230) [stacktrace] [2021-01-07 14:42:18] production.ERROR: imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled {"exception":"[object] (Webklex\IMAP\Exceptions\ConnectionFailedException(code: 0): imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled at /www/html/overrides/Webklex/IMAP/Client.php:230) [2021-01-07 14:42:19] production.ERROR: imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled {"exception":"[object] (Webklex\IMAP\Exceptions\ConnectionFailedException(code: 0): imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled at /www/html/overrides/Webklex/IMAP/Client.php:230) [2021-01-07 14:42:19] production.ERROR: imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled {"exception":"[object] (Webklex\IMAP\Exceptions\ConnectionFailedException(code: 0): imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled at /www/html/overrides/Webklex/IMAP/Client.php:230) [stacktrace] [2021-01-07 14:42:20] production.ERROR: imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled {"exception":"[object] (Webklex\IMAP\Exceptions\ConnectionFailedException(code: 0): imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled at /www/html/overrides/Webklex/IMAP/Client.php:230) [2021-01-07 14:42:21] production.ERROR: imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled {"exception":"[object] (Webklex\IMAP\Exceptions\ConnectionFailedException(code: 0): imap_open(): Couldn't open stream {secure.emailsrvr.com:143/imap/tls}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled at /www/html/overrides/Webklex/IMAP/Client.php:230) [stacktrace] |
Change the server with SSL configuration without certificate and the error persists: imap_open(): Couldn't open stream {secure.emailsrvr.com:993/imap/novalidate-cert/ssl}. IMAP protocol error: Authentication aborted by client.; IMAP Authentication cancelled; File: /www/html/overrides/Webklex/IMAP/Client.php (230) |
Good evening, after several tests the error in the configuration with the SSL certificates is detected. |
Thanks for the info. We never thought that someone would fetch emails from the Sent folder. We will add a notice to gudes. |
Hi, I want to clarify the problem that Jessica reports. There is an option in freescout that allows to save the outgoing replies in an IMAP folder. When we activate that option freescout sends an email using the SMTP server and then opens an IMAP connection. Looking in to it a little further, we found that the error generated by freescout when it tries to save the reply is:
However our setup uses SSL connections, but it uses a TLS connection. When we change it to a TLS connection it uses SSL, but the fetching fails. So, our understanding of the problem is when freescout tries to open a connection for saving the outgoing reply it uses the wrong settings for opening the connection. For us is really important to save the reply, can you help us to fix this issue? |
@freescout-helpdesk can you please re-open the issue? Thanks in advance!! |
Now when saving outgoing reply to the IMAP folder fails, the system will not send multiple emails to a customer. But we've checked when FreeScout saves an outgoing reply to the IMAP folder, it uses same settings as when fetching emails. Maybe at the moment you received |
Thank you! We will check in detail the IMAP connection problem ... |
Your help please, after the update to system version 1.6.12, when answering a ticket from the platform, the client receives the same answer 200 or 300 emails:
The problem is that an error is generated when sending and it is sent again. Although it was sent successfully:
The text was updated successfully, but these errors were encountered: