On 2017-02-13 14:39, Reindl Harald wrote:
Am 13.02.2017 um 14:33 schrieb TBits.net, Mailinglists:
On 2017-02-13 13:19, Reindl Harald wrote:
Am 13.02.2017 um 13:05 schrieb TBits.net, Mailinglists:
Hi @all,
clamav-milter identify an email as infected by
Heuristics.Phishing.Email.SSL-Spoof.
Thi
Am 13.02.2017 um 14:33 schrieb TBits.net, Mailinglists:
On 2017-02-13 13:19, Reindl Harald wrote:
Am 13.02.2017 um 13:05 schrieb TBits.net, Mailinglists:
Hi @all,
clamav-milter identify an email as infected by
Heuristics.Phishing.Email.SSL-Spoof.
This is correct, but when I scan this file i
On 2017-02-13 13:19, Reindl Harald wrote:
Am 13.02.2017 um 13:05 schrieb TBits.net, Mailinglists:
Hi @all,
clamav-milter identify an email as infected by
Heuristics.Phishing.Email.SSL-Spoof.
This is correct, but when I scan this file in the quarantine with
clamdscan or clamscan the file is cle
Am 13.02.2017 um 13:05 schrieb TBits.net, Mailinglists:
Hi @all,
clamav-milter identify an email as infected by
Heuristics.Phishing.Email.SSL-Spoof.
This is correct, but when I scan this file in the quarantine with
clamdscan or clamscan the file is clean.
It seams that the clamscan or clamdsc
Hi @all,
clamav-milter identify an email as infected by
Heuristics.Phishing.Email.SSL-Spoof.
This is correct, but when I scan this file in the quarantine with
clamdscan or clamscan the file is clean.
It seams that the clamscan or clamdscan do not scan this file for
Phishing.
Is it possible