Closed qjebbs closed 4 months ago
the second commit skip all potential excessive SPACEs
tries to solve all similar problems as it suggests, but I am not sure if I do it in the right way.
It works good in my env, the only question that comes to mind is whether SP()
, ExpectSP()
needs to be renamed (e.g.: LSP()
for leading Space) for method semantics reasons.
This PR improves compatibility with non-compliant servers, by skipping excessive SPACE between elements and the trailing SPACE
* CAPABILITY IMAP4<SP>IMAP4rev1<SP><CRLF>
* SEARCH<SP><CRLF>
related: #571 #540