Header of test message, massaged for privacy, is here:
http://pastebin.com/EV6g15aN
I have this in user_prefs:
trusted_networks 198.1.2.3/32
[...lots snipped...]
whitelist_from_rcvd *@wetransfer.com *.wetransfer.com
Why is the whitelist not firing?
--
Please *no* private copies of
On 25 Feb 2015, at 17:15, Yves Goergen wrote:
Am 25.02.2015 um 20:42 schrieb Bill Cole:
On 24 Feb 2015, at 17:06, Yves Goergen wrote:
I can't block all archives with executable files in them.
Then in all seriousness: why bother filtering email specifically for
malware?
Email is an
I was preparing to ask about an error message I was getting when I started up
spamd:
spamd[18145]: config: failed to parse line, skipping, in
/usr/local/etc/mail/spamassassin/whitelist.cf: whitelist_from_spf
*@covisp.net *@kreme.com
But I fixed the problem. It turns out that the SPF plugin
Matteo Dessalvi wrote:
I am using a centralized Redis instance to
host the bayesian data for a bunch of MTAs.
AFAICS the SA filter is working quite well
and the BAYES_* rules are triggered correctly,
no false positive so far.
But I am concerned about the expiration of the
bayesian data.
On 27.02.2015 13:54, Axb wrote:
Is it possible you reject so much spam tha SA sees very little spam?
I believe it's the case. A combination of Postfix policies, blacklists,
ClamAV plus additional signatures, etc. greatly reduces the amount of
email sent through the filtering pipeline.
If
On 02/27/2015 01:38 PM, Matteo Dessalvi wrote:
Hi all.
I am using a centralized Redis instance to
host the bayesian data for a bunch of MTAs.
AFAICS the SA filter is working quite well
and the BAYES_* rules are triggered correctly,
no false positive so far.
But I am concerned about the
Thanks a lot for the explanation Mark, it was very clear.
It would be a good idea considering to add that to the
perldoc of the BayesStore/Redis.pm module.
Regards,
Matteo
On 27.02.2015 14:55, Mark Martinec wrote:
When redis automatically expires tokens internally based on their
TTL, this
Hi all.
I am using a centralized Redis instance to
host the bayesian data for a bunch of MTAs.
AFAICS the SA filter is working quite well
and the BAYES_* rules are triggered correctly,
no false positive so far.
But I am concerned about the expiration of the
bayesian data. sa-learn reports the
