Morris Hansen Posted December 28, 2012 Posted December 28, 2012 I have been migrating my notifications from Elk over to the ISY. Everything for the most part is working great. One item I can't seem to figure out is why I am not able to actually send an email to my cell number@mms.att.net. It works fine to @txt.att.net. Using my email client, I can send just fine to the mms address. The reason I want to use mms.att.net is to get rid of the annoying sequential numbers that show up on text messages to @txt.att.net. If I use MMS, the messages show up as my email address which I can then assign different ring tones to. I can't seem to find where I have anything wrong. I am only changing the destination email address and it goes from working to not working with no errors. Any ideas?
Michel Kohanim Posted December 28, 2012 Posted December 28, 2012 Hi mohansen, It should work! Have you tried sending one directly from your mail client? If so, do you get it? Also, please try mms and then check Error Log and look for -50000 errors. Let me know if you see any and, if so, please copy/paste here. With kind regards, Michel
Morris Hansen Posted December 28, 2012 Author Posted December 28, 2012 I forgot to add that if I test the notification from the Configuration,Emails/Notifications,Settings/Groups tab, it works great. It only fails if I do a test my THEN part of a program. If I change the email address to txt.att.net, my program tests just fine. I am able to send emails just fine to mms.att.net from the same email account I am using on the ISY as well as other email accounts. I am not getting any errors on the screen or in the error log. There is only one line in my THEN statement and that is Send Notification to 'Cell' content 'Driveway Incoming'
Michel Kohanim Posted December 28, 2012 Posted December 28, 2012 Hi mohansen, 1. Can you remove the customized content and let me know if you get the mms message? I suspect there's something in the customization that mms does not like 2. Do you see any errors in the Error Log? With kind regards, Michel
paulw Posted December 28, 2012 Posted December 28, 2012 I have seen similar issues when the body is left blank. Adding anything to the body resolved it for me.
biredale Posted December 28, 2012 Posted December 28, 2012 Same.. Will not work with a blank body. Thanks! Brian
Morris Hansen Posted December 29, 2012 Author Posted December 29, 2012 Appreciate the help. I have a Subject of 'Driveway Activity' and the body is 'Vehicle entering the driveway at ${sys.time12} on ${sys.date}' all formatted as text. I changed the body to be Hello and still did not get any message. Also tried the HTML format. I tried a different customization message and it did not work either. So I then tried a message with content of Default and that worked. So it has something to do with the customization. I am not seeing any error's in the error log.
Michel Kohanim Posted December 30, 2012 Posted December 30, 2012 Hi mohansen, In all likelihood, the header is evaluating to empty. Try a static header with customized body please. With kind regards, Michel
Morris Hansen Posted December 30, 2012 Author Posted December 30, 2012 Not sure what you mean by static header. Are you referring to the Subject? I have tried both leaving the subject blank and putting something in there. Here is what my customization looks like.
Morris Hansen Posted December 30, 2012 Author Posted December 30, 2012 I was able to get a message to work through mms.att.net If I put the default subject (which is the program name), this works sort of. I get the default header information but none of the message body comes through. Here is what I got to work but again the body did not get sent.
Michel Kohanim Posted December 31, 2012 Posted December 31, 2012 Hi mohansen, Can you please send the same message to sms, mms, and email (create a group with all three)? With kind regards, Michel
Morris Hansen Posted December 31, 2012 Author Posted December 31, 2012 I sent the same message that worked yesterday. (ie. default subject of program name and customized body). I received a message at txt.att.net and email but did not get any message to mms.att.net. Both of the received messages did have the customized body. So to be sure of my testing yesterday, I did another test directly to mms.att.net by itself. The same message that I used yesterday did not work today. I created another similar custom notification and it did not work either. I may have just gotten lucky yesterday. I can still send test messages to mms.att.net. Nothing with any content seems to work today.
Michel Kohanim Posted December 31, 2012 Posted December 31, 2012 Hi mohansen, This is extremely odd. Can you tell me whether or not you have setup SMTP server settings? It's possible that AT&T does not like the SMTP (from server). With kind regards, Michel
Morris Hansen Posted December 31, 2012 Author Posted December 31, 2012 Michel, I do have my own SMTP server setup. The same one I have configured in Outlook. I have tried another email account though it is on the same domain with the same SMTP server. Same results. I switched to the default SMTP server and it acted the same. All testing shows that I get messages to @txt.att.net and my email address but nothing other than the test message will go to @mms.att.net I also sent a message from Outlook using the same smtp account and I was able to send a message to @mms.att.net without any issues.
Michel Kohanim Posted January 1, 2013 Posted January 1, 2013 mohansen, I just sent a few different messages with customized contents to vzwpix.com (mms for Verizon) and they all worked properly and instantaneously. Unfortunately I really do not know what else to suggest especially if you do not see any errors in your error log. With kind regards, Michel
Morris Hansen Posted January 1, 2013 Author Posted January 1, 2013 I appreciate the support. Without seeing the actual traffic between the ISY and the SMTP server, it may be tough to figure out. What is so odd is that the test email's work, just nothing from a program or with non-default content. Here is my error log for the last couple of days. I didn't see any of the error number (50000) you indicated before. Do any of these make sense? Sun 2012/12/30 08:48:51 AM System -5012 49 Sun 2012/12/30 09:17:47 AM System -110022 /CONF/MAIL/5.NTC Sun 2012/12/30 09:17:47 AM System -110012 /CONF/MAIL/5.NTC Sun 2012/12/30 09:19:36 AM System -110022 /CONF/MAIL/5.NTC Sun 2012/12/30 09:19:36 AM System -110012 /CONF/MAIL/5.NTC Sun 2012/12/30 11:03:31 AM System -140005 CLI-WBug Sun 2012/12/30 08:55:31 PM System -140005 CLI-WBug Sun 2012/12/30 09:05:32 PM System -140005 CLI-WBug Sun 2012/12/30 09:25:31 PM System -140005 CLI-WBug Sun 2012/12/30 10:05:33 PM System -170001 [uDSockets] RSub:27 error:6 Sun 2012/12/30 10:05:38 PM System -5012 50 Mon 2012/12/31 10:00:12 AM System -60006 n/a Mon 2012/12/31 10:36:49 AM System -50001 -19 Mon 2012/12/31 10:55:26 AM System -140005 CLI-WBug Mon 2012/12/31 10:57:26 AM System -140005 CLI-WBug Mon 2012/12/31 10:59:26 AM System -140005 CLI-WBug Mon 2012/12/31 11:01:27 AM System -140005 CLI-WBug Mon 2012/12/31 11:03:27 AM System -140005 CLI-WBug Mon 2012/12/31 11:05:26 AM System -140005 CLI-WBug Mon 2012/12/31 12:03:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:23:27 PM System -140005 CLI-WBug Mon 2012/12/31 02:25:27 PM System -140005 CLI-WBug Mon 2012/12/31 02:27:27 PM System -140005 CLI-WBug Mon 2012/12/31 02:29:27 PM System -140005 CLI-WBug Mon 2012/12/31 02:31:27 PM System -140005 CLI-WBug Mon 2012/12/31 02:33:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:35:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:37:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:39:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:41:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:43:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:45:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:47:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:49:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:51:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:53:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:55:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:57:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:59:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:01:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:03:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:05:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:07:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:09:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:11:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:13:25 PM System -140005 CLI-WBug Mon 2012/12/31 03:15:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:17:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:19:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:21:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:23:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:25:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:27:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:29:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:31:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:33:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:35:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:37:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:39:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:41:29 PM System -140005 CLI-WBug Mon 2012/12/31 03:43:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:45:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:47:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:49:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:51:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:53:25 PM System -140005 CLI-WBug Mon 2012/12/31 03:55:25 PM System -140005 CLI-WBug Mon 2012/12/31 03:57:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:59:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:01:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:03:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:05:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:07:29 PM System -140005 CLI-WBug Mon 2012/12/31 04:09:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:11:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:13:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:15:26 PM System -170001 [TCP-Conn] -1/-140002, CLI-WBug Mon 2012/12/31 04:17:29 PM System -140005 CLI-WBug Mon 2012/12/31 04:19:27 PM System -140005 CLI-WBug Mon 2012/12/31 04:21:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:21:48 PM System -5012 51 Mon 2012/12/31 04:28:53 PM System -50001 -19 Mon 2012/12/31 05:30:36 PM System -50001 -14
Morris Hansen Posted January 1, 2013 Author Posted January 1, 2013 I setup a packet capture. Hopefully this will help. The first section below is when a test message is sent. The second section is when sending from the program. It appears the setup at the beginning is different and there is extra data (Mime-Version....) in the actual data when it doesn't work. 220 m1plsmtpa01-02.prod.mesa1.secureserver.net ESMTP EHLO [192.168.1.18] 250-m1plsmtpa01-02.prod.mesa1.secureserver.net hello [98.245.240.129], secureserver.net 250-HELP 250-AUTH LOGIN PLAIN 250-SIZE 31457280 250-PIPELINING 250-8BITMIME 250 OK AUTH PLAIN 334 AHNlY3VyaXR5QDUzMzcubmV0AHYxMGplZXA= 235 ... authentication succeeded MAIL FROM: 250 sender ok RCPT TO: <10digitnumber@mms.att.net> 250 <10digitnumber@mms.att.net> recipient ok DATA 354 enter mail, end with "." on a line by itself X-Mailer: ISY Mailer v1.0 (http://www.universal-devices.com) From: Home Security To: 10digitnumber@mms.att.net Date: Mon, 31 Dec 2012 20:00:35 -0700 Subject: ISY Test 2012/12/31 20:00:34 Test message from ISY Home Automation device. . 250 iT0X1k00F2oCq5N01 mail accepted for delivery QUIT 221 m1plsmtpa01-02.prod.mesa1.secureserver.net closing connection ===================================================== 220 p3plsmtpa01-07.prod.phx3.secureserver.net ESMTP EHLO [192.168.1.18] 250-p3plsmtpa01-07.prod.phx3.secureserver.net 250-AUTH LOGIN PLAIN 250-8BITMIME 250 PIPELINING AUTH PLAIN 334 AHNlY3VyaXR5QDUzMzcubmV0AHYxMGplZXA= 235 Authentication succeeded. MAIL FROM: 250 Sender accepted. RCPT TO: <10digitnumber@mms.att.net> 250 Recipient accepted. DATA 354 End your message with a period. X-Mailer: ISY Mailer v1.0 (http://www.universal-devices.com) From: Home Security To: 10digitnumber@mms.att.net Date: Mon, 31 Dec 2012 20:55:44 -0700 Subject: Driveway Incoming Alert : Alert Mime-Version:1.0; Content-Type: text/plain; charset="utf-8"; Vehicle entering the driveway . 250 Accepted message qp 5088 bytes 440 QUIT 221 Good bye.
Michel Kohanim Posted January 1, 2013 Posted January 1, 2013 Hello mohansen, Thank you. Quite useful! 1. The test does include mime-type since text is implicit 2. It seems that the mail server actually accepted the message ... so, at this point, I believe the problem is that the mail server is NOT forwarding to the MMS server With kind regards, Michel
Morris Hansen Posted January 1, 2013 Author Posted January 1, 2013 pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:= 14px; font-family: Calibri, sans-serif; "> v> My Name Morris@mydomain.net =div>
Michel Kohanim Posted January 1, 2013 Posted January 1, 2013 mohansen, Thanks so very much for the detailed detective work. Please try HTML in customization and let me know if that works. About the semi colon, we will look into it but I am afraid changing it will have adverse impact on other things that currently work. With kind regards, Michel
Morris Hansen Posted January 1, 2013 Author Posted January 1, 2013 Michel, I think I tried html before but just to make sure I did several more tests. I am still not able to receive anything that is not the default or test message. Morris
Michel Kohanim Posted January 1, 2013 Posted January 1, 2013 Hello mohansen, Just sent you an email with a link to firmware with ; removed. With kind regards, Michel
Morris Hansen Posted January 2, 2013 Author Posted January 2, 2013 Unfortunately that didn't fix it. This morning I enabled my emails again on the Elk and captured what it is sending to ATT. The emails from Elk work. Thanks, 220 m1plsmtpa01-06.prod.mesa1.secureserver.net ESMTP EHLO mydomain.net 250-m1plsmtpa01-06.prod.mesa1.secureserver.net hello [98.245.240.129], secureserver.net 250-HELP 250-AUTH LOGIN PLAIN 250-SIZE 31457280 250-PIPELINING 250-8BITMIME 250 OK AUTH LOGIN 334 VXNlcm5hbWU6 xxxxxxxxxxxxxxxx 334 UGFzc3dvcmQ6 xxxxxxxxx== 235 ... authentication succeeded MAIL FROM: 250 sender ok RCPT TO: <10digitnumber@mms.att.net> 250 <10digitnumber@mms.att.net> recipient ok DATA 354 enter mail, end with "." on a line by itself MIME-Version: 1.0 To: 10digitnumber@mms.att.net From: security@mydomain.net Cc: Subject: Email Alert X-Mailer: Allegro Software RomMailer /4.01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Incoming Driveway . 250 j2cZ1k0012oCq5N01 mail accepted for delivery QUIT 221 m1plsmtpa01-06.prod.mesa1.secureserver.net closing connection
Michel Kohanim Posted January 2, 2013 Posted January 2, 2013 Hi mohansen, Thank you. The only differences are: 1. Semi colons at the end of Mime-version and Content-type 2. Charset is ISO8859-1 ... I wonder why 3. Content encoding: 7 bits In short, this is basically SMS and the reason is works is the same reason that non-customized content works. So, it has to do with these headers and perhaps UTF-8 is problematic. With kind regards, Michel
Morris Hansen Posted January 2, 2013 Author Posted January 2, 2013 Finally made some progress. I simulated a SMTP client by telneting into the SMTP server and entering the commands myself. What I was able to determine is: - semi-colon after the Mime-version doesn't matter. - it does seem to matter that there cannot be a semi-colon after the charset. I tried utf and iso, both worked without a semi-colon and both failed with a semi-colon. - Mime-Version:1.0 works. The space after the colon doesn't need to be there and neither does it need to be capitalized. - Mime by itself works. Doesn't need content type - It worked without any content encoding. So it appears that AT&T doesn't like the semi-colon after the charset. At least I can recreate it at will.
Recommended Posts