Hello Chris,

Thanks for the elaborate response!

Several of the possibilities I had thought of myself, but the best ones
aren't in for me (or anyone else with an email account at uni).

> Create an email address just for the mailing list, and put a restriction on
> your mail server so only the mailinglist server can send to that mailbox.

With 50+ mailing lists it would become a bit of a maintainance issue,
otherwise good - but I don't control my MTA.

> Get an ISP who uses one or more of the black holes,

Not bad, but me thinks cows will walk before uni deploys this. For
practical purposes, it would probably also mean to send with a different
email account as the one used for receiving - what's the solution to
that? Esp if the email client is also different?

> Don't partake of lists that publish their archive online.

Sure :-)
(And I'll unsubscribe here too?)

The problem with that is that I think many spammers are subscribed to
the mailing list - this one has been spared so far by the looks of it.

> Create an email address that you only use for the lists, and use your client
> software to filter everything not from the list server.

This would be the obvious and best choice - if I had my own MTA.

> Use a procmail or other similar tool to filter the mail pre-client

spambouncer is great, but it's less than perfect. List emails need
to be filtered and stored first (a good idea anyway), friend's email
addresses need to be listed (to prevent blocking in any case), and
although it basically never let a spam through, it files too much under
blocked and not enough under spam. It's as good as it's going to get
with delivery-filtering.

What's peoples' experience with services which obscur the sender? How
easy are they to use, or in other words, how much additional effort
is required?

Does anyone have info on the efficiency of From: mangling, like I've
done here?

Thanks again,

Volker

Reply via email to