[Bug 1656856] Re: fail2ban looks in wrong log for postfix

2020-01-07 Thread ñull
I posted it as https://github.com/fail2ban/fail2ban/issues/2589


** Bug watch added: github.com/fail2ban/fail2ban/issues #2589
   https://github.com/fail2ban/fail2ban/issues/2589

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656856

Title:
  fail2ban looks in wrong log for postfix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1656856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656856] Re: fail2ban looks in wrong log for postfix

2020-01-07 Thread ñull
Still present in 18.04LTS. For instance the first postfix jail filter
rule catching RBL blacklisted intruders:

^%(__prefix_line)sNOQUEUE: reject: RCPT from \S+\[\]: 554 5\.7\.1
.*$

It simply does not appear in mail.warn making the rule basically
useless.

I will repost this on https://github.com/fail2ban/fail2ban/issues

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656856

Title:
  fail2ban looks in wrong log for postfix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1656856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656856] Re: fail2ban looks in wrong log for postfix

2020-01-07 Thread ñull
on 18.04 LTS this is still an issue. mail.warn just does not include all
the intrusion attempts making it complicated to jail them. An example is
on of the default filter rules:

^%(__prefix_line)sNOQUEUE: reject: RCPT from \S+\[\]: 554 5\.7\.1
.*$

It simply does not appear in mail.warn but it does in mail.log .

What would be a work around in stead of waiting for a fix?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656856

Title:
  fail2ban looks in wrong log for postfix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1656856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656856] Re: fail2ban looks in wrong log for postfix

2019-02-28 Thread Bill McGonigle
Seems to have been fixed upstream with the package:
 
https://github.com/fail2ban/fail2ban/commit/57ea38c342b2caa17b61a8cd17f142c218fd0742

and in 0.10.2-2.1 in Debian, but not backported to 0.9.6-2 in Debian or
0.9.3-1 in Ubuntu 16.04.5 LTS, so this is still failing to detect
certain attempted intrusions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656856

Title:
  fail2ban looks in wrong log for postfix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1656856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656856] Re: fail2ban looks in wrong log for postfix

2017-08-14 Thread Jonathan Kamens
Seven months old and no progress on fixing this SECURITY BUG?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656856

Title:
  fail2ban looks in wrong log for postfix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1656856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1656856] Re: fail2ban looks in wrong log for postfix

2017-03-26 Thread scnaifeh
This may also be related to the following bugs.

#1482899
#1669512
#1645693

If postfix jail is enabled at time of upgrade, upgrading fails because
when fail2ban attempts to restart after upgrade, it can't find the
postfix log file now set in paths-delian.conf.

Also occurs if dovecot jail is enabled, because by default, dovecot jail
looks in the same log file as postfix jail.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656856

Title:
  fail2ban looks in wrong log for postfix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1656856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1656856] Re: fail2ban looks in wrong log for postfix

2017-03-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: fail2ban (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656856

Title:
  fail2ban looks in wrong log for postfix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1656856/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs