On Fri, May 21, 2004 at 01:40:37PM +0200, Dale Gallagher wrote: > ---- Sean Matheson <[EMAIL PROTECTED]> ---- > > Is there perhaps a more effiecient way to san my > > incoming and outgoing qmail mail using clamd for > > instance? > > The following is fast - scans and rejects infected > mail before it reaches the real queue... > > clamav-0.71 > run clamd as user clamav > > ripmime-1.3.1.2 > http://www.pldaniels.com/ripmime/ > With this (tiny) patch (vital): > http://www.pldaniels.com/pipermail/ripmime-general/2004-May/000161.html > > qmail-1.03 > with/without QMAILQUEUE patch > > qscanq-0.42 > http://pobox.com/~lbudney/software/qscanq/ > > Relevant conf-* compile time options: > > # head -2 conf-qmailq > /var/qmail/bin > (running with QMAILQUEUE patch) > > # head -2 conf-ripmime-cmd > /usr/bin/ripmime --disable-qmail-bounce -i - -d . > > # head -2 conf-scancmd > /usr/bin/clamdscan --quiet ./ > > # head -2 conf-spool > /var/qmail/qscanq > > # head -2 conf-users > clamav > log > > # head -2 conf-groups > qscanq > > Optional, though recommended: > http://cr.yp.to/daemontools.html > > I will put a quick install guide on-line within a few days. > > cheers > Dale > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Clamav-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/clamav-users
I must admit some confusion regarding these answers to your original post. First, we
must have more information if we are to provide helpful guidance. Given that your
signature suggests that you are a student, I can't help but wonder if you are routing
mail within a network or simply receiving mail on a single machine. If the former is
true, clearly qmail is a sound choice; if, however, the latter is the case, you would
probably do much better streamlining your configuration by use of postfix tools.
What is your network architecture? What volume of mail are you dealing with?
For instance, if you are receiving mail for a single machine, regardless of quantity,
you would probably do better with a simple fetchmail > procmail > clamd > spamd
configuration. This kind of setup is quite efficient, easy to administer, and will
teach you a great deal about mail recipes and how to manipulate lists, archives, etc..
If you answer these questions, I'm sure that many of us can help you develop the best
solution for your needs. Rather than using a hammer to squash an ant, I suspect you
might do better thinking along the lines of resource economy. Remember, many of the
current mail packages for *nix are designed with large networks in mind, often
providing far more functionality than is needed for small networks or local filtering.
While learning how to administer complex systems is important if you are considering a
career in systems admin, understanding how to tailor your approach in an economical
way will put you a cut above - or, at least simplify your life and improve your
computer's performance.
--
John Lalla
Santa Barbara, CA
.~. _
/v\ -o)
no gates... /( )\ /\\ running GNU/Linux
no windows! ^^^^^ _\_v free at last!
"Only those who attempt the absurd can achieve the impossible."
"Those who would trade liberty for security deserve neither."
- Benjamin Franklin
pgpokcZdPpOqI.pgp
Description: PGP signature
