Peter Bradeen wrote:
I see that there are ways to limit the level of archive that will be
scanned as well as the size of the entities to be scanned. Is there a
way for CLAMAV to then flag them as not allowed? Seem that if you
can't scan it, it should be rejected.
It's not about not being
On Wed, 2011-11-09 at 10:31 +0100, Per Jessen wrote:
Peter Bradeen wrote:
I see that there are ways to limit the level of archive that will be
scanned as well as the size of the entities to be scanned. Is there a
way for CLAMAV to then flag them as not allowed? Seem that if you
can't
Rob Sterenborg (lists) wrote:
On Wed, 2011-11-09 at 10:31 +0100, Per Jessen wrote:
Peter Bradeen wrote:
I see that there are ways to limit the level of archive that will
be
scanned as well as the size of the entities to be scanned. Is
there a
way for CLAMAV to then flag them as not
Per Jessen wrote:
It's not about not being able to scan, it's about not wanting to
scan. Regardless, clamav doesn't reject or approve mails, that's for
your MTA to do.
If you use ClamAV as milter, it's up to ClamAV to tell the MTA what to
do so I guess there's a task for ClamAV too..
Simon Hobson wrote:
Per Jessen wrote:
It's not about not being able to scan, it's about not wanting to
scan. Regardless, clamav doesn't reject or approve mails, that's
for your MTA to do.
If you use ClamAV as milter, it's up to ClamAV to tell the MTA what
to do so I guess there's a
On 11/08/11 17:41, Peter Bradeen wrote:
I see that there are ways to limit the level of archive that will be
scanned as well as the size of the entities to be scanned. Is there a way
for CLAMAV to then flag them as not allowed? Seem that if you can't scan
it, it should be rejected.
Hi
Per Jessen wrote:
The OP started by saying there are ways to limit the level of archive
that will be scanned as well as the size of the entities to be
scanned, which are performance optimizing options one can use if
desired. To which I commented that it's not about a message that can't
be
On 11/09/2011 10:42 PM, Simon Hobson wrote:
Per Jessen wrote:
The OP started by saying there are ways to limit the level of archive
that will be scanned as well as the size of the entities to be
scanned, which are performance optimizing options one can use if
desired. To which I commented
