Elk email through Uverse

[jparry]

Are there folks out there using an Elk M1G system and M1XEP to send email messages through the Uverse Residential Gateway?

I tried to set up a test email rule last night and after trying to test have lost the ability to connect to the M1XEP through the RP2 gui. It does not even find the M1XEP anymore.

I have the email configured to the smtp.att.yahoo.com port 465 and the login/pswd that works to get me into att webmail.

Is there something in the RG that I need to set to allow the Elk to send out email?

Also, what steps do I need to take to restart my system so that I can re-gain access through the ElkRP2 software?

 

[Gearhead]

Try this, it works for my AT&T DSL connection.

server address: smtp.att.yahoo.com
port: 587
username: [email protected]
password: xxxxxx
from email address: [email protected]

 

[jparry]

Thanks. But my biggest obtsacle now seems that I cannot access the M1XEP. I need to re-boot my system. What steps should I take?

 

[jparry]

Ok, I have regained control of my M1XEP...now on to getting email to function. In reading doco on the XEP, it states that I should check the box to login to POP before SMTP. I understand that and agree that ATT will require that. However, in the ElkRP2 mail tab of the M1XEP setup this box does not exist. Can someone else look at their RP2 and verify that I am not crazy (advanced degree not necessary )?

 

[Spanky]

What documentation are you referring to? We’re not aware of any documentation that recommends using POP before SMTP. And to our knowledge, ATT doesn’t require it. No, you’re not crazy. Elk removed that options because it is an antiquated option used several years ago by only a handful of mail providers. In recent years, Elk has not encountered any providers that still require it. Some people were checking it incorrectly which caused email to not work, so we removed it.



Try Gearhead’s suggestion. If it works for him, it ought to for you, too. Some of Yahoo’s “sub” accounts like AT&T now require SSL encrypted email message bodies. The M1XEP does not support that. IMPORTANT: Make sure you have a valid DNS address on the TCP/IP tab. That is required for the XEP to translate the “smtp.att.yahoo.com” into an IP address. As an alternative, call AT&T to find out what the mail server’s address is and enter that instead of the URL.

Provided by ELKRP Guru

 

[nov0798]

Spanky,
When will the XEP support SSL messages? Since verizon recently did their upgrade, my XEP is basically useless!

 

[gatchel]

To all users that are having recent email problems, call Elk tech support. Explain the issue to them...

 

[jparry]

What documentation are you referring to? We’re not aware of any documentation that recommends using POP before SMTP. And to our knowledge, ATT doesn’t require it. No, you’re not crazy. Elk removed that options because it is an antiquated option used several years ago by only a handful of mail providers. In recent years, Elk has not encountered any providers that still require it. Some people were checking it incorrectly which caused email to not work, so we removed it.



Try Gearhead’s suggestion. If it works for him, it ought to for you, too. Some of Yahoo’s “sub” accounts like AT&T now require SSL encrypted email message bodies. The M1XEP does not support that. IMPORTANT: Make sure you have a valid DNS address on the TCP/IP tab. That is required for the XEP to translate the “smtp.att.yahoo.com” into an IP address. As an alternative, call AT&T to find out what the mail server’s address is and enter that instead of the URL.

Provided by ELKRP Guru

Looks like I had an old electronic copy (L524 9/07) of the M1XEP manual with this:
"Some email servers require the user to login to the incoming server in order to send mail"

Plus it seems I had seen it in one of the forum posts on the M1 dealer site.

Regardless, it is a moot point now. I got the DNS entries set up correctly and email is now working!