On Wed, 1 May 2002, Marc G. Fournier wrote:
> > 1. Nobody has made a good enough case for this belonging in Cyrus
> > instead of the MTA (yes, I know that Sieve can be used anywhere, but
> > this discussion has been in the context of Cyrus).
>
> Cyrus IMAPd, IMHO, is meant to be used in a 'black box environment' ... no
> user accounts or directories, which is how we set ours up here ... with
> the extra spam extension in Sieve ("the filter"), end users would have the
> option of enabling/disabling the filtering as/when they wish to ... also,
> by putting it in "the filter", the end user has an option of *not*
> filtering email coming from specific senders, so, for instance, the
> postmaster account wouldn't have any spam filtering done for all email
> coming from the local machine, or things like that ...
This can all be done currently by tagging the spam in the MTA and
appplying a header-based filter within sieve. There is no reason that
sieve needs to call an external program. The header can be used or
ignored at the user's whim.
> Personally, I'd love to see an if(virus) thrown into the mix too ...
Again, you could use MIMEDefang (or similar) with a virus scanner that
tagged the emails and allowed the users to filter as they liked.
> All I'm advocating is putting more control into the hands of the end users
> as to what they want to have happen to their email ... if they want
> spam/virii, who am I to take that away from them? But give the end-users
> the *tools* to make that decision on their own, which Sieve currently does
> not give ... draft-segmuller-sieve-relation-01.txt doesn't give them that
> choice either, as you are still controlling the flow of email without the
> user have a choice of whether he/she *wants* it to be controlled ...
Yes it does. See above. draft-segmuller-sieve-relation-01.txt only gives
a finer-grained control.
> if you have spamassassin working with Sendmail/Milter, I know there are a
> *ton* of ppl on the spamassassin mailing list that would love to hear your
> success story ... or do you run it on a system of one? There have been
> several postings there (myself included) that talk about how they have to
> restart the daemons whenever sendmail receives two messages
> simultaneously, and nobody appears to know how to fix it ...
We have it working here at CMU. We use MIMEDefang (a milter) to call
SpamAssassin on each message, and add a header as appropriate. There was
not a terrible trial configuring it either.
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 235 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper
