-
Notifications
You must be signed in to change notification settings - Fork 113
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
scan-mailbox/Low execution failed #678
Comments
What a mysterious error message – have to improve this…. Could you maybe check the logs of joex? Could you try without the additional glob filter? I'll also check the code later tonight. When you look at these two mails, can you think of something "strange", like maybe attachments that don't have a name or something like this? Thanks! |
Now I tried it without the additional glob filters, similar result. Interesting: It says:
Where do I find the logs of joex? |
This is expected, it only tells that there is no filter to apply.
How did you run docspell? Via docker-compose? if so, you should be able to do a The |
Here is an excerpt of the log
|
Thank you - this helps a lot. Well, it's an annoying bug. E-Mails are quite hard sometimes. It seems that there is a mail that defines a charset in the header, but the body cannot be decoded using this charset. Unfortunately, this error is not guarded. I'm going to fix this for the next release (using some fallback, which might result in strange characters in the text for these mails). If it would be possible to share this mail, it would help to make sure this particular problem is fixed. But of course, it is usually not possible, just asking :). |
Aha, great. I will send you a test mail tomorrow and will check the charset |
Fix via #701 |
Hi, after importing one pdf attachment per imap successfully, my next attempts failed. Here is the log:
The text was updated successfully, but these errors were encountered: