Problem sending emails with M1XEP

[Dogman]

1) Yes clicking the email test button in RP email setup tab and the response is "system did not respond, connection may have terminated ". Then a second later I get "Control disconnected" and sure enough it does and no email is sent.   However, like I also said using the special ELK diagnostic software running all the different tests for XEP everything works fine including the email test application it has I get the email just fine.
 
2) Yes of course it is disconnected when doing an operational test.
 
 

 

[jpmargis]

I'm not seeing any problems with your setup.  Just a wild guess, but try changing the DNS Server.  OpenDNS should be fine, but it's worth a try.  Google is 8.8.8.8 and 8.8.4.4.  Also, log into SMTP2GO using the exact credentials the from M1XEP.  The error message you are seeing is an indication that the M1XEP is hung up in one of the email client processes.

 

[Dogman]

Ok tried changing DNS servers and  no changes also verified SMTP2GO by logging in.  Had already done that a few days ago but just in case.   I will try DELs suggestion of hitting the ports from outside the LAN when I can.  I don't have tethering plan on my phone. So need to go to Starbucks I guess .  If that fails then I guess an call to ELK tech support is next.

 

[Del91574]

I don't think Elk is going to give you much to work with because the issue resides on the WAN and not the LAN.
 
For giggles, were there any firewall changes on your network hardware? Have you tried putting the XEP into a DMZ?
 
It seems like your ISP is running a firewall or blocking ports.

 

[Dogman]

Update:  Well sent ELK some data and they are perlexed as well they have asked for more trace data ie when using the test utility and during normal operation. There is something that is causing a differnce between normal operation and the diagnostic utility that blocks the emails during normal operation but during testing they work.

 

[chrisexv6]

Some things:
 
1.  have you tried using just the IP for the smtpcorp.com server?
2.  have you tried changing where the emails are sent? (i.e. to an actual email server instead of the AT&T text server)

 

[Dogman]

Yes tried all of those things.   Still working with Elk Tech support via email to find the problem.  It had been working fine for quite awhile so I am inclined to thing something has failed in the XEP but Tech support is still asking me to try different things.

 

[Mark S.]

Dog - any resolution to your problem? I think I' m in the same boat.

 

[Mark S.]

I have spent 3 days wrestling with getting an email out of my XEP.  I've tried Comcast email, gmail email, gmx email - using all the advice I could find on this forum - no go.  My ISP is Comcast - are they the problem?.  Are they blocking all ports?  Has anyone with Comcast gotten this to work?

 

[sda]

Debugging Elk email problems can be challenging.
First of all, make sure the XEP has the correct IP, gateway, and DNS for your network.
 
If you use telnet from a (command) prompt to send an email manually, you might be able to see where it breaks.
When you do this, make sure your computer is configured on the same subnet and uses the same gateway and DNS as the XEP.
 
>telnet smtpserver  port
(you should connect and get a response, if not the port is probably blocked)
 
for example
>telnet smtp.comcast.net 25
220 omta14.emeryville.ca.mail.comcast.net comcast ESMTP server ready
 
If you get that far, continue with what the XEP is sending to the mail server (ehlo, mail from, rcpt to, data, text). 
See this post for details on what the XEP is sending.
http://cocoontech.com/forums/topic/23910-elk-m1xep-email-revealed

 

[vc1234]

I have spent 3 days wrestling with getting an email out of my XEP.  I've tried Comcast email, gmail email, gmx email - using all the advice I could find on this forum - no go.  My ISP is Comcast - are they the problem?.  Are they blocking all ports?  Has anyone with Comcast gotten this to work?

I have it working. The only thing I needed to change was port number (25->587):
 
Server:smtp.comcast.net  Port: 587
 
Username: xxxx Password yyyy
 
That works in MA. CT may be different.

 

[Mark S.]

Thanks. I can get to SMTP.comcast.net 587 via Telnet. But the XEP won't send to it. I cannot figure out why. The gateway, subnet and DNS all appear to be correct.

I am using:
SMTP.comcast.net, port 587, my username and password, from same comcast email address, to same comcast email address.

Nothing.

This problem seems all too common. Where is Elk with a fix?

 

[vc1234]

I am using:
SMTP.comcast.net, port 587, my username and password, from same comcast email address, to same comcast email address.
 

 
That's exactly what I am using.
 
You may try to download ELK-M1XEP Diagnostic Utility (1.0.2)  from http://www.elkproducts.com/m1_downloads.html.
and play with it. Perhaps, the XEP cannot resolve smtp.comcast.net in which case you may want to hardcode the ip address.
 
I agree that XEP is rather a mediocre pieace of hardware for more reasons than one in comparison to the rest of the product. However, in my case, it seems to be working OK so far.

 

[vc1234]

Here's the output from the diagnostic utility:
Name: XEP01
MAC Addr: 00-40-9D-6C-DD-05
IP Addr: 10.1.1.5
Secure Port: 2601
M1XEP serial port OK: Yes
M1XEP has initialized: Yes
DHCP: Yes
Subnet: 255.255.255.0
Gateway: 10.1.1.250
Pri DNS: 159.240.24.229
Sec DNS: 159.240.24.229
Non-secure Port: 0
AMX Beacon: Yes
Email Server: smtp.comcast.net (URL)
Email Port:  587
Email From Addr: [email protected]
Email Username: yyy
Email POP before SMTP: No
DDNS Server:  (IP)
DDNS Username:
DDNS Hostname:
DDNS Email To:
DDNS Email on Change: No
SNTP Server: north-america.pool.ntp.org (URL)
SNTP Update Time: 00:00
SNTP Time Zone: GMT-5.00
SNTP Email on Errors: No
Bootware Version: 1.2.0
Application Version: 1.3.28

Problems:
A 'pool' server may be selected as the SNTP server.  Please read the 'Details' on the Time Server tab of the M1XEP Setup window in ElkRP.
 

 

[chrisexv6]

That's exactly what I am using.
 
You may try to download ELK-M1XEP Diagnostic Utility (1.0.2)  from http://www.elkproducts.com/m1_downloads.html.
and play with it. Perhaps, the XEP cannot resolve smtp.comcast.net in which case you may want to hardcode the ip address.
 
I agree that XEP is rather a mediocre pieace of hardware for more reasons than one in comparison to the rest of the product. However, in my case, it seems to be working OK so far.

 
Something interesting I noticed: if you do an nslookup on smtp.comcast.net, it resolves to two addresses (not uncommon) but one of their addresses is an IPV6 address (i.e. looks more like a MAC address than what we're used to as an IP address)
 
Its an out-there stretch but I wonder if your DNS server resolves to the IPV6 address and the XEP has no idea what to do with it.  A quick test, I think, would be to put the actual IPV4 IP address into the server section of the XEP (smtp.comcast.net = 68.87.26.155)