| MMS to e-mail problem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 14, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Mindaugas Riauba Unregistered guest |
There is problem with sending an e-mail from mms-phone. NowSMS does not "double" dot if e-mail contains single dot on line. Single dot in SMTP conversation means end of data. Version: 5.01 (b20031230) | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2421 Registered: 10-2002 |
If an MMS to e-mail contains a single dot on a line, NowSMS will encode that body part using BASE64 encoding, which gets around the problem. I just tried here, sending an MMS from a phone to an e-mail address, and didn't see any problem. Perhaps you are doing something else. If so, please explain. -bn | |||
| Mindaugas Riauba Unregistered guest |
I did not preserve the message but I looked into the .RFC file in MMSDATA\ folder. And that dot was not in the already BASE64 encoded part but somewhere in mime-boundary part. Anyway - why to assume that message cannot contain single dot? Just do the escaping. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2431 Registered: 10-2002 |
I'd have to see the file, or understand how to submit a message such that it would be encoded in that way. If I configure an MMS client to send a message to an e-mail recipient, that includes text with a line that contains a single dot, my tests show that the MMSC encodes the text in BASE64 format to avoid any problems transmitting the text. We decided to use BASE64 encoding on the text rather than escaping it. That was an implementation decision on our end. I see no problem with our implementation decision (unless there is a scenario for which this does not occur, which is why I was asking you for more information). -bn | |||
| Mindaugas Riauba Unregistered guest |
The problem was that line containing sinlgle dot was not in the MMS text. It appeared in already BASE64 encoded SMTP message in mime headers. Maybe it's had to believe but I had three such messages in outbound queue. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2540 Registered: 10-2002 |
Unfortunately, I think I'd have to see it to understand. If it happens again, please save the message file. The "." character is not part of the BASE64 character set. So encoding such text as BASE64 gets around problems like this (that's why we do it). By all means, if it happens again, save a message, and forward it to me ... as perhaps there is some other way that a single dot could get in there that I cannot think of. In all of my tests, I couldn't recreate a problem. -bn | |||
| Mindaugas Riauba Unregistered guest |
Got one more in queue. Sending it to you by e-mail. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2547 Registered: 10-2002 |
That example explained a lot. The problem is that during quoted printable encoding, we automatically insert line breaks on lines of text longer than 79 characters. The first character after one of those automatically inserted line breaks might be a "." character. That is where the problem occurs. If it was a manually inserted line break (like I assumed on the forum), then it would have been handled properly. But we hadn't accounted for the automatically inserted line breaks. I have sent you an update via e-mail that addresses this problem. | |||
