AT&T Mail Blocks

[ebell]

Originally Posted by GatorRichard

There's no way to escalate this if AT&T and its subsidiaries don't recognize there is a problem. I've gotten at least a dozen reports where AT&T/SBC/Bellsouth have stated in so many words "there is no block in place".

This is easy to prove by the bounced messages. If it is hitting their servers and bouncing...this is why I stated that two heads are better than one...PROVE to them it is a problem! (Problem #1)

Sorry for the "frustration," but as you stated this (blacklisting) happens to everyone; however, it usually does not take a week to get off the list. (Problem #2)

[GatorRichard]

Originally Posted by Goddess Dix

i have a question: are you getting cleared in roughly the same order as you're sending in the requests?

i was notified that you requested my dedi be delisted on monday and am still getting bounces. i certainly don't have a problem with waiting because, well, it takes what it takes, but am wondering at what point i should update my ticket and/or try to follow up? frankly, i have very little trust for the efficiency of their system at the moment...

I have no real idea, they're coming in such small batches its hard to tell how they're doing it. It seems like they're just doing whatever comes in to their request queue (I have no idea how this is set up).

[GatorRichard]

UPDATE

This is now my second or third time calling AT&T this week, each time I get different information. This time however I was told a funny quip from the CSR on the phone:

"Sir, we don't have a Postmaster Department."

Shoot, could've fooled me. She transferred me to her supervisor who sort of confirmed that there is no central Postmaster Department despite what I'd been told earlier this week. He's going to contact some internal personnel and call me back today as I laid it on pretty thick that I've been trying to get in touch with someone all week to no avail.

Here's to hoping. This is turning into the Yahoo fiasco all over again.

[GvilleRick]

Reminds me of the old SNL sketch. I found the transcript here.

Here at the Phone Company we handle eighty-four billion calls a year. Serving everyone from presidents and kings to scum of the earth. We realize that every so often you can't get an operator, for no apparent reason your phone goes out of order [plucks plug out of switchboard], or perhaps you get charged for a call you didn't make.

We don't care.

Watch this - [bangs on a switch panel like a cheap piano] just lost Peoria.

You see, this phone system consists of a multibillion-dollar matrix of space-age technology that is so sophisticated, even we can't handle it. But that's your problem, isn't it ? Next time you complain about your phone service, why don't you try using two Dixie cups with a string.

[loud, booming "Liquid Plummer" voice-over] We don't care. We don't have to. We're the Phone Company.

(Text source: "Saturday Night Live: The First 20 Years", 1994 Cader Company.)

[dave g]

Originally Posted by GatorRichard

Snipped.....

It's a good idea but it's also impossible to know which IPs are blacklisted at the time of an SMTP transaction. AT&T provides no public query system so we can't query that and then switch to another IP if the current one is listed. That's actually the very reason we're having to rely on customers to send us bounces, we have zero way of checking these.

So insted of flooding support with blacklist info how about posting here as I did in a previous post? I have another list if you interested? Would it help?

Dave G

[GatorRichard]

Originally Posted by dave g

So insted of flooding support with blacklist info how about posting here as I did in a previous post? I have another list if you interested? Would it help?

Dave G

I prefer support requests because it offers a much easier 'paper trail' for us to follow and track. Plus it adds a higher level of accountability which is something I take very seriously.

[dave g]

Originally Posted by GatorRichard

I prefer support requests because it offers a much easier 'paper trail' for us to follow and track. Plus it adds a higher level of accountability which is something I take very seriously.

GatorRichard 3 block reports on there way.

Dave G

[GatorRichard]

UPDATE

The supervisor from AT&T Internet Services did call me back but did not have any news to report. His contacts had left for the day so I won't get any information from him until at least Monday.

However, a work-around for this is to use port 465 in your email client if you are using one (many people reporting issues are). This will get the emails delivered.

[dave g]

Originally Posted by GatorRichard

UPDATE

The supervisor from AT&T Internet Services did call me back but did not have any news to report. His contacts had left for the day so I won't get any information from him until at least Monday.

However, a work-around for this is to use port 465 in your email client if you are using one (many people reporting issues are). This will get the emails delivered.

GatorRichard

I know this has been asked before but for the life of me I can't seem to find it.

How do we get around the security warning in Thunderbird?

Dave G

Originally Posted by dave g

GatorRichard

I know this has been asked before but for the life of me I can't seem to find it.

How do we get around the security warning in Thunderbird?

Dave G

1. From the Thunderbird toolbar, select Tools > Account Settings. The Account Settings window opens.

2. In the Account Settings window, in the left column, select Outgoing Server (SMTP). The Outgoing Server (SMTP) Settings display.

3. Select the account and click . The SMTP Server window opens.

4. In the Settings area, in the Port field, Change 25/26 to 465.

5. In the Use secure connection field, select the No option.

6. When you are finished, click OK. The SMTP Server window closes.

7. In the Account Settings window, click OK. The Account Settings window closes and the SMTP port is changed.

I hope this solves your problem..

[dave g]

Originally Posted by GatorNasser

1. From the Thunderbird toolbar, select Tools > Account Settings. The Account Settings window opens.

2. In the Account Settings window, in the left column, select Outgoing Server (SMTP). The Outgoing Server (SMTP) Settings display.

3. Select the account and click . The SMTP Server window opens.

4. In the Settings area, in the Port field, Change 25/26 to 465.

5. In the Use secure connection field, select the No option.

6. When you are finished, click OK. The SMTP Server window closes.

7. In the Account Settings window, click OK. The Account Settings window closes and the SMTP port is changed.

I hope this solves your problem..

Nope no luck I found that the Use secure connection field, SSL needs to be selected or else you get a SMTP error when sending. Any other suggestions?

Dave G

[GatorTeddy]

Do you know what gator box you are on? If you use port 465, you need to use SSL and use the shared server certificate for the service. If you know what gator box you are on you can use, secureXXX.hostgator.com for the outgoing mail server.

[Goddess Dix]

Well, I'm finally cleared today! Whew. Will still be watching for info on what caused this mess, though...

[Rockoids]

This past weekend I ran my two regular mailings (a pair of weekly newsletters), and everything worked fine.

I'd also like to recommend a great new mailing list package for you folks that's not only neat-looking but has a mostly great interface, bounce handling, etc., etc. It beat the pants (or panties ) off phpList.

Check out:

http://dadamailproject.com/

[mp3]

I looked around and didn't see another thread on this topic, so I thought I'd post this here.

I have a bounce notice from Monday:

SMTP error from remote mail server after initial connection:
host relay.verizon.net [206.46.232.11]: 571 Email from 74.54.131.2 is currently blocked by Verizon Online's anti-spam system. The email sender or Email Service Provider may visit http://www.verizon.net/whitelist and request removal of the block.

Should I open a ticket for this?
(It may actually be resolved, I haven't attempted to send to Verizon again - yet).

EDIT: I rarely send out any email, just a few messages a month.

[Goddess Dix]

yeah, you'd need to open a ticket, even if it was connected to the mass thing at at&t (and it doesn't appear that it is, since it's verizon). that lets hg review what's going on with it and take any necessary action to solve potential issues before requesting the removal...

[mp3]

Ah thanks, I'll open a ticket.

[GatorRichard]

UPDATE

OK well, the supervisor didn't call me back on Monday or Tuesday, I'm surprised at this. However, the reports we've received this week show a marked decrease in problems for people. They're still occurring but in a much lower frequency than before. None of my emails to AT&T or Bellsouth regarding any changes have been answered and probably won't be (unless they manage to get around to it in a week or so).

I'm going to try calling the same supervisor again as it'll be a shot in the dark since he wouldn't give me a direct line.

[Goddess Dix]

i'm betting they got bombarded with complaints, richard, and if the supervisor won't give you a direct line, i also wouldn't be surprised if they wouldn't like to avoid the whole issue. i mean, c'mon, you know? evidently, he doesn't want to be the point of contact for it.

but perhaps the badgering got them to step up our removals...

[GatorRichard]

Originally Posted by Goddess Dix

i'm betting they got bombarded with complaints, richard, and if the supervisor won't give you a direct line, i also wouldn't be surprised if they wouldn't like to avoid the whole issue. i mean, c'mon, you know? evidently, he doesn't want to be the point of contact for it.

but perhaps the badgering got them to step up our removals...

You're more than likely right. This is the same thing that happened with our Yahoo issue a few months ago. They simply got flooded with thousands upon thousands of requests and silently dropped all the blocks without so much as a reason why it happened in the first place.

[dave g]

So does anyone think we could start a class action law suit for denial of service against AT&T/SBC/etc...?

Dave G

[Rockoids]

Originally Posted by dave g

So does anyone think we could start a class action law suit for denial of service against AT&T/SBC/etc...?

Dave G

It's a silly proposition. The only people who gain from class-action lawsuits are the lawyers.

[dave g]

Originally Posted by Rockoids

It's a silly proposition. The only people who gain from class-action lawsuits are the lawyers.

But don't you think it would make SBC/etc.. think twice about making changes to there email system, as much as I dislike lawyers, let them make some money, or maybe we can find one to do it for free.

Dave G

[Goddess Dix]

Uh, no, I wouldn't be interested in a legal attempt to hold companies somehow liable for blocking mail in an attempt to thwart spam. I block mail in an attempt to thwart spam. And I believe wholeheartedly that it's up to ME to decide exactly how to do that. The accountability comes from my customers.

I'm more than happy to get on with my life now that my email is getting through. While I would have liked to know the cause, it's more out of curiosity than the drive to "take action" somehow.

[dave g]

It was just a thought.

I also would like to know what went on, but I don't think we will ever find out.

Dave G