Need abuse/postmaster contact for AT&T to resolve IP block
A few of our exchange IPs get blocked intermittently, but only by ATT. Ips are clean, no issues, we’re diligent about finding and fixing these types of issues as it has a large impact. It would be very helpful to know why the IP below got blocked so we can find and fix the problem to prevent further listing. We have a few ips in rotation and some have no issue. It’s a “blind” listing, so we only find out about it when customers complain that they getting blocked. ff-ip4-mx-vip1.prodigy.net #<ff-ip4-mx-vip1.prodigy.net #5.3.0 smtp; 553 5.3.0 flph399 DNSBL:ATTRBL 521< 67.215.167.170 >_is_blocked.__For_information_see_http://att.net/blocks> #SMTP# Any info/help would be most helpful. Many thanks, Webhosting.net Postmaster
Interestingly, your mail to the nanog list went to my spam folder, rather than my nanog folder (I'm using gmail or domains for my mail.) That rarely happens. On Tue, Aug 30, 2016 at 9:22 AM, Webhosting.net Admin <admin@webhosting.net> wrote:
A few of our exchange IPs get blocked intermittently, but only by ATT. Ips are clean, no issues, we’re diligent about finding and fixing these types of issues as it has a large impact.
It would be very helpful to know why the IP below got blocked so we can find and fix the problem to prevent further listing. We have a few ips in rotation and some have no issue. It’s a “blind” listing, so we only find out about it when customers complain that they getting blocked.
ff-ip4-mx-vip1.prodigy.net #<ff-ip4-mx-vip1.prodigy.net #5.3.0 smtp; 553 5.3.0 flph399 DNSBL:ATTRBL 521< 67.215.167.170 >_is_blocked.__For_ information_see_http://att.net/blocks> #SMTP#
Any info/help would be most helpful.
Many thanks,
Webhosting.net Postmaster
Gmail here, went to my Inbox. On Wed, Aug 31, 2016 at 10:41 AM, Jay Farrell via NANOG <nanog@nanog.org> wrote:
Interestingly, your mail to the nanog list went to my spam folder, rather than my nanog folder (I'm using gmail or domains for my mail.) That rarely happens.
On Tue, Aug 30, 2016 at 9:22 AM, Webhosting.net Admin < admin@webhosting.net> wrote:
A few of our exchange IPs get blocked intermittently, but only by ATT. Ips are clean, no issues, we’re diligent about finding and fixing these types of issues as it has a large impact.
It would be very helpful to know why the IP below got blocked so we can find and fix the problem to prevent further listing. We have a few ips in rotation and some have no issue. It’s a “blind” listing, so we only find out about it when customers complain that they getting blocked.
ff-ip4-mx-vip1.prodigy.net #<ff-ip4-mx-vip1.prodigy.net #5.3.0 smtp; 553 5.3.0 flph399 DNSBL:ATTRBL 521< 67.215.167.170 >_is_blocked.__For_ information_see_http://att.net/blocks> #SMTP#
Any info/help would be most helpful.
Many thanks,
Webhosting.net Postmaster
Try posting that to the mailop list. I had been having trouble with att.net for about a month, and I filled out the form at http://att.net/blocks/ 3 times with no response. I posted to mailop a few days ago and they resolved the issue within an hour. ...then a few days later I received the response to the form that my IP had already been unblocked. Even though they say they will get back to you within 2-3 days, it's more like 10-14. -A On Tue, Aug 30, 2016 at 6:22 AM, Webhosting.net Admin <admin@webhosting.net> wrote:
A few of our exchange IPs get blocked intermittently, but only by ATT. Ips are clean, no issues, we’re diligent about finding and fixing these types of issues as it has a large impact.
It would be very helpful to know why the IP below got blocked so we can find and fix the problem to prevent further listing. We have a few ips in rotation and some have no issue. It’s a “blind” listing, so we only find out about it when customers complain that they getting blocked.
ff-ip4-mx-vip1.prodigy.net #<ff-ip4-mx-vip1.prodigy.net #5.3.0 smtp; 553 5.3.0 flph399 DNSBL:ATTRBL 521< 67.215.167.170 >_is_blocked.__For_ information_see_http://att.net/blocks> #SMTP#
Any info/help would be most helpful.
Many thanks,
Webhosting.net Postmaster
participants (4)
-
Aaron C. de Bruyn -
Andrew Kirch -
Jay Farrell -
Webhosting.net Admin