- apt-get install subversion subversion-tools - Control access through svnserve+ssh
Can even do hot backups, and has a compact database back-end (remember about sector granularity on hard disks? database lives in 10 files). Perfect for my needs.
Effectively, EStamps are not the solution. The easiest solution would be to "indirectly" transfer the cost to the sender, without adding fees for non-spammers, as follows:
You make sure mail is stored on the sending server, and that only a message header with a link to the message body is stored on the receiving server.
This way, spammers will either a) need their own server (which can unambiguously identified and blocked), or b) the spammer's ISP will have to store the millions of message bodies and handle all the generated traffic. This will give a good incentive to the spammer's ISP for getting rid of the spammer.
A nice side effect of this is that you get rid of fake originating server identification in headers, as a fake header would lead to no message body.
For this to work, it is important that the message subject be considered a part of the message body, not its header. Otherwise, spammers will try to put their message in the subject! It doesn't necessarily even require the SMTP infrastructure change.
This change does not equire any change to the SMTP protocol. Emails can still be sent as they are now. But we add a new "MIME Type" with something such as:
MIME-Content-Link: (address/ID information)
All the message is is a standard message header with no body, but the above information, and a dummy subject "Subject: none". If a mail client sees the above it would have the option of retrieving it based on the address/ID information given.
Slashdot Mirror
- apt-get install subversion subversion-tools
- Control access through svnserve+ssh
Can even do hot backups, and has a compact database back-end (remember about sector granularity on hard disks? database lives in 10 files). Perfect for my needs.
Effectively, EStamps are not the solution. The easiest solution would be to "indirectly" transfer the cost to the sender, without adding fees for non-spammers, as follows:
You make sure mail is stored on the sending server, and that only a message header with a link to the message body is stored on the receiving server.
This way, spammers will either a) need their own server (which can unambiguously identified and blocked), or b) the spammer's ISP will have to store the millions of message bodies and handle all the generated traffic. This will give a good incentive to the spammer's ISP for getting rid of the spammer.
A nice side effect of this is that you get rid of fake originating server identification in headers, as a fake header would lead to no message body.
For this to work, it is important that the message subject be considered a part of the message body, not its header. Otherwise, spammers will try to put their message in the subject!
It doesn't necessarily even require the SMTP infrastructure change.
This change does not equire any change to the SMTP protocol. Emails can still be sent as they are now. But we add a new "MIME Type" with something such as:
MIME-Content-Link: (address/ID information)
All the message is is a standard message header with no body, but the above information, and a dummy subject "Subject: none". If a mail client sees the above it would have the option of retrieving it based on the address/ID information given.