Is your feature request related to a problem? Please describe.
During the work at #145 I noticed that we always assume the charset for any mime multipart with the same charset as the charset defined for the Msg. While this absolutely makes sense, hypothetically each part can have its own charset.
Describe the solution you'd like
Therefore we should implement a per-part charset option while still relying on the Msg charset being set as default if no different chartset is set the corresponding part.
Is your feature request related to a problem? Please describe.
During the work at #145 I noticed that we always assume the charset for any mime multipart with the same charset as the charset defined for the
Msg. While this absolutely makes sense, hypothetically each part can have its own charset.Describe the solution you'd like
Therefore we should implement a per-part charset option while still relying on the
Msgcharset being set as default if no different chartset is set the corresponding part.Describe alternatives you've considered
No response
Additional context
No response