On 2016-08-27 16:27, Nikolaos Milas wrote:
What may be a problem here?
you miss update of SPF plugin to a never version
you may need to if version > around rules there
so spf none only is used on versions that support it
upstream bug here
On Sat, Aug 27, 2016 at 05:27:18PM +0300, Nikolaos Milas wrote:
> Thank you Sean for all your help.
>
> I am focusing on amavisd-new / spamassassin for my efforts.
>
> I have started a thread in the amavisd-new users mailing list, since
> bayesian filtering is off-topic here.
>
> However, before
On 25/8/2016 7:46 μμ, Sean Greenslade wrote:
Make sure the SPF rules have weights set, then check the spam report for
a message. If SPF is working, you should see at least one of the SPF
rules trigger for every message.
Thank you Sean for all your help.
I am focusing on amavisd-new / spamassa
On Thu, Aug 25, 2016 at 05:28:35PM +0300, Nikolaos Milas wrote:
> On 23/8/2016 11:58 μμ, Sean Greenslade wrote:
>
> > Hope this is helpful,
>
> Thanks Sean for your time and eagerness to help. I appreciate it.
>
> I am planning to try your suggestions.
>
> I am using CentOS 6. Can you please le
On 23/8/2016 11:58 μμ, Sean Greenslade wrote:
Hope this is helpful,
Thanks Sean for your time and eagerness to help. I appreciate it.
I am planning to try your suggestions.
I am using CentOS 6. Can you please let me know about the perl package
SPF-related bug you mentioned?
I have install
On Tue, Aug 23, 2016 at 11:27:39PM +0300, Nikolaos Milas wrote:
> On 20/8/2016 7:56 μμ, Sean Greenslade wrote:
>
> > ...
> > - Enable & configure per-user bayesan filtering
> > - Increase allowed storage space for bayesan databases
> > - Update a particular perl package to make SPF work (CentOS /
On 20/8/2016 7:56 μμ, Sean Greenslade wrote:
...
- Enable & configure per-user bayesan filtering
- Increase allowed storage space for bayesan databases
- Update a particular perl package to make SPF work (CentOS / RHEL
specific bug)
...
- Re-weight a bunch of internal rules, in particular the
On Fri, Aug 19, 2016 at 04:30:38PM +0300, Nikolaos Milas wrote:
>
> We are already using postscreen, many RBLs, the fqrdns.pcre, amavis,
> spamassassin with scamp and we are filtering about 60-70% of total incoming
> mail as spam, but there is still much more that should be filtered out.
>
> Any
Nikolaos Milas:
> Hello,
>
> Has anyone developed and/or maintains PCRE filtering for porn spam senders?
>
> (Something like
> https://github.com/stevejenkins/hardwarefreak.com-fqrdns.pcre)
>
> I guess many sender / client domains could be filtered-away if they
> include keywords like "kiss",
On Fri, Aug 19, 2016 at 04:30:38PM +0300, Nikolaos Milas wrote:
> Hello,
>
> Has anyone developed and/or maintains PCRE filtering for porn spam senders?
>
> (Something like
> https://github.com/stevejenkins/hardwarefreak.com-fqrdns.pcre)
>
> I guess many sender / client domains could be filtered
On Fri, Aug 19, 2016 at 7:30 AM, Nikolaos Milas wrote:
> Hello,
>
> Has anyone developed and/or maintains PCRE filtering for porn spam senders?
>
> (Something like https://github.com/stevejenkins/hardwarefreak.com-fqrdns.
> pcre)
>
> I guess many sender / client domains could be filtered-away if
On 2016-08-19 19:56, Nikolaos Milas wrote:
[no porn seen]
I understand your suggestion to query the fail2ban db directly from
postfix but I need to research more on how to implement that.
yes if that could be done, it save alot, but if not fail2ban could
possible just call a wrapper that upd
On 19/8/2016 5:29 μμ, Benny Pedersen wrote:
fail2ban ?
Thank you,
I am already using fail2ban directly with the following rules:
/etc/fail2ban/filter.d/:
failregex = reject: RCPT from (.*)\[\]: 554
reject: RCPT from (.*)\[\]: 450
reject: RCPT from (.*)\[
On 2016-08-19 15:30, Nikolaos Milas wrote:
Any additional suggestions?
fail2ban ?
(permenent blocking is easy, hint, fail2ban uses sqlite db, its pretty
simple to query it from postfix sqlite map)
Hello,
Has anyone developed and/or maintains PCRE filtering for porn spam senders?
(Something like
https://github.com/stevejenkins/hardwarefreak.com-fqrdns.pcre)
I guess many sender / client domains could be filtered-away if they
include keywords like "kiss", "girl", "date", "adult", "cute",
15 matches
Mail list logo