Alpine and afaicr pine expose this information. Each ML mail has a link at
the bottom in the mail viewer which gives you a list of all the things you
can do e.g. unsubscribe.
Stu.
On Thu, 19 Feb 2009, Ian Eiloart wrote:
>
>
> --On 18 February 2009 14:26:11 -0800 Dennis Peterson
> wrote:
>
>>
Ventsyslav Vassilev wrote, on 30/07/08 16:26:
>> ; <<>> DiG 9.2.1 <<>> current.cvd.clamav.net
>
> First, you may want to upgrade your BIND version!
> This one is vulnerable to cache poisoning!
> http://www.kb.cert.org/vuls/id/800113
>
Well they all are really: it's just got somewhat more difficul
>
> Ok, I found it. There exists a bug in clamav 0.90.1 (did not find a bug
> number, only some comments in the web) that makes it take very long to build
> the socket. After some 15 minutes after restart of the clamd it works. This
> old version is provided by Debian Etch, should I switch to a ne
Berényi Attila wrote, on 19/05/08 16:44:
>
> So if I'm right I have three options:
> 1) install clam from source,
> 2) use testing or unstable branch,
> 3) wait for the update package.
>
4) add volatile to your sources.list and get recent clamav (although not
0.93 yet for some reason) that is ta
Upgrade all clam packages to the versions in volatile.
Mixing versions is the road to madness. All components should at least be
at the *same* version.
The version(s) in Etch / stable are old and do have problems, by upgrading
all components to the versions in volatile, you should see a lot few
Hi Stephen,
Thanks for your great work packaging clam* for Debian. I was just wondering
when we can expect 0.92 in volatile / backports or whether you plan to hold
off until e.g. the 0.92.1 release?
Kind regards,
Stu.
___
Help us build a comprehensive
Really for the attention of Stephen Gran but I thought this might be useful
for the archives ...
Any plans to get 0.90 into volatile.debian.net for sarge and/or etch?
Cheers,
Stu.
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clama
Hi,
Clam has been working great on our mailservers, recently a particular
client has been sending us zip files that have caused clamd to fall over
with the "Zip module failure" error.
I've verified this error by letting the zips through the mail gateway and
then running clamscan on them, deb
