Hi,

Perfect, it works.
Thanks a lot.

Regards,

Tshimanga.




Tshimanga Minkoka

Mobile: +243814443113



This e-mail is classified C2 - Vodacom Restricted - Information to be used 
inside Vodacom but it may be shared with authorised partners.

Ce courriel est classifie C2 – Vodacom Restreint. Ce sont des informations dont 
la divulgation non autorisée, en particulier en dehors de l'organisation, 
serait inappropriée et inopportune


From: [email protected] [mailto:[email protected]] On Behalf Of 
Tshimanga Minkoka
Sent: Friday 06 July 2012 09:24
To: Jacob Eiler; [email protected]
Subject: RE: Is there a way to force a sender in sendsms-user group?



Dear Jacob,

OK. I will give it a try and post feedback.

Regards,

Tshimanga.

PS: Sorry for the double posting. I first took a while to come in back in my 
inbox, and I thought it had failed, so I reposted.




Tshimanga Minkoka

Mobile: +243814443113



This e-mail is classified C2 - Vodacom Restricted - Information to be used 
inside Vodacom but it may be shared with authorised partners.

Ce courriel est classifie C2 – Vodacom Restreint. Ce sont des informations dont 
la divulgation non autorisée, en particulier en dehors de l'organisation, 
serait inappropriée et inopportune


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]]<mailto:[mailto:[email protected]]> On 
Behalf Of Jacob Eiler
Sent: Friday 06 July 2012 08:54
To: [email protected]<mailto:[email protected]>
Subject: Re: Is there a way to force a sender in sendsms-user group?

Sorry, it a 'faked-sender', but I believe it has higher priority than the 
'from' specified in the HTTP request.

I believe the priority is

faked-sender
from variable
default-sender
global-sender

/Jacob

On 2012-07-06 09:48, Jacob Eiler wrote:
There is a "forced-sender" setting for sendsms-user.

/Jacob

On 2012-07-06 09:36, Tshimanga Minkoka wrote:

Dears,



What I want to achieve is to force and use a kind of forced-sender in 
sendsms-user group, in order for smsbox to always ignore the supplied sender 
(by the from parameter in the HTTP request) in the HTTP request to replace it 
by the forced-sender.



I was not able to find something clearly related in the user guide.



The only thread I found in mailing list ("Senders/from white-list" on 09 Nov 
2009) that somehow discusses the problem is quite old and does not come to a 
final conclusion. Being old, maybe some patches have already been merged in the 
latest versions.



Any help or suggestion will be appreciated.



Best regards,



Tshimanga







Tshimanga Minkoka

Manager VAS  & Data Systems

Billing & IT Group

Desk   : +243815560341 ext 0583

Mobile: +243814443113

http://www.vodacom.cd/

https://twitter.com/#!/Vodacomcongo<https://twitter.com/#%21/Vodacomcongo> 
http://www.facebook.com/VodacomRDC

This e-mail is classified C2 - Vodacom Restricted - Information to be used 
inside Vodacom but it may be shared with authorised partners.

Ce courriel est classifie C2 – Vodacom Restreint. Ce sont des informations dont 
la divulgation non autorisée, en particulier en dehors de l'organisation, 
serait inappropriée et inopportune











--
Jacob Eiler
Apide ApS
e: [email protected]<mailto:[email protected]>
t: +45 23740486
w: apide.com

[cid:[email protected]]



--
Jacob Eiler
Apide ApS
e: [email protected]<mailto:[email protected]>
t: +45 23740486
w: apide.com

[cid:[email protected]]





Mobile:



This e-mail is classified C2 - Vodacom Restricted - Information to be used 
inside Vodacom but it may be shared with authorised partners.

Ce courriel est classifie C2 – Vodacom Restreint. Ce sont des informations dont 
la divulgation non autorisée, en particulier en dehors de l'organisation, 
serait inappropriée et inopportune





Mobile:



This e-mail is classified C2 - Vodacom Restricted - Information to be used 
inside Vodacom but it may be shared with authorised partners.

Ce courriel est classifie C2 – Vodacom Restreint. Ce sont des informations dont 
la divulgation non autorisée, en particulier en dehors de l'organisation, 
serait inappropriée et inopportune


<<inline: image001.png>>

Reply via email to