Skip to content
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

Trailing space in STATUS response #9

Open
duesee opened this issue Oct 12, 2023 · 1 comment
Open

Trailing space in STATUS response #9

duesee opened this issue Oct 12, 2023 · 1 comment
Labels
PROTO=IMAP Related to IMAP protocol STATE=REPRODUCED Issue could be reproduced (explained in issue)

Comments

@duesee
Copy link
Contributor

duesee commented Oct 12, 2023

See emersion/go-imap#540

Observed in: Exchange (outlook.office365.com:993)
Reported: No
Status: Unknown
Comment: None
Proposed solution(s):
    Consume the trailing space (making sure not to reproduce the defect.) Implemented in https://github.com/emersion/go-imap/pull/541, https://github.com/duesee/imap-codec/pull/468, and [Ruby](https://bugs.ruby-lang.org/issues/13649).
* STATUS INBOX (MESSAGES 0) 
                           ^
                           |
                           Extra whitespace
@duesee
Copy link
Contributor Author

duesee commented Oct 20, 2023

It could be a setup with Dovecot <--> Exchange.

@duesee duesee changed the title imap: Dovecot (seemingly) sends an extra whitespace during STATUS response imap: Dovecot/Exchange (seemingly) sends an extra whitespace during STATUS response Oct 20, 2023
@duesee duesee changed the title imap: Dovecot/Exchange (seemingly) sends an extra whitespace during STATUS response imap: Trailing space in STATUS response Jan 22, 2024
@duesee duesee closed this as completed Jan 22, 2024
@duesee duesee reopened this May 11, 2024
@duesee duesee added PROTO=IMAP Related to IMAP protocol STATE=REPRODUCED Issue could be reproduced (explained in issue) labels May 11, 2024
@duesee duesee changed the title imap: Trailing space in STATUS response Trailing space in STATUS response May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PROTO=IMAP Related to IMAP protocol STATE=REPRODUCED Issue could be reproduced (explained in issue)
Projects
None yet
Development

No branches or pull requests

1 participant