| Filenames in mm7 SubmitReq |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 03, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Tilman Unregistered guest |
Hello! I've noticed that the nowmms gateway changes the filenames of the soap attachments if I post a mm7 SubmitReq to it. Now, that will give me a problem with my smil files, that reference the files by its name. Or am I missing out on something here? See a trace below: SubmitReq: ------=_Part_0_5699121.1090863836014 Content-Type: image/gif Content-Transfer-Encoding: base64 Content-ID : flower_small.gif ... more binary data... NowMMS changes this to (in the *.rfc file): ----mime-boundary-mms-message-B4E4E059 Content-Type: image/gif; name="671567D8.gif" Content-disposition: attachment; filename="671567D8.gif" Content-location: 671567D8.gif Content-Transfer-Encoding: base64 | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3138 Registered: 10-2002 |
Hi Tilman, We don't look at the "Content-ID:" field for a filename. Adding a "Content-Location:" header, or adding a "name=" parameter to the "Content-type:" field would resolve this. That said, are you submitting MM7 but then having that routed via MM4/SMTP? As I look at this, we do maintain the "Content-ID:" when routing from MM7 to direct MMS delivery (NowSMS as the MMSC). And it should be maintained when going out to MM4. So, actually, this has me a bit confused, because some quick tests here suggest that the "Content-ID:" field does go through the different conversions that I can think of trying. So maybe I'm not following the routing that you are using. Could you explain? Also, I notice some white space in your post above between "Content-ID" and the ":". That could also cause a problem. I don't think NowSMS will pick up the "Content-ID:" header because it considers "Content-ID :" to be a different header than "Content-ID:". -bn | |||
| tilman Unregistered guest |
Hi Bryce! Yes, I figured that out by now, setting the filename in the content-type header, and setting the content-location did the job. Must say, that you have an eye for http traces, that Content-ID whitespace bug did actually give some trouble on another occasion... Yes I post SubmitRequests to the nowmms gateway via mm7, using my own api, which I'm developing. At first I routed the incoming traffic to mm4, but that somehow never got relayed (how do you set credentials for the smtp server?), then I wanted to relay it via mm7, that does not work either, turned on debug mode, everything seems fine there? Anyway I'm just starting out, thanx for the detailed reply, that's a great forum that you guys maintain here, about the only address for mm7 development problems. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3148 Registered: 10-2002 |
Hi Tilman, We don't have a way to set the SMTP authentication credentials for the general relay out to SMTP. (When you send MMS out to an e-mail address.) You could define an MM4 connection under "MMSC Routing", and that does support SMTP authentication. The only catch is that then you would be sending to phonenumber/TYPE=PLMN@configuredMM4DomainName. That is a little confusing, but if you have some control over your SMTP server to create a mailbox or alias for this address format, then that might help you out. Good luck! | |||
