All replies
-
Hey, ffit37129!
I've seen an uptick in situations such as yours. It's possible that your company's domain just needs to be whitelisted. While I don't have the answers to why the sudden change, there is a ticket that can be filed. I know you've already worked with our tech support a few times with no luck. Do you happen to know if a ticket was previously filed?
-
Yes, I do have an existing ticket. The number is 19367035. Thanks for your help!
-
-
Thanks for that info, but that did not work. We have verified our SPF policy on the outgoing mail server is valid and even tried routing through a totally different server, but we are still being blocked and have no idea why. I have not heard back from tech support.
-
Just to clarify, I can send the exact same message to my personal gmail account, and the gmail e-mail headers clearly state that SPF passes and that the sender is designated as permitted.
-
If yours is a business account - you should have a rep to directly deal with.
-
Thanks, but it's not a business account - these are messages being sent to personal devices.
-
-
-
-
-
-
1 of 1 people found this helpfulHi ffit37129 are the message still blocking? I dont always check this forum, but follow me and I can follow back so that you can send me details. For faster support, f its a public domain, just type it here and put a space between the domain(dot).com and I will look for blocked content and get it corrected. Thanks!
-
srickar - I'm also having issues with sending messages to T-Mobile phones via the e-mail to SMS gateway. My messages are getting a 550 - permanent failure. I noticed that you had recommended that others with the same problem follow you and communicate directly, so I went ahead and did that. If you could approve my Follow request, I'll send you the details directly. Thanks!
Other info...
It appears that my SPF is set up correctly.
I can send to other mobile services (AT&T, Verizon, etc.)
-
Hi srickar - it took a few weeks, but we finally got in touch with someone high enough in the tech chain who whitelisted us. Unfortunately, no one was able to really explain why it happened or give any real assurances that it wouldn't randomly happen again. Thanks, though.
-
-
We did finally get this resolved. A few key points:
- @tmo_amanda was correct - we needed to get whitelisted. However, finding the right people for this was nearly impossible as it seems no one in tech support has any clue what that means, and the doc number was apparently not helpful.
- I tried calling tech support as well as opening a ticket via twitter. Both of them directed me back to support here on this forum, which was not useful.
- We were asked several times if we had a business account and had to explain repeatedly that these are messages going out to people's personal devices, so a business account wouldn't help us even if we had one.
- Our CIO finally managed to contact T-Mobile people through LinkedIn and other channels who finally connected us to someone high enough in the support chain who unblocked us. We never got any information on why we were suddenly blocked, so it seems possible it could happen again.
- I'm glad it's working for us again, but my suggestion is that if you're going to have such aggressive blocking, you should really have a more clear path for people to get whitelisted.
-
@tmo_amanda and srickar - It looks like ffit37129 was able to get this issue fixed for his domain, which is very encouraging! Who do I need to get in touch with to get the blocking issue resolved for my domain? Sounds like I need to get whitelisted. ffit37129 - if you can direct message me the info of whoever was finally able to help you, I would be eternally grateful.
-
I can assist you but we don't typically whitelist domains outright without verifying the problem. Can you please submit a ticket via 611 about tmomail.net messaging? I can also check on my end, but would need to know the inbound address domain. Thanks.
-
srickar - I'm not a T-Mobile customer, but my domain sends messages to T-Mobile users who use my company's service. I think that means that I can't submit a ticket via 611. I'd be happy to send you the info directly if you are able to assist with verifying the problem. I sent you a "Follow" request earlier today. Thanks! Our T-Mobile customers will be so excited once we get this resolved! Can't wait.
-
Okay thats fine too John. I followed you on inbox. If you follow me on inbox as well, send me the details and I will be happy to research. Thanks!
-
2 of 2 people found this helpful
Just as an FYI to others, I reviewed the PM you sent and removed the block that was due to high volume. Please check out the PM and let me know if you see messages passing.
-
srickar, wanted to inquire on a similar possible block for another domain. I can PM or work on details here, if possible?
-
1 of 1 people found this helpful
Certainly. If its a unique domain and you feel comfortable sharing it here I can take a look and see why its blocking. Please dont share the full address here if you choose to do that, just the domain. If its gmail.com or some mass domain, you'll need to follow me on inbox and send it there instead. Thanks!
-
Gotta say you're doing a phenomenal job with this. We use the SMS alerting to check MX uptime, and this is a public domain so:
-
1 of 1 people found this helpful
Yikes there's a lot of traffic from that envelope where 99% are passing through just fine. I found 1 blocked message but it was due to 1-2 items.
In the header, the message is blocking because of ehlo domain containing .ru which is TLD for .Russia. We do not accept .RU TLD traffic because of the preponderance of spam originating from international sources. Secondly, there is a bit.ly link in the footer. We do not accept bit.ly links because of spammers using short URLs to send spam blasts.
If this is not your situation, please follow me via inbox, and I can take a look at specific recipient number. Thanks.
-
A follow was sent, I'll send further info to you via PM once you accept.
-
Followed via inbox, this time the right way
-
-
-
-
-
-
-
-
-
Okay thanks for letting me know it is working.
SMTP email requires spam filtering, which is globally and dynamically subjected to filter changes based on global spam trends from top spam reputation lists and content phrase databases. IP's and SMTP host reputation also plays a factor in pass/fail for email in addition to content.
Grammar, alphanumeric phrases, volume, and CAPS LOCK contribute to spam scoring properties. Email is intended for casual quantity and over-extending volumetric limits may result in blocking. These are industry standard methods to thwart spam attacks that have increased in the last decade.