search for: dovecot_log

...> When a host has been banned, can you look at the iptables rules to see > what is actually being applied. Hi Pete, I did wonder that myself. I have now amended to Dovecot definition in jail.conf to: [dovecot] port = pop3,pop3s,imap,imaps,submission,sieve,25,1025,465,587 logpath = %(dovecot_log)s backend = %(dovecot_backend)s I then unbanned and banned each IP address manually with for F in 46.232.112.21 106.226.231.159 [snip] 52.38.234.254 ; do fail2ban-client set dovecot unbanip $F fail2ban-client set dovecot banip $F done which worked. However, having done this, the connections are...

...ILBOX_DOMAIN = '%d' #user_query = SELECT MAILBOX_ROOT AS home,uid,gid FROM MAIL WHERE MAILBOX_USERNAME = '%n' and MAILBOX_DOMAIN='%d' dovecot config file base_dir = /var/run/dovecot/ protocols = imap pop3 imap_listen = * pop3_listen = * ssl_disable = yes log_path = /var/log/dovecot_log info_log_path = /var/log/dovecot_info_log log_timestamp = "%b %d %H:%M:%S " login_dir = /var/run/dovecot/login login = imap login_executable = /usr/local/libexec/dovecot/imap-login login_user = dovecot login_process_size = 16 login_process_per_connection = yes login_processes_count = 3 lo...

...5 | +------------------------+----------------+-------------+ 6 rows in set (0.00 sec) pls help :-) dovecot -n # 1.1.8: /etc/dovecot/etc/dovecot.conf # OS: Linux 2.6.22.14-72.fc6 x86_64 Fedora Core release 6 (Zod) ext3 base_dir: /etc/dovecot/var/run/dovecot/ log_path: /etc/dovecot/var/log/dovecot_log info_log_path: /etc/dovecot/var/log/dovecot_log protocols: imaps ssl_cert_file: /etc/pki/dovecot/server.crt ssl_key_file: /etc/pki/dovecot/server.key ssl_cipher_list: ALL:!ADH!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM verbose_ssl: yes login_dir: /etc/dovecot/var/run/dovecot/login login_executable: /etc/dovecot...

...ota: mysql:/etc/dovecot-dict-quota.conf expire: mysql:/etc/dovecot-dict-expire.conf 2: Installation B # 1.1.19: /usr/local/dovecot/etc/dovecot.conf # OS: Linux 2.6.22.14-72.fc6 x86_64 Fedora Core release 6 (Zod) base_dir: /usr/local/dovecot/var/run/dovecot/ log_path: /usr/local/dovecot/var/log/dovecot_log info_log_path: /usr/local/dovecot/var/log/dovecot_log protocols: imaps ssl_cert_file: /usr/local/ssl/certs/dovecot/certificate_04102009.crt ssl_key_file: /usr/local/ssl/certs/dovecot/privateKey_04102009.key ssl_cipher_list: ALL:!ADH!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM verbose_ssl: yes login_dir: /usr/loc...

> > I did wonder that myself. I have now amended to Dovecot definition in jail.conf to: > > [dovecot] > > port = pop3,pop3s,imap,imaps,submission,sieve,25,1025,465,587 > logpath = %(dovecot_log)s > backend = %(dovecot_backend)s > > I then unbanned and banned each IP address manually with Did you reload the configuration? ("fail2ban-client reload") What action are you using - you mention ipset, are you using iptables- ipset-proto4? I don't know anything about ips...

On Monday 29 April 2019 02:21:05 Gordon Messmer wrote: > That's one approach.? I believe that you could modify fewer files by > setting "port = 0:65535" in your definition in "jail.local" and not > install firewallcmd-ipset.local. I have just tried this, and re-started fail2ban. It does not seem to have worked. I have looked at /var/log/exim/main.log and found

On Friday 19 April 2019 15:19:26 Pete Biggs wrote: > > I've added a fail regex to /etc/fail2ban/filter.d/exim.conf as suggested > > on another page: > > The standard exim.conf already has a 535 filter. Was that not working > for you? I was following the instructions as shown on the page. I did find after sending my post that there was already a regex in the standard

Hi, On 27-06-2016 08:58, Mark Foley wrote: > So, I'm apparently lacking in the kerberos stuff. Here's the problem -- Samba4 uses Heimdal > Kerberos and when I provisioned my domain apparently none of these needed kerberos files were > set up. I can, however, kerberos authenticate from domain workstations both WIN7 and Linux. You don't need any Samba4 stuff, to get it