Zaahid Bateson

Yeah, although there's no harm in expanding that to either ISO-8859-1 or UTF-8, as they're both compatible for the first 127 bytes.

The point is though, that you can check if a charset isn't set, and use ```setCharsetOverride``` if it isn't, thereby setting your own default charset using that.

I don't know why there are no results on your specific case and emails without further details of what you're doing.

> Well, if I override the existing charset, it's not "default" anymore! Default means: If there is no value, use this one. We're running in circles a bit here :stuck_out_tongue:...

Hi @mariuszkrzaczkowski -- In your case it would make more sense to look at the parts using 'getParts'. The comment parts aren't necessarily 'part' of a received part, I don't...

My bad, it's just ``` getParts ```. I've updated the previous comment/example as well.

Actually it's already kind of separated and parsed in the various 'Consumer' classes already. Currently the comment portion is returned separately if it doesn't match what the consumer expects to...

That could be changed to be both separate and part of the 'ReceivedDomainPart' maybe, so if it's not matched at least the raw value is available or something... not sure,...

Hi @h4mpy -- Thanks for the detailed report... unfortunately I'm unable to reproduce what you're experiencing, but that might just be the environment I'm running... this is what I'm getting...

Hi @h4mpy Someone had requested that in the past and I'd reworked the code to make it work. Unfortunately it seems when I split out the code into separate libraries...