I just started sending text from laptop to people rather than phone, if I can. (I have a hand tremor that makes "typing" text hard.) Dictation to phone only works some of the time. No problems so far.
I might be wrong - it would appear text can be handled/processed via TM or Google. (I have a Pixel phone.)
Not sure if you are experiencing an issue or just making a general comment. But yes, sending email to mobile is good option. You may not be aware, but T-Mobile also offers a laptop based texting software called DIGITs. You can login to a webpage or download the software. It allows you to make/receive calls/texts and type from keyboard to same recipients synced with your phone. you can access it here T-Mobile DIGITS
This explains how DIGITs functions and the various uses.
Also with most phone devices, you can already choose Siri or "OK Google" to trigger the assistant to send a text using voice commands.
WOW!! Didn't realize all this tech is out there - FOR FREE!.
I am no longer active enough (business) to take advantage of most of it - but some will be useful.
It looks like you are the one to talk to for these 550 errors.
I too have a particular person (my boss) that is unable to send me email to text messages due to being blocked.
I have requested a follow and awaiting approval.
Please let me know what information you may need so that we can resolve this.
Hi srickar, same here if you can help.
Have you reached out to your IT team? Please inform your IT admin to correct the SPF DNS entry. SPF is a DNS policy setup by the domain owner that specifies what networks are authorized to send emails on behalf of the domain. The SPF entry has conflicting hard and soft fail entries explicitly allowing and denying certain network segments at the same time, so each time a message is sent, depending on which entry is queried first, the message is either accepted or denied. Cant have both "~all" and "-all", that's contradictory. Dash means hard fail explicit requirement, and "~", signifies soft fail. For more info, What is Sender Policy Framework, and How to Setup SPF Record? IF anything, the IP listed in the SPF is not matching network the message originating from.
@dneph.com does not designate xx.xx.213.17 as permitted sender.
The TXT records found for your domain are:
v=spf1 include:_spf.google.com ~all
v=spf1 ip4:126.96.36.199 a:zixvpm.dneph.com -all
Ok, I'll reach to our Managed Service IT group. So from your knowledge
there isn't any thing that TMobile needs to do in order to allow messages
to be sent to the 20-30 Physicians that use TMobile as their service
I blocked that yesterday because it was flooding our SMTP connections. This type of automation traffic should ideally be sent over a shortcode provider due to the characteristics of the message. This front end interface is not designed to accept that amount of traffic for an enterprise. Please see section 4.2 pertaining to enterprise traffic volume and why dedicated shortcode gateways are setup to handle this. https://api.ctia.org/wp-content/uploads/2019/07/190719-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf
Even if I did not block, the messages were easily exceeding rate control connection limits which is generous. Also, the messages sent to each device was causing flooding to device delivery to the point devices couldnt acknowledge the messages fast enough.
srickar thank you for the quick response!
typically we only use if for verification codes but yesterday we sent 4800 (8 messages x 600 customers) so i understand what you are saying. Can you unblock so we can continue to verify. I will review the document and see if blasts can go another route.
I have removed the outright block, but please note that exceeding rate control volume is still possible and I cant circumvent since rate control is a global setting. For this type of A2P automation, the traffic should move to a shortcode provider like Syniverse, Twilio, Sybase, etc. These dedicated routes have different anti-spam policies for vetted traffic and perform ENUM lookup automatically to find the right carrier owner.
Since you are using email, if a subscriber ports between different carriers, you are essentially emailing a stale address which ENUM lookups are performed in real-time by the shortcode operator. Also, if a subscriber were to swap numbers and a former number is now assigned to a new user who's getting these email blasts, they could report it to FCC for TCPA violation. Something to consider as to why enterprise compliance is crucial these days. Thanks.