<html><body><div><div><a target="_blank" rel="noopener noreferrer" href="http://txt.att.net">txt.att.net</a><span> is returning MX records and those machines don't have port 444 open...</span></div><br><div><span>Wouldn't you want to be sending something like a SNPP message instead? It's a much less convoluted delivery process and is almost real-time (no queuing).</span></div><br><div><span>I guess it's been a decade or so since I've dealt with emergency services and paging...is SNPP even a thing anymore? </span></div><br><div><span>I looked at some old code I wrote (</span><a target="_blank" rel="noopener noreferrer" href="https://github.com/darkpixel/snppsend/blob/master/more-providers">https://github.com/darkpixel/snppsend/blob/master/more-providers</a><span>), and it doesn't look like </span><a target="_blank" rel="noopener noreferrer" href="http://snpp.attws.net">snpp.attws.net</a><span> exists.</span></div><br><div><span>-A</span></div></div><br><div><div>On Fri Jan 20, 2023, 02:12 PM GMT, <a href="mailto:bill@herrin.us">William Herrin</a> wrote:<br></div><blockquote style="margin:0 0 0 4pt;padding-left:4pt;border-left:1px solid #CCC"><div style="color:#212121;font-size:14px;font-weight:normal;line-height:20px">On Thu, Jan 19, 2023 at 8:09 PM Dan Walters via NANOG <nanog@nanog.org> wrote:<blockquote>Know this is a longshot, any chance anyone from the txt.att.net domain might be able to help us with what we believe is a blacklist block or possibly an outage?<br>We deal with 911 cad dispatching and is affecting first responders so looking to see if there is a faster way to resolution.</blockquote><br>Hi Dan,<br><br>As I understand it, txt.att.net is a low-volume courtesy service not<br>intended for important communications. A paid service like Twilio can<br>handle production-grade SMS delivery.<br><br>Regards,<br>Bill Herrin<br><br>-- <br>For hire. https://bill.herrin.us/resume/<br></div></blockquote></div></body></html>