@slava Thank you so much for having a further look into this! And I’m glad that I was right that subject is involved. But it’s strange, anyway, as it would mean that multiple sources (BlackBerry BB10 phones, the iPhone, and also my operator’s voice mail MMS service) produce MMS messages with such broken headers. Or maybe the phones generate correct header but it is the operator’s MMSC (or whatever else is involved on the way between the sender and me) that currupts the header somehow?
Anyway, other phones / OS seem to be somehow immune to this issue if the same MMS that fails on SFOS, sent from the Z10 to the iPhone (and vice versa) is received correctly. So maybe if the SFOS parser encounters this error, it should ignore it, or interpret it as an empty string like you changed it? Maybe that’s how other systems handle it and that’s why they correctly receive such messages?
P.S. I didn’t have the opportunity to get those logs for you yet. I should be able to do it on Sunday. Do you still need them?