Free perfection software for linux

openMSX is the MSX home computer system emulator that aims for perfection.

Almost all MSX machines are emulated: MSX1, MSX2, MSX2+, Turbo-R... And also quite some extra hardware is emulated: SCC, SCC+, FM-PAC, Music Module, PSG, Moonsound, Sunrise IDE, Disk Controllers, MIDI, almost all memory mappers, etc... Actually, more than any other MSX emulator!

It also features quite some extras: rendering using openGL acceleration, full screen, built in console (based on TCL), MSX debugging facilities, scalers, using directories as disk images (still buggy though), screenshots, speed settings, frame skip, scanlines, TV-blur, afterglow (GL), and more...

For a really long description: again, please see our home page.

Do note that openMSX is alpha software, which means that some things work but not all features are implemented yet.

maRBL project is a policy daemon for Postfix that lets you trigger any Postfix action as a result of an RBL match.

There are only a couple good, practical options for spam filtering, but none of them are 100% effective. Statistical filters can come very close to perfection, but at the cost of CPU time -- you cant filter something until youve received it and spent some time analyzing it -- and there are few good options for blocking hosts outright.

What about RBLs?
RBLs are simple, fast and efficient but they frequently have false positives. Theres an implicit level of trust required: you have to trust RBL administrators to add and remove hosts in a timely and accurate fashion from their lists. The problem is that only a fraction of lists are entirely automated, mosts have humans involved in the process, and humans are fallible. Worse, humans are vindictive, many lists go for collateral damage by blocking large ranges of IP addresses in an effort to arm-twist ISPs into being more responsive about their spam problem.

What about Greylisting?
Greylisting relies on the fact that most spam is no longer sent through real mail servers, and instead is sent from subpar SMTP engines. Greylisting forces senders to wait for a period of time and retry, something many of these engines are incapable of. The problems are that it fares poorly when handling mail from large ISPs that have SMTP clusters (theres no guarantee that the retry will come from the same IP address), that it introduces more delay to the process of receiving an email, and that occasionally you will run across non-RFC compliant mailservers that treat a temporary delivery failure as a permanent one.