-
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. Retrying later.: Empty address #691
Comments
Thanks for reporting! This is probably a problem with some mail. Could you maybe paste the logs of the joex (container)? |
Bit long, sorry, and not sure how helpful it is. |
Very helpful, thanks! It seems that there is a mail with an empty |
Which version of Docspell are you using? I just realized that I fixed this before, but I might have just overlooked some case(s). See #606 – I have a simple test with a mail with an empty reply-to header…. So I'm a bit puzzled now :) Of course, it would be interesting to see this mail (it's headers), but it usually is not possible to share. If it is, I'd be interested to take a closer look. |
The container is using: eikek0/docspell:joex-LATEST
I don't know which email it refers to, so I honestly can't say if I can share it or not. Any way I can work that out? |
Ok, then this should be the current version. The version is on the login page, it is printed below the login form. Or via
Yes, this is indeed difficult. I hoped that the folder you are trying to import had not too many mails, so a guess would work :). Don't worry, I'm going to try to reproduce it a bit harder. |
:)
I may have found it. I've continually been getting emails from Microsoft to update authentication regarding importing from another mail box. When I hit reply there's no email to reply to:
|
Thank you! Unfortunately I can't reproduce it with this. |
I also deleted all of these specifically and I still get issues scanning my inbox. |
Thank you for your efforts here! Let me try some things; I should be able to reproduce this somehow, or at least a similar error, which can lead to some new ideas; and maybe fixing some more related problems. |
I could get this exact error with a |
Interesting. I couldn't see any of those in my inbox though. |
Just a few things before I maybe open new issues: Can Mail scan tasks have their own names? It also seems subject filtering only accepts ONE subject, it's not separated. E.G. You've sent a payment you made a payment |
You can raise this limit in the config file for joex, here is the default config. Then when moving away imported mails (or deleting them), this task will fetch the next 500 mails next time it runs. The reason for this limit is to avoid one user blocking the executor for too long. For the other things, some brief comments (you can always open new issues you'd like to discuss; I'd suggest to create issues for these if you like a more in depth look at it):
|
Fix via #701 |
@voarsh2 if you like, it's now (or when dockerhub is done) possible to use the SNAPSHOT images to test the fix. But one caveat: you then should not go back to the current version (there are some db changes; you can change back to LATEST once this is released). |
I'm pleased to say that I can now run mail scan on my main inbox folder. Seems your fix is working. Grats 🎆 |
Oh great, nice to know. Thanks for the update! |
I get this error whenever the mail scan starts.
I think I only got it working once.
The text was updated successfully, but these errors were encountered: