[Clamav-users] Accessing the virus-db via php or perl

2004-02-05 Thread Luc de Louw
Hi all, I want to set up a website were people can check if a particular virus is allready in the database. I know, there is the r/o mailinglist on sourceforge, but most of my customers do not speak english. I most propably will set up a multi-language website for checking that. What I need t

Re: [Clamav-users] Accessing the virus-db via php or perl

2004-02-05 Thread Luc de Louw
Tomasz Kojm wrote: On Thu, 05 Feb 2004 22:43:41 +0100 Luc de Louw <[EMAIL PROTECTED]> wrote: What I need to know is: What format has the database? bdb? gnudb? somthing else? The simplest way to get the virus list is to execute sigtool -l (CVS version required). I "cvs co"

Re: [Clamav-users] Accessing the virus-db via php or perl

2004-02-06 Thread Luc de Louw
Quoting Bruno Treguier <[EMAIL PROTECTED]>: [..] > Let me guess: main.cvd doesn't exist or has 0 in size? :-) The guess was right :-) [..] Luc could also just unpack the database (via "sigtool -u") each time it is updated, and work with the plain text list ? It wastes a bit of disk space, but on

[Clamav-users] clamav info-site (WAS: Accessing the virus-db via php or perl)

2004-02-07 Thread Luc de Louw
Folks, I'm on the way to build up a multilanguage info site about clamav and the viruses known by clamav. The code is in PHP and the license will be GPL Right now implemented: (almost nothing) - GNU gettext i18n To be done in the next few days: - import of sigtool -u in a MySQL|PostgreSQL Dat

Re: [Clamav-users] 0.65 is deprecated ?

2004-02-10 Thread Luc de Louw
Fajar A. Nugraha wrote: I would say use a CVS version AND use an external program to extract attachment :) However, with exim+exiscan patch it's the mail server (or MTA) that does all the mime-ripping. So in a way no "external" program required : only mail server and virus scanner. I would als

[Clamav-users] Problems updating virus sigs

2004-02-11 Thread Luc de Louw
Hi all, since a few days I have problems to fetch updates of the virus DB The cron is /usr/lo/usr/local/bin/freshclam --quiet -l /var/log/clam-update.log and the cron-output is: ERROR: CVD file not found on remote server ERROR: Can't read main.cvd header from database.clamav.net (200.68.106.40

[Clamav-users] How to handle quarantined SPAM

2004-02-17 Thread Luc de Louw
Hi all, Does someone know a software, that allows users to browse and handle quarantined Mails? Preferably a Web-interface... rgds Luc --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linu

Re: [Clamav-users] How to handle quarantined SPAM

2004-02-18 Thread Luc de Louw
Quoting Kevin Spicer <[EMAIL PROTECTED]>: On Wed, 2004-02-18 at 00:19, Luc de Louw wrote: Hi all, Does someone know a software, that allows users to browse and handle quarantined Mails? Preferably a Web-interface... You don't say what you are using to quarantine, but if using MailS

[Clamav-users] could pls someone send me a passwd protected zipped virus?

2004-03-02 Thread Luc de Louw
Hi all, I'm confused about passwd-zipped viruses/worms. Myself I did not got any of this viruses, and I did not got feedback from users not found some amavisd-new notices in the log. Is it possible, that someone is sending me one of this viruses, so I'm able to check my system? (I'm not vurner

[Clamav-users] [ANNOUNCEMENT] Postfix-Cyrus-Web-cyradm-HOWTO Version 1.2.5 available

2004-03-28 Thread Luc de Louw
Folks, First, sorry for the crossposting. I just want to be sure enought people can do some feedback before commiting the document at the tldp.org CVS. Addition: - ClamAV - Spamassassin - Amavisd-new - Upgraading cyrus-imapd from 2.1.x to 2.2.x Updates: - All software to most recent release Plea

Re: [Clamav-users] [ANNOUNCEMENT] Postfix-Cyrus-Web-cyradm-HOWTO Version 1.2.5 available

2004-03-30 Thread Luc de Louw
Krištof Petr wrote: Luc de Louw wrote: [..] If you are writing some documentation, you _should_ read the another before. Your document says: > I suggest to update the signatures with a hourly cronjob. To edit the crontab issue *crontab -e* and add the following line: > 0 * * *