The result of the conversion is Sun, 29 Dec 2582 21:56:16 UTC
I think it is correct but maybe something else is wrong in my message. This is my last encode of the message and obviously is not working. 8c82 9831423500 8d90 8a80 8e0164 880481020100 83687474703A2F2F31302E322E32342E3132362F7075626C69632F72696265732F6D6172636F 2F706965727761702E6D6D7300 I expect the telephone to start to browse and go to retrieve the content. Is it correct? And the telephone seems to receive two messages but it doesn't do anything. And the pap file is always unchanged. Thank you again. Alessandro. -----Messaggio originale----- Da: Paul Keogh [mailto:[EMAIL PROTECTED]] Inviato: giovedì 12 settembre 2002 12.32 A: [EMAIL PROTECTED] Oggetto: RE: R: MMS Push Problem > I tryed with "date -r filename" but I just get back the date > of creation of > the file. I can't understand how the X-MMS-Expiry date is > encoded. Is there > any documentation about that? > Look at 7.2.10 of WAP-209-MMSEncapsulation-20020105-a for Expiry field encoding. Then look at WSP for long integer encoding. ================================= "STRICTLY PERSONAL AND CONFIDENTIAL This message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies. The contents of this message that do not relate to the official business of our company shall be understood as neither given nor endorsed by it." =================================
