They're charged with overcharging on their software. The legal costs for this charge are added to the cost of the software that they are already being charged with overcharging on. And you see that as OK?
The response to being formally charged with overcharging on your software is *raising* prices?
No. Just keep the list accurate. Only include IP addresses of actual spammers. If someone who does not spam is blocked, then the list is a bad list, and you need a better mechanism
So you're saying spammers should get many free runs of spam from within ISPs that support them (say tens of thousands from this particular one, since it's a class B)? Why should they get that? Why should the ISP be allowed to profit from spam?
I noticed you still haven't answered my original question. What is the class B being affected?. Until you happen to answer that and I can validate the evidence on my own, I trust SpamHaus' claims over yours.
"Listed in Spamhaus" can be considered "not legitimate"
Have another mechanism that works without consuming excessive amounts of network or hardware resources, especially given that spammers frequently move?
OMG, what astonishing bullshit. "certainly", he has the balls to say! Either you have never used VS.NET and are blatently lying, or you're just spreading FUD for some reason. Another typical slashdot 'tard...
No more bullshit than what you just said. He said a statement without proof, as are you. Start stating the feature differences.
The number I've seen is something along the lines of 30% of spam is from compromised machines. We're talking millions to billions of e-mails daily. That's pretty damn visible.
Are you being sarcastic? We're already at this point with most of the prevelant viruses being used to forward spam, and the problem hasn't healed itself yet. I don't know when or even if it's possible to be self-healing considering what happens with most of these viruses.
Huh? It simply has to proxy to port 25 on the target mail server. Done, no headers are an issue at all. You get the IP of the original compromised box in the Received headers, but BFD, that box is a throw away.
MyDoom (source code is available) could be implemented trivially in Perl or almost any other scripting language, and have identical behavior, barring use of Windows executables in the "download and run" command. It wouldn't require root permissions to do any of it's work either.
Interbase, no idea - a default password isn't really a source defect, though, and it was both known and intentional, so I guess it was found instantly.
It wasn't a default password, it was a hidden account with a hardcoded password. And it was 1 1/2-2 years (after opening. Don't know how long before), *NOT* instantly. "Many eyes" only work if there are many eyes, not could be many eyes.
Yes, OSS get scrutinized - often every line. Because every person out there who for whatever reason is *interested* in how a printer driver or IO toolkit works can pull it apart and learn to understand it. And while they're in there, they add to the percentage chance that a bug will be found and an explit patched. Keep adding those little percentages together, and you approach 100% - "given enough eyes, all bugs are shallow."
Which does *NOT* necessarily mean a short time period.
How long was the admin username/password in Interbase after it went OSS? Year and a half or so? Doesn't get much more blatant than that.
Slashdot Mirror
Consider that there is (probably pretty conservatively) 100,000,000 emails sent per day in the US.
That's extremely conservative. AOL blocks 10x that amount as spam daily.
I believe it is still legal to send marketing spams as long as the recepients have given consent, no?
Actually, that's impossible.
If the recipients have given consent, it's not spam by definition.
How can we, the spam victims, prove that we NEVER gave consent to such-and-such website?
You can't prove a negative except by exhaustion. It should be up to them to prove you gave consent.
Lemme get this straight.
They're charged with overcharging on their software.
The legal costs for this charge are added to the cost of the software that they are already being charged with overcharging on. And you see that as OK?
The response to being formally charged with overcharging on your software is *raising* prices?
You don't know what you're talking about. Firewalls have nothing to do with spam,
Yes, they do. If you deny port 25 (or, even better *ANY*) access to IPs belonging to a spammer, they aren't getting any spam through to your system.
No. Just keep the list accurate. Only include IP addresses of actual spammers. If someone who does not spam is blocked, then the list is a bad list, and you need a better mechanism
So you're saying spammers should get many free runs of spam from within ISPs that support them (say tens of thousands from this particular one, since it's a class B)? Why should they get that? Why should the ISP be allowed to profit from spam?
I noticed you still haven't answered my original question. What is the class B being affected?. Until you happen to answer that and I can validate the evidence on my own, I trust SpamHaus' claims over yours.
Define legitimate.
"Listed in Spamhaus" can be considered "not legitimate"
Have another mechanism that works without consuming excessive amounts of network or hardware resources, especially given that spammers frequently move?
So who's your provider's provider?
It's hard to agree with "overzealous" without knowing that.
BZZZT. Wrong Answer. SCO has yet to sue an "end-user", at least for simply using Linux.
AutoZone used SCO. They converted to Linux (with SCO's help even), and SCO claims there's no way they could've done it without using SCO's IP.
That's why this year I'm going to vote with my... vote... for a regime that's more in line with my goals.
Name one. Chances are if they're in politics, they aren't in line with your goals.
OMG, what astonishing bullshit. "certainly", he has the balls to say! Either you have never used VS.NET and are blatently lying, or you're just spreading FUD for some reason. Another typical slashdot 'tard...
No more bullshit than what you just said. He said a statement without proof, as are you. Start stating the feature differences.
The number I've seen is something along the lines of 30% of spam is from compromised machines. We're talking millions to billions of e-mails daily. That's pretty damn visible.
Are you being sarcastic? We're already at this point with most of the prevelant viruses being used to forward spam, and the problem hasn't healed itself yet. I don't know when or even if it's possible to be self-healing considering what happens with most of these viruses.
more than one "." is not a problem in Windows, nor is a "," . Just enclose filenames in quotes.
Huh? It simply has to proxy to port 25 on the target mail server. Done, no headers are an issue at all. You get the IP of the original compromised box in the Received headers, but BFD, that box is a throw away.
MyDoom (source code is available) could be implemented trivially in Perl or almost any other scripting language, and have identical behavior, barring use of Windows executables in the "download and run" command. It wouldn't require root permissions to do any of it's work either.
You're assuming that ruining data is the goal.
You don't need root perms to open up a non-privileged port (assuming iptables isn't running blocking it).
Someone with malicious intent could then relay/spam through that.
Interbase, no idea - a default password isn't really a source defect, though, and it was both known and intentional, so I guess it was found instantly.
It wasn't a default password, it was a hidden account with a hardcoded password. And it was 1 1/2-2 years (after opening. Don't know how long before), *NOT* instantly. "Many eyes" only work if there are many eyes, not could be many eyes.
Yes, OSS get scrutinized - often every line. Because every person out there who for whatever reason is *interested* in how a printer driver or IO toolkit works can pull it apart and learn to understand it. And while they're in there, they add to the percentage chance that a bug will be found and an explit patched. Keep adding those little percentages together, and you approach 100% - "given enough eyes, all bugs are shallow."
Which does *NOT* necessarily mean a short time period.
How long was the admin username/password in Interbase after it went OSS? Year and a half or so? Doesn't get much more blatant than that.
How long was that double free in zlib?
umm, that could be encryption.
Nothing says that the output has to be binary.
What software is used to make the stream?
You can seek payment quite easily. Whether you get it or not is another question.
If it's cheaper to submit than to go to court, what is going to happen with most companies that get shaken down?
There isn't one site out there that lets me buy music online that works in Linux!!
Yes, there is
Mainstream artists it's not, but it is MP3s and you can stream through XMMS, no problem.
My wife is planning on getting a few albums through them.
Oh, and allowing it in standard players worked much better?
Tell that to Tommy Chong
GUID's aren't (obviously/reversibly) MAC dependent any more, that was considered a security hole and removed. 2K/XP don't have that issue.
So? That just means shares aren't on the stockmarket, it doesn't mean shares aren't available.