-
Notifications
You must be signed in to change notification settings - Fork 490
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
Error Fetching Emails #351
Comments
Fantastic if this is really fixed. Fetching errors over character set differences has been a nightmare. Thank you! |
We had issue with missing email for a full day again. But running Manage -> System -> Tools -> Fetch Email the error was a bit different:
It's really a problem as it doesn't only stop the single email from being processed, it also stops all the other emails from processing. I'm also attaching the email which was causing the issue, the name in the email looks like this:
The bad email .eml file (note you may need to change the extension from Both this issue and the other similar issue #360 are tagged "help wanted", so I had a look: I see that the issue might be with https://github.com/Webklex/laravel-imap but FreeScout seems to be using version 1.2.7 while 2.4.0 is out: https://github.com/Webklex/laravel-imap/blob/master/CHANGELOG.md So I tried to put in verision 1.2.9 using composer - last of the 1.2.x branch. No improvement. Next I tried version 1.6.2 - the last release of the 1.x breanch - but then I only got "Whoops, looks like something went wrong." when trying to run Manage -> System -> Tools -> Fetch Email. The error in Laravel logs is:
Version 1.3.1 didn't crash FreeScout anymore, but didn't fix the issue. 1.4.5 gave me that same "Whoops, looks like something went wrong." when trying to run Manage -> System -> Tools -> Fetch Email. I haven't tried to put in 2.4.0 as I'm sure it would also fail. So it looks like the webklex/laravel-imap component should be upgraded to the latest version and the FreeScout code fixed to work with it. Thanks, |
Try to comment |
It didn't help. I got this error:
And the emails were not imported. Even if you do not update to latest webklex/laravel-imap for some reason it would make sense to improve the process so that a single email with some encoding issue won't stop the whole processing. |
It's not supposed to help - we need the full error stack trace. Please send. |
Last time I was able to find the full error trace in So that error doesn't seem to produce the trace somehow. But actually - when I commented out that line 203 in app/Console/Commands/FetchEmails.php as well: https://github.com/freescout-helpdesk/freescout/blob/dist/app/Console/Commands/FetchEmails.php#L203 It gave me this error trace:
So getting rid of that |
Still the real reason of the issue is not clear. It looks like you will need to find someone who can debug and fix it. Or you can send us SSH access to support@freescout.net |
Could we just provide access to a mailbox with the problematic email in it? That way you could set your test FreeScout instance try download the email and see if you run into the same issue. |
Yes. If you can provide access to the email address containing the problematic email. |
Thank you, I sent the mailbox access information to support@freescout.net I also ensured that I run into that same issue with this new mailbox:
|
Fixed in the |
I updated to 1.7.4 and then added the changes from e52711d It works, thank you very much! |
Hi,
On one Mailbox, I get an error when fetching emails:
Error: iconv(): Wrong charset, conversion from "1252" to "UTF-8//IGNORE" is not allowed; File: /var/www/html/vendor/webklex/laravel-imap/src/IMAP/Query/Query.php (189)
This is also a fresh installation.
Using Nginx, followed installation guide with the web installer
Any Ideas?
Thanks in advance
The text was updated successfully, but these errors were encountered: