Short answer is: Doubtful. The order of the headers is determined
within mmlib/mms_msg.c, where the order in the binary formatted
message is asserted. Likely the kyocera doesn't like the other headers
that come as part of the mime message (even though per spec they
should be ok).
On Apr 15, 2008, at 17:46, gbarrosGMAIL wrote:
Hi Paul,
I am having troubles with kyocera cell phones while doing fetch of a
mms from email.
According to WAP 209, mandatory headers in a retrieval of multimedia
message are:
X-Mms-Message-Type
X-Mms-MMS-Version
Date
Content-Type
Otherwise, WAP 209 says:
"In the encoding of the fields, the order of the fields is not
significant, except that Message-Type, Transaction-ID and
MMS-Version MUST be at the beginning of the message headers, in that
order, and the content type MUST be the last
header, followed by message body."
In a mms sended by email, before X-Mms-Message-Type header you have
headers like Return-Path, Subject, X-Priority, so, when doing fetch,
you call mms_retrieveconf in order to re-order
headers, which is correct, but in this method, if the MmsMsg passed by
param is not NULL you call http_header_combine, which combine new
headers (ordered ones) with all ones.
I think you are loosing the order in this function, so the cell phone
could not retrieve the mms because of the invalid order of headers
(X-Mms-Message-Type,X-Mms-MMS-Version at the beginning and
Content-Type at the end.).
I am wrong?
Is there a patch in CVS ?
Thkxs,
Germán.
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
