AOL Sued For Over-Zealous Blocking

mik writes "America Online has been sued by CI Host, a Texas-based hosting company for defamation, interference with contractual rights and unfair competition. CI Host has been awarded a temporary restraining order, though AOL has apparently not complied. This may be the first such in a series of suits leading up to, perhaps, to class-action status relating to AOL's recent zealotry in anti-spam policy resulting in the presumption that shared-hosting providers are guilty (of spamming) unless proven innocent."

Bout Damn Time

[Sklein382 (615377)]

Now we just need to put together some kind of class action suit for them spamming my regular mailbox with those damn CDs

Re:Bout Damn Time

[kaltkalt (620110)]

They are paying to spam your mailbox with those CDs. They pay for the CDs and the postage. Thus there is a check on how pervasive it can be. Note that you don't get 40 CDs a day from them.

Re:Bout Damn Time

[swordboy (472941)]

Now we just need to put together some kind of class action suit for them spamming my regular mailbox with those damn CDs

I actually called them and asked to be removed from their mailing list and they told me that it wasn't possible because they send the CDs at random. That is, they just pick a few hundred thousand fucking addresses and then spam them with CDs. So I told the representative to whom I was speaking (after I told her that I was not angry with her) what I would do about it.

Basically, anytime I see a stack of AOL CDs at a supermarket or restaurant, I pick the whole damn thing up and put it in the nearest garbage can.

Fuck them.

Oh... and print up some "return to sender" labels and take them to the mail box with you every day. I put them on all postal spam and send it back before I even get it into my house. Junk mail is down about 75% after 6 months or so.

Good luck!

Mail server

[by Anonymous Coward]

I manage the web and email account for the church I attend. The pastor has an aol account, so his e-mail from our server simply redirects to his aol account. Just last week, I found that we had been put on aol's blocklist for some reason - all e-mails being redirected through the server to aol were being blocked for 2 weeks by aol. Blocking messages like this results in missed personal communication. This could possibly result in lawsuits from consumers themselves.

Re:Mail server

[John Seminal (698722)]

Get a different provider if you do not like it. Or you could call AOL and explain to them who you are and what you are doing and hope they let your email server send mail.

And I doubt you could sue. The service provider decides what services you get. It you do not like it, you are free to find another company.

I had AOL for about six months, and it sucked because of all the spam. I left for the opposite reason, that they did little to stop spam.

I would like to see other internet providers follow, especially broadband ISP's.

AOL is going to stomp on CI Host

[signe (64498)]

And I'm going to enjoy watching.

CI Host is a lousy company. I had nothing but trouble with them when I was hosting there. They continued to charge me after I cancelled my account, they refused to issue refunds in a timely manner. I very nearly took them to court over it. CI Host has spammers as customers. I told them about a few that were causing problems for me, and they never did anything about them. Doesnt' surprise me, because their customer support is poor, bordering on non-existant.

AOL is going to turn around and clean them out in court, and I'm going to thoroughly enjoy it. All they have to do is point to a few CI Host customers that spam, and that CI Host has been notified of several times, and it will either be a wash (in which case, AOL wins because they can stand the legal fees better than CI Host), or AOL will be able to counter-sue without a problem and make CI Host feel the hurt. Either way, I say yay AOL, which is something that I don't often say.

-Todd

Re:AOL is going to stomp on CI Host

[Stephen Samuel (106962)]

I very nearly took them to court over it. CI Host has spammers as customers. I told them about a few that were causing problems for me, and they never did anything about them.

You might want to provide an affidavit to AOL on this. CI appears to have gotten their injunction on the basis of that they've got a really tight anti-spam policy. If they're providing support to commercial spammers, then AOL has (or should have) the right to block them.

I think that it may be something different about what AOL support is saying about CI hosting... It's one thing to simply report that AOL gets to much spam from CI customers -- it's another thing to call them spam bags.... (although I really like the term).

Spamming is illegal in many states, and congress is looking at making it nationally illegal. To say that you have a right to spam is silly.

Spamming is all about finances, and refusing to route IPs from a hosting company that supports spammers is a way to shift the finances against them allowing spammers on their net.

CI Host has been good to me

[budcub (92165)]

I've been a happy CI Host customer for almost two years. My domain gets very little traffic, but the few times I've had to call for support, they've been quick and very helpful.

Re:AOL is going to stomp on CI Host

[junkdomain (701522)]

I agree, CI host seems to be full of hypocrites. I work for a small Texas based ISP. CI Host spammed our customer base and null routed the netblocks that our nameservers were on to keep people from replying. It took months to get the route removed and when we finally got to an engineer, they had no idea why it was there. Obviously a favor by an engineer for a marketing/sales guy.

The good news, we only lost one customer, who came back a few months later after they realized how bad CI Host actually was.

Re:AOL is going to stomp on CI Host

[signe (64498)]

No, this wasn't just auto-renewal. I cancelled within the first month because of the massive downtime and lack of support, so I was supposed to get that month back (by their guarantee). It took me 2 months (during which they did not charge me) to get that refunded back, and the only way I did it was by disputing the charge with my card company.

The week after they refunded it, they charged 2 months' service to my card. It could only have been to "recoup" the money that the credit card company "took" from them. I started talking to them about that, and the next month they charged my card AGAIN. I had to change the number on my card. I had to dispute it with the card company again. After a couple more months, I finally got my money back again. And I'm sure that if I hadn't changed my card number, they would have continued to charge me again.

And this doesn't even cover the support issues and downtime. Just the fraudulent billing.

-Todd

Stupid

[asavage (548758)]

If it is your own network and you aren't the government, you can block whatever messages you want.

At least AOL can defend itself

Re:Stupid

[ThatDamnMurphyGuy (109869)]

How is choosing what to filter against the law?

For the same reason Microsoft can't do what they want with their OS to a certain extent: antitrust laws and the fact that AOL IS a monopoly in the ISP market for the most part. Sure, there is Earthlink and the like, but when the Giant in any arena gets as large as AOL's subscriber base, they have to play by a different set of rules.

CI Host does indeed suck

[SkoZombie (562582)]

I had the misfortune of having a dedicated server with them for 2 long years. The machine would lock up frequently, and i'd have to make a 30min call from Australia to the US to listen to their on hold crap so i could talk to a tech and then try and convince him to hit the big red button.

CI Host has a huge marketing and sales department and tiny tech support division. Dont you dare, ever, believe a word of their marketing crap. They suck. Pure and simple. They've cost me thousands because of the clients i've lost because of their incompetence. Some of the people are nice enough but they simply dont have the technical skills of other places.

I'm now with rackspace.com and they kick arse!

Any filtering is too much

[localghost (659616)]

I'd rather spam filtering be left to myself. Any decent e-mail client has the capability for filtering, and by doing that way, I have control over what gets thrown out and what doesn't. I would not trust AOL to tell my what e-mail I should and shouldn't read. That, of course, is one of the many reasons why I would never be an AOL customer.

Re:Any filtering is too much

[Frater 219 (1455)]

I'd rather spam filtering be left to myself. Any decent e-mail client has the capability for filtering, and by doing that way, I have control over what gets thrown out and what doesn't.

There are substantial disadvantages to a client-side filtering only spam defense as opposed to a server-side blocking only defense. It is, of course, fully possible to use both; I merely wish to point out some factors you may not have considered.

For the definitions of "filtering" and "blocking", please see this Wikipedia article [wikipedia.org]. Roughly, DNSBLs and Sendmail's milter feature are blocking tools -- they take effect during the SMTP transaction. Client-side tools are filtering tools -- they take effect when you check your mail.

Consider:

• Client-side filtering destroys false positives rather than bouncing them. Any spam defense can have false positives, in which non-spam email is incorrectly classed as spam. When a mail server doing blocking experiences a false positive, it returns an SMTP error to the sending system. Ultimately, the human sender sees a bounce message, which indicates that their message did not make it to the intended recipient. The sender can then attempt to get around the block (by sending from another site) or can try to contact the recipient by other means. However, when a client-side filter has a false positive, the mail is either deleted or filed in a rarely-seen "spam folder". The sender gets no notification that it will not be seen (or not seen promptly). Since false positives do happen, it is better that they not happen silently!
• Client-side filtering isolates and hides useful information. A mail site, particularly a large one such as AOL, is in a position to gather a great deal of information about spam sources and patterns. Users complain about receiving spam. If a site can cause these complaints to be expressed in a useful way (such as sending full headers to an abuse address) rather than a useless one (such as cussing out the helpdesk), the site can aggregate a huge amount of information about spam offenders, which can be used to the whole site's spam defenses (or to mount litigation or prosecution of spam offenders). In contrast, your client-side filtering is informed chiefly by your own experience, and has no access to the experience of the other bazillion people on your ISP or mail site.
• Client-side filtering doesn't alleviate large mail sites' resource problems. A site such as AOL dedicates significant amounts of disk space, backup capacity, and network bandwidth to email. Since over half of AOL's incoming email is spam, if AOL did no blocking then it would probably spend over twice as much money on these resources than it would on a spamless Internet. In client-side filtering, mail must be delivered to the user's mailbox on disk, and the user must then check his mail, before any spam is removed from disk. If that spam were blocked at SMTP time, however, it would never have occupied AOL's disk and never consumed those resources.

However, as I mentioned above, it is possible to combine blocking and filtering in useful ways. A mixed strategy is what I prefer for my own site: we use a number of blocking strategies (such as DNSBLs and regular-expression patterns matching common spam elements), but we also use SpamAssassin and encourage users to filter with its scores or other criteria.

They should sue the spammers for $ damages

[kaltkalt (620110)]

Seriously. I realize AOL has the deep pockets, but the spammers are the cause of AOL's blocking email from the domain. The spammers, not AOL, are responsible for any monetary damages the plaintiff here suffers. Public policy dictates that AOL should be immune and the spammers who spammed from that address should be liable. Does everyone have the right to send email to AOL addresses? I would say no, although AOL should have to say "hey, when you have an account with us there are people who will be unable to email you."

AOL is free to do whatever they want.

[John Seminal (698722)]

People are also free to chose whatever provider they want. The only downside I can see is if someone brings up an "Interstate Commerce" violation- congress has the power to regulate commerce between the states, including internet sales. But as long as AOL does not stop people from pointing their browsers at whatever stores they want, I do not see how anyone can win a lawsuit.

I personally think it is good that someone is trying to block spam. Now if they could validate forged headers.

Re:AOL is free to do whatever they want.

[kaltkalt (620110)]

a private company can't violate the commerce clause.

In my opinion CI Host are scum

[augustz (18082)]

Don't be to quick to defend them.

http://www.forumhosts.com/cihost.htm for a taste of what these guys are like.

http://www.stevemaas.com/selbstbild/archives/000 27 3.html is another link.

Let's hope to god the EFF's and Timothy don't fall for their lawsuit stuff.

More of AOL's anti-spam zealotry is a good thing (I speak as someone who has had something like 10,000 emails blocked by them in the past few weeks).

I'm now definitely a proud customer....

[heXXXen (566121)]

Been with CI Host for awhile, pretty good network, really like the price too.

Also, AOL/RR is blocking email from my office (Sprint SHDSL, fiber optic DSL, faster than T1, business only stuff in case you weren't aware). Ever since I got the first bounced message AOL has been #1 on my shit list.

Bravo, CI Host, Bravo.

Odd..

[WhiteHatDave (701509)]

Being as I at one time worked in the abuse capacity for a ISP. Although AOL may have over zealous policies as of late they do have a postmaster number which they could call and have the validity of the block checked. I had done this in the past and had resolution in ~24hours.

Oh, the irony.

[faedle (114018)]

"C I Host is very aggressive about attacking the spam issue," Faulkner said. "C I Host does not spam, and we don't tolerate spamming by our clients," said Faulkner. "In fact, we were one of the first Web hosting companies to install spam filters that our clients cannot turn off. This week alone our spam filters blocked over 16 million spam e-mails.

Am I the only one that finds this ironic? It's not okay for AOL to filter spam, but it's okay for us to. Uh huh.

Re:Oh, the irony.

[kaltkalt (620110)]

Well, I'm sure in response, they would say "we're not saying spam filtering is wrong, we're saying blocking huge domains and refusing to narrow it down even when it's been pointed out the spam didn't come from us is wrong."

People really need to learn what the words "irony" and "hypocrisy" really mean. These two words are used interchangeably for any situation that sounds sorta funny.

ci host == bad isp

[asv108 (141455)]

Just do a quick /. search [slashdot.org] to see what people think of ci host. I was a ci host customer back in 99/2000 when their whole accounting database was open to the internet, customer information and credit card numbers. There were $5000 of fraudulent charges on my check card around the turn of millenium from my information being readily available to any idiot with a web browser. The bank took care of everything but it was a pain the in ass.

Just had to say

[Faust7 (314817)]

C I Host, one of the world leaders in Web hosting and Internet solutions, was awarded a temporary restraining order against America Online

I can't be the only one that finds the concept of an online restraining order more than a little amusing.

For all the "Good for AOL" people

[Kostya (1146)]

If you don't run a webhosting company or an ISP, shut up. If you run a webhosting company or an ISP, you know how crappy AOL's system is.

Consider if you have an AOL client who has a site on your hosting server. They forward their site mail to their AOL account. Their site account gets spam. What happens? Well, the spam gets forwarded, the clueless AOLer reports it as SPAM, and AOL's system sees your hosting server as a spam source. There is nothing you can do to protect your hosting server. Nothing.

This really happens. If you call AOL, they basically say it isn't their problem. If an AOL client thinks a mailing list email they signed up for is spam, then AOL thinks it is spam. They tell you to setup a feedback loop where they send spam reports, but you have no way to respond to AOL. You just get flooded with tons of reports by clueless AOL users with no way to tell AOL, "Hey, this isn't SPAM!"

Only on two occasions where a client had an exploited formmail script did the AOL system work as it should (i.e. spam was reported, we saw the report and found the problem). Every other day of the week, it is a massive time-sink that you get nothing out of.

AOL wanted to make up for sucking on the SPAM front. So they become complete asses and made the job that much harder for the rest of us. Bravo!

I hope the class-action suit makes them stop. I don't expect anyone will see any money, but at least AOL will be held accountable for being such idiots.

Re:For all the "Good for AOL" people

[Dimensio (311070)]

I understand your desire for AOL to lose. After all, they have a contractual obligation with CI Host to carry their e-mail.

Oh, wait, they don't. They're a privately owned company and they have the right to drop any mail traffic that they choose, even if the reasoning is completely stupid (though in the case of CI Host, it isn't). I guess that you believe that the government should be dictating how people run their private networks, including accepting the additional costs of spamming just because it makes spam-friendly ISPs feel bad when their packets get dropped.

You've got mail!

[beacher (82033)]

From: State District Judge Bonnie Sudder [e-mail]
To: [e-mail]; [e-mail]
Subject: AOL, Save Thousands in Under One Minute! Quickest Quote!

Dear AOL,
This is your chance to opt-out of a completely unique program! You May Be Closer (Maybe Hours Away) To Financial Punishments than you think...
* 100% Safe To Take, With Abosultely No Side Effects
* Totally confidential, no one needs to know!

Uh, since when you HAVE to provide service?

[PierceLabs (549351)]

I mean really, this could easily be levied against anyone blocking spam in that case. If its their servers and their bandwidth and you're violating their terms of service, I don't see why they HAVE to deliver email or anything else. Heck MSN is effectively blocking linux with the way they respond to search results through their search engines and you couldn't bring a court case against them about that. If CI Host (which really DOES suck and consists of mostly spam and porn hosts)) can't contain their customers - why would AOL be liable if they choose to protect their systems? Last I heard the laws about Cybertresspass (the very laws AOL used to sue spammers - denial of chattel) were in AOL's favor - not CI Hosts'.

Good! AOL is non-compliant anyway...

[bourne (539955)]

Among other petty annoyances, AOL is incorrectly refusing connections from blacklisted hosts, as follows:

$ telnet mailin-01.mx.aol.com 25
554- (RTR:BB) The IP address you are using to connect to AOL is a dynamic
554- (residential) IP address. AOL will not accept future e-mail transactions
554- from this IP address until your ISP removes this IP address from its list
554- of dynamic (residential) IP addresses. For additional information,
554 please visit http://postmaster.info.aol.com.

According to RFC 821 [ietf.org] (sections 4.3 and 4.2.2), the server can respond to new connections in with a 220 ("let's dance") or a 421 ("go away, I have a headache") response. Not a 554 ("you're lousy in bed") code. Among other things, the manner in which they reject mail from residential IPs causes it to languish in the queue, rather than bouncing as it should if they intend to permanently refuse delivery.

I'm sure they do this intentionally so that it will look like your mail server is at fault ("sorry, couldn't get through") rather than theirs ("buzz off, I don't like your IP address").

AOL is RFC-compliant; you have an archaic RFC!

[Frater 219 (1455)]

According to RFC 821 (sections 4.3 and 4.2.2), the server can respond to new connections in with a 220 ("let's dance") or a 421 ("go away, I have a headache") response. Not a 554 ("you're lousy in bed") code.

You're citing an out-of-date RFC. 821 was superseded by RFC 2821 [faqs.org], which makes it clear that 554 is a valid connection-opening response, to indicate that mail service is not available. (Indeed, 2821 spells out two codes for use at connection establishment -- 220 to accept, or 554 to reject access.) AOL is correctly using 554 to indicate that it will not provide mail service to your IP address.

A 4xx code would be improper in this case. 4xx codes indicate temporary failures. They mean that the client should queue its messages and retry them later, rather than returning a bounce message to the sender. That's not what is intended here -- the server doesn't want you to retry, it wants you to not try. A 5xx error code is correct.

CI Host

[suwain_2 (260792)]

For those thinking that CIHost sounds like some insane overlitigous company that tries to use lawsuits to make its profit... You're right. :)

I spend some time at WebHostingTalk.com [webhostingtalk.com] (a huge forum site for web hosting), and they have a horrible reputation. Actually, you can't search for "CIHost" -- it's banned, apparently due to WHT itself being threatened with legal actions because of posts about CIHost in the forums. But I've read some posts about "See Eye Host" and such. :) You can play with the search and creative misspellings, and you'll find a lot of posts about them.

Much as I hate AOL...

[petard (117521)]

I hope they win this one. First of all, CI Host are a bunch of f$cking spambags [google.com]. Second of all, it'll be a dark day when a court forces someone to carry unwanted traffic. AOL owns their own network. AOL can decide who they want or don't want to accept mail from, for whatever reason AOL wants. If AOL customers don't like AOL's decision, they'll leave, and AOL will lose in the market. Oddly enough, only spammers seem to have any trouble grasping the fact that a network owner can restrict what flows over said network for any reason at all.

Free advice to CI Host: Your legal action has just landed you permanently on hundreds of private blocklists. I know of at least 5. You and your customers now going to have a lot more trouble getting your mail deliverd to many more places than AOL. Find a new line of work because no netblock you are associated with will ever be useful for email, which you indicate to be your main line of business in your lawsuit. Cut your losses and get off the net now. Sell your equipment on eBay. Sell your netblocks back to ARIN. Do something productive. You'll be happier if you avoid the world of frustration you just entered. Just unplug instead.

About time...

[smash (1351)]

As I see it, AOL should be able to do what they like with regards to data entering/exiting their network, and in fact, I'm willing to bet dollars to donuts that they have words to that effect in their customer contract.

So, given that their users have signed up consenting to this, the only people who can legitimately be pissed, are third parties - who have no right to use AOL's network at all.

nutter.

AOL mail filtering to the extreme

[japorms (559865)]

I work for an ISP (holding the name for obvious reasons). We recently had a customer abuse our AUP by sending 3,000+ unsolicited emails with attachments to AOL customers in just one week (total emails reached ~18,000). AOL in turn blocked any and every email with attachments from our domain indefinitely. Our legal team is now trying to resolve this issue with them. Even though emails without attachments go through fine, it has become a huge inconvience for many our customers. I don't understand why they did not block the specific account only instead of our domain. The following is the rejection notice we receive when sending emails with attachments to *@aol.com: > ----- The following addresses had permanent fatal errors ----- > > > ----- Transcript of session follows ----- > ... while talking to mailin-02.mx.aol.com.: > ... while talking to mailin-03.mx.aol.com.: > >>> QUIT

Re:AOL mail filtering to the extreme

[RipCurl808 (672919)]

Its their servers and if you still kept the person on your server ( as a customer ) after the the first day of the abuse ( says you took 1 week to notice; that's far too long to notice an abuse ). Did you not read your Abuse@ when the first spam message was reported? Why'd it take you so long to act?

A spam run doesn't just happen for a week long without going unnoticed. Your server logs would have shown the unusual amt of traffic being sent from your space.

Just playing devi's advocate. Again, AOL can run their servers as they like. Dont like it? Set up a smart-host so you can send attachment from that ip unti lits resolved.

Oh and is that customer still with you? The one that spammed? Why not collect damage fees from them?

From Rutgers University

[mikeage (119105)]

One of our TD guys posted the following:

We just finished a conversation with staff from AOL's postmaster team. We have an agreement, but it may or may not be satisfactory to users.

First, let me say what they are doing. They have a button on their mail software that lets users report email as spam. They check to see the host
from which AOL got the mail, i.e. the previous hop. In principle, if they get a significant number of complaints for any given host, they refuse to accept mail from it. In practice, there is sometimes human review, although they don't guarantee to do that. In practice, they will often alert [e-mail] before cutting off mail, although they don't promise to do that either. They will, however, allow us to give them a list of our major MTA's, and exempt that list. What we believe they will do reliably is notify us after the fact when they have cut an IP address off. We will dispatch those reports to the liaison.

They should have most of the major MTA's by now. However we don't have a complete list of all MTA's on campus, so it is certainly possible that in
the future some might be cut off. If that happens, we will find out about it after the fact. In some cases, the abuse staff may recognize it as an
MTA, and ask them to add it to the list. However we won't always know the way departments use systems, and thus cases might occur where we would have to depend upon responses from the system administrator.

Note that in principle they could remove systems that send announcements to the user community, if users report the messages from the President or
other official email as spam. They regard the customers as right, and accept their definition of spam. In practice, that system will be on the
list of MTA's. For the moment they look OK.

There are some systems that were on earlier lists that we have been unable to understand. In one case we verified that they had no forwarding entries pointing to AOL. The system itself is not an open relay, and being Solaris, would not have been contaminated by Sobig. In the discussion today, it didn't seem possible to develop an understanding of what had led to these systems being considered problematical. However those systems are MTA's, and should not be cut off in the future.

They have offered to send us all email from any Rutgers host that users report as spam, so we can review it and try to forestall any problems.
Since this is in the thousands per day during periods when problems are occuring, we are not currently taking them up on this. In the opinion of our staff, if AOL can't afford the staff time to do intelligent review of their own users' reports, we can't do that job for them.

In this situation, I recommend that no system administrator use AOL for email, since we need to make sure we can contact sysadmins no matter what
decisions AOL might have made. Other uses with critical need for mail connectivity might want to do the same. Also, it might be useful for users
to understand that they should be careful about reporting as spam mail that comes through Rutgers.

Re:Anti-spam zealotry is a good thing

[Rellik66 (596729)]

wait a sec, I thought we hated AOL on even numbered days.

Re:Anti-spam zealotry is a good thing

[Ravensfire (209905)]

But this is an odd numbered day, so we like AOL.

Re:Anti-spam zealotry is a good thing

[NanoGator (522640)]

"But this is an odd numbered day, so we like AOL. "

Wait a sec. Today's Monday. Is Monday a 1 or a 0?

Do you have to ask?

[YrWrstNtmr (564987)]

Today's Monday. Is Monday a 1 or a 0?

Monday is definately a zero.

Re:Anti-spam zealotry is a good thing

[Kaeru the Frog (152611)]

What timezone are you in? 23 hours a day someone could bash AOL.

Re:Anti-spam zealotry is a good thing

[EvilAlien (133134)]

Ya, I need another copy of the /.drone handbook. I'm not sure what to do here... we hate spam, but we hate AOL, but we like security, but we hate restrictions on our (ab)use of broadband, but we support the rights of network admins to admin their network, but we like freedom, but we hate government interference, but... *bzzzt*

> ERROR
> KERNEL PANIC

Re:Anti-spam zealotry is a good thing

[by Anonymous Coward]

AOL are a bit zealos with their blocking. Worse there is no apparent (from what we could see) removal process or information on *why* you were blocked.

I maintain a few mail server that a number of customers of ours use to send out mail. We have a non-spam TOS and we check up on our customers. We got blocked. We went on to complain to a mass of different addresses. We got a two replys a few days later, the most notable was one from an address that didn't exsist (at aol.com) scolding us for not providing information that we had actually provided in our barrage. The other was just as worthless (telling us to read the usless help) though a reply to it didn't bounce.
Then as mysteriously as we went on the RBL we came off it again. To this day we are still cluless as to how we got on this RBL or how we got off it.

Worse though is Excite. There RBL is entirly hidden. No URLs, no help, no reasons, no nothing. We have had NO reply to our barrage of mails after a week and a bit. We even opened an account and complained as a customer. So we have taken to re-assigning our SMTP sender's IP address. I'm sure they will block that too, but we have a /19.... we can play this game for a while.
Maybe I should see if we can sue Excite....

>

Re:Anti-spam zealotry is a good thing

[Zeinfeld (263942)]

AOL are a bit zealos with their blocking. Worse there is no apparent (from what we could see) removal process or information on *why* you were blocked.

There are several separable issues here.

The first thing to notice is that our only information on this dispute comes from a press release put out by CI-host. I find it somewhat surprising to see it alleged that AOL is in contempt of court. On the other hand one wonders how a judgement from a Texas court affects AOL off in Loudoun county VA. I suspect the AOL/Time lawyers may have a different opinion.

Another thing missing from the report is any mention of the reply filled by AOL? Was AOL even aware of the hearing? In most cases a court order does not have immediate effect, thus allowing the defendant to file an appeal. It seems unlikely that a court would issue an order with immediate effect given that AOL has had considerable success in preventing spammers gaining orders of this type in the past.

Another suspicious factor is the rapid escalation to littigation. A legitimate ISP would be unlikely to sue until it was clear that AOL was not going to be reasonable - unless of course they knew AOL was being reasonable.

At this point it is reasonably settled law that an ISP cannot be forced to accept email from an address that it does not want to service. The defamation claims might work against a third party such as a blacklist but it is hard to see how a company can be prohibited from acting on its own assesment of CI's behavior.

The other thing that is odd here is that Sudereth is a recent President of the American Judges Association. You would not expect a judge in that situation to be making whacky judgements which suggests strongly that there is something here that we are not being told in the CI PR puff. It is very rare for a court to order an injunction with immediate effect unless the damage done is irreversible. In this case the effect is very obviously only money.

Re:Anti-spam zealotry is a good thing

[bobetov (448774)]

My mom, using Earthlink, has been unable for 4 days to email her business partner. Which is wasting her time. Preventing her from getting work done.

The thing to realize here is that, while punishing an ISP may or may not be a good thing, harming *tens of thousands* of innocent users of that ISP (and Earthlink is a good one, IMHO) is incredibly irresponsible.

The bounce email said basically "Go whine to your ISP" which was, frankly, insulting. Never having been a fan of AOL, I'm not really surprised by this, but I can tell you it's caused her business partner to drop his account damn quick. Hope other AOL customers are doing the same.

Email is critical infrastructure. It's a public communication medium just like telephone lines are. How would you like it if all Bell South customers couldn't call you because your regional Baby Bell didn't like dealing with all the telemarketing coming in from Atlanta?

At a certain point, services become too valuable to play this kind of game with. I think email has passed that threshhold long ago.

am I your enemy?

[SHEENmaster (581283)]

I am on a small ip block, with losers that catch the latest winshit worm and start spamming every few weeks.

Because of this, AOL has blocked my mailserver despite 7 requests to whitelist it (3 from myself, 4 from AOL victims^H^H^H^H^H^H^Hconsumers). It gets whitelisted for a few days, then group punishment kicks in and it's blacklisted again.

I have never spammed, I never intend to spam. Getting accused of sending half a billion unrequested emails in half an hour from a upstream as small as mine is both hilarious and insulting.

Fighting spam is one thing, blanket bombing to prevent spam is quite another. If anyone at the evil empire's apprentice is reading, "Hope you're glad that my dad left you because of your stunts. See you in court."

Bullshit

[GojiraDeMonstah (588432)]

Anti-spam zealotry is a good thing

A good friend of mine is no longer able to send her regular op-ed piece to AOLers due to anti-spam zealotry. She can't reply to her subscribers when they write and ask why she's stopped sending it. She's even blocked from emailing AOL tech support to ask why she's blocked in the first place.

Arbitrarily cutting off an entire ISP with the inexplicable finality AOL has shown towards several ISPs isn't making the world a better or more spam-free place.

Repeat after me: arrog

Re:Anti-spam zealotry is a good thing

[PktLoss (647983)]

I don't know, I am tired of over zealous spam lists, network admins, strange anti-spam mechanisms.

Recently, one of our mail servers got listed with a major spam list with a major time lag. It was allowing open relay (but was never used for nefarious purposes) 6 months ago, and this was resolved 3 months ago.

As a result, all of the mail that was sent to paying Road Runner customers was bounced back, this was mail that was requested, and mail they had just paid to receive. I attempted to forward from my ISP, but lo and behold, my personal ISP (different country than our corporate mail servers) had also been blocked by Road Runner.

I attempted to email Road Runner to get more information, but got standard auto-responders that didnt answer my question.

I ended up mailing the paying customers via my webmail account on my personal domain.

We lost about six accounts to refunds over non-recipt of information, since it took us a week to figgure out what was going on (mails are sent from an unmonitored account).

Also:
Most non-technical users don't know how to properly manage opt-in spam blockers (the ones with auto responders pointint you to websites where you can fill out all your personal information, your mothers maiden name, and perhaps the person might deem it acceptable to let your mail in). They sign up for things, dont add the posted address to their list, the mail gets blocked, so they email us complaining, not bothering to add the email address they just messaged to the allowable list. With the current virii going around, spoofing return headers, I just dont have the time to wade through all the mailer daemon/postmaster/spamblocker/virus blocker emails comming in.

ISP Level Spam blockers MUST:

• Allow users to turn them on/off
  
• Allow users to view blocked mail
  
• Provide external groups with EXACT information on why a message was blocked, rather than pawning off responsibility to some Not-For-Profit.
  
• Respond to queries from external groups within 1 business day, either with removal from lists, or more detailed information
  
• Upon removal from a blocked list, spam cached within the past week from affected senders should be forwarded with an attached apology header.
  

Re:Anti-spam zealotry is a good thing

[Gherald (682277)]

> So what do you call getting numerous AOL installation CDs?

Untargeted marketing.