[cap-talk] charging for spam. What are the implications

[Valerio Bellizzomi]

On 24/01/2007, at 15.23, John McCabe-Dansted wrote:

>On 1/24/07, Rob Meijer <rmeijer at xs4all.nl> wrote:
>> in what way ever combined with sender based filtering, you still would
>> only end up at the equivalent of ACL's. If you configure/patch the
>> receiving mail server to not accept mail targeted at devbox at selnet.org,
>> but to for example  decompose mail sent to
>> key819f6d46104b2a7acacb47ad9fc92438.devbox at selnet.org and check
>> 819f6d46104b2a7acacb47ad9fc92438 against some whitelist in
>> ~devbox/whitelist.db and accept it based on its occurance then you
would
>> have a solution that is both more flexible (you are not a required
party
>in
>> introductions) and free from the false negatives of sender based
>> whitelisting.
>
>Also, if you cannot alter the mail server you are using you can instead
use
>  devbox+key819f6d46104b2a7acacb47ad9fc92438 at selnet.org
>as your email address. This email address means "the folder
>key819f6d46104b2a7acacb47ad9fc92438 of the user devbox at the host
>selnet.org".
>Most mail servers will deliver such mail to user devbox, but pass
>   devbox+key819f6d46104b2a7acacb47ad9fc92438 at selnet.org
>as the "to" address to the mail client.
>
>It is much easier to install new software on our own machine if we
>don't have to upgrade all the servers we use first :)

This requires a mail client that can interpret such address format,
doesn't it ?
Perhaps this could be done with filtering rules, but there is another
issue: the mailman server will reject a message from this address since it
is not subscribed.

>
>-- 
>John C. McCabe-Dansted
>PhD Student
>University of Western Australia
>_______________________________________________
>cap-talk mailing list
>cap-talk at mail.eros-os.org
>http://www.eros-os.org/mailman/listinfo/cap-talk