| MM4 problems |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | ||||
| Bryan English New member Username: Fbc_admin Post Number: 1 Registered: 04-2005 |
Bryce, I am attempting to use NOWSMS to forward SMTP error messages from our server monitoring software to a mobile phone as an SMS message. I have set up a VASP account, connected to NOWSMS on port 25 using putty and went through the example of sending SMTP messages in the documentation supplied with the software. The SMTP session accepts all of the authentication, rcpt, data inputs and idicates a code 250 message accepted at the end. The only problem is the message is never sent. Please see a dubug log I created whe trying the send an SMTP message. BTW the phone number was entered correctly I have just masked it for privacy.
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4408 Registered: 10-2002 |
Hi Bryan, Are you able to send other MMS messages, like from our MMS web interface? I'm wondering if the problem is specific to SMTP, or if it is more general. (I'm suspecting more general, but I'd like to be sure.) The most common problems with MM1 over GPRS MMSC connections are that when you define the "MMSC Routing", you need to verify the following settings: 1.) "Default Sender Address" should be left blank. 2.) "Allow sender address override" should NOT be checked. 3.) Make sure that the first "Login Name" and "Password" fields on the page (under "Server Address") are blank. (I can see from the log file that there are values set here, so this may be the problem.) If you've got all of those settings in place, then I'd like you to enable the MMSWAPDEBUG.LOG so that I can see what is going on at that level. -bn | ||||
| Bryan English New member Username: Fbc_admin Post Number: 2 Registered: 04-2005 |
Bryce, Many thanks for a quick response. The web interface has always worked well so that has not been an issue. I have made the changes recommended in the three points above and enabled MMSWAPDEBUG. I'm not sure if it's correct or not but my MMSCWAP.INI had no settings in it before I added the debug command, not even the [MMSCWAP] heading.
| ||||
| Bryan English New member Username: Fbc_admin Post Number: 3 Registered: 04-2005 |
Bryce, For additional info I have added a log of the smtp session i was using just in case I am making a mistake at the entry stage. Again I have masked the phone number
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4417 Registered: 10-2002 |
Bryan, I'm going to do some more investigation, but can you try sending a message with some content. I think that the lack of content is somehow confusing the MMSC. Because there was no content, we've inserted a text file that contains only a blank character. Actually, upon further examination, I'm guessing that the MMSC does not like the null subject header. If there isn't a subject, we should probably be leaving out the header. (A null value is valid, but my guess is that this particular MMSC can't handle it.) Try modifying your content to make it a valid message ... for example: From: x@x.com Subject: test <insert blank line here> test message . The "From:" header will be ignored here, so you could leave it out. -bn | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4418 Registered: 10-2002 |
Bryan, I've confirmed. The Vodafone MMSC does not like a message with a null subject header. You can work-around this problem with the following setting in MMSC.INI, under the [MMSC] header: MMSNoSubject=(none) Or insert any text that you want to appear in the subject when a message is received via SMTP with a blank or missing subject header. We're going to make a modification for the next update, so that if the subject header is blank or missing, we will not generate a subject header in the resulting MMS message, which seems to keep the Vodafone MMSC happy. -bn | ||||
| Bryan English New member Username: Fbc_admin Post Number: 4 Registered: 04-2005 |
Bryce, Thanks again for the quick response. The MMSNoSubject=(none) worked a treat. NOWSMS is an even more valuable business tool than we we first implemented it. For info, the data component is sent as clear text and doesn't require MIME encoding. Cheers for your help. | ||||
MMSC Debug log
