Problem sending emails with M1XEP

[wuench]

It will only resolve to IPV6 if your system supports it, it's a different type of DNS record AAAA vs A.  You are probably on Windows7+ with IPv6 enabled.   The Elk shouldn't run into that, an IPv4 system will never ask for that type of record.

 

[Mark S.]

Thanks, guys.
 
I have tried using the Comcast smtp URL and the IP - same result either way.
 
I tried the diagnostic utility - ran all the available tests.  My output upon starting it was pretty much the same as vic1234's - no errors, nothing stands out.  The only real difference is that I don't have the AMX Beacon on (I have no idea what that does).
 
The "Get DNS" test passed according to the interpretation instructions.
 
The only one that indicated a problem was the Send Test Email.  I get the following:
21:03:08 Send Email 0
21:03:08 Send Email Subject: Email Alert from M1XEP
21:03:08 Send Email GlobalSMTPType: 0, DNSGood: True, GlobalSMTPAddr: 68.87.26.155
21:03:08 Send Email smtp_addr: 68.87.26.155
21:03:08 Send Email To: [email protected]
21:03:08 Send Email Body: This is a test email from the ELK-M1XEP M1XEP
21:03:08 Send Email Username: [email protected]
21:03:08 Send Email Password: mypassword
21:03:08 Send Email From: [email protected]
21:03:08 Send Email Domain: @comcast.net
21:03:08 Send Email mailserv: 00602E68
21:03:08 Send Email MCSetDomain returned 0
21:03:08 Send Email MCSetSmtpAuthentication returned 0
21:03:08 Send Email MCNewMail returned 0, mailid=00608E28
21:03:08 Send Email MCSendMail returned FFFFFFF3
21:03:08 Send Email MCClose returned 0
21:03:08 Send Email Done
 
According to the interpretation guide, any non-zero return on the MCSendMail apparently indicates a problem.  So there it is.  Any ideas?
 
One other odd thing I found with the Diagnostic Utility.  When it searches for XEP's it often find duplicates - two lines for the same XEP - one with a MAC address and one without, both with same IP address - and the utility throws out a warning - "The M1XEP's IP address is in a different subnet than the network adapter.  You should change either the M1XEP's address, the adapter's address, or select a different adapter".  But I have verified that they are on the same subnet.  Now I did have a second un-used adapter on the same PC that I use to set up the M1XEP, so maybe that freaked out the XEP?  I disabled that adapter, but still get the duplicate XEP and the warning. What might be going on there?  Did the XEP save a second configuration?  Any chance this is causing the email failures?
 
I'm not network savvy, so this is baffling to me.  Thanks for your help.

 

[vc1234]

My trace is below:
 
16:52:30 Send Email 0
16:52:30 Send Email Subject: Email Alert from XEP01
16:52:30 Send Email GlobalSMTPType: 1, DNSGood: True, GlobalSMTPAddr: smtp.comcast.net
16:52:30 Send Email smtp_addr: 68.87.26.155
16:52:30 Send Email To: [email protected]
16:52:30 Send Email Body: This is a test email from the ELK-M1XEP XEP01
16:52:30 Send Email Username: xxx
16:52:30 Send Email Password: yyy
16:52:30 Send Email From: [email protected]
16:52:30 Send Email Domain: @comcast.net
16:52:30 Send Email mailserv: 00602210
16:52:30 Send Email MCSetDomain returned 0
16:52:30 Send Email MCSetSmtpAuthentication returned 0
16:52:30 Send Email MCNewMail returned 0, mailid=00602D58
16:52:31 Send Email MCSendMail returned 0
16:52:31 Send Email MCClose returned 0
16:52:31 Send Email Done
 
 
Not sure what "Send Email MCSendMail returned FFFFFFF3" means. It appears to be indeed indicating an error.

 

[Mark S.]

I followed the recommendations on this board - tried a whole lot of combinations of settings and email providers - nothing.  I finally tried SMTP2GO - that works, so far, but it is a workaround for something that Elk needs to fix. 
 
I realize that there are probably many possible configurations for smtp servers out there, but Elk really needs to provide a better solution for email.  This was a ridiculous exercise, and had me real close to returning my entire Elk system.
 
Thanks to all for the help.

 

[chrisexv6]

I followed the recommendations on this board - tried a whole lot of combinations of settings and email providers - nothing.  I finally tried SMTP2GO - that works, so far, but it is a workaround for something that Elk needs to fix. 
 
I realize that there are probably many possible configurations for smtp servers out there, but Elk really needs to provide a better solution for email.  This was a ridiculous exercise, and had me real close to returning my entire Elk system.
 
Thanks to all for the help.

 
I see a difference between your trace and vc1234's - the successful trace is using just the username portion as the Email username, yours was using the full email address.  Have you tried the same on yours?

 

[Mark S.]

 
I see a difference between your trace and vc1234's - the successful trace is using just the username portion as the Email username, yours was using the full email address.  Have you tried the same on yours?

Yes, I tried both ways.

 

[vc1234]

Yes, I tried both ways.

That's a good point: the user name should be without the domain name(in my case at least) otherwise I get an authentication error. I've wiresharked the exchange between my XEP and the comcast server (the XEP strings are in bold):
 
----------
220 omta08.westchester.pa.mail.comcast.net comcast ESMTP server ready
EHLO comcast.net
250-omta08.westchester.pa.mail.comcast.net hello [], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 OK
AUTH LOGIN
334 VXNlcm5hbWU6
eHh4 <- base64 encoded xxx
334 UGFzc3dvcmQ6
eXl5 <- base64 encoded yyy password
235 2.7.0 ... Authentication succeeded
MAIL FROM: <[email protected]>
250 2.1.0 <[email protected]> sender ok
RCPT TO: <[email protected]>
250 2.1.5 <[email protected]> recipient ok
DATA
354 enter mail, end with "." on a line by itself
MIME-Version: 1.0
To: [email protected]
From: [email protected]
Cc:
Subject: Email Alert from XEP01
X-Mailer: Allegro Software RomMailer /4.01
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

This is a test email from the ELK-M1XEP XEP01
.
250 2.0.0 lARt1m00i36WzCQ3UARuz9 mail accepted for delivery
QUIT
221 2.0.0 omta08.westchester.pa.mail.comcast.net comcast closing connection
---------------
 
One can easily recreate the dialog above through telnet:
---
telnet smtp.comcast.net 587
Trying 68.87.26.155...
Connected to smtp.comcast.net (68.87.26.155).
Escape character is '^]'.
220 omta04.westchester.pa.mail.comcast.net comcast ESMTP server ready
EHLO comcast.net
250-omta04.westchester.pa.mail.comcast.net hello [], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 OK
AUTH LOGIN
334 VXNlcm5hbWU6
eHh4
334 UGFzc3dvcmQ6
eXl5
235 2.7.0 ... Authentication succeeded
MAIL FROM: <[email protected]>
250 2.1.0 <[email protected]> sender ok
RCPT TO: <[email protected]>
250 2.1.5 <[email protected]> recipient ok
DATA
354 enter mail, end with "." on a line by itself
To: [email protected]
From: [email protected]
Subject: Any subject

Any text
.
250 2.0.0 lAYa1m00c4tyuGD01AZLK5 mail accepted for delivery
quit
221 2.0.0 omta04.westchester.pa.mail.comcast.net comcast closing connection
Connection closed by foreign host.
 
The username and password need to be base64 encoded:
e.g. perl -MMIME::Base64 -e 'print encode_base64("xxx");'
eHh4
 
 
So, I'd try to type in an email message as illustrated (maybe the comcast password is incorrect) ? Otherwise, if the telnet exercise is successfull,  most likely the XEP is broken.

 

 

[wojeda]

OK guys, I have WASTED!!! a whole week with this junk, brand new XEP has consumed my life trying to get this email junk to work.
Nothing I have tried from forums, ELK website, ELK Webinars and ELK Tutorials has worked. They bluntly have lied to me.
 
BUT, Thanks to chrisexv6, and his suggestion of using SMTP2GO, now I have it working as well. It is unfortunate that the free account is limited. ELK should pay for that or, implement encryption already so I can use my gmail account.
 
Why oh, why does ELK do this?  Do they enjoy seeing customers suffering or what?
 
PS. Sorry for the rant. I am very busy and don't handle time wasting very well... :mellow:

 

[baby007]

Same here until lately,i have to set elk to send email to my yahoo account and get yahoo to forward to gmail. It wont work if i tell elk to send to gmail. Im on fios

 

[gatchel]

Hopefully, in the near future Elk will make some big announcement about the email capabilities. It has definitely been a long time...The EXP is very limited by today's standards.