Well, I just did (47 * 75) : 25 = 47 * 3 = something that will end with a 1. So only 141 would be a valid option. No need to complete the calculation. Besides the point that 47 * 3, will also certainly never be above 1000 if you make an estimate, which also only leaves 141 as the only option.
> The classic is the stupid "the autobahn doesn't have speed limits so why do we have limits on > Road X" argument. Nicely forgetting that the unlimited sections of the autobahn have been designed > for high speed travel, and only roads with very specific and strict design criteria are allowed to > have no limit.
Besides that you are at least half responsible for any accident when your speed is above 130kph on the autobahn unless you can prove your speed was not a factor in the accident. And of course on the german autobahn you can expect to be passed by cars that are travelling much faster than you do.
No, that is why for serious environments you have a development, test, acceptance and time travel environment.
Only when an application or change makes it through all those stages without problems it is ready to be put onto the production environment. If a problem is detected in one of these stages it should be fixed and the test process start over again.
I already block connections from windows machines to my primary MX for over 2 years now using pf. Normal windows mailserver will switch to using the secondary backup, and mail will come through. Hence only the spam mail coming from zombies directly connecting to the secondary MX is left to the filtering software. Currently I filter out approximately over 1500 spammessages using this firewall setup.
Scheduling using the earliest deadline late algorithm from the real time computing field might work. Based on the maintenance windows you should have different deadlines for different systems.
> I have very nearly given up on atheism in the back of German taxis. 10 feet behind the vehicle in front at 150kph, > where the vehicle in front is a truck so long its rear axles are still paying tolls in Belgium, is not fun.
Although 10 feet is indeed very close, there sometimes is a very good reason to drive closer than 2 seconds behind the car in front of you, when driving over 150kph on the German highway. If you keep the 2 seconds distance between you and the car in front of you this gap can be over 100 meter. Some people (mostly with yellow license plates and bikes on the top of their car) believe they can merge into that gap with their 100kph or less. So driving one second behind the car in front of you, which avoids this merging, is in fact safer.
You seem to forget that there are people making money from releasing viruses and taking advantage of exploits. They probably will label that as doing something useful with their life.
> What will happen is that you will eventually blacklist all of them
There is a timeout after which a host is removed from the blacklist. But in fact I do not really see this as a problem, why should I want email from a provider sending spam through their mailserver? The mailserver of an ISP will only send spam created by their own users (on which they should act) and will not act as an open relay for others.
Also note that I do not block on sender address, but on the IP of the delivering mail server.
Yes. But when a legitimate mail is send the mail is rejected by my server, the yahoo server (or hotmail etc.) bounces the mail to the sender, with normally the 554 reject message which contains a link to remove the host from the blacklist by the user. The idea is that spammers will not do this, but people who really want to send mail do. And if people really need me anyway, they can call me, or pay me a visit.
I use the OS fingerprinting options from pf to block windows machines from delivering mail on the primary mx. This saves approximately between 300 and 1600 spams a day. Beside that, rejecting mail from hosts without an A record, blacklisting
all hosts sending mail to spamtraps with spamikaze, rejecting hosts which falsely claim to be a host in my domain and filtering with bogofilter.
Slashdot Mirror
Well, I just did (47 * 75) : 25 = 47 * 3 = something that will end with a 1. So only 141 would be a valid option. No need to complete the calculation. Besides the point that 47 * 3, will also certainly never be above 1000 if you make an estimate, which also only leaves 141 as the only option.
> The classic is the stupid "the autobahn doesn't have speed limits so why do we have limits on
> Road X" argument. Nicely forgetting that the unlimited sections of the autobahn have been designed
> for high speed travel, and only roads with very specific and strict design criteria are allowed to
> have no limit.
Besides that you are at least half responsible for any accident when your speed is above 130kph on the autobahn unless you can prove your speed was not a factor in the accident. And of course on the german autobahn you can expect to be passed by cars that are travelling much faster than you do.
No, the time travel environment is an environment to test with date settings. I.e. what happens with your software in leap years etc.
No, that is why for serious environments you have a development, test, acceptance and time travel environment. Only when an application or change makes it through all those stages without problems it is ready to be put onto the production environment. If a problem is detected in one of these stages it should be fixed and the test process start over again.
So you are trying to say that people with lower IQ's are more succesfull? Time to take another beer to kill those unnecessary braincells.
I already block connections from windows machines to my primary MX for over 2 years now using pf. Normal windows mailserver will switch to using the secondary backup, and mail will come through. Hence only the spam mail coming from zombies directly connecting to the secondary MX is left to the filtering software. Currently I filter out approximately over 1500 spammessages using this firewall setup.
Scheduling using the earliest deadline late algorithm from the real time computing field might work. Based on the maintenance windows you should have different deadlines for different systems.
> I have very nearly given up on atheism in the back of German taxis. 10 feet behind the vehicle in front at 150kph,
> where the vehicle in front is a truck so long its rear axles are still paying tolls in Belgium, is not fun.
Although 10 feet is indeed very close, there sometimes is a very good reason to drive closer than 2 seconds behind the car in front of you, when driving over 150kph on the German highway. If you keep the 2 seconds distance between you and the car in front of you this gap can be over 100 meter. Some people (mostly with yellow license plates and bikes on the top of their car) believe they can merge into that gap with their 100kph or less. So driving one second behind the car in front of you, which avoids this merging, is in fact safer.
You seem to forget that there are people making money from releasing viruses and taking advantage of exploits. They probably will label that as doing something useful with their life.
> What will happen is that you will eventually blacklist all of them
There is a timeout after which a host is removed from the blacklist.
But in fact I do not really see this as a problem, why should I want
email from a provider sending spam through their mailserver? The mailserver of an
ISP will only send spam created by their own users (on which they should act)
and will not act as an open relay for others.
Also note that I do not block on sender address, but on the IP of the delivering
mail server.
Yes. But when a legitimate mail is send the mail is rejected by my server, the yahoo server (or hotmail etc.) bounces the mail to the sender, with normally the 554 reject message which contains a link to remove the host from the blacklist by the user. The idea is that spammers will not do this, but people who really want to send mail do. And if people really need me anyway, they can call me, or pay me a visit.
I use the OS fingerprinting options from pf to block windows machines from delivering mail on the primary mx. This saves approximately between 300 and 1600 spams a day. Beside that, rejecting mail from hosts without an A record, blacklisting all hosts sending mail to spamtraps with spamikaze, rejecting hosts which falsely claim to be a host in my domain and filtering with bogofilter.
We use SILC for communication.
Well, not exactly. You are forgetting the witty worm which appeared in march this year.