XBMC includes a python interpreter and allows for extensions via python scripts. One of these extensions is a front end module for mythTV which allows you to schedule and playback recordings from a backend server using network shares. The XBox makes an excellent low-cost frontend if you want multiple MythTV frontends in the house, or if you have a big noisy box you'd rather keep far away from your component rack.
Not sure if this has been suggested before, but rather than all this expensive signing and encryption, why not just have each MTA append its IP to an X-header of every message before it goes out the door? The receiving MTA would check the header, verify that the message it received was, indeed, from the last IP in the X-header list, and either deliver the message locally or append its own IP and forward the message on.
This would not prevent spam initially, but it would provide traceability for a message. Spammers would be required to put their real IP on a message to have it delivered, and since they have no control of the message after it leaves their MTA, a clear trace is left back to them.
No, this does not prevent open relays from being a problem, but it would sure make them easy to find.
Inexpensive, clean, and relatively easy to implement on top of SMTP. Of course you'd have to get large ISP buy-in, but any sort of spam-killing is really in their best interest if only from a bandwidth point of view.
In the beginning, rather than blocking messages without this header, a warning could be issued to the involved parties informing them that they really should upgrade to an MTA that supports this extension.
Clear identification is the spammer's achilles heel. Exploit that and we'll be a lot closer to getting rid of spam.
Slashdot Mirror
XBMC includes a python interpreter and allows for extensions via python scripts. One of these extensions is a front end module for mythTV which allows you to schedule and playback recordings from a backend server using network shares. The XBox makes an excellent low-cost frontend if you want multiple MythTV frontends in the house, or if you have a big noisy box you'd rather keep far away from your component rack.
Not sure if this has been suggested before, but rather than all this expensive signing and encryption, why not just have each MTA append its IP to an X-header of every message before it goes out the door? The receiving MTA would check the header, verify that the message it received was, indeed, from the last IP in the X-header list, and either deliver the message locally or append its own IP and forward the message on.
This would not prevent spam initially, but it would provide traceability for a message. Spammers would be required to put their real IP on a message to have it delivered, and since they have no control of the message after it leaves their MTA, a clear trace is left back to them.
No, this does not prevent open relays from being a problem, but it would sure make them easy to find.
Inexpensive, clean, and relatively easy to implement on top of SMTP. Of course you'd have to get large ISP buy-in, but any sort of spam-killing is really in their best interest if only from a bandwidth point of view.
In the beginning, rather than blocking messages without this header, a warning could be issued to the involved parties informing them that they really should upgrade to an MTA that supports this extension.
Clear identification is the spammer's achilles heel. Exploit that and we'll be a lot closer to getting rid of spam.
-S-