1 Answer
- Newest
- Most votes
- Most comments
0
Below was what I hit in Hong Kong region as the past.
This is related to a Mobile carrier-level content filtering issue:
• Mobile carriers and\or SMS aggregators apply content filtering rules to block messages that look like spam, phishing, or automated login attempts. • The line @domain.com #123456 matches patterns used by SMS OTP auto-complete formats (Android/iOS use this convention to auto-fill codes). • Some carriers treat this syntax as suspicious or “application-to-person” traffic that requires special registration. As a result, they silently drop the message even though SNS reports it as “delivered to carrier.” • That’s why removing the last line makes the SMS arrive, the message no longer triggers the filter.

That's awful, I forgot to mention that this sometimes occurs, there are a few messages that do arrive. How can I approve or send an SMS with the autocomplete line without it get silently dropped then?