Help with M1XEP and Smtp email

[shenandoah75]

I have this device working great and can run the virtual keypad over my lan, etc no issues... However, i can't get it to email out.

using the same smtp server (smtp-server.cfl.rr.com) from a netscape client on the same network works just fine. the device is using correct gateway and dns servers match those on my pc's when i do "ipconfig /all". I rebooted the m1xep just in case, but to no avail

any advice?
-brad


fyi for testing i have a rule on "whenever task01" then email message 1 to... (firing task one from the virtual keypad in my office)

i also have a rule on one of my zones becoming unsecure (i.e. front door) to send another email. Neither has worked though i know both should trip.

 

[Steve]

I know its been said before in similar threads, but...

1. Upgrade to latest XEP firmware
2. Try IP addr instead of DNS
3. Make sure ElkRP is not connected
4. Make sure you are using the correct port
5. If auth is required, make sure proper user name and pwd are entered in RP

 

[mustangcoupe]

I am experencing the same issues... I am waiting on a tech support call back as the first guy couldnt answer the question (he said he is a sales rep just fielding the "over flow tech calls" and can only answer some of the questions) it is 5:00 pm and they close soon... hope they still call back. but I will post what I come up with in both this thread and my original.

 

[shenandoah75]

OK no luck upgrades the control and the ethernet interface to laterst boot/firmware... no luck... change the smtp to 65.32.5.130 instead of the named one

dns servers are still 65.32.5.74/75 as before (as are my pcs)

no go... tried from the actual keypad too (with elkrp disconnected)

since my email client has no port setting and sense RR doesn't specify, i'm assuming it has to be the default of 25...

any other thoughts?
brad

 

[Spanky]

There is one type of email accounts, encrypted authentation, that the XEP operating system does not support. I will ask the XEP guru tomorrow if Road Runner has that type of encryption.

 

[Steve]

Many ISP's either block port 25 or don't allow you to do impersonation. So make sure the email addr you specify in the XEP is your actual email addr you authenticate with/used in your email client.

 

[shenandoah75]

yep it is....

 

[electron]

A few other suggestions:

• Turn on advanced logging for on your internet router, and see if you can see it attempting to connect to the mail server.
• Plug both your machine and the XEP into a hub, and run a sniffer (something like WireShark should do the job).
• Make sure your IP settings are correct, especially the default gateway and subnet mask.
• Make sure you use a valid 'from' email address.

 

[mustangcoupe]

Brad @ elk had me wants me to run a sniffer and email him the results so that he can see if it is actually trying to send the email, or if it is a problem with my host

 

[shenandoah75]

well i'm ashamed to admit it, but i have solved my problem:

Shen = Moron....

as many times as i looked at the setup form, i just missed the fact that the default gateway was 192.168.0.1 and that it didn't change when i changed the static ip from "..0." Sorry - used to linksys cascading the first three segments down to all the setups.

-brad

 

[mustangcoupe]

Ok, I am going to add the result here so I can be ridiculed and sent into the beating circle by everyone (or hope it helps others in some small way)
with help from shenandoah75 but unknown I basically did the same thing! My wireless router bit the dust two weeks ago and I forgot to change the static Gateway address in the ELK.... 192.168.10.1 vs 192.168.10.240. Can you say duh!

 

[Steve]

Hehe, we've all been there. Glad you got it working - it almost always does come down to something really simple or stupid. I will add a check DNS to my list for future troubleshooting.

 

[electron]

A few other suggestions:

• Turn on advanced logging for on your internet router, and see if you can see it attempting to connect to the mail server.
  
  
• Plug both your machine and the XEP into a hub, and run a sniffer (something like WireShark should do the job).
  
  
  
  [*] Make sure your IP settings are correct, especially the default gateway and subnet mask.
  
  
• Make sure you use a valid 'from' email address.

what prize do I win? Glad to hear you got it all up and running, without having to do major surgery or sending the unit back!

 

[BraveSirRobbin]

Yes, sometimes the simple things will bite you like this. I was trying to get a wireless network setup on a computer last night and could have sworn I entered the MAC address to the list of "accepted" devices on my wireless router. Well, after sleeping on it I went through all the settings again and "holy cow" I didn't have it in there!

Nowadays if I'm having setup problems (which is usually late on Friday nights) I sleep on it and attack the problem fresh the next day.

 

[gcimmino]

OK, it's late, so I'll ask for folks opinion:

Should there be some logging or diagnostics available on the XEP?

I've had them since the first release and love them. I'm firmly in the camp that there should be an M1 Platinum with the XEP onboard and tightly coupled so we can get more functionality than 16 numbered emails with static content...

That said, many who have learned the lessons of not being connected via RP when trying to send have been experiencing various issues with sender authentication or simple IP/routing issues like typos or need to use IPs vs domain names.

Having the ability to Ping from the XEP or bubble up errors that should be happening somewhere in the IP/SMTP stack to the M1's log would have kept folks from pulling out some hair and probably also cut down on Elk Tech Support's load.

Just a thought.