Mms: bcc shows 1st number of the list

Mms: bcc shows 1st number of the list SearchSearch

SMS & MMS Technical Forum » NowSMS Lite (Product Support Only) » Mms: bcc shows 1st number of the list « Previous || Next »
Author Message
peter chanq
New member
Username: Qqblog

Post Number: 20
Registered: 10-2012
Posted on Friday, October 11, 2013 - 02:20 pm:   

unlike bcc in email, the to: contains the 1st number of the list for all mms received.

how could make the mms showing the recipient number in the to field and hiding all other recipients?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4686
Registered: 08-2008
Posted on Friday, October 11, 2013 - 03:08 pm:   

Hi Peter,

I need a lot more detail to have any hope of answering your question.

How exactly are you submitting the MMS message? How are the recipients encoded in that MMS message submission?

What is the outbound MMS delivery protocol?


--
Des
NowSMS Support
peter chanq
New member
Username: Qqblog

Post Number: 21
Registered: 10-2012
Posted on Monday, October 14, 2013 - 09:36 am:   

i just use your web interface (:8800) to send. only

send as BCC: yes

all of options are default. i am using the latest version from your download site.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4690
Registered: 08-2008
Posted on Monday, October 14, 2013 - 06:01 pm:   

Hi Peter,

OK ... I'm not seeing any BCC problems when I use that technique. That is why I wanted to verify how you were specifying the BCC.

I suspect it may be an issue with your mobile operator's MMSC having some bugs processing BCC recipients.

Before jumping to that conclusion, let's try something.

Locate the file VASPOUT\nowsmslite\VASP.INI (with the current version of NowSMS Lite, that should be under ProgramData\NowSMS, where ProgramData is often a hidden directory).

Edit this file with NOTEPAD.

Under the [VASP] header, add on a blank line:

ForceBCC=Yes

This setting is an override that forces all outbound message recipients to be encoded as BCC.

If after applying this setting, you still encounter a problem with BCC recipients, I believe the issue is that your operator's MMSC has a bug in processing all recipients as BCC, and the MMSC is expecting at least one TO recipient.

I can't really think of a good way to work-around this, other than going back to that VASP.INI file and under the [VASP] header adding:

MaxRecips=1

That setting forces a separate message to be sent for each recipient instead of sending to multiple recipients at the same time. It will be slower, but the operator MMSC will see each recipient getting their own message.

--
Des
NowSMS Support

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics