Sms to email reply not working

Sms to email reply not working SearchSearch
Author Message
lee vitez
New member
Username: Leevitez

Post Number: 6
Registered: 03-2011
Posted on Thursday, May 05, 2011 - 06:59 am:   

Hi,

I have configued Nowsms and successfully got working regarding the email to sms. i can send already an email message satisfyingly but i still have no success making it work the other way around, replying back to the original email address. here is my configuration, picture below:

2waysettng

i followed the thread from here:
http://www.nowsms.com/doc/2-way-sms-support

i also checked this troubleshooting guide,
http://support.nowsms.com/discus/messages/1/4520.html

Maybe i have something missing?


Another Issue:

Is it also possible for Nowsms to insert automatically a message in order for the mobile sms user to know thereby instructing him what he should do when replying to the email sender?

For example, typically my message is:

"hello, how are you? this is Lee. Please reply."

When the recipient reads the sms, there is a note for example just like this:

"To reply back, pls type the email adress before ur message."


Is this possible? If yes, how would i edit it?

Thank you for your time,

Lee
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3148
Registered: 08-2008
Posted on Thursday, May 05, 2011 - 09:22 pm:   

Hi Lee,

Questions about SMS to email functionality always leave me a little bit frustrated. At issue is the problem of directing am SMS reply back to the email sender.

Mobile operator gateways (primarily in the US only), solve this dilemma by allocating a range of short code or phone numbers to the email gateway. Each time an email sender sends to an SMS number, a new number is taken from the allocation, so that the system can associate that number with an email address in order to support replies being routed back to the correct email address.

We are currently working to build that support into a future version of NowSMS. Of course, it will be a bit limited if you only have a single SMS sender address, as we can only remember the last email sender to send to a particular number, and any SMS to email replies would get routed back to the last email sender to send to that particular number.

Until then, the only solutions is to get the SMS side to start the reply with an email address.

There is no way to include instructions in the outgoing message. But if you change the SMS command prefix for the mailto: command to *, the system will send back a reply with some more info about how an email address is required to start the message.

Or, you can add a new command using *as the prefix. This command would be triggered if the keyword does not contain @. And you could have that command return other information.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3149
Registered: 08-2008
Posted on Thursday, May 05, 2011 - 09:25 pm:   

Just had another thought. Are you saying the reply to email is not working even when the SMS starts with a valid email address? If so, enable the SMSDEBUG.LOG and MMSCDEBUG.LOG and let's take a look at those. I expect the messages are making it to the MMSCOUT directory which is the outbound mail queue, in which case we'd want to look at MMSCDEBUG.LOG to see what is going on.
lee vitez
New member
Username: Leevitez

Post Number: 7
Registered: 03-2011
Posted on Saturday, May 07, 2011 - 04:16 am:   

Hi Des,
(Just had another thought. Are you saying the reply to email is not working even when the SMS starts with a valid email address?)
Thank you for the quick respond. Yes, you got my point. i can't recieve a reply back to email despite of valid email address b4 my message. I enabled the SMSDEBUG.LOG and MMSCDEBUG.LOG and here what it says:

17:45:47:146 [0] UseRouteCache: No
17:45:49:190 [0] main: Now SMS/MMS Gateway v2011.03.21 Web server started on port number 8800
17:45:49:206 [3] ThreadProcessModem: HUAWEI Mobile Connect - 3G Modem
17:45:49:206 [3] ThreadProcessModem: Before ModemAllocate - HUAWEI Mobile Connect - 3G Modem
17:45:49:206 [3] ThreadProcessModem: After ModemAllocate - HUAWEI Mobile Connect - 3G Modem - OK
17:45:49:206 [3] ThreadProcessModem: Re-initializing modem: HUAWEI Mobile Connect - 3G Modem ...
17:45:49:408 [3] ThreadProcessModem: ATI0
17:45:49:408 [3] ThreadProcessModem:
Manufacturer: huawei
Model: E220
Revision: 11.117.10.03.99
IMEI: 354137020891075
+GCAP: +CGSM,+FCLASS,+DS

OK

17:45:49:455 [3] ModemTest: HUAWEI Mobile Connect - 3G Modem
17:45:49:533 [3] ModemTest: OK
17:45:49:533 [3] ThreadProcessModem: AT+CPMS?
17:45:49:549 [3] ThreadProcessModem:
+CPMS: "ME",0,255,"SM",0,30,"SM",0,30

OK

17:45:49:549 [3] ThreadProcessModem: AT+CNMI=2,2,2,1,0
17:45:49:564 [3] ThreadProcessModem:
+CMS ERROR: 303

17:45:49:564 [3] ThreadProcessModem: AT+CNMI=2,2
17:45:49:580 [3] ThreadProcessModem:
+CMS ERROR: 303

17:45:49:580 [3] ThreadProcessModem: AT+CNMI=2
17:45:49:596 [3] ThreadProcessModem:
+CMS ERROR: 303

17:45:49:596 [3] ThreadProcessModem: AT+CNMI?
17:45:49:611 [3] ThreadProcessModem:
+CNMI: 2,0,0,2,0

OK

17:45:49:611 [3] ThreadProcessModem: AT+CNMI=2,1
17:45:49:627 [3] ThreadProcessModem:
OK

17:45:49:627 [3] ThreadProcessModem: AT+CNMI?
17:45:49:642 [3] ThreadProcessModem:
+CNMI: 2,1,0,2,0

OK

17:45:49:642 [3] ThreadProcessModem: AT+CNMI=2,1,0,1
17:45:49:658 [3] ThreadProcessModem:
+CMS ERROR: 303

17:45:49:658 [3] ThreadProcessModem: AT+CNMI=2,1,0,2
17:45:49:674 [3] ThreadProcessModem:
OK

17:45:49:674 [3] ThreadProcessModem: AT+CPMS=?
17:45:49:689 [3] ThreadProcessModem:
+CPMS: ("ME","MT","SM","SR"),("ME","MT","SM","SR"),("ME","MT","SM","SR")

OK

17:45:49:689 [3] ThreadProcessModem: AT+CPMS="SM","SM","SM"
17:45:49:705 [3] ThreadProcessModem:
+CPMS: 0,30,0,30,0,30

OK

17:45:49:705 [3] ThreadProcessModem: AT+CPMS?
17:45:49:720 [3] ThreadProcessModem:
+CPMS: "SM",0,30,"SM",0,30,"SM",0,30

OK

17:45:49:736 [3] ThreadProcessModem: AT+CNMI?
17:45:49:752 [3] ThreadProcessModem:
+CNMI: 2,1,0,2,0

OK

17:45:49:752 [3] ThreadProcessModem: AT+CNMI=?
17:45:49:767 [3] ThreadProcessModem:
+CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1)

OK

17:45:49:767 [3] ThreadProcessModem: AT+COPS?
17:45:49:783 [3] ThreadProcessModem:
+COPS: 0,2,"51505",0

OK

17:45:49:783 [3] ThreadProcessModem: AT+CSQ
17:45:49:798 [3] ThreadProcessModem:
+CSQ: 24,99

OK

17:45:49:798 [3] ThreadProcessModem: AT+CNUM
17:45:49:814 [3] ThreadProcessModem:
OK

17:45:49:814 [3] ThreadProcessModem: Modem initialization complete: HUAWEI Mobile Connect - 3G

Modem
17:47:33:164 [3] ModemReceiveMessages: AT+CPMS?
17:47:33:164 [3] ModemReceiveMessages:
+CPMS: "ME",0,255,"SM",1,30,"SM",1,30

OK

17:47:33:289 [3] ModemReceiveMessages:
+CMGL: 0,0,,44
0791362902005110040C913629525936390000115060717423231C6C78999D1E87DD65C0B91D4EB3 5DE3771B242FC3D979

50BB0C

OK

17:47:33:289 [3] ModemReceiveMessages: Decoding received message index 0 from message storage SM
17:47:33:289 [3] ModemReceiveMessages:

0791362902005110040C913629525936390000115060717423231C6C78999D1E87DD65C0B91D4EB3 5DE3771B242FC3D979

50BB0C
17:47:33:289 [3] ModemReceiveMessages: SMSC address len = 7
17:47:33:289 [3] ModemReceiveMessages: SMSC Address = +639220001501
17:47:33:289 [3] ModemReceiveMessages: SMS Message Type = SMS-DELIVER
17:47:33:289 [3] ModemReceiveMessages: Sender address len = 12
17:47:33:289 [3] ModemReceiveMessages: Sender Address = +639225956393
17:47:33:289 [3] ModemReceiveMessages: PID = 00
17:47:33:289 [3] ModemReceiveMessages: DCS = 00
17:47:33:289 [3] ModemReceiveMessages: Anticipated user data length = 28
17:47:33:289 [3] ModemReceiveMessages: Message = lpelicane@gmail.com reply me
17:47:33:305 [3] ModemReceiveMessages: AT+CMGD=0

17:47:33:320 [5] ThreadProcessInboundSMS: Processing 4DAFBEDF.in...
17:47:33:320 [5] GetProgramToExecute: mailto:@@SMSPREFIX@@
17:47:33:320 [5] GetProgramToExecute: mailto:lpelicane@gmail.com
17:47:33:320 [5] ThreadProcessInboundSMS: Executing mailto:lpelicane@gmail.com
17:47:33:320 [5] ThreadProcessInboundSMS: Processing complete 4DAFBEDF.in...
17:47:33:601 [3] ModemReceiveMessages:
OK

17:48:51:164 [3] ModemTest: HUAWEI Mobile Connect - 3G Modem
17:48:51:242 [3] ModemTest: OK
17:50:40:223 [1] ThreadListenForConnections: Before accept
17:50:40:223 [1] ThreadListenForConnections: After accept
17:50:40:410 [3] ThreadProcessModem: AT+CNMI=2,0
17:50:40:442 [3] ThreadProcessModem: Before ModemRelease - HUAWEI Mobile Connect - 3G Modem
17:50:40:442 [3] ThreadProcessModem: After ModemRelease - HUAWEI Mobile Connect - 3G Modem
17:50:50:357 [0] main: Shutdown: Closing log files

the strange thing i discovered, instead of recieving the reply from the email inbox, the sms reply is sent back to the mobile. i can only see a message that says "SMS ERROR:..." but i cannot
proceed to download the remaining contents of the error message.

It really gave me a hard time. i need ur help badly, my friend.
Thank you again for your time.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3160
Registered: 08-2008
Posted on Monday, May 09, 2011 - 02:52 pm:   

Hi Lee,

As I mentioned in the previous reply:


quote:

I expect the messages are making it to the MMSCOUT directory which is the outbound mail queue, in which case we'd want to look at MMSCDEBUG.LOG to see what is going on.




The information in your SMSDEBUG.LOG confirms this. So, I'd need to see MMSCDEBUG.LOG to see why the outbound e-mail is blocking.

It's either a DNS problem, or an outbound e-mail path problem.

Depending on what you're trying to accomplish, instead of configuring NowSMS as a full SMTP server, it might be easier to send out e-mails via an external e-mail account. There is a PHP script example that sends via GMail in the following thread: http://support.nowsms.com/discus/messages/1/70113.html

--
Des
NowSMS Support
lee vitez
New member
Username: Leevitez

Post Number: 9
Registered: 03-2011
Posted on Wednesday, May 11, 2011 - 03:14 am:   

Hi Des,

Thanks for your time again. Here is my MMSCDEBUG.LOG:

10:02:34:956 [1] MoveMMSCUsersFiles: Thread started
10:02:34:956 [2] MMSCMigrateUserDBThread: Thread started
10:02:34:958 [4] ThreadListenSMTPIn: Thread started
10:02:34:958 [3] ThreadListenForConnections: Thread started
10:02:36:957 [1] MoveMMSCUsersFiles: Thread ended
10:02:36:958 [0] main: Now SMS/MMS Gateway v2011.03.21 service started.
10:02:36:959 [1] ThreadRouteSMTPOut: Thread started
10:02:36:960 [1] ThreadRouteSMTPOut: MMSCOUT
10:02:36:960 [4] ThreadListenSMTPIn: Now MMSC SMTP server started on port number 25
10:02:36:960 [5] ThreadRouteSMTPIn: Thread started
10:02:36:960 [7] ThreadProcessIPNotifyQ: Thread started
10:02:36:961 [10] ThreadRouteSMTPOut: Thread started
10:02:36:960 [3] ThreadListenForConnections: Now MMSC server started on port number 8080
10:02:36:961 [10] ThreadRouteSMTPOut: MMSCACK
10:02:36:960 [9] ThreadListenPOP3In: Thread started
10:02:36:960 [6] ThreadStartVASPQ: Thread started
10:02:36:960 [8] ThreadRecombineSARMessages: Thread started
10:02:36:961 [9] ThreadListenPOP3In: Now MMSC POP3 server started on port number 110
10:02:36:961 [2] MMSCMigrateUserDBThread: Thread ended
10:08:26:106 [2] ThreadProcessConnection: Thread started
10:08:26:106 [2] ThreadProcessConnectionSMTP: Processing SMTP connection from 180.192.13.14...
10:08:26:107 [2] SendCommand: 220 SMTP Ready
10:08:26:107 [2] ThreadProcessConnectionSMTP: 220 SMTP Ready
10:08:29:028 [2] ThreadProcessConnectionSMTP: quit
10:08:29:028 [2] SendCommand: 221 Goodbye
10:08:29:028 [2] ThreadProcessConnectionSMTP: 221 Goodbye
10:08:29:029 [2] ThreadProcessConnectionSMTP: Closing SMTP Connection
10:08:29:029 [2] ThreadProcessConnection: Thread ended
10:08:46:865 [2] ThreadProcessConnectionPOP3: Thread started
10:08:46:865 [2] ThreadProcessConnectionPOP3: Processing POP3 connection from 180.192.13.14...
10:08:46:866 [2] SendCommand: +OK POP3 Server Ready <AB53E1DD.4DC8901E@txtport.me>
10:08:46:866 [2] ThreadProcessConnectionPOP3: +OK POP3 Server Ready

<AB53E1DD.4DC8901E@txtport.me>
10:08:53:953 [2] WaitForResponsePOP3: ioctlsocket reports no more data
10:08:53:954 [2] ThreadProcessConnectionPOP3: Closing POP3 Connection
10:08:53:954 [2] ThreadProcessConnectionPOP3: Thread ended
10:10:23:170 [2] ThreadProcessConnection: Thread started
10:10:23:170 [2] ThreadProcessConnectionSMTP: Processing SMTP connection from 209.85.212.170...
10:10:23:170 [2] SendCommand: 220 SMTP Ready
10:10:23:170 [2] ThreadProcessConnectionSMTP: 220 SMTP Ready
10:10:23:406 [2] ThreadProcessConnectionSMTP: EHLO mail-px0-f170.google.com
10:10:23:406 [2] SendCommand: 250-Ok
250-AUTH LOGIN
250 HELP
10:10:23:406 [2] ThreadProcessConnectionSMTP: 250-Ok
250-AUTH LOGIN
250 HELP
10:10:23:645 [2] ThreadProcessConnectionSMTP: MAIL FROM:<lpelicane@gmail.com>
10:10:23:645 [2] SendCommand: 250 Ok
10:10:23:645 [2] ThreadProcessConnectionSMTP: 250 Ok
10:10:23:895 [2] ThreadProcessConnectionSMTP: RCPT TO:<09225956393@sms.txtport.me>
10:10:23:900 [2] SendCommand: 250 Ok
10:10:23:900 [2] ThreadProcessConnectionSMTP: 250 Ok
10:10:24:164 [2] ThreadProcessConnectionSMTP: DATA
10:10:24:165 [2] SendCommand: 354 Ok, end with "." on a new line...
10:10:24:165 [2] ThreadProcessConnectionSMTP: 354 Ok, end with "." on a new line...
10:10:24:520 [2] ThreadProcessConnectionSMTP: Message received 1722 bytes ... processing ...
10:10:24:523 [2] SendCommand: 250 Message Accepted
10:10:24:523 [2] ThreadProcessConnectionSMTP: Received: by pxi19 with SMTP id 19so4016674pxi.29
for <09225956393@sms.txtport.me>; Mon, 09 May 2011 19:10:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:date:from:x-priority:message-id:to:subject
:mime-version:content-type:content-transfer-encoding;
bh=zS7KNTV0HyeorkDDGwxB1AV6enuRKzO5rthkhdHIRnY=;
b=lx0TPKkYtNFF1NMkqAzZHfPltL0N+Zq4l9Z4YSc5GnvT9DB4zaK9FsN4KKmpNSFEEd
rkkDpn6WMyKi145u91C2FhrdcfMVr2ecuDP5URI5PuCRnIgbaW6LyOIBeWmANNEfhuKJ
ZiPeHaVKBW9XdsGLq2127wkuRYg1pw1E7tqS0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=date:from:x-priority:message-id:to:subject:mime-version
:content-type:content-transfer-encoding;
b=q7htMTVA23ex95WsLxLqukLsoKvYeKzESj5b22C/7yDTo0uQYIzDO3JFzHi7Q5LbKj
gBa/qjb5PNkrJEI2QrVLMJ45dH99FhG+eZJfzz8AHdfK0JKCFnYcNcHupoJv9pVBvrcO
SIxc27abpLWkAP7wQbFHD8sR4rp2BVMyNISjM=
Received: by 10.68.48.3 with SMTP id h3mr10951953pbn.505.1304993428689;
Mon, 09 May 2011 19:10:28 -0700 (PDT)
Return-Path: <lpelicane@gmail.com>
Received: from [180.192.13.14] ([180.192.13.14])
by mx.google.com with ESMTPS id k7sm4480382pbe.32.2011.05.09.19.10.22
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 09 May 2011 19:10:26 -0700 (PDT)
Date: Tue, 10 May 2011 10:10:11 +0800
From: lpelicane <lpelicane@gmail.com>
X-Priority: 3 (Normal)
Message-ID: <1955184830.20110510101011@gmail.com>
To: 09225956393@sms.txtport.me
Subject: test nowsms
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable

hello

10:10:24:524 [2] ThreadProcessConnectionSMTP: 250 Message Accepted
10:10:24:988 [5] ThreadRouteSMTPIn: 244C5E5C.RFC
10:10:24:988 [5] ThreadRouteSMTPIn: X-MMSC-RCPT-TO: SMS:09225956393
10:10:24:988 [5] ThreadRouteSMTPIn: X-MMSC-Received-From: 209.85.212.170
10:10:24:988 [5] ThreadRouteSMTPIn: X-MMSC-ENV-MAIL-FROM: <lpelicane@gmail.com>
10:10:24:988 [5] ThreadRouteSMTPIn: From: lpelicane <lpelicane@gmail.com>
10:10:24:988 [5] ThreadRouteSMTPIn: To: 09225956393@sms.txtport.me
10:10:24:989 [5] ThreadRouteSMTPIn: Subject: test nowsms
10:10:24:989 [5] ThreadRouteSMTPIn: Content-Type: text/plain; charset=iso-8859-15
10:10:24:991 [5] ThreadRouteSMTPIn: charset=
10:10:24:991 [5] ThreadRouteSMTPIn: iso-8859-15
10:10:54:835 [2] ThreadProcessConnectionSMTP: QUIT
10:10:54:835 [2] SendCommand: 221 Goodbye
10:10:54:835 [2] ThreadProcessConnectionSMTP: 221 Goodbye
10:10:54:835 [2] ThreadProcessConnectionSMTP: Closing SMTP Connection
10:10:54:835 [2] ThreadProcessConnection: Thread ended
11:45:02:278 [2] ThreadProcessConnection: Thread started
11:45:02:279 [2] ThreadProcessConnectionSMTP: Processing SMTP connection from 180.192.13.14...
11:45:02:279 [2] SendCommand: 220 SMTP Ready
11:45:02:279 [2] ThreadProcessConnectionSMTP: 220 SMTP Ready
11:45:07:348 [2] ThreadProcessConnectionSMTP: qy
11:45:07:348 [2] SendCommand: 500 Unknown command
11:45:07:348 [2] ThreadProcessConnectionSMTP: 500 Unknown command
11:45:10:273 [2] WaitForResponsePOP3: ioctlsocket reports no more data
11:45:10:274 [2] ThreadProcessConnectionSMTP: Closing SMTP Connection
11:45:10:274 [2] ThreadProcessConnection: Thread ended
11:48:22:319 [2] ThreadProcessConnection: Thread started
11:48:22:319 [2] ThreadProcessConnectionSMTP: Processing SMTP connection from 209.85.214.42...
11:48:22:319 [2] SendCommand: 220 SMTP Ready
11:48:22:319 [2] ThreadProcessConnectionSMTP: 220 SMTP Ready
11:48:22:704 [2] ThreadProcessConnectionSMTP: EHLO mail-bw0-f42.google.com
11:48:22:704 [2] SendCommand: 250-Ok
250-AUTH LOGIN
250 HELP
11:48:22:704 [2] ThreadProcessConnectionSMTP: 250-Ok
250-AUTH LOGIN
250 HELP
11:48:23:112 [2] ThreadProcessConnectionSMTP: MAIL FROM:<lpelicane@gmail.com>
11:48:23:112 [2] SendCommand: 250 Ok
11:48:23:112 [2] ThreadProcessConnectionSMTP: 250 Ok
11:48:23:494 [2] ThreadProcessConnectionSMTP: RCPT TO:<09225956393@sms.txtport.me>
11:48:23:499 [2] SendCommand: 250 Ok
11:48:23:499 [2] ThreadProcessConnectionSMTP: 250 Ok
11:48:24:862 [2] ThreadProcessConnectionSMTP: DATA
11:48:24:863 [2] SendCommand: 354 Ok, end with "." on a new line...
11:48:24:863 [2] ThreadProcessConnectionSMTP: 354 Ok, end with "." on a new line...
11:48:28:523 [2] ThreadProcessConnectionSMTP: Message received 1683 bytes ... processing ...
11:48:28:525 [2] SendCommand: 250 Message Accepted
11:48:28:525 [2] ThreadProcessConnectionSMTP: Received: by bwz18 with SMTP id 18so5258236bwz.29
for <09225956393@sms.txtport.me>; Mon, 09 May 2011 20:48:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:date:message-id:subject:from:to
:content-type;
bh=ogkq12czqnQwZoL/RLhoKJGRWg2zcrcjXwTUEyj1DsY=;
b=OhFseIv8RwAnIxPlGj+k0xRwe19+FaqCWAiJJTKcYuKIMWFRJMXJ/0h3PG1HW3orXn
UwiMWl5ucZiti4p8kmI3gxilNxOq5DGXmlTy4vdBVNR8L0xjM2seD5vQIHA8iIUdpBwS
toKSaZ8nzYWQRz2IR7e0Iwvpgf4q7jIQdVeE0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:date:message-id:subject:from:to:content-type;
b=Owc+6yWKPUhbqA7pD9PrQlIb0T6blgAFaqMiKJc1QEgFj47vN4siahn0LLg5Aq55aG
f94fPHMLf5lhckZVDPq93Y9zKnrwyp+1bv8QSq57svcLCRTqo2/WeAMNpMB5lHbLusdn
3L5zcxe2Jh9qlDKGqQjx9BjrWGMkl9eMig8aQ=
MIME-Version: 1.0
Received: by 10.204.126.144 with SMTP id c16mr923633bks.6.1304999304309; Mon,
09 May 2011 20:48:24 -0700 (PDT)
Received: by 10.204.5.198 with HTTP; Mon, 9 May 2011 20:48:24 -0700 (PDT)
Date: Tue, 10 May 2011 11:48:24 +0800
Message-ID: <BANLkTik+O4qAMKWqJZgzzXfcO8fs9MVfxQ@mail.gmail.com>
Subject: test now2
From: Leonie Pelicane <lpelicane@gmail.com>
To: 09225956393@sms.txtport.me
Content-Type: multipart/alternative; boundary=0016e6daa892f72a6604a2e3d3a9

--0016e6daa892f72a6604a2e3d3a9
Content-Type: text/plain; charset=ISO-8859-1

hello milx

--0016e6daa892f72a6604a2e3d3a9
Content-Type: text/html; charset=ISO-8859-1

<div class="gmail_quote">hello milx<br><br></div><br>

--0016e6daa892f72a6604a2e3d3a9--
11:48:28:527 [2] ThreadProcessConnectionSMTP: 250 Message Accepted
11:48:29:372 [5] ThreadRouteSMTPIn: B9853459.RFC
11:48:29:372 [5] ThreadRouteSMTPIn: X-MMSC-RCPT-TO: SMS:09225956393
11:48:29:372 [5] ThreadRouteSMTPIn: X-MMSC-Received-From: 209.85.214.42
11:48:29:372 [5] ThreadRouteSMTPIn: X-MMSC-ENV-MAIL-FROM: <lpelicane@gmail.com>
11:48:29:372 [5] ThreadRouteSMTPIn: Subject: test now2
11:48:29:372 [5] ThreadRouteSMTPIn: From: Leonie Pelicane <lpelicane@gmail.com>
11:48:29:372 [5] ThreadRouteSMTPIn: To: 09225956393@sms.txtport.me
11:48:29:373 [5] ThreadRouteSMTPIn: Content-Type: multipart/alternative;

boundary=0016e6daa892f72a6604a2e3d3a9
11:48:29:381 [5] ParseAttachmentsFromInboundMessage: Skipping , content type text/html
11:48:58:879 [2] ThreadProcessConnectionSMTP: QUIT
11:48:58:880 [2] SendCommand: 221 Goodbye
11:48:58:880 [2] ThreadProcessConnectionSMTP: 221 Goodbye
11:48:58:880 [2] ThreadProcessConnectionSMTP: Closing SMTP Connection
11:48:58:880 [2] ThreadProcessConnection: Thread ended
12:03:26:021 [1] QueryMXRecord: Querying host 202.138.128.54 for MX record of gmail.com
12:03:26:029 [1] QueryMXRecord: MX Result for gmail.com: gmail-smtp-in.l.google.com 5
12:03:26:029 [1] QueryMXRecord: MX Result for gmail.com: alt1.gmail-smtp-in.l.google.com 10
12:03:26:029 [1] QueryMXRecord: MX Result for gmail.com: alt2.gmail-smtp-in.l.google.com 20
12:03:26:029 [1] QueryMXRecord: MX Result for gmail.com: alt3.gmail-smtp-in.l.google.com 30
12:03:26:030 [1] QueryMXRecord: MX Result for gmail.com: alt4.gmail-smtp-in.l.google.com 40
12:03:26:373 [1] InetServerConnect: Connected to gmail-smtp-in.l.google.com (74.125.155.27:25)
12:03:26:571 [1] ThreadRouteSMTPOut: 220 mx.google.com ESMTP w1si21716134pbh.199

12:03:26:572 [1] ThreadRouteSMTPOut: HELO txtport.me
12:03:26:572 [1] SendCommand: HELO txtport.me
12:03:26:784 [1] ThreadRouteSMTPOut: 250 mx.google.com at your service

12:03:26:784 [1] ThreadRouteSMTPOut: MAIL FROM:<+639225956393@sms.txtport.me>
12:03:26:784 [1] SendCommand: MAIL FROM:<+639225956393@sms.txtport.me>
12:03:26:998 [1] ThreadRouteSMTPOut: 250 2.1.0 OK w1si21716134pbh.199

12:03:26:998 [1] ThreadRouteSMTPOut: RCPT TO:<lpelicane@gmail.com>
12:03:26:998 [1] SendCommand: RCPT TO:<lpelicane@gmail.com>
12:03:27:779 [1] ThreadRouteSMTPOut: 250 2.1.5 OK w1si21716134pbh.199

12:03:27:779 [1] ThreadRouteSMTPOut: DATA
12:03:27:779 [1] SendCommand: DATA
12:03:27:969 [1] ThreadRouteSMTPOut: 354 Go ahead w1si21716134pbh.199

12:03:27:970 [1] ThreadRouteSMTPOut: .
12:03:27:970 [1] SendCommand:
.
12:03:29:829 [1] ThreadRouteSMTPOut: 250 2.0.0 OK 1305000215 w1si21716134pbh.199

12:03:29:829 [1] ThreadRouteSMTPOut: QUIT
12:03:29:830 [1] SendCommand: QUIT
12:03:30:019 [1] ThreadRouteSMTPOut: 221 2.0.0 closing connection w1si21716134pbh.199

__

Quote:
"Depending on what you're trying to accomplish, instead of configuring NowSMS as a full SMTP server, it might be easier to send out e-mails via an external e-mail account."

As per your suggestion, i'm working on the thread you reffered: http://support.nowsms.com/discuss/messages/1/70113.html.
And in reference of http://www.nowsms.com/now-sms-native-php-scripts, i followed all the directions as well as the installation of PHP, PEAR and the PEAR Mail package. But there appear another problem. With the suggested update of nowsms, (http://www.nowsms.com/download/nowsms20110419.zip), i got an error message that says nowsms can't find the php-cgi.exe, although i installed it inside nowsms folder C:\Program Files (x86)\NowSMS\PHP). and the update version is not adding a new MMSC user, just nothing after i had input data on it.

so, how do i proceed from here? Looking forward for your reply. Thnx.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3167
Registered: 08-2008
Posted on Wednesday, May 11, 2011 - 07:27 pm:   

Hi Lee,

The message certainly seems to be getting sent out. Maybe its in a spam folder on GMail?

Regarding PHP, did you install the full PHP under the NowSMS directory structure? Normally you would just place the scripts you create there, and install PHP in its own location. NowSMS searches the PATH environment variable to find php-cgi.exe. The PHP installer should set this up automatically.

Regarding the problem adding users, we did recently find a caching problem with the display of this list, especially when there are just a handful of users. Exiting and restarting should fix the display. This was fixed in the update at http://www.nowsms.com/download/nowsms20110509.zip

--
Des
NowSMS Support
lee vitez
New member
Username: Leevitez

Post Number: 10
Registered: 03-2011
Posted on Friday, May 13, 2011 - 01:52 pm:   

Hi Des,

What a stupid am i, haha. Yeah. i didn't even think of the spam folder. I went to my gmail spam folder and your right. Well, im happy now that i got nowsms working.

Quote:
"...did you install the full PHP under the NowSMS directory structure?"

As i mentioned,i have it installed inside nowsms folder C:\Program Files(x86)\NowSMS\PHP). So, you mean that i should install the PHP outside the Nowsms folder?

Thank you also for information and the updates of the program.

Again, thank you very much for the time and effort you spent working this out.

__

Lee
lee vitez
New member
Username: Leevitez

Post Number: 11
Registered: 03-2011
Posted on Saturday, May 14, 2011 - 05:28 am:   

Hi Des,

I have updated nowsms to 2011.05.09, the one you sent me, but it still do not display the added users at the MMSC tab. No matter how many times did i enter the data and the times i went exiting and opening the application, it just display nothing.

No problem with the SMS Users Tab, only the MMSC. Picture below:

MMSC tab

I need ur help again, pls...
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3172
Registered: 08-2008
Posted on Saturday, May 14, 2011 - 04:41 pm:   

Hi Lee,

Let PHP install itself in it's default location. Chances are that it's installer does not set the configuration up properly when it is in a different location.

I am puzzled by the MMSC Users problem. I can tell you that these accounts are stored in a file named MMSCUSERS.DB. I can only conclude that something is wrong with that file. Normally this file is in the ProgramData\NowSMS directory. I hate to delete it and recreate it, but since I do not expect you have any users in it, that may be the quickest solution.

--
Des
NowSMS Support
lee vitez
New member
Username: Leevitez

Post Number: 12
Registered: 03-2011
Posted on Sunday, May 15, 2011 - 09:56 am:   

Hi Des,

Thanks again for the support. I just uninstalled the nowsms, then reinstalled it, voila...then it works fine already.

Merci!

--

Lee