Hello all,
I am using mmsbox, mmsproxy and mmsrelay without any problems in a small
project, a small application that sends a constructed MMS to mmsbox. I just
have some questions regarding the behavior of Mbuni when a malformed MMS is
sent to mmsbox. When I say malformed, I mean any kind of multipart headers or
multipart content errors.
At some point, due to some bugs, the MMS message that was created by the
application was corrupted. Everything that was between the multipart boundaries
(where headers and content for an images should have been, for example...),
except the pair of \r\n, was missing. Mmsbox crashed due to a segmentation
fault, caused by some string manipulation for the empty multipart.
The code that generates the MMS is out of my reach now, so I can't answer my
question by modifying the way the MMS is created and observing mmsbox
reactions. And the application seams to works without a flaw now, so.... That
is way I am writing this email.
So, if someone could please explain how does mmsbox react when a corrupt MMS
arrives? It forwards the MMS to mmsc, even though it doesn't "understand" it
(it can't parse it, or finds some bad headers...), and responds with 200ok, or
discards the message and answers with some 4xx code, or what? (I did leave out
"it crashes" on purpose, because I hope that is not the case...)
Thank you for your time
Gabi Mahu
---------------------------------
Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos. _______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
