search for: unbanned

...er, because I'm still banned. I seemed to be Emmett's favorite person to pick on. He told me to "eat a bag of dick" in his Ogg internet radio station thing, and generally ruined my reputation as a self-respecting programmer in #vorbis. Blah...anyway. Is there any way I can get unbanned? --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages se...

man_in_shack banned me during a casual conversation where i was explaining my dual x server wine setup, saying I was contradicting myself. I obviously wasn't trying to contradict myself, if I did, and I don't see how this is ban-worthy under any circumstance.

I've followed one of the pages on line specifically for installing fail2ban on Centos 7 and all looks fine. I've added a fail regex to /etc/fail2ban/filter.d/exim.conf as suggested on another page: \[<HOST>\]: 535 Incorrect authentication data which appears to be successfully matchnig lines in /var/log/exim/mail.log such as 2019-04-19 13:06:10 dovecot_plain

> 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? > > \[<HOST>\]: 535 Incorrect authentication data > > which appears to be successfully matchnig lines in /var/log/exim/mail.log such > as > > 2019-04-19 13:06:10 dovecot_plain

I got the fail2ban from epel. There were a number of issues relating to using a log file... logwatch was looking for both fail2ban and fail2ban.log logrotate file fail2ban added looked for fail2ban.log and then reset itself to syslog fail2ban itself went to syslog, over riding its fail2ban.log. took a while, but I use /var/log/fail2ban now, that finally worked through logrotates and logwatch.

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

...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 still getting through to EXIM. [root at ollie2...

I find csf/lfd much easier to configure and can be used in combination with fail2ban. Gary Stainburn <gary.stainburn at ringways.co.uk> wrote: >I've followed one of the pages on line specifically for installing fail2ban on >Centos 7 and all looks fine. > >I've added a fail regex to /etc/fail2ban/filter.d/exim.conf as suggested on >another page: > >

On Sat, Aug 03, 2019 at 04:50:05PM +0100, Giles Coochey wrote: > > On 02/08/2019 19:38, Jon LaBadie wrote: > > On Fri, Aug 02, 2019 at 10:19:49AM -0400, mark wrote: > > > Fred Smith wrote: > > > > On Fri, Aug 02, 2019 at 09:28:23AM -0400, mark wrote: > > > <MVNCH> > > I've been using fail2ban for some time, I have a number of ports open

> > 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 ipset, but can you see what ports are being blocked in the fail2ban...

On 05/08/2019 08:50, Jon LaBadie wrote: > > I've found the default 10min bans hardly bother some attackers. > So I've added the "recidive" feature of fail2ban. After the > second 10min ban, the attacker is blocked for 1 week. > Interesting, didn't know about that feature, but, oh, I just generally ban for a whole week regardless, yes, I realise that a typo

...aemons (nmbd, smbd and winbind) and kills itself, node 1 claims : ctdb_recovery_lock: Failed to get recovery lock on '/ctdb/.ctdb.lock' (This directory is clvm + gfs2 shared, writable and correctly accessible from both nodes) This leads node 1 to get banned. Then, (I guess), when being unbanned, reelection occurs, but I get : Recmaster node 1 no longer available. Force reelection I suppose that node 1 can't become recmaster as it can not get the recovery lock. But there's no way I see why this node claims it can take this lock. I don't know if this may help, but : - I rem...

Hello folks, Recently more and more messages are being killed by xiph.org's postfix anti-spam filter, followed by pleading messages from the author to 'unban' them :-) There's no banning on the group, but the anti-spam filter doesn't take prisoners. Remember these tips: Mail in HTML format is unceremoniously dropped on the floor. You will not be informed it has been

Hello folks, Recently more and more messages are being killed by xiph.org's postfix anti-spam filter, followed by pleading messages from the author to 'unban' them :-) There's no banning on the group, but the anti-spam filter doesn't take prisoners. Remember these tips: Mail in HTML format is unceremoniously dropped on the floor. You will not be informed it has been

Changes in CTDB 2.2 =================== User-visible changes -------------------- * The "stopped" event has been removed. The "ipreallocated" event is now run when a node is stopped. Use this instead of "stopped". * New --pidfile option for ctdbd, used by initscript * The 60.nfs eventscript now uses configuration files in /etc/ctdb/nfs-rpc-checks.d/ for

Changes in CTDB 2.5 =================== User-visible changes -------------------- * The default location of the ctdbd socket is now: /var/run/ctdb/ctdbd.socket If you currently set CTDB_SOCKET in configuration then unsetting it will probably do what you want. * The default location of CTDB TDB databases is now: /var/lib/ctdb If you only set CTDB_DBDIR (to the old default of

I have been using centos 6 in a virtualized system for a few months now. Took a while to batten down the hatches with postfix, rbls, and to use fail2ban correctly. The mailserver for my website(s) are located on the http server as well..an 'all in one' server. DNS servers are separated. My two sites, and their emails addresses (1 for each) have been around for 10 and 15 years

On Mon, March 9, 2015 13:11, John Plemons wrote: > Been working on fail2ban, and trying to make it work with plain Jane > install of Centos 7 > > Machine is a HP running 2 Quad core Xeons, 16 gig or ram and 1 plus TB > of disk space. Very generic and vanilla. > > Current available epel repo version is fail2ban-0.9.1 > > Looking at the log file, fail2ban starts and stops

Hello, I'm looking for some advice on securing Asterisk. Recently my servers been under several brute-force SIP attacks. I have several remote sites, as well as many roaming users, who may have PC softclients and/or SIP based hardphones. My first step will be to strengthen the passwords in use, and for the hardphones to restrict by IP address, but that still leaves the softphone