Right, back to my problem with o2

[texy]

From the previous board I had a problem updating to version 0.3.6 - that is now sorted, and I could send mms's because of a corrupt message error.
Here is another logfile with version 0.3.6 -

SwirlyMMS, version: 0.3.6 started at: 2008-03-18 18:18:24 +0000
u: inet 193.113.200.195;

u: link 69.70.31.0;

Sending MMS...
/var/mobile/Media/DCIM/100APPLE/IMG_0009.JPG: w=1600, h=1200
Posting to 193.113.200.195:8080, uri=http://mmsc.mms.o2.co.uk:8002/, host=mmsc.mms.o2.co.uk:8002
Port : 8080, Address : 0xC3C871C1
Sending request:

POST http://mmsc.mms.o2.co.uk:8002/ HTTP/1.1

Host: mmsc.mms.o2.co.uk:8002

Accept: application/vnd.wap.mms-message, */*

Content-Type: application/vnd.wap.mms-message

Cache-Control: no-cache

Accept-Charset: utf-8, utf-16, iso-8859-1, iso-10646-ucs-2

Pragma: no-cache

Connection: close

User-Agent: iPhone-SwirlyMMS

x-wap-profile: "http://swirlyspace.com/UAprof/iPhoneSwirlyMMS.xml"

Content-Length: 4667



"HTTP/1.1 200 OK"

"Content-Length: 40"

"content-type: application/vnd.wap.mms-message"

"Connection: close"

""

hdr-len=105, cont-len=40

Content-Type:
MMS-Version: 1.0
Message-Type: m-send-conf
Response-Status: The network reported: message format corrupted
Response-Text: message-format-corrupt
Transaction-Id: 47E0078F
Error: The network reported: message format corrupted

Failed to send MMS, reason: The network reported: message format corrupted
worker thread now signals main thread.
SwirlyMMS terminated at: 2008-03-18 18:19:58 +0000


so you can see that version 0.3.6 did not fix my problem. Also what is version 0.3.6 meant to give for 02 customers - I sent an mms from my other phone
and I see no difference for the iphone - no message from swirly, but the usualy txt from o2 saying to go to the wwen to see it.

Any help appreciated,
thanks,
Texy