-
Notifications
You must be signed in to change notification settings - Fork 958
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
[BUG] Incompatibility with mail server that does not seem to support CHARSET option in SEARCH #6815
Comments
All the imap code is through imap-tools, please report this upstream for any resolution. |
Hi. Maybe I didn't express myself clearly. The problem here is paperless forcing using the CHARSET option. This option is not supported by some of the email providers. imap-tools is totally fine if paperless allows sending requests without CHARSET. There is nothing wrong with it. Paperless does not allow configuring an email account without specifying this CHARSET option. I tried with imap-tools and found that at least for my email provider, this option is completely unnecessary and only causes trouble. To be compatible with a larger range of email providers, maybe paperless should allow setting up email account without this CHARSET option. |
imap-tools always sets a charset: Support for none would have to start there. |
I don't think this is the correct function to look at. The error message from paperless indicates the problem is with the I tested this
|
You are right. Imap-tools needs to support omitting CHARSET first. Simply changing the UI and function calling in paperless is not sufficient. |
Description
Similar to #4685
I figured out using imaplib and ipython that if not specifying CHARSET in imap.uid command, my mailbox works fine' If CHARSET is included in the command, no matter what it is set to (UTF-8/US-ASCII), it reports error.
{"headers":{"normalizedNames":{},"lazyUpdate":null},"status":400,"statusText":"OK","url":"https://paperless.example.com/api/mail_accounts/1/","ok":false,"name":"HttpErrorResponse","message":"Http failure response for https://paperless.example.com/api/mail_accounts/1/: 400 OK","error":{"character_set":["该字段不能为空。"]}}
It is not obvious why this charset option is needed in setting up the email function. I tried to remove it but the settngs in paperless won't let me do it.
If I run the following code it works.
UID SEARCH without CHARSET successful: [b'']
If I run the following, there is an error
Steps to reproduce
Webserver logs
Browser logs
No response
Paperless-ngx version
2.8.6
Host OS
ubuntu 23.04
Installation method
Docker - official image
System status
No response
Browser
No response
Configuration changes
No response
Please confirm the following
The text was updated successfully, but these errors were encountered: