MM4 and MIME Encoding | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
Author | Message | |||
zafir Unregistered guest |
Hi, While sending a MMS through SMTP i.e MM4 what is the format of MMS file.Is it MIME Encoded as mentioned in Help or WSP Encoded? If anyone has MMS file for MM4 please send it to me. Thanks in Advance. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3326 Registered: 10-2002 |
The standard MIME enocoding for attachments is used. NowSMS will allow you to have an attachment that is in MMS Encapsulation format (e.g., WSP encoded attachment included as one of the MIME parts), but that is somewhat non-standard. We provide that particular support primarily for testing purposes so that people have an easy way to send a pre-compiled MMS to the gateway. | |||
zafir Unregistered guest |
Thanks, According to your example in help the MM4/SMTP dialog looks something like this: --------------------------------------------- IN: 220 SMTP Ready OUT: HELO client.name (or EHLO client.name) IN: 250 OK (or a multiline response if EHLO was used) OUT: AUTH LOGIN IN: 334 VXNlcm5hbWU6 ("Username:" BASE64 encoded) OUT: dGVzdA== ("test" BASE64 encoded) IN: 334 UGFzc3dvcmQ6 ("Password:" BASE64 encoded) OUT: dGVzdA== ("test" BASE64 encoded) IN: 235 Ok OUT: MAIL FROM: <username@domain.com> IN: 250 Ok OUT: RCPT TO: <+447778889999/TYPE=PLMN@mms.domain.com> IN: 250 Ok OUT: DATA IN: 354 Ok, end with "." on a new line... OUT: (Transmit MIME encoded message, then end with a line with only the . character) IN: 250 Message Accepted OUT: QUIT ------------------------------ What will be the format of DATA.Is it just MIME Encoded or MIME WSP Encoded? Please send example file which will be transmited as data. Thanks | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3339 Registered: 10-2002 |
As I stated above, the standard MIME enocoding for attachments is used. A standard SMTP envelope with a MIME encoded message body. I don't have an example handy, but it is the same format that you would use from a standard internet e-mail client. It is nothing special. I just did a quick web search using a keyword of "MIME Example", and found the following link, which has a reasonable example. You would just change the "From" and "To" headers. http://www.mars.dti.ne.jp/~torao/program/mail/mime-example.html The only additional thing that I would point out is that if you have a SMIL file included, you should use a different "Content-type:" header in the main SMTP envelope to be "multipart/related" instead of "multipart/mixed". (NowSMS will recognise the SMIL file properly even if you use "multipart/mixed", but technically if a SMIL file is included it should be "multipart/related" with a "start=" parameter pointing to the "Content-ID:" of the SMIL part.) From: xxxxxxx To: xxxxxxx Subject: Message Subject MIME-Version: 1.0 Content-Type: multipart/related; boundary="mimeBoundary"; type="application/smil"; start=<message.smil> --mimeBoundary Content-Type: application/smil Content-location: message.smil Content-id: <message.smil> message.smil here --mimeBoundary Content-Type: image/gif Content-Location: image.gif Content-Transfer-Encoding: base64 image.gif here base64 encoded --mimeBoundary Content-Type: text/plain Content-Location: text.txt test.txt here --mimeBoundary-- | |||
william Unregistered guest |
but I want to know where do the mms header appear in the smtp message format. e.g. Mms-version, Mms transaction Id, Mms expiry etc. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3722 Registered: 10-2002 |
For specific technical information, you should refer to the appropriate 3GPP specification, in this case TS 23.140. Generally speaking, if present, these headers appear in the SMTP message header. For example, extending the above example, you might see this: From: xxxxxxx To: xxxxxxx Subject: Message Subject X-Mms-3GPP-MMS-Version: 5.3.0 X-Mms-Message-Type: MM4_forward.REQ X-Mms-Transaction-ID: blahblah X-MMS-Message-ID: "F17FE2F7@mms.host.name" MIME-Version: 1.0 Content-Type: multipart/related; boundary="mimeBoundary"; type="application/smil"; start=<message.smil> |