Slashdot Mirror

The OSI and FSF agree that free or open source licenses, respectively, should never have any sort of usage clause in them. Richard Stallman has publicly encouraged everybody to find ways to profit off free software.

Profit is not everything. My little project may be for sale, but I will not sell to anyone owning a Che Guevara T-shirt, for example.

What can be owned? Software? Oh no it can't.

?? Of course, it can. Microsoft owns Windows... Semantec owns Norton Utilities. I own skem. You can buy the ownership of software (if the current owner is willing to sell), although people usually prefer to license it instead — they get a lot fewer rights, but pay a lot less money.

Probably, this difference between buying and licensing is what got you so confused...

Well, try skem. Maybe, you'll like it better :-)

Whether it is a zombie, which is not supposed to have an SMTP server at all, or a legitimate mail-server fooled into relaying spam to you, my milter will black-list it for a few hours after your spam-detectors issue their first verdict against the relay.

Unlike with most blacklists, though, the damage from a false-positive is merely a delayed, rather than rejected (or, worse, dropped) message...

SKEM ( /usr/ports/mail/milter-skem on FreeBSD) will not eliminate spam, but it will throttle the volume of it arriving from rogue servers and hi-jacked PCs, while the worst effect of a false-positive is delayed (rather than rejected) legitimate e-mail.

Most spam engines don't use a mail queue, which is why greylisting works so well.

As for spamd's greylisting, yes, it is another way to implement it. It has an inconvenience, IMHO, requiring a database, whereas my skem keeps the state in a way, that's easy to monitor and alter without special utilities -- relying on the filesystem for efficiency.

You did not really look into it before rushing to "plug" your favorite operating system here, did you?

Try my milter -- it should build on OpenBSD without a problem...

This way the accidentally blacklisted server has several days to straighten things out while the really spammy server gets overloaded with huge mail queue.

Using my skem milter is one way to do that intelligently... :-)

If you use bayesian filter software, like bogofilter or spamprobe, you can turn this into an advantage.

Why limit yourself to bayesian? <plug>With my state-keeping milter, for example</plug>, you can automatically blacklist the relay, that handed this spam to your server. So that you would not waste any CPU nor bandwidth talking to the abusive machine again.

And I have photos too -- can I get to frontpage now?

stories about RBLs that add people, but never remove them.