dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2758
share rss forum feed

t3kt3hgrrl

join:2012-12-27
Lafayette, LA

IP Address not being removed from ATT Blacklist

Hello,

The company I work at has an ip address blacklisted by ATT. We have submitted the form on the att.com/blocks site twice, the first being a week ago. We have only received the typical response stating we will hear back in 2 days.

The issue we have is that a client is trying to send very important emails to people who use ATT/Bellsouth/Packardbell accounts and they will not go through. It is an urgent situation that we get this ip removed off the blacklist immediately.

I have emailed Tier 2 and have had no response, and have been on the phone with a plethora of people. What could I do next?!

Thanks!



graysonf
Premium,MVM
join:1999-07-16
Fort Lauderdale, FL
kudos:1

You might want to find out why the IP was blacklisted in the first place.

It would probably help your case if you could tell them why AT&T was wrong to blacklist the IP, or that you have corrected the problem that caused the IP to be blacklisted.

In the meantime, if you are running your own mail server smarthost around the problem.



NetFixer
Snarl For The Camera Please
Premium
join:2004-06-24
The Boro
Reviews:
·Cingular Wireless
·Comcast Business..
·Vonage
·Comcast

4 edits
reply to t3kt3hgrrl

said by t3kt3hgrrl:

The issue we have is that a client is trying to send very important emails to people who use ATT/Bellsouth/Packardbell accounts and they will not go through.

AT&T's email servers are used for Packard Bell? I was not even aware that Packard Bell still operated (or sold products) in the US.*

* I used to work for the company who assimilated the PC manufacturing entity known as Packard Bell. The current owner of the name Packard Bell only bought the name, not the company or its assets, and unless something has very recently changed, they do not even export anything using the Packard Bell brand name to North America (much less have any facilities here that would have email handled by AT&T).

I will admit that my eyesight is not what it used to be, but I don't see a US flag anywhere on the Packard Bell homepage:




--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander.


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:11
Reviews:
·SONIC.NET
·Pacific Bell - SBC

said by NetFixer:

said by t3kt3hgrrl:

The issue we have is that a client is trying to send very important emails to people who use ATT/Bellsouth/Packardbell accounts and they will not go through.

AT&T's email servers are used for Packard Bell? I was not even aware that Packard Bell still operated (or sold products) in the US.*

I noticed that as well. As a former AT&T West customer, I have to assume the OP thought that, 'pacbell.net' had something to do with "Packard Bell".

To the OP: The 'pacbell.net' domain belonged to "Pacific Bell Telephone", which was bought by SBC Global in 1996.

In addition, SBC bought AT&T, changing its corporate identity to AT&T, in 2005.

And these AT&T forums are geared to users of the 'at&t Yahoo! HSI service. Their purpose is for user-to-user assistance in troubleshooting problems with the DSL service; and related user account problems.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum


NetFixer
Snarl For The Camera Please
Premium
join:2004-06-24
The Boro
Reviews:
·Cingular Wireless
·Comcast Business..
·Vonage
·Comcast

said by NormanS:

said by NetFixer:

said by t3kt3hgrrl:

The issue we have is that a client is trying to send very important emails to people who use ATT/Bellsouth/Packardbell accounts and they will not go through.

AT&T's email servers are used for Packard Bell? I was not even aware that Packard Bell still operated (or sold products) in the US.*

I noticed that as well. As a former AT&T West customer, I have to assume the OP thought that, 'pacbell.net' had something to do with "Packard Bell".

Actually that confusion is/was intentional. The name "Packard Bell" was a clever gimmick designed to make uninformed people think that there was an association with Hewlett Packard, Bell & Howell, and the multiple Bell telephone companies.
--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander.


SmokChsr
Who let the magic smoke out?
Premium
join:2006-03-17
Saint Augustine, FL
reply to t3kt3hgrrl

Good luck trying to get it removed, the last time I tried (back when AT&T did their own email) I got a nasty gram back from the post master basically telling me to go take a long walk off a short pier. At least it was an actual response from a person.



Mr Anon

@k12.il.us

said by SmokChsr:

Good luck trying to get it removed, the last time I tried (back when AT&T did their own email)...

That's a good point. If the email sending is blocked not the IP, shouldn't the OP be contacting Yahoo?

Also NormanS, made a good point too, you want to find out why you are blocked. If you are not the admin or the sender, you need to get to them and see if you NDR mesages or if the connection logs hold any clue to what is going on. I don't have my resources but there are many places online to check to see if your server is on block lists and some say why.


David
I start new work on
Premium,VIP
join:2002-05-30
Granite City, IL
kudos:101
Reviews:
·DIRECTV
·AT&T Midwest
·magicjack.com
·Google Voice
reply to t3kt3hgrrl

I can work on removing these but keep a few things in mind

1.) be sure to do your homework! if you are on a blacklist somewhere (mxtoolbox is what I use to check-blacklist) you can bet at&t will blacklist.

2.) rDNS delegations- top reason #2 that I find in email exchanges with tier 2 that will earn you a black list. As it was explained to me, rDNS is like having an ID to check when going in the door to a club. Are you who you say you are?

3.) Check all your IP's that are sending- I am working on one now that his mailhost got blocked and his 3rd IP was blocked by SORBS. and mcafee and others had his other IP's listed. because it was a mixed bag all of them got blocked. He currently only keeps checking one.

4.) Clean it up!- ok so your mail server got compromised and you got blacklisted... clean it up and don't make excuses as to why you got blocked or tell me (See note) "it's cheaper for me to contact you and get unblocked than it is for me to deal with it." My answer back was like "Uhhh..."

Note: Yes I got this excuse via email! An @hotmail.com address which makes it funnier!
--
If you have a topic in the direct forum please reply to it or a post of mine, I get a notification when you do this.
Koetting Ford, Granite City, illinois... YOU'RE FIRED!!



nwrickert
sand groper
Premium,MVM
join:2004-09-04
Geneva, IL
kudos:7
Reviews:
·AT&T U-Verse
reply to Mr Anon

said by Mr Anon :

If the email sending is blocked not the IP, shouldn't the OP be contacting Yahoo?

No.

My experience has been that very little is blocked by Yahoo, though it might put email in a users spam box.

Mail to an AT&T address goes first through AT&T servers, then on to yahoo. Most of the blocking is done by AT&T servers.
--
AT&T Uverse; Zyxel NBG334W router (behind the 2wire gateway); openSuSE 12.2; firefox 17.0


NetFixer
Snarl For The Camera Please
Premium
join:2004-06-24
The Boro
Reviews:
·Cingular Wireless
·Comcast Business..
·Vonage
·Comcast

said by nwrickert:

said by Mr Anon :

If the email sending is blocked not the IP, shouldn't the OP be contacting Yahoo?

No.

My experience has been that very little is blocked by Yahoo, though it might put email in a users spam box.

Mail to an AT&T address goes first through AT&T servers, then on to yahoo. Most of the blocking is done by AT&T servers.

Absolutely correct. Yahoo! does the spam filtering, but AT&T still does the incoming email server/IP address blocking since they are indeed still the first to see incoming email to AT&T email accounts. Shown below is a test email I just sent from one of my Comcast accounts to one of my BellSouth accounts to illustrate that is so (for the doubters).


From - Sat Dec 29 19:27:48 2012
X-Account-Key: account17
X-UIDL: AN/FimIAAKrKUN+YgQi0fB2+gvg
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:                                                                                 
X-Apparently-To: myname@bellsouth.net via 98.138.197.223; Sat, 29 Dec 2012 17:27:29 -0800
Received-SPF: pass (domain of comcast.net designates 76.96.62.64 as permitted sender)
X-YMailISG: vBjC_58WLDvZ2.k_sv8Q_uc13XeCBPMGg_l_aSmf1oEHzy6r
 CffWhJjH6eWWVhsoGYW6mI_U3z4.4B8TZJqLQIK0nr5VnpTTpRgjy7SySzdR
 i27ypifOgbMyOjnqQ8rzNRNtAT_718BumH3.IAWAg3uxtOxOuX.oXWE.Eb66
 pgDvzRNTd3ibnT57Z.UNlDXDRxvbyMfnz2YNOPzXr4j6nFvGt7l74VhaMlaz
 8eE0.ZzTu5cQ6t2oI29QvRbnp3sU.BEyN6pKPuh6wXlWOsAcbRhf.uR1gwpl
 f3m4GzKdo9ysXSzlFQEZ6UD.Wsb1F.hvODmUfdeySuTmhA_QS.AVP9ghYr9E
 G9UsFOAZll85lyN0Crl3WVEgdRW1kDlbRlza7RBfCi1DLhkocOp3BwIvFe9A
 ZoRkXXhBRTsbbmFHQJYG9P6n2r0e3pyhO4IgL9eJb6T2rNWt97xiWd5FAmrm
 mmOjxl7GLR7lxr_J5bTV4.44VWR2a8ZiOQ8686GyY_9yJbWd3lT1G9KS5Ucj
 M9LOuR1HilohnwMw7UZ4I7Wb5GuX7DqWkiAWXe02DotaMS0Z7TcCBhzPzbUd
 bUeoARWcBbTswnPOzEIQJOpkDP.Q0h32.M19H4YpQQOBSyBMymPxosXlm08G
 WVda5_em2rxQgUJ4uRiUwCfX5GpHODiOUHY6XBUbPWZmtVDugoFicMXgjrq3
 Y_KJjPHLAf.w6YRpktidSdzldxgvCCGJe_mbZiRhJI3Mm_jm2YIZ9jv4FhTq
 8FAkDdRXrYYIeD6S2_uiyx3a0ECkfBShCzkCtQC.xBDUvy3H2D8aknCMXubE
 nrghG9maKjnxxLc4.W7JBpqmdJk.SH0DejWsn6jUBK.hMMHaFkqFAzftjLXw
 hIU4pPJVIu5LmGYrrQDYqKTVzjRvVxzkP1t7tJw9iWgX1wzJlzDJeg3CfLho
 jvo6h.ejWKTPPREa0JwcadAgpkZDLu6UWD1NeSCETIRTDD6oZHKv3lyG6mXF
 XuGmtZx6bufnDHY7ks65zymPoyGETkc6C57CCKjorW53P76.Yi4.9n6QUfnm
 .T6Eac_8Yds.8J.DESnMkdtycmk-
X-Originating-IP: [76.96.62.64]
Authentication-Results: mta1046.sbc.mail.mud.yahoo.com  from=comcast.net; domainkeys=neutral (no sig);  from=comcast.net; dkim=pass (ok)
Received: from 204.127.217.75  (EHLO fgateway05.isp.att.net) (204.127.217.75)
  by mta1046.sbc.mail.mud.yahoo.com with SMTP; Sat, 29 Dec 2012 17:27:29 -0800
Received: from qmta07.westchester.pa.mail.comcast.net ([76.96.62.64])
          by isp.att.net (frfwmxc05) with ESMTP
          id <20121230012728M0500kopnfe>; Sun, 30 Dec 2012 01:27:28 +0000
X-Originating-IP: [76.96.62.64]
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36])
by qmta07.westchester.pa.mail.comcast.net with comcast
id hdRY1k0020mv7h057dTUKR; Sun, 30 Dec 2012 01:27:28 +0000
Received: from [IPv6:2601:5:c80:91:e291:f5ff:fe95:beac] ([IPv6:2601:5:c80:91:e291:f5ff:fe95:beac])
by omta11.westchester.pa.mail.comcast.net with comcast
id hdTU1k00G2255H93XdTUcC; Sun, 30 Dec 2012 01:27:28 +0000
Message-ID: <50DF9880.3040206@comcast.net>
Date: Sat, 29 Dec 2012 19:27:28 -0600
From: My Name <my-name@comcast.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:16.0) Gecko/20121026 Firefox/16.0 SeaMonkey/2.13.2
MIME-Version: 1.0
To: myname@bellsouth.net
Subject: Test message from Comcast account to BellSouth account
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
s=q20121106; t=1356830848;
bh=WuTsYE9rMYyPcE0VMbLDz8KoWairbzW4b/xqLFojFAo=;
h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject:
 Content-Type;
b=Kq5I+Y9s8ZvNCgCcS8SwhCMFf4qkb5F0g/d/ZusQrIorLHhfTb771uwGLTvUBhWBD
 NDakGxolvzVssKip3j26qPl9o0dTRJ2be2cxYpGzcCFTQykfFm0NyNYMy1mR4FO/QY
 M41CIFmTZBsnO7kxUeo4wBIz75KzKhUR4MSZQTh4jHMngZ9Li4ncsFwizRqbapzHlX
 1l9P+UCkiLVuXexQmIY25PrMNa1aGYYscpncJ14ac+nw2RdstZ3A3Y2KYXmV20GQo9
 fK/Gu4x+OIkt7D/3JVNrTXyjyKxly+6FYATNgatSNHwcUnQUaIY53E+2PC2OcjFvjq
 xoLlNG0IB4zqA==
 
This is a test message from one of my Comcast accounts to one of my 
BellSouth accounts
 


The *.isp.att.net email server gets the mail first, and then relays it to the *.mail.mud.yahoo.com server.

--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander.