I have been working on a similar issue and thought I would share a bit. This may be old news and if so sorry for wasting bandwidth As to:
>>If I set the M1G to Email from the M1G to
[email protected] , it works great.
>>If I send an email from [email protected] to myphone#@vtext.com , it works great
>>If I send from M1G to myphone#@vtext.com nothing happens
This may be obvious but in case not, some basics on SMTP. In general (but not always), an SMTP server will accept inbound mail either (a) addressed to an account that it hosts or is a gateway for, or (B) from an account it hosts, or is a gateway for address to others. There are all sorts of increasingly onerous restrictions on this to prevent relay, and in particular for (B), the primary one being that authentication is usually required for (B) and not (a). So you will get different behaviour depending on addressee (and sometimes from address also).
So your mail may disappear into a black hole if you violate any number of these issues. For example, if I am using a server on which I have an account
[email protected], and I send to
[email protected] it may work fine (because that is case (a) and authentication is not required), but if I send to
[email protected] trying to send to
[email protected], it will fail unless it believes I am me, thus requiring authentication. Otherwise it will give a "relay not allowed" error.
The catch in case (a) is that many server administrators are starting to filter out mail arriving via SMTP directly from homes, they have lists of DSL, Cable, etc. address blocks, and simply say "we accept none of those". The really bad news is I have found no way to get the Elk device to provide the actual SMTP transcript so you can see the error message. You need a packet sniffer to see it, and a way to get it in line with the Elk M1EXEP device, something also increasingly hard with home equipment now that cheap switches have replaced hubs.
Anyway... if you want to maximize your chance to get things to work, I would suggest starting sending mail to your own mail server addressed to yourself, get that working then experiment sending to other addresses. Expect to not be able to send to others without authenticating. And (based on notes here) don't expect it to work if your mail server requires encryption.
To try case (B) you need to know from your provider where SMTP clients can authenticate and drop off mail.
To try case (a) you can find out from the MX record for your email. For example, if you were
[email protected] (and still doing your own system!) you could do this from windows:
C:\Users\Myself>nslookup
Default Server: stuff
Address: stuff
> set type=mx
> whitehouse.gov
Server: stuff
Address: stuff
Non-authoritative answer:
whitehouse.gov MX preference = 105, mail exchanger = mail1.eop.gov
whitehouse.gov MX preference = 105, mail exchanger = mail2.eop.gov
whitehouse.gov MX preference = 105, mail exchanger = mail3.eop.gov
whitehouse.gov MX preference = 105, mail exchanger = mail4.eop.gov
Any one of those can be used to drop off email using case (a) without authentication, but it will only accept email for @whitehouse.gov, and it MIGHT OR MIGHT NOT accept it from your home's IP address. But if all else is failing, try case (a) with your own address (not whitehouse of course) and no authentication.
Oh... and until you get the nameservers right, nothing will work. Try testing NTP if you get frustrated with SMTP, it is a bit more sure fire. Use something like 2.north-america.pool.ntp.org as an address, and see if it tests. If not, you either have a DNS problem (probably) or a firewall issue at your router, or some other problem and SMTP is likely not to work either.
