Added new function to allow keeping the flags original case #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to RFC 9051 "Servers MAY permit the client to define new
keywords in the mailbox".
For my use-case this makes it necessary that I change the encoding of
keywords from UTF-8 to UTF7-IMAP to allow Umlauts in keywords.
Example: "Bööm" will be encoded as "B&APYA9g-m"
If I insert the lowercase Version of this string into
mb_convert_encoding()
, I receive a different result ("b??m").Therefore I propose a method that allows us to fetch keywords in their
original case to prevent encoding from becoming corrupted.
I created a patch that simply adds a new method to fetch flags, that
hopefully has no impact on the existing code. The constant I added for
flags with their original case is currently 999 since I don't know if
you're simply counting up or if the values of the constants have a
system.