Help with M1XEP and Smtp email

gcimmino said:
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...
YES, I beleive there should there be some logging or diagnostics available on the XEP.

Re Platnium, maybe a package with the M1G a larger can and the XEP.
 
I definitely would love to see the XEP connected to the rs485 bus as well, which would give you a way of talking to the XEP even when the network interface is all screwed up (either due to user error or other issues). Pinging an internet address in this case would have shown right away where the problem was, so I do see it being a very useful. Or maybe a way of manually connecting to the XEP with hyperterminal, and have it accept commands through this session, allowing someone to setup the IP address etc, without having to rely on RP, plus more.
 
Well, while I agree all of that would be nice, I'm not going to squeek on this one for now. I'd certainly like to see some of these improvements, but there are lots of other things I would rather see first. Elk is not a behemoth like MS where they can design many things in parallel. I would be perfectly happy to see this part of the M2 in a few years. For now, the XEP works great as designed and most config issues are of the Duh! type (happens to me too) and would happen whether the XEP was onboard or not. I think we've got a pretty good troubleshooting checklist now that maybe Elk should put on their site somewhere and maybe we should make a sticky (since we can't search on 3 letters). As far as the email or logging, that maybe just a firmware issue that can be adjusted sooner without hardware/engineering changes.
 
I had this same email issue on my Elk, and with the correct subnet mask. As I use SMTP-Server.Houston.rr.com for my email, it turned out that if I actually put in a username and password into the Elk then it would fail. If I left it out then it will send emails quite happily!

Another little-known tidbit is that there are public SMTP servers out there that don't require a username and password so if you are having problems using your ISP SMTP server you may want to try another instead (reliability with this route might be questionable?)

Just my .02 cents
HoustonFirefox
 
Back
Top