| Charset and contenttype MM4 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| Robert Kristensen New member Username: Linkmobilitymms Post Number: 5 Registered: 11-2015 |
Our provider asks us to change the charset within the boundry: -----mime-boundary-D095192F.8DC378F0^M Content-Type: text/plain^M Content-ID: <text_1.txt>^M Content-location: text_1.txt^M Content-Transfer-Encoding: base64^M Should be changed to: Content-Type: text/plain; charset=UCS-2 (or UTF-8) Is there a setting for that or how is that possible to do? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5502 Registered: 08-2008 |
Hi Robert, At present no, but we are reviewing this and other feedback. We have been using strict rules for SMTP encoding (used by MM4), with the intent of supporting old SMTP relays. But based on yours and other feedback, this seems to be causing more issues with modern systems than help with older. We are making changes and adding options for this encoding, but it won't be ready for another week. -- Des NowSMS Support | |||
| Robert Kristensen New member Username: Linkmobilitymms Post Number: 6 Registered: 11-2015 |
Hi Des Is there any possibility you can make the patch sooner? We got a customer pressuring us, so this change is VERY important for us. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5505 Registered: 08-2008 |
I'm working on it. We have some changes pending that are working through testing. But we've prioritized this ahead of them. It's still going to take another approx 24 hours. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5506 Registered: 08-2008 |
Hi Robert, We've posted an update at http://www.nowsms.com/download/nowsms20151117.zip The default settings in this version will have the formatting you want. Note that the web UI is updated in this build. If you have customized an templates, make sure to back them up before updating. -- Des NowSMS Support | |||
| Robert Kristensen New member Username: Linkmobilitymms Post Number: 7 Registered: 11-2015 |
Hi Des Thank you very much for the update, we appreciate it very much. But, our provider was very a bit unclear about the format. Can it be changed from: Content-Type: text/plain; name="AD8737DE.txt"; charset=utf-8 To: Content-Type: text/plain; name="AD8737DE.txt"; charset="utf-8" With double quotation marks around the charset value. Again thank you very much for helping us. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5509 Registered: 08-2008 |
Hi Robert, I checked the MIME spec, and the quotes are only required when the value contains certain characters. The period is one of those characters, which is why the name value is quoted. Unfortunately I have a previous change request that removed the quotes for an interoperability problem. So we have to make it configurable. It is frustrating because the MIME spec is very clear, and to be honest, I expect that after we add a configuration option to do what you ask, your provider will still not handle utf-8 correctly. In other words I suspect the advice is a junior tech person looking at the trace and hoping the added quotes fix the problem. I say this because the MIME spec is very clear, and most examples don't include quotes. We will try to add an option by late Friday, but set your expectations accordingly. This may not resolve the issue. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5510 Registered: 08-2008 |
Hi Robert, I apologize, but the addition of this option is going to slip to Monday. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5511 Registered: 08-2008 |
Hi Robert, We've posted an update at http://www.nowsms.com/download/nowsms20151121.zip Upon further review we decided to just add the quotes for consistency with the encoding of other parameter values. -- Des NowSMS Support | |||
| Robert Kristensen New member Username: Linkmobilitymms Post Number: 8 Registered: 11-2015 |
Well now the provider is asking us to send "EUC-KR" encoding because the operators do not support "UTF-8". I have tried to convert MMStext to "EUC-KR", but the attached file is still "Utf-8": Content-Type: text/plain; name="046A9D4D.txt"; charset="utf-8" Content-ID: <046A9D4D.txt> Content-location: 046A9D4D.txt Is their any way that nowsms can either autodetect it or I can define it per MMS message? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5519 Registered: 08-2008 |
Hi Robert, NowSMS is expecting to always use utf-8 for text with MM4. Whatever character set is used as input will be converted to utf-8 when routed to MM4. EUC-KR is an unusual encoding to require, as it is unlikely that any partner system outside of Korea would support it. I will check with engineering to see if it might be possible to add configurable charset support to MM4, but I am concerned that converting from utf-8 to EUC-KR may be a more difficult conversion than other character sets. Unfortunately, this will require several days to investigate. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5521 Registered: 08-2008 |
Hi Robert, We are looking into this. I got feedback from engineering that converting to/from EUC-KR is feasible. So we are looking into adding a character set conversion option into the outbound MM4. We are going to try to get a test of this ready by the middle of next week. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5525 Registered: 08-2008 |
Hi Robert, A follow-up at http://www.nowsms.com/download/nowsms20151201.zip Here are details on the setting: * MM4/MM7: Add configuration parameter to use an alternative character set for text in outbound MM4 and MM7 messages. By default utf-8 is used. To specify an alternate character set, edit VASPOUT\routename\VASP.INI, and under the [VASP] header, add TextCharset=xxxxxxx. Only 8-bit multibyte character sets are supported (do not attempt to use UCS2 or UTF-16). -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5526 Registered: 08-2008 |
Hi Robert, A follow-up at http://www.nowsms.com/download/nowsms20151201.zip Here are details on the setting: * MM4/MM7: Add configuration parameter to use an alternative character set for text in outbound MM4 and MM7 messages. By default utf-8 is used. To specify an alternate character set, edit VASPOUT\routename\VASP.INI, and under the [VASP] header, add TextCharset=xxxxxxx. Only 8-bit multibyte character sets are supported (do not attempt to use UCS2 or UTF-16). -- Des NowSMS Support | |||
