2
[Feature Request] Add processing treatment for emails that fail to get processed.
Source: paperless-ngx/paperless-ngx#12521 · opened by @oakypokey
Description
Currently, when an email is successfully processed, it is possible to either move, label, flag, or trash the email. However, when an email is unsuccessfully processed, nothing happens in the email client.
It's possible to see which email/attachments failed in the paperless UI, but ideally, I would like to be able to at least move/flag/label an email if it was unable to be successfully processed by paperless-ngx. Even better, it would be even better to be able to do different things based on different errors: ie. duplicate attachment adds one label, generic processing error adds another label etc.
Other
This is something that I would be willing to contribute if there is enough interest :)
Currently, when an email is successfully processed, it is possible to either move, label, flag, or trash the email. However, when an email is unsuccessfully processed, nothing happens in the email client.
It's possible to see which email/attachments failed in the paperless UI, but ideally, I would like to be able to at least move/flag/label an email if it was unable to be successfully processed by paperless-ngx. Even better, it would be even better to be able to do different things based on different errors: ie. duplicate attachment adds one label, generic processing error adds another label etc.
Other
This is something that I would be willing to contribute if there is enough interest :)
No pledges yet. Be the first to back this.
Comments
Similar requests
[Feature Request] Exclude documents from AI processing by filter or tag
1 vote · 0 comments
[Feature Request] processing emails - add custom field
4 votes · 0 comments
Native Docling Integration for PDF-to-Markdown/Text conversion (Consumer & Full-Text Indexing)
3 votes · 0 comments
Support for importing S/MIME‑encrypted emails
3 votes · 0 comments
[Feature Request] Improvements: Logging
6 votes · 0 comments
No comments yet.