On Fri, Dec 26, 2003 at 01:00:07AM +0100, Örn Hansen wrote: Content-Description: signed data
The answer is to have two or more accounts, one that you will only give to friends, family, etc. And some othes, you communicate on regular basis ... when those accounts become to flooded with moron-mail ... dump it. Keep track of the "companies" that give your email to spammers, and make sure you *know* how to deal with them properly.
Actually I'm toying with the idea of white-listing, for my personal mail system. While switching addresses every once in a while will certainly 'work', it's not a universally applicable solution. One of the reasons I'm looking into this whole thing, is that sometime in the not too distant future, I'm going to have to take my company's mail in-house[1]. And to do that I'm going to have to have (among other things) some kind of spam-handling plan. In a company-situation switching/dumping addresses is simply not an option. Now, since setting up {spam|ham|forget}@domain seems to require too much of the users (in that they would be required to edit the headers, before forwarding to those accounts) I think the {spam|ham|forget}-mailbox+cronjob-sa-learn is probably the better solution. Because this would only require the users to move the message(s) to said mailbox(es). This, however, begs the next (couple of) question(s); - I want the users to access mail through imap. - Setting up 'shared' {spam|ham|forget}-folders should be No Big Deal, right? - In order for the sa-learn script to not have to keep processing the same messages, content will have to be removed from said folder after each run. So is it neccessary to run something like 'reconstruct' to keep Cyrus happy? Hmmm... Maybe the above belongs in a separate thread; '(Cyrus) Imap "mechanics"' TIA Jon [1] The company that's hosting our web/mail currently is not performing very well on several counts, including (but not limited to); - they insist on 'warning the sender' when their system detects virus attachments, but they refuse to set up smtp-authentication, effectively rendering those warnings useless. - they have too many (virtual) domains served from each machine, resulting in massive delays/connectivity problems, and even lost mail. - it's a win32 shop. -- Whatever rocks your boat!