Paul, how are things looking from your side?
--
Joel Esler
Sr. Manager
Community, Branding, and Open Source
Talos Group
http://www.talosintelligence.com
On Aug 11, 2018, at 6:12 PM, Joel Esler (jesler)
mailto:jes...@cisco.com>> wrote:
I actually just made an adjustment today to see if that will
Hi,
We are looking for documentation that will help us "whitelist" a
sender's email. Thank you for any suggestions.
Wed Aug 8 07:37:00 2018 -> Message w78BaxBt005717 from
to <> with subject 'RE: '
message-id '<8q3v8vqrv8bva5u46f6qy0mf.1533728212...@email.android.com>'
date 'Wed, 8 Aug 2018 11
It's my experience that Heuristics.Phishing.Email.SpoofedDomain engine checks
URL's to make sure the hyperlink actually takes you to a site related to what
the text shows. I'm not aware of any public information on whitelisting these,
but do know it can be done by adding and x- or m- entry in th
Hi
You cannot whitelist a sender in ClamAV. Whitelisting happens in the
software that calls ClamAV.
The alternative is to disable spoofing checks in ClamAV configuration.
They're not enabled by default, so if your ClamAV checks spoofing, then
someone enabled it on purpose.
As Al already pointed
cd /path/to/clamav/signatures
echo -n offending.rule.name >> whitelist.ign2
ensure there is no trailing empty newline at the end of whitelist.ign2
On 14.08.2018 23:52, Groach wrote:
> Could you detail how to whitelist the offending rule please? (I fear it will
> be some time, or never, before
