Re: [Qmail-scanner-general]Scanning only the incomming mails

2005-07-12 Thread C. Bensend
> per message isn't killing us - so I'm not bothering. And of course I > could always disable all the network tests - but that effectively makes > SA useless - so I can't imagine doing that. Hi Jason, I beg to disagree with your above statement - I run with all network tests disabled, and I h

Re: [Qmail-scanner-general]Modifying qmail-scanner 1.24 headers?

2005-01-18 Thread C. Bensend
> You say Received headers, and yet the above refers to the Return-Path. > It thinks it begins with a single-quote??? That's correct. And if I remove the qmail-scanner headers, it works. I've been through the headers, and all of the quotes match up just fine. :( The error isn't on that Return-

Re: [Qmail-scanner-general]Modifying qmail-scanner 1.24 headers?

2005-01-18 Thread C. Bensend
> You may want to look into 822field (part of the mess822 package from > DJB)---it can pull headers out of mail for you, as long as you're okay > with running another program to do it. It may not be the most convenient > thing you ever did in perl, but it's definitely not fragile. Thanks for the

Re: [Qmail-scanner-general]Modifying qmail-scanner 1.24 headers?

2005-01-18 Thread C. Bensend
> I find that hard to believe. A mail header is a mail header. And they > aren't any different from what 1001 other mail-mungers do. > > What do you think is wrong? The custom headers that qmail-scanner adds breaks Mail::Field::Received's parsing of Received: headers: unterminated quoted string

[Qmail-scanner-general]Modifying qmail-scanner 1.24 headers?

2005-01-17 Thread C. Bensend
Hey folks, I have some email parsing software running behind one of my scanning machines, and I just realized tonight that the headers that qmail-scanner adds are breaking this additional software. :/ While going through the code, I don't notice any real big "don't do this you drooling id

Re: [Qmail-scanner-general]corrupt or unknown clamd scanner error

2005-01-15 Thread C. Bensend
> No... more likely need to increase softlimits by another 10Megs perhaps? O... Softlimit in which run script? -- "I'm on the Zoloft to keep from killing y'all." -- Mike Tyson --- The

Re: [Qmail-scanner-general]corrupt or unknown clamd scanner error

2005-01-15 Thread C. Bensend
> If it's intermittent, it's virtually guaranteed to be resources. Add > more ram :) Agreed. This install will be replaced by an AMD64 with 2GB of RAM in two weeks, so I'm going to limp along until then. :) Thanks! Benny -- "I'm on the Zoloft to keep from killing y'all."

Re: [Qmail-scanner-general]corrupt or unknown clamd scanner error

2005-01-15 Thread C. Bensend
>>We also faced this error when installed qmail scanner >>with clamav, spam assassin in a Mandrake9.1 machine (Production Server). >>This problem was attended by one my colleaque. I don't know exactly what >> he >>did. But he was telling it was related to permissions. Some wher

Re: [Qmail-scanner-general]corrupt or unknown clamd scanner error

2005-01-15 Thread C. Bensend
> Upgrading clamd helped here. To .. ? I'm already running the latest stable release, 0.80. I just want to make sure that this problem is a result of the interim machine I'm running on (the one that's a little underpowered), rather than my config. Benny -- "I'm on the Zoloft to keep from ki

[Qmail-scanner-general]corrupt or unknown clamd scanner error

2005-01-14 Thread C. Bensend
Hey folks, I just upgraded my main mailserver, and suddenly I'm getting several (ie, a dozen or two) of these errors each day, out of possibly a thousand or two thousand messages: Jan 14 18:00:32 host X-Qmail-Scanner-1.24: [host.bennyvision.com110574723048612678] clamdscan: corrupt or unknown

Re: [Qmail-scanner-general]Email reports - never to sender, always to admin?

2004-12-04 Thread C. Bensend
> If you can run logwatch on the machine, the latest version has a nice > output of virii caught... quite informative... Exactly what I'm planning on doing. :) Benny -- "... i want to be a farting burping maniac." -- "kerry",

Re: [Qmail-scanner-general]Email reports - never to sender, always to admin?

2004-12-03 Thread C. Bensend
> How can you not know? What about the standard Q-S logging? Assuming > you're running the current release, it defaults to logging a one-line > syslog record of the e-mail transaction - whether it's Clear, infected, > SPAM, etc. > > A quick look through your logs should show you that you DON'T wan

Re: [Qmail-scanner-general]Email reports - never to sender, always to admin?

2004-12-03 Thread C. Bensend
> If you put notify admin, it shouldnt ever send a notification to anyone > other than admin. OK. I just wanted to make sure I wasn't missing any "feature" that might send a notification to others. > As far as the silent viruses goes, are you *really* sure you want this? > I had it sending me

Re: [Qmail-scanner-general]Email reports - never to sender, always to admin?

2004-12-03 Thread C. Bensend
>I have run configure with the '--notify admin' and '--admin address' > options (address being the local part of the admin email address), and > it appears to work fine. However, I want to be 100% sure that QS will > _only_ send a virus alert to the admin, and _never_ to a sender. Are > thes

[Qmail-scanner-general]Email reports - never to sender, always to admin?

2004-11-30 Thread C. Bensend
Hey folks, I'm in the process of testing qmail-scanner on a new mailserver I'm setting up. It is running on OpenBSD 3.6-STABLE, and serves a handful of personal domains (low traffic, coupla thousand messages a day). I have run configure with the '--notify admin' and '--admin address' opti