| Auto BCC |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
| Author | Message | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 69 Registered: 08-2006 |
Hi Des When i am submitting mms messages to a VASP account on NowSMS gateway the AutoBCC email id defined in the MMSC.ini creates an error and this mms messages submitted via the VASP account are not auto bcced to the email id. Following is the setting: AutoBCC=mms@test.com Following is the log error: mms@test.com,Error: No SMSC defined to route message -- SYSTEM,SubmitUser=localsystem-mmsc;SMSCRouteName=SYSTEM Also i see a Mailer-Daemon@test.com user being created automatically in the mms users folder. Is this normal? Kindly let me know Thanks Sam | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4097 Registered: 08-2008 |
Hi Sam, What protocol is the VASP using? Are you using any routing or accounting callbacks that could be setting a route? Or maybe the VASP account has a forced route? -- Des NowSMS Support | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 70 Registered: 08-2006 |
Hi Des Thanks for your response. Tested VASP using mm7 and mm4. Both had identical issues. So this wont be an issue in my opinion. There is no accounting callbacks defined. There is no forced route either. In the VASP account tested using standard mms delivery and local recipients only. What i notice is that the autobcc email id is being treated as a mms recipient and its being routed via the VASP account (the stat counter does increase by 1 more..that is when the VASP is submiiting 1 mms it shows as 2 mms for the vasp account..the additional one for the autobcc) Kindly let me know if you require any further information. Also wanted to know that if a VASP is submitting lets say 1000 same mms messages...then does the autobcc email id get 1000 emails of the same MMS? or only one MMS? Also i tried testing submitting mms messages from one nowsms to another nowsms. Same thing happened. The routing had only 44*,+44* defined in the route messages option. That is only one specific country code allowed. On this point regarding submitting mms messages via NowSMS web interface.i see that the submitted mms messages are not being logged in the user log files. I mean the content of the mms messages is not being logged...Can this be logged? Kindly let me know Thanks for your time on this. Sam | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 71 Registered: 08-2006 |
Hi Des I just tested right now sending mms message from web interface of nowsms directly on the server. I mean VASP is not submitting messages. Even in this case the autobcc doesnt work and gives the same errors as above. It seems autobcc is working only when nowsms is being used as mmsc on the mobile handset. Oterwise its not working. Regards Sam | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4101 Registered: 08-2008 |
Hi Sam, There's something more to this, I just don't know what it is. Let's focus on sending MMS via the web interface, as that should be easiest to recreate. When I define an AutoBCC to an e-mail address ... and submit an MMS via the web interface, I get an MMS and an e-mail. So I'm trying to figure out what could be different in your setup. Can you enable the MMSCDEBUG.LOG and send another test message. Either post it in reply here, or e-mail to nowsms@nowsms.com with Attention: Des in the subject line. Meanwhile, I'll keep trying other scenarios. -- Des NowSMS Support | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 72 Registered: 08-2006 |
Hi Des Thanks for your reply. Found the following issues in the debug.log. Does this help? 14:26:43:968 [5] ThreadRouteSMTPOut: MAIL FROM:<@test.com> 14:26:43:968 [5] SendCommand: MAIL FROM:<@test.com> 14:26:43:984 [5] ThreadRouteSMTPOut: 555 5.5.2 Syntax error. w19si10087005qct.59 14:26:46:171 [17] ThreadProcessConnectionSMTP: 250 Ok 14:26:46:171 [5] ThreadRouteSMTPOut: MAIL FROM:<Mailer-Daemon@test.com> 14:26:46:171 [5] SendCommand: MAIL FROM:<Mailer-Daemon@test.com> 14:26:46:171 [17] ThreadProcessConnectionSMTP: MAIL FROM:<Mailer-Daemon@test.com> 14:26:46:171 [17] SendCommand: 250 Ok 14:26:46:171 [5] ThreadRouteSMTPOut: 250 Ok 14:26:46:171 [17] ThreadProcessConnectionSMTP: 250 Ok 14:26:46:171 [5] ThreadRouteSMTPOut: RCPT TO:<@test.com> 14:26:46:171 [5] SendCommand: RCPT TO:<@test.com> 14:26:46:171 [17] ThreadProcessConnectionSMTP: RCPT TO:<@test.com> 14:26:46:171 [17] SendCommand: 550 Recipient unknown or not local 14:26:46:171 [5] ThreadRouteSMTPOut: Recipient rejected 14:26:46:171 [17] ThreadProcessConnectionSMTP: 550 Recipient unknown or not local 14:26:46:171 [5] ThreadRouteSMTPOut: 550 Recipient unknown or not local | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 73 Registered: 08-2006 |
Hi Des Is this related to the following update in nowsms 2011-10-18: E-Mail: Fix for a problem where a message to an invalid recipient could trigger an e-mail loop with messages to Mailer-Daemon@ the local e-mail domain name. | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 74 Registered: 08-2006 |
Strangely i get the following nowsms error logs NowSMS Error Report. SMS message could not be sent to mms@test.com, Error: No SMSC defined to route message NowSMS Error Report. SMS message could not be sent to Mailer-Daemon@test.com, Error: No SMSC defined to route message Why would autobcc be considered as an SMS? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4102 Registered: 08-2008 |
If you have a loop where Mailer-Daemon messages keep getting generated ... from and to the same address. What's not clear to me is why it is treating the e-mail address as if it was a phone number. So the problem is earlier than that log snippet. I do believe there is a scenario where if a VASP has a forced route defined (i.e., "MMSC Routing for Received Messages" other than "Standard"), then there will be a problem routing an AutoBCC similar to what you describe for messages submitted by that account. What I'd like to see from the MMSCDEBUG.LOG is activity around the submission of the message, to try to see what configuration setting is triggering the unexpected behaviour. -- Des NowSMS Support | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 75 Registered: 08-2006 |
Hi Des Thanks for the inputs. I will try to get you the logs asap as currently i dont have access to the machine having the nowsms installed. What's not clear to me is why it is treating the e-mail address as if it was a phone number. So the problem is earlier than that log snippet. I think this might be due to the fact that a user is created automatically in MMSCUSERS with the name of the autobcc email id. I have a user automtically created in the folder as "mms" and when i click on it it has mms@test.com folder and then it has .QTA This user is only present in the MMSCUSERS folder. It doesnt show up in the MMSC users tab of nowsms. I do believe there is a scenario where if a VASP has a forced route defined (i.e., "MMSC Routing for Received Messages" other than "Standard"), then there will be a problem routing an AutoBCC similar to what you describe for messages submitted by that account. Just wanted to mention that the logs which i provided were for mms messages submitted via the web interface. The mms was not being submitted by VASP. Also in case of VASP i tested using standard mms delivery. What happens is that the mms routing defined on nowsms is ignored and each and every mms submited is sent as a wap push (sms direct). It doesnt send direct mms to the handset for the local recepients and/or ignores the routing defined in the mms routing. So i would require "local mms recepients only" in the VASP routing for nowsms to work fine with the mms routing. Thanks Sam | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4103 Registered: 08-2008 |
Hi Sam, There is some configuration option on your system that I'm still missing. I can see where if a VASP has a forced route defined (i.e., "MMSC Routing for Received Messages" other than "Standard" or "Local Recipients Only"), then there will be a problem routing an AutoBCC similar to what you describe for messages submitted by that account. However, this scenario would not effect a message submitted via the web interface. This is telling me that what you are seeing is something different. I'm not sure why there is a .QTA file and directory for this address. In my AUTOBCC tests I do see similar behaviour with this being created. However, that is just an errant statistic counter, it is not indicative of a problem. (We are investigating, it does seem to be related to submitting from the web interface, where it is not expected that this type of submission would result in an e-mail being generated.)
I edited some of your statements out of the above quote. Are you saying that every MMS you try to send ends up going out as a wap push (sms direct)? It sounds like the system is treating the AutoBCC e-mail address in the same way. There's something odd in the configuration. The only way I could see this happening is if an "MMSC Routing" definition was defined that had * and *@* as outbound preferred masks. I think I need to see not only MMSCDEBUG.LOG, but also configuration files ... MMSC.INI and all VASP.INI files under VASPIN and VASPOUT directories (best to just ZIP or RAR contents of VASPIN and VASPOUT). -- Des NowSMS Support | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 77 Registered: 08-2006 |
Hi Des Figured out this issue: What happens is that the mms routing defined on nowsms is ignored and each and every mms submited is sent as a wap push (sms direct). It doesnt send direct mms to the handset for the local recepients and/or ignores the routing defined in the mms routing. It seems i was submitting via the webinterface and via VASP without the + sign. The local MMSC users were defined with +MobileNumber and i was sending to MobileNumber. Hence the local recpeints were ignored. This is fixed. Anyway to preappend + sign for each and every outgoing mms? This are the logs of the mms message being submitted via the web interface which triggers of that email issue: 16:35:43:953 [17] ThreadProcessConnection: Got application/vnd.wap.mms-message 16:35:43:953 [17] ThreadProcessConnection: Got m-send-req 16:35:43:968 [17] ThreadProcessConnection: TO: +9718097394041/TYPE=PLMN 16:35:43:968 [17] MMSRoutingCallback: +9718097394041/TYPE=PLMN 16:35:43:968 [17] MMSRoutingCallback: +9718097394041/TYPE=PLMN 16:35:43:968 [17] CheckMMSBlockedContent: body part #1 Content-Type = application/smil 16:35:43:968 [17] CheckMMSBlockedContent: body part #2 Content-Type = image/jpeg 16:35:43:968 [17] CheckMMSBlockedContent: body part #3 Content-Type = text/plain 16:35:43:968 [17] DeliverMMSMessage: TO: +9718097394041/TYPE=PLMN 16:35:43:968 [17] DeliverMMSMessage: Found Phone Recip 16:35:43:968 [17] DeliverMMSMessage: BCC: mms@test.com 16:35:43:968 [17] DeliverMMSMessage: Found E-Mail Recip 16:35:43:968 [17] DebugTime: 2012/09/14 11:05:43 - 50530F87 16:35:43:984 [17] DeliverMMSMessage: C:\PROGRA~2\NowSMS\MMSCOUT\C7CE50EA.RFC 16:35:43:984 [17] DeliverMMSMessage: sending to mms@test.com 16:35:43:984 [17] ThreadProcessConnection: body part #1 name = 04FB4886.smil 16:35:43:984 [17] ThreadProcessConnection: body part #1 charset = utf-8 16:35:43:984 [17] ThreadProcessConnection: body part #1 Content-Type = application/smil 16:35:43:984 [17] ThreadProcessConnection: body part #1 Content-ID = <04FB4886.smil> 16:35:43:984 [17] ThreadProcessConnection: body part #1 Content-location = 04FB4886.smil 16:35:43:984 [17] ThreadProcessConnection: body part #1 Content-Type = image/jpeg 16:35:43:984 [17] ThreadProcessConnection: body part #1 Content-ID = <captain-haddock-500-500.jpg> 16:35:43:984 [17] ThreadProcessConnection: body part #1 Content-location = captain-haddock-500-500.jpg 16:35:44:000 [17] ThreadProcessConnection: body part #3 Content-Type = text/plain 16:35:44:000 [17] ThreadProcessConnection: body part #3 Content-ID = <04FB4886.txt> 16:35:44:000 [17] ThreadProcessConnection: body part #3 Content-location = 04FB4886.txt 16:35:44:000 [17] ThreadProcessConnection: Packet Length is 154 bytes 16:35:44:000 [17] ThreadProcessConnection: 48 54 54 50 2F 31 2E 30 20 32 30 30 20 4F 4B 0D HTTP/1.0 200 OK 16:35:44:000 [17] ThreadProcessConnection: 0A 43 6F 6E 6E 65 63 74 69 6F 6E 3A 20 63 6C 6F Connection: clo 16:35:44:000 [17] ThreadProcessConnection: 73 65 0D 0A 43 6F 6E 74 65 6E 74 2D 54 79 70 65 se Content-Type 16:35:44:000 [17] ThreadProcessConnection: 3A 20 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E : application/vn 16:35:44:000 [17] ThreadProcessConnection: 64 2E 77 61 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 d.wap.mms-messag 16:35:44:000 [17] ThreadProcessConnection: 65 0D 0A 43 6F 6E 74 65 6E 74 2D 4C 65 6E 67 74 e Content-Lengt 16:35:44:000 [17] ThreadProcessConnection: 68 3A 20 34 39 0D 0A 0D 0A 8C 81 98 35 30 35 33 h: 49 5053 16:35:44:000 [17] ThreadProcessConnection: 31 30 35 36 00 8D 90 92 80 8B 32 30 31 32 30 39 1056 201209 16:35:44:000 [17] ThreadProcessConnection: 31 34 2F 31 36 2F 43 37 43 45 35 30 45 41 40 6D 14/16/C7CE50EA@t 16:35:44:000 [17] ThreadProcessConnection: 6D 73 70 61 64 2E 63 6F 6D 00 est.com 16:35:44:000 [17] ThreadProcessConnection: Processing Complete 16:35:44:000 [17] InternalProcessConnection: Thread ended 16:35:44:609 [5] QueryMXRecord: Querying host 107.128.149.150 for MX record of test.com 16:35:44:609 [5] QueryMXRecord: MX Result for test.com: aspmx.l.google.com 1 16:35:44:609 [5] QueryMXRecord: MX Result for test.com: alt2.aspmx.l.google.com 5 16:35:44:609 [5] QueryMXRecord: MX Result for test.com: alt1.aspmx.l.google.com 5 16:35:44:609 [5] QueryMXRecord: MX Result for test.com: aspmx2.googlemail.com 10 16:35:44:609 [5] QueryMXRecord: MX Result for test.com: aspmx3.googlemail.com 10 16:35:45:609 [5] InetmmsConnect: Connected to aspmx.l.google.com (173.194.76.27:25) 16:35:45:625 [5] ThreadRouteSMTPOut: 220 mx.google.com ESMTP fx6si1607750qab.12 16:35:45:625 [5] ThreadRouteSMTPOut: HELO test.com 16:35:45:625 [5] SendCommand: HELO test.com 16:35:45:640 [5] ThreadRouteSMTPOut: 250 mx.google.com at your service 16:35:45:640 [5] ThreadRouteSMTPOut: MAIL FROM:<@test.com> 16:35:45:640 [5] SendCommand: MAIL FROM:<@test.com> 16:35:45:656 [5] ThreadRouteSMTPOut: 555 5.5.2 Syntax error. fx6si1607750qab.12 16:35:46:671 [5] QueryMXRecord: Querying host 107.128.149.150 for MX record of test.com 16:35:46:671 [5] QueryMXRecord: MX Result for test.com: test.com 10 16:35:46:671 [5] QueryMXRecord: MX Result for test.com: test.com 20 16:35:46:671 [5] QueryMXRecord: MX Result for test.com: test.com 30 16:35:47:671 [5] InetmmsConnect: Connected to test.com (274.284.138.177:25) 16:35:47:671 [17] ThreadProcessConnection: Thread started 16:35:47:671 [17] ThreadProcessConnectionSMTP: Processing SMTP connection from 274.284.138.177... 16:35:47:671 [17] SendCommand: 220 SMTP Ready 16:35:47:671 [5] ThreadRouteSMTPOut: 220 SMTP Ready 16:35:47:671 [17] ThreadProcessConnectionSMTP: 220 SMTP Ready 16:35:47:671 [5] ThreadRouteSMTPOut: HELO test.com 16:35:47:671 [5] SendCommand: HELO test.com 16:35:47:671 [17] ThreadProcessConnectionSMTP: HELO test.com 16:35:47:671 [17] SendCommand: 250 Ok 16:35:47:671 [5] ThreadRouteSMTPOut: 250 Ok 16:35:47:671 [17] ThreadProcessConnectionSMTP: 250 Ok 16:35:47:671 [5] ThreadRouteSMTPOut: MAIL FROM:<Mailer-Daemon@test.com> 16:35:47:671 [5] SendCommand: MAIL FROM:<Mailer-Daemon@test.com> 16:35:47:671 [17] ThreadProcessConnectionSMTP: MAIL FROM:<Mailer-Daemon@test.com> 16:35:47:671 [17] SendCommand: 250 Ok 16:35:47:671 [5] ThreadRouteSMTPOut: 250 Ok 16:35:47:671 [17] ThreadProcessConnectionSMTP: 250 Ok 16:35:47:671 [5] ThreadRouteSMTPOut: RCPT TO:<@test.com> 16:35:47:671 [5] SendCommand: RCPT TO:<@test.com> 16:35:47:671 [17] ThreadProcessConnectionSMTP: RCPT TO:<@test.com> 16:35:47:671 [17] SendCommand: 550 Recipient unknown or not local 16:35:47:671 [5] ThreadRouteSMTPOut: Recipient rejected 16:35:47:671 [17] ThreadProcessConnectionSMTP: 550 Recipient unknown or not local 16:35:47:671 [5] ThreadRouteSMTPOut: 550 Recipient unknown or not local 16:35:47:671 [17] WaitForResponsePOP3: ioctlsocket reports no more data 16:35:47:671 [17] ThreadProcessConnectionSMTP: Closing SMTP Connection 16:35:47:671 [17] ThreadProcessConnection: Thread ended 16:35:48:671 [5] QueryMXRecord: Querying host 107.128.149.150 for MX record of test.com 16:35:48:671 [5] QueryMXRecord: MX Result for test.com: test.com 10 16:35:48:671 [5] QueryMXRecord: MX Result for test.com: test.com 20 16:35:48:671 [5] QueryMXRecord: MX Result for test.com: test.com 30 16:35:49:671 [5] InetmmsConnect: Connected to test.com (274.284.138.177:25) 16:35:49:671 [17] ThreadProcessConnection: Thread started 16:35:49:671 [17] ThreadProcessConnectionSMTP: Processing SMTP connection from 274.284.138.177... 16:35:49:671 [17] SendCommand: 220 SMTP Ready 16:35:49:671 [5] ThreadRouteSMTPOut: 220 SMTP Ready 16:35:49:671 [17] ThreadProcessConnectionSMTP: 220 SMTP Ready 16:35:49:671 [5] ThreadRouteSMTPOut: HELO test.com 16:35:49:671 [5] SendCommand: HELO test.com 16:35:49:671 [17] ThreadProcessConnectionSMTP: HELO test.com 16:35:49:671 [17] SendCommand: 250 Ok 16:35:49:671 [5] ThreadRouteSMTPOut: 250 Ok 16:35:49:671 [17] ThreadProcessConnectionSMTP: 250 Ok 16:35:49:671 [5] ThreadRouteSMTPOut: MAIL FROM:<Mailer-Daemon@test.com> 16:35:49:671 [5] SendCommand: MAIL FROM:<Mailer-Daemon@test.com> 16:35:49:671 [17] ThreadProcessConnectionSMTP: MAIL FROM:<Mailer-Daemon@test.com> 16:35:49:671 [17] SendCommand: 250 Ok 16:35:49:671 [5] ThreadRouteSMTPOut: 250 Ok 16:35:49:671 [17] ThreadProcessConnectionSMTP: 250 Ok 16:35:49:671 [5] ThreadRouteSMTPOut: RCPT TO:<Mailer-Daemon@test.com> 16:35:49:671 [5] SendCommand: RCPT TO:<Mailer-Daemon@test.com> 16:35:49:671 [17] ThreadProcessConnectionSMTP: RCPT TO:<Mailer-Daemon@test.com> 16:35:49:671 [17] MMSRoutingCallback: Mailer-Daemon 16:35:49:671 [17] MMSRoutingCallback: Mailer-Daemon 16:35:49:671 [17] SendCommand: 250 Ok 16:35:49:671 [17] ThreadProcessConnectionSMTP: 250 Ok 16:35:49:671 [5] ThreadRouteSMTPOut: 250 Ok 16:35:49:671 [5] ThreadRouteSMTPOut: DATA 16:35:49:671 [5] SendCommand: DATA 16:35:49:671 [17] ThreadProcessConnectionSMTP: DATA 16:35:49:671 [17] SendCommand: 354 Ok, end with "." on a new line... 16:35:49:671 [5] ThreadRouteSMTPOut: 354 Ok, end with "." on a new line... 16:35:49:671 [17] ThreadProcessConnectionSMTP: 354 Ok, end with "." on a new line... 16:35:49:671 [5] ThreadRouteSMTPOut: . 16:35:49:671 [5] SendCommand: . 16:35:49:671 [17] ThreadProcessConnectionSMTP: Message received 157 bytes ... processing ... 16:35:49:671 [17] SendCommand: 250 Message Accepted 16:35:49:671 [5] ThreadRouteSMTPOut: 250 Message Accepted 16:35:49:671 [17] ThreadProcessConnectionSMTP: To: Mailer-Daemon@test.com From: Mail Delivery <Mailer-Daemon@test.com> Subject: ERROR: ERROR: Subject Message could not be delivered to @test.com 16:35:49:671 [5] ThreadRouteSMTPOut: QUIT 16:35:49:671 [17] ThreadProcessConnectionSMTP: 250 Message Accepted 16:35:49:671 [5] SendCommand: QUIT 16:35:49:671 [17] ThreadProcessConnectionSMTP: QUIT 16:35:49:671 [17] SendCommand: 221 Goodbye 16:35:49:671 [5] ThreadRouteSMTPOut: 221 Goodbye 16:35:49:671 [17] ThreadProcessConnectionSMTP: 221 Goodbye 16:35:49:671 [17] ThreadProcessConnectionSMTP: Closing SMTP Connection 16:35:49:671 [17] ThreadProcessConnection: Thread ended 16:35:50:328 [7] ThreadRouteSMTPIn: 826067E3.RFC 16:35:50:328 [7] ThreadRouteSMTPIn: X-MMSC-RCPT-TO: Mailer-Daemon 16:35:50:328 [7] ThreadRouteSMTPIn: X-MMSC-RCPT-TO: BCC: mms@test.com 16:35:50:328 [7] ThreadRouteSMTPIn: BCC: mms@test.com/TYPE=PLMN 16:35:50:328 [7] ThreadRouteSMTPIn: X-MMSC-Received-From: 274.284.138.177 16:35:50:328 [7] ThreadRouteSMTPIn: X-MMSC-ENV-MAIL-FROM: <Mailer-Daemon@test.com> 16:35:50:328 [7] ThreadRouteSMTPIn: To: Mailer-Daemon@test.com 16:35:50:328 [7] ThreadRouteSMTPIn: Mailer-Daemon@test.com/TYPE=PLMN 16:35:50:328 [7] ThreadRouteSMTPIn: From: Mail Delivery <Mailer-Daemon@test.com> 16:35:50:328 [7] ThreadRouteSMTPIn: Subject: ERROR: ERROR: Subject 16:35:50:343 [7] DeliverMMSMessage: BCC: mms@test.com/TYPE=PLMN 16:35:50:343 [7] DeliverMMSMessage: Found Phone Recip 16:35:50:343 [7] DeliverMMSMessage: Mailer-Daemon@test.com/TYPE=PLMN 16:35:50:343 [7] DeliverMMSMessage: Found Phone Recip Kindly let me know if anything else is required. Thanks a million for your time on this. Sam | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 78 Registered: 08-2006 |
Hi Des Somethings wrong with my setup i guess...i tried to test the ShortCode thing for MMS. Messages are comming in but again the email id specificed for that short code is being treated as a mobile number. Can you kindly give me some pointers on how to get email servers settings done? Thanks Sam | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8027 Registered: 10-2002 |
Hi Sam, Sorry for the delay in response (and thanks for answering the retry questions in another thread). I hope to answer all of your outstanding questions shortly, but as it's been a little hectic with Des on holiday, for now, I'm going to respond to one question at a time in order to minimise delay.
The MMSC.INI / [MMSC] / MSISDNRecipientPrefixConvert= setting can do this. It is a little confusing, but this would apply the transformation: MSISDNRecipientPrefixConvert=1:+1,2:+2,3:+3,4:+4,5:+5,6:+6,7:+7,8:+8,9:+9 Basically this looks for a recipient address that starts with the value before the : and replaces the matching prefix with the value after the : I did leave out 0:+0, because in most regions, you'd want to convert 00:+ (00 is a common international dialing prefix) and 0:+99, where 99 is your local country code. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8028 Registered: 10-2002 |
Is the sender address for the MMS message blank? When the message is routed to e-mail, the MMS sender address is used to build the e-mail sender address. The blank sender results in an invalid e-mail sender address. For VASP submissions, the solution to this is to set a "Default Sender Address" for the account. That will be applied if the sender address is blank. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8029 Registered: 10-2002 |
If those mailer-daemon messages are triggering a loop, you can either update, or edit MMSC.INI, and under the [MMSC] header add: SystemUser1=mailer-daemon | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8030 Registered: 10-2002 |
Sam, I think I need more detail on this. What have you configured and what is happening? -bn | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 81 Registered: 08-2006 |
Hi Bryce Its indeed an honour to interact with you and your wonderful support team. MSISDNRecipientPrefixConvert fixes the issue for mobile numbers. Thanks for that. Is the sender address for the MMS message blank? This fixes the autobcc issue. Thanks a million for this. That means the MMSFrom and Sender is different. I didnt knew that. For the VASP it would be the Vasp Sender Address right? Regarding SystemUser1=mailer-daemon I am testing using the latest version. So i belive this wont be required as the issue is fixed. Regarding the Last issue....the Short code issue....I got the following defined in the MMSC.INI, [ShortCode] section: 55555=test@gmail.com What happens is that instead of fowarding the mms to the designated email id...the email id is considered a mobile number...Following logs.... 05:47:32:875 [17] ThreadProcessConnection: TO: 55555/TYPE=PLMN 05:47:32:875 [17] MMSRoutingCallback: 55555/TYPE=PLMN 05:47:32:875 [17] MMSRoutingCallback: test@gmail.com 05:47:32:875 [17] MMSRoutingCallback: E-mail address 05:47:32:875 [17] MMSRoutingCallback: test@gmail.com 05:47:32:875 [17] CheckMMSBlockedContent: body part #1 Content-Type = application/smil 05:47:32:875 [17] CheckMMSBlockedContent: body part #2 Content-Type = image/jpeg 05:47:32:875 [17] DeliverMMSMessage: TO: test@gmail.com/TYPE=PLMN 05:47:32:875 [17] DeliverMMSMessage: Found Phone Recip Also the MSISDNRecipientPrefixConvert settings affects the short codes also. Should it not only affect the mobile numbers only and ignore the short codes? Kindly let me know Thanks for your time. Its highly appreciated. Sam | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8033 Registered: 10-2002 |
Hi Sam, You're right, there is something wrong with the [ShortCode] processing to an e-mail address. We are investigating.
Unfortunately this is true. My suggestion to use MSISDNRecipientPrefixConvert so broadly may have other side effects such as this. I don't know that there is any good current solution that would also work with short codes. -bn | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 82 Registered: 08-2006 |
Thanks for your time on this. Looking forward to a fix on the [ShortCode] processing to an e-mail address Also There is following fix required: http://support.nowsms.com/discus/messages/1/70549.html The new ReRouteOnError setting does not seem to be working for SMPP connections. Also would request your inputs if MMS signature while sending MMS to email IDs is doable? Something like MMSEMailTemplate=@@Text@@ (sent:using server1) Ref: http://support.nowsms.com/discus/messages/1/71112.html Thanks once again. Sam | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8037 Registered: 10-2002 |
Hi Sam, Yes we have implemented the engineering fixes for both those issues, but we are holding off posting it until after Des is back from holiday and has a chance to review. Regarding the MMS to email issue, I assume you are looking more for an added signature than a full blown template? -bn | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 83 Registered: 08-2006 |
Hi Bryce Thanks for your reply. Regarding: Regarding the MMS to email issue, I assume you are looking more for an added signature than a full blown template? Yes. full blown template is not required. Something similar to the SMS to email signature as explained by Des in that particular thread. Adding a setting in the MMSC.ini. Looking forward to the fixes. Thanks once again Sam | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 85 Registered: 08-2006 |
Hi Bryce nowsms 20121004 fixes the [ShortCode] processing to an e-mail address issue. MMS Signature is the only issue remaining. Thanks for this. Highly appreciated. Sam | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4131 Registered: 08-2008 |
Hi Sam, Yes, the email signature option is still on our todo list. It has proven to be more difficult than expected. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4204 Registered: 08-2008 |
Hi Sam, A follow-up ... we added a configuration setting to add an e-mail signature when routing MMS to e-mail. In version 2012.11.16 and later: To add a signature, edit MMSC.INI and under the [MMSC] section header add MMSEMailSignature=xxxxxxx. To include a blank line in the signature, use the escape sequence \r\n. http://www.nowsms.com/download/nowsms20121116.zip -- Des NowSMS Support | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 108 Registered: 08-2006 |
Bingo!!! works great. Thanks a million for your time on this | |||
