> > My view on this (here, now) is :
> > If it is trivially easy to flag the virus within the existing SA
> > framework, why not?
Because I like how viruses are dealt with by my mail virus checker, and I
fear this will interfere.
> > Just three more lines in the config file, and easy enough for
> Besides, why not block it with the content filtering rules of your MTA?
I would also add that it is best to catch viruses based upon *the potential*
for damage. Otherwise you are always one step behind.
Our "promail sanatizer" does just that and has done a great job. IMHO, your
request, and o
Maybe this is an old philpsophical debate, but I'd be afraid of code bloat
in catching all mail viruses on top of spam. We too have an open source
virus checker that works very well, and I'd prefer that each do its own
specialized job.
> Has anybody created a rule for the MyParty virus? It is t
> This is fixed in SpamAssassin 2.0
I got my Ver 1.5 source from the download link on the website. Is it out of
date, should I still ignore the error, or why & how should I upgrade?
Thanks,
MC
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
ht
rsion is 2.0 >
1.9. Besides, I applied it and it didn't `make test` cleanly.
I was able to make install, and I am using procmail. Should I ignore it?
_____
Mike Coughlan
GOTHAM BROADBAND
3 West 18th Street
NYC 10011
USA
Tel: +1.212.206.9620 ext 310
Fax: +1.212.2
Can someone please send a sample .procmailrc for courier.
This seems to work, I made it up, but I'd like a sanity check before I go
live.
Thanks
=
# This added for Maildir support (Courier-IMAP)
MAILDIR=$HOME/Maildir/
DEFAULT=$MAILDIR
:0fw
| spamassassin -P
:0e
{
