| MM4 with Bandwidth.com |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| John Bittner New member Username: Johnbittner Post Number: 2 Registered: 04-2026 |
Hello, We're having trouble trying to get MM4 to work correctly with bandwidth.com. Were seeing messages try to come in but they are being rejected with this error. 2026-04-30 21:06:08,SMTPIN,3.82.123.96,+18624770899/TYPE=PLMN@mms.messaging.bandwidth.com,+19733901090,REJECTED,REJECTED-550 Recipient unknown or not local,0 I assume its getting rejected because the message is coming in with a malformed address. How do I fix this ? Any help is much appreciated Thanks John Bittner This is debug 10:56:39:282 [19] ThreadProcessConnectionSMTP: NOOP 10:56:39:282 [19] ThreadProcessConnectionSMTP: 250 Ok 10:56:39:357 [19] ThreadProcessConnectionSMTP: MAIL FROM:<+18624770899/TYPE=PLMN@mms.messaging.bandwidth.com> 10:56:39:357 [19] ThreadProcessConnectionSMTP: 250 Ok 10:56:39:432 [19] ThreadProcessConnectionSMTP: RCPT TO:<+19733901090/TYPE=PLMN@null> 10:56:39:432 [19] ThreadProcessConnectionSMTP: 550 Recipient unknown or not local 10:56:39:505 [19] ThreadProcessConnectionSMTP: RSET 10:56:39:505 [19] ThreadProcessConnectionSMTP: 250 Ok 10:56:40:579 [19] ThreadProcessConnectionSMTP: QUIT 10:56:40:579 [19] ThreadProcessConnectionSMTP: 221 Goodbye 10:56:40:654 [19] WaitForSocketClose: WinSock reported ioctlsocket complete 10:56:40:654 [19] ThreadProcessConnectionSMTP: Closing SMTP Connection 10:56:40:654 [19] ThreadProcessConnectionSMTP: Thread ended 10:56:52:632 [18] ThreadProcessConnectionSMTP: QUIT 10:56:52:632 [18] ThreadProcessConnectionSMTP: 221 Goodbye 10:56:52:632 [18] WaitForSocketClose: WinSock reported ioctlsocket complete 10:56:52:632 [18] ThreadProcessConnectionSMTP: Closing SMTP Connection 10:56:52:632 [18] ThreadProcessConnectionSMTP: Thread ended 10:56:52:673 [18] ThreadProcessConnection: Thread started 10:56:52:673 [18] ThreadProcessConnectionSMTP: Processing SMTP connection from 67.231.1.16... 10:56:52:673 [18] ThreadProcessConnectionSMTP: 220 SMTP Ready 10:56:52:714 [18] ThreadProcessConnectionSMTP: EHLO mms-dfw.bandwidthclec.com 10:56:52:714 [18] ThreadProcessConnectionSMTP: 250-Ok 250-AUTH LOGIN 250 HELP My config files. [MMSC] Debug=Yes SMTPPort=25 LocalDomain=mms.xaccel.net RelayHost=mail2.xaccel.net SMSEMail=Yes SMSDomainName=sms.xaccel.net SMSPerEMail=1 SMSEMailSender= WebPort=8080 HostName=sms.xaccel.net DomainName=mms.messaging.bandwidth.com SMTPRequireAuth=No EnableDeliveryNotification=No ConvertImages=No ConvertScaleToScreen=Yes SMTPUseStartTLS=No [AuthEMailSMS] User1=john@xaccel.net [Outbound MMS Routing] Bandwidth=* [SMSGW] Modem1=SMPP - 3.224.76.201:2775 WebAuth=Yes WebMenu=Yes WebDisplaySender=Yes WebDisplayRoute=Yes WebPort=8800 SeparateUserQueues=Yes ReceiveSMS=Yes ReceiveMMS=Yes PHPEnable=No PHPAllowRemote=No ReceiveSMSCharset=utf-8 IPAddress=199.73.108.114 Debug=Yes 2WayMMSToSMS=Yes [2Way-Keywords] Keyword1=*##+19733901090 Keyword2=* [SMPP - 3.224.76.201:2775] RouteName=bandwidth.com SMPPVersion=v3.4 SenderAddressOverride=Yes Receive=Yes ReceiveMMS=Yes UseSSL=No LongSMSAlt=Yes MMSURL=custmm4-1.messaging.bandwidth.com UseDial=No UserName=5000107 Password=dKZJ4rPQ ReceiveSingleConnection=Yes [Inbound SMS Routing] [2Way-Keyword-*##+19733901090] MailTo=john@xaccel.net [2Way-Keyword-*] Run=https://share01.xbabble.com/sms-bridge/inbound.php?sender=@@SENDER@@&text=@@FULLSMS@@&receiver=@@RECIP@@ | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8615 Registered: 10-2002 |
Hi John, I replied to your e-mail submission to our website several days ago, but there was a problem with your return e-mail address. I don’t think the problem is in the configuration on your end, it's the other side. The problem is that the inbound MM4/SMTP message is addressed to +19733901090/TYPE=PLMN@null And based on your config, we’re expecting +19733901090/TYPE=PLMN@mms.messaging.bandwidth.com If you’re unable to get this fixed on the other end , you should be able to get this working by editing MMSC.INI and under the [MMSC] header adding DomainNameAlias1=null Regards, Bryce Norwood NowSMS Support | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8616 Registered: 10-2002 |
Do you have any MM4 connections defined in NowSMS? If not, then the software doesn't know that this is an MM4 message being received from a provider. Specifically, you need to define one or more "MMSC VASP" accounts. In the Windows version of the software, you need to define an "MMSC VASP" account for each source IP address that your provider (Bandwidth) can possibly use. Enter the IP address as the "Account Name", leave the "Password" and "IP Address Restrictions" blank. The following settings are what I expect to be required:  Assuming that you are sending MMS via Bandwidth, you would define an "MMSC Routing" for that. Once an "MMSC Routing" is defined, go back and edit any "MMSC VASP" accounts to set the "MM4 Ack Route" to point to the outbound route so that the software understands that the accounts are related. Setting the "MMSC Routing for Received Messages" to "Receive to MMS-IN Directory" means that any messages received on this account will be routed to the 2-way command processing. | |||
