We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
parse FetchMessageBuffers error,trace stack discovery is parsing BodyStructure error。
* 150 FETCH (UID 1733220355 INTERNALDATE "10-Dec-2024 15:11:12 +0800" FLAGS (\Seen) ENVELOPE ("Tue, 10 Dec 2024 10:49:37 +0800" "=?UTF-8?B?MjE1NDk3MzU1MCAtIE9PQ0wgQm9va2luZyBBY2tub3dsZWRnZW1lbnQgKCBTWlUgKQ==?=" ((NIL NIL "PLEASE-No-Reply-IRIS-4" "XXXX.COM")) ((NIL NIL "edith.test" "oocl.com")) NIL ((NIL NIL "OP-XXXX" "YYYY.COM")) NIL NIL NIL "<[email protected]>") BODY (("text" "html" ("charset" "UTF-8") NIL NIL "quoted-printable" 1224 16)("application" "octet-stream" ("name" "2154973550.pdf") NIL """" "base64" 65322) "MIXED") BODY[] {69100}
Error Prompt:
in response-data: in body-type-mpart: in body-type-1part: imapwire: expected atom, got "("
Error location:
The text was updated successfully, but these errors were encountered:
Sounds like a server bug. The body structure:
( ("text" "html" ("charset" "UTF-8") NIL NIL "quoted-printable" 1224 16) ("application" "octet-stream" ("name" "2154973550.pdf") NIL """" "base64" 65322) "MIXED" )
The Content-Description is """" in the second part. Seems like the server doesn't escape quotes in the original header.
""""
Sorry, something went wrong.
Which server gives you this reply?
Which server gives you this reply
netease 163
Do you need me to provide you with the original email?
That'd be interesting to check what the Content-Disposition is set to there and confirm the above comment.
No branches or pull requests
parse FetchMessageBuffers error,trace stack discovery is parsing BodyStructure error。
Error Prompt:
Error location:
The text was updated successfully, but these errors were encountered: