-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
BINARY vs BODY and "invalid" messages #6383
Comments
tomsommer
changed the title
BINARY vs BODY and "corrupt" messages
BINARY vs BODY and "invalid" messages
Aug 6, 2018
There's a fallback, but we use it only on |
Dovecot 2.3.2 |
Looks like dovecot 2.3 uses |
Good catch, Dovecot can return both |
Fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Roundcube uses
BINARY.PEEK
whenever possible, however this prevents the display of broken mails, that usually work withBODY.PEEK
BINARY.PEEK
returnsUID NO [PARSE] Invalid data in MIME part (0.012 + 0.000 + 0.011 secs)
whereasBODY.PEEK
returns the mail body.Perhaps add a fallback to
BODY.PEEK
ifBINARY.PEEK
fails?The text was updated successfully, but these errors were encountered: