Replies: 1 comment
-
I agree with that. It is ok If you provide the pull request from v3.4.0 branch. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I perform some specific actions with custom IMAP functions in order to optimize performance (I retrieve all the messages from a search with a single fetch). Using custom IMAP functions requires me to decode encoded fields myself. I use some of your functions such as getEncodingFromCharset(), decodeLatin1_UTF8() and RFC2047Decoder. As these are private I made them public in order to use them directly in my application (RFC2047_Decoder itself is not private, but I wanted to reuse the RFC2047Decoder instance from MailClient in order to save resources). Would you consider making these public in your source, so other people using custom IMAP functions can use them as well? If you do, I am also happy to provide a pull request (for the sake of consistency I would also make decodeTIS620_UTF8() public)...
Beta Was this translation helpful? Give feedback.
All reactions