[191069] in North American Network Operators' Group
RE: Email to text - vtext.com blacklisting ip
daemon@ATHENA.MIT.EDU (Sam Norris)
Tue Aug 16 19:34:25 2016
X-Original-To: nanog@nanog.org
From: "Sam Norris" <Sam@SanDiegoBroadband.com>
To: "'Ryan, Spencer'" <sryan@arbor.net>,
"'Josh Luthman'" <josh@imaginenetworksllc.com>,
"'Mike'" <mike-nanog@tiedyenetworks.com>
In-Reply-To: <hejie1mgs520olm24dmwxewg.1471385512811@email.android.com>
Date: Tue, 16 Aug 2016 16:33:01 -0700
Cc: 'NANOG list' <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Same boat... We are sending messages to PHONENUMBER@vtext.com and getting
bouncebacks or lost items. I assume its because some limits are now being put
into place. We are a Verizon subscriber so I am paying, it is not a free
service. But .... I am totally up for paid services if you can recommend some
that will reliably get us texts to our verizon phones.
Sam
> -----Original Message-----
> From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Ryan, Spencer
> Sent: Tuesday, August 16, 2016 4:17 PM
> To: Josh Luthman; Mike
> Cc: NANOG list
> Subject: RE: Email to text - vtext.com blacklisting ip
>
> I agree. Pay Pager duty or a SMS gateway with a SLA. Relying on the free
service
> for anything critical is asking for trouble.
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>
> -------- Original message --------
> From: Josh Luthman <josh@imaginenetworksllc.com>
> Date: 8/16/16 6:09 PM (GMT-05:00)
> To: Mike <mike-nanog@tiedyenetworks.com>
> Cc: NANOG list <nanog@nanog.org>
> Subject: Re: Email to text - vtext.com blacklisting ip
>
> If it's critical I'd suggest a service than can depended on...
>
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
> On Aug 16, 2016 5:45 PM, "Mike" <mike-nanog@tiedyenetworks.com> wrote:
>
> > Hi,
> >
> >
> > I have a server that monitors my network and issues text messages if
> > there are events of note that require human intervention. There is some
> > process filtering that ensures it also is not able to issue more than 1
> > alert maximum per 5 minutes, to ensure it doesn't flood pagers with
> > messages all screaming the sky is falling when things are not going well.
> > Recently however, this server is no longer able to deliver messages to
> > vtext.com - it gets nothing but 554 errors:
> >
> >
> > telnet 69.78.67.53 25
> > Trying 69.78.67.53...
> > Connected to 69.78.67.53.
> > Escape character is '^]'.
> > 554 txslspamp10.vtext.com
> > Connection closed by foreign host.
> >
> > Granted on some days during challenging times it can send 30 or 40
> > messages before we get to it and get it squelched / silenced, but it's
> > otherwise reasonably well behaved IMHO and I don't think we are any heavy
> > volume sender. So I am trying to figure out why it's blacklisted then and
> > am rolling snake eyes. If anyone who is an admin for verizon or who has
> > any insight to share I'd certainly appreciate it. Email to text is a
> > critical function we depend on.
> >
> >
> > Thank you.
> >
> >
> >
