<div dir="ltr">What legal grey area? Every carrier I've worked with monitors the content of MMS and SMS and will block outgoing messages, per CTIA guidelines. Carriers are already expected to block SHAFT content and other misuse/abuse, and some will even return specific errors when this happens. It's unfortunate that the FCC is allowing T-Mobile to surcharge every part of the messaging lifecycle, e.g. I learned recently that T-Mobile surcharges carriers on both directions of traffic, unlike others who only surcharge to send messages to them.<div><br></div><div>For those not familiar with the CTIA Messaging Principles & Best Practices:</div><div><a href="https://www.ctia.org/the-wireless-industry/industry-commitments/messaging-interoperability-sms-mms">https://www.ctia.org/the-wireless-industry/industry-commitments/messaging-interoperability-sms-mms</a><br><br></div><div>Current version: <a href="https://api.ctia.org/wp-content/uploads/2023/05/230523-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf">https://api.ctia.org/wp-content/uploads/2023/05/230523-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf</a></div><div><br></div><div>The CTIA Messaging Security Best Practices also touch on content, blocking, and sharing content when necessary:<br><a href="https://www.ctia.org/the-wireless-industry/industry-commitments/messaging-security-best-practices">https://www.ctia.org/the-wireless-industry/industry-commitments/messaging-security-best-practices</a><br></div><div><br></div><div>Current version: <a href="https://api.ctia.org/wp-content/uploads/2022/06/Messaging-Security-Best-Practices-June-2022.pdf">https://api.ctia.org/wp-content/uploads/2022/06/Messaging-Security-Best-Practices-June-2022.pdf</a></div><div><br></div><div>Take a look at <a href="https://support.bandwidth.com/hc/en-us/articles/360000111087-SMPP-SMS-Delivery-Receipts-and-Error-Codes">https://support.bandwidth.com/hc/en-us/articles/360000111087-SMPP-SMS-Delivery-Receipts-and-Error-Codes</a><div><br></div><div>470<br>spam-detected<br>This message has been filtered and blocked by Bandwidth for spam. Messages can be blocked for a variety of reasons, including but not limited to volumetric filtering, content blocking, SHAFT violation, etc.<br><br></div><div>481<br>rejected-from-number-in-blacklist<br>The From number has been flagged by Bandwidth as prohibited from sending messages. Numbers can be added to a blacklist when they are associated with messages that repeatedly violate spam policies, fraud policies, or messaging AUP. <br><br></div><div>770<br>destination-spam-det<br>The Carrier is reporting this message as blocked for SPAM. Some examples of common spam blocks: unwanted content, SHAFT violations (including specific keywords), or originating address has been flagged for repeated spam content.<br><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 20, 2023 at 10:41 AM Jay Hennigan via VoiceOps <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 12/20/23 10:24, Peter Beckman via VoiceOps wrote:<br>
> I received this information from Bandwidth 2 days ago:<br>
> <br>
> <a href="https://support.bandwidth.com/hc/en-us/articles/19939626519575-New-non-compliance-fees-on-January-1" rel="noreferrer" target="_blank">https://support.bandwidth.com/hc/en-us/articles/19939626519575-New-non-compliance-fees-on-January-1</a><br>
> <br>
> T-Mobile is stating that starting January 1, 2024, they will be fining<br>
> carriers for every SMS that violates these three tiers of unwanted<br>
> messaging:<br>
<br>
[snip]<br>
<br>
This sounds kind of like Mr. T deciding to fine T-Mobile $10,000 a day <br>
for having a name that starts with "T". How would he collect, or would <br>
he just pity the fools that came up with the idea?<br>
<br>
-- <br>
Jay Hennigan - <a href="mailto:jay@west.net" target="_blank">jay@west.net</a><br>
Network Engineering - CCIE #7880<br>
503 897-8550 - WB6RDV<br>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div>