Problems with MM4 multiple recipients

Problems with MM4 multiple recipients SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Problems with MM4 multiple recipients « Previous || Next »
Author Message
Mindaugas Riauba
Unregistered guest
Posted on Wednesday, May 19, 2004 - 09:42 am:   

It;s me again and once more with MM4 problems :-).

When I'm trying to send MMS to multiple recipients (Nokia7650) NowSMS seems to break e-mail headers.
For the first e-mail NowSMS sends headers:
From: +[number]/TYPE=PLMN
To: +[number]/TYPE=PLMN
That's correct.
For the second:
From: +37069923387/TYPE=PLMN
And where from appeared comma and where is "To:"?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2742
Registered: 10-2002
Posted on Tuesday, June 08, 2004 - 06:30 pm:   


Apologies for the delay in responding to your message. This is a rather severe problem, and I wish that you would have contacted us directly via e-mail, as sometimes the discussion board volume does get overwhelming for us to keep up with.

I can confirm that there is a problem that appears to have been introduced in v5.50 where multiple recipients are not handled correctly when routing outbound via MM4.

As a temporary solution, I would recommend the following.

In the VASPOUT\accountname directory, you will find a file named VASP.INI. In this file, under the [VASP] header, add the following:


When a message is sent to multiple recipients, the above setting controls how many recipients will be sent per message instance over a connection to an external MMSC.

The default for MM4 connections is 1.

The default for MM7 connections is 100.

The default for MM1 connections is 5.

The default for EAIF connections is 10.

Basically, there is a bug in the MM4 handling, where when a message is sent to more than this recipients per message limit, the "To:" header is not constructed properly.

We have applied a patch, and you can send me an e-mail ( to request the patch. However, this work-around should also be sufficient.


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