Am 10.01.2015 um 22:07 schrieb Marcin Mirosław:
W dniu 2015-01-10 o 15:27, Reindl Harald pisze:
Am 10.01.2015 um 15:19 schrieb David Flanigan:
Is anyone using the Malware Patrol 3rd party Spamassassin Rules
(https://www.malwarepatrol.net/index.shtml)?
I have downloaded and looked them over a
W dniu 2015-01-10 o 15:27, Reindl Harald pisze:
>
> Am 10.01.2015 um 15:19 schrieb David Flanigan:
>> Is anyone using the Malware Patrol 3rd party Spamassassin Rules
>> (https://www.malwarepatrol.net/index.shtml)?
>>
>> I have downloaded and looked them over and, in concept, they look pretty
>> go
opendkim have minimal keysize of 1024, else its considered invalid, so i
am asking should Mail::DKIM follow this as valid or invalid even if the
key check is PASS ?
this leads to spamassassin VALID, but opendkim testing INVALID
hmm
Hi folks,
I'm very new to SpamAssassin and have some issues getting log messages I
can't get rid of.
I'm running a server with ubuntu 14.04.1 and spamassassin version
3.4.0-1ubuntu2. Spamassassin was installed from the ubuntu repositories.
1. When I stop spamassassin I get the following message:
Am 10.01.2015 um 18:14 schrieb Steve:
On 10/01/2015 14:35, Jeff Mincy wrote:
use blacklist_to bogus_us...@mydomain.com ... This will lead to hits
on USER_IN_BLACKLIST_TO
That works perfectly to blacklist 'completely bogus' "To" addresses.
Many thanks.
On 10/01/2015 14:36, Reindl Harald wrote
Am 10.01.2015 um 17:39 schrieb Martin Gregorie:
> On Sat, 2015-01-10 at 15:36 +0100, Reindl Harald wrote:
>> headerCUST_LESS_SPAM_TO X-Local-Envelope-To =~
>> /^(\|\)$/i
>> score CUST_LESS_SPAM_TO 4.0
>> describe CUST_LESS_SPAM_TO Custom Scoring
>>
> That is pretty much what I'd do, ex
Steve skrev den 2015-01-10 15:23:
If I were to have a list of a few dozen email addresses of the form:
bogus_us...@mydomain.com
onlyspample...@mydomain.com
...
unwantedrubb...@mydomain.com
blacklist_from *@mydomain.com
blacklist_to *@mydomain.com
unblacklist_to trusted_recipi...@mydomain.co
On 10/01/2015 14:35, Jeff Mincy wrote:
use blacklist_to bogus_us...@mydomain.com ... This will lead to hits on
USER_IN_BLACKLIST_TO
That works perfectly to blacklist 'completely bogus' "To" addresses.
Many thanks.
On 10/01/2015 14:36, Reindl Harald wrote:
it can work like below by let ad
On Sat, 2015-01-10 at 15:36 +0100, Reindl Harald wrote:
> headerCUST_LESS_SPAM_TO X-Local-Envelope-To =~
> /^(\|\)$/i
> score CUST_LESS_SPAM_TO 4.0
> describe CUST_LESS_SPAM_TO Custom Scoring
>
That is pretty much what I'd do, except that I wouldn't write the rule
directly because I d
Am 10.01.2015 um 15:23 schrieb Steve:
I have a domain for which (for historic reasons) I want a catch-all rule
to accept email. Until recently, Spamassassin has done a great job of
separating the ham from the spam. Recently, I've been receiving a large
number of spam emails which have been misc
From: Steve
Date: Sat, 10 Jan 2015 14:23:36 +
I have a domain for which (for historic reasons) I want a catch-all rule
to accept email. Until recently, Spamassassin has done a great job of
separating the ham from the spam. Recently, I've been receiving a large
num
Am 10.01.2015 um 15:19 schrieb David Flanigan:
Is anyone using the Malware Patrol 3rd party Spamassassin Rules
(https://www.malwarepatrol.net/index.shtml)?
I have downloaded and looked them over and, in concept, they look pretty
good.
However the cf file is over 8.5megs (yes megs) in size. By
I have a domain for which (for historic reasons) I want a catch-all rule
to accept email. Until recently, Spamassassin has done a great job of
separating the ham from the spam. Recently, I've been receiving a large
number of spam emails which have been misclassified as ham. These
annoying
Hello,
Is anyone using the Malware Patrol 3rd party Spamassassin Rules
(https://www.malwarepatrol.net/index.shtml)?
I have downloaded and looked them over and, in concept, they look pretty
good.
However the cf file is over 8.5megs (yes megs) in size. By far the
biggest ruleset I have. I ca
On 09.01.15 21:46, Juan Pablo wrote:
sa-update -D gives the follow
# sa-update -D
[27738] dbg: logger: adding facilities: all
[27738] dbg: logger: logging level is DBG
[27738] dbg: generic: SpamAssassin version 3.2.5
you apparently have non-system version of spamassassin installed.
run "whic
On 10.01.15 00:34, Steffen Mutter wrote:
I just started fiddling around with spamassassin, very good software
but a high level of complexity. Already run into several problems
because mail headers were not rewritten and whitelisting of mails did
fail -> had to trigger amavis to do the job.
sa
On Sat, 10 Jan 2015 00:34:49 +0100
Steffen Mutter wrote:
> Hi,
>
> I just started fiddling around with spamassassin, very good software
> but a high level of complexity. Already run into several problems
> because mail headers were not rewritten and whitelisting of mails did
> fail -> had to trig
17 matches
Mail list logo
