similar to: Fwd: Re: IP drop list

I wonder if there is an easy way to provide dovecot a flat text file of ipv4 #'s which should be ignored or dropped? I have accumulated 45,000+ IPs which routinely try dictionary and 12345678 password attempts. The file is too big to create firewall drops, and I don't want to compile with wrappers *if* dovecot has an easy ability to do this. If dovecot could parse a flat text file of

On 04 Mar 2015, at 21:46 , Jim Pazarena <dovecot at paz.bz> wrote: > On 2015-03-02 2:02 AM, Jochen Bern wrote: >> On 03/01/2015 08:53 AM, Jim Pazarena wrote: >>> I wonder if there is an easy way to provide dovecot a flat text file of >>> ipv4 #'s which should be ignored or dropped? >>> >>> I have accumulated 45,000+ IPs which routinely try

It works ! It was THAT easy ! Can you suggest how to replace the hair I pulled out ? :-) On 2016-12-29 5:27 PM, Larry Rosenman wrote: > login_access_sockets = tcpwrap > > service tcpwrap { > unix_listener login/tcpwrap { > group = $default_login_user > mode = 0600 > user = $default_login_user > } > } > > > > On Thu, Dec 29, 2016 at

V2 of dovecot has had the following releases (to recap) 2.0.0 2010-08-16 2.0.1 2010-08-24 2.0.2 2010-09-08 2.0.3 2010-09-17 2.0.4 2010-09-26 2.0.5 2010-10-01 I am on FreeBSD, and the port committers want to wait till dovecot V2 "stabilizes" prior to adding it to the FreeBSD ports base. So, my question is, respectfully, is dovecot V2.0.5 stable enough for prime-time on a busy ISP

I have compiled dovecot2 for FreeBSD with the tcpwrap option. A tcpwrap binary gets built and resides in the FreeBSD directory /usr/local/libexec/dovecot an examination of the compiled options (using the FreeBSD pkg install dovecot2) confirms: LIBWRAP : on yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap I get the following logged error message: 20161229 17:02:49

Hi, I wonder if there will be a 3rd and 4th disk (additional Packages) to 4.8-Release ... or won't there like in 5.0-Release. Thanks! Zheyu -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte l?cheln! Fotogalerie online mit GMX ohne eigene Homepage!

On 03/01/2015 08:53 AM, Jim Pazarena wrote: > I wonder if there is an easy way to provide dovecot a flat text file of > ipv4 #'s which should be ignored or dropped? > > I have accumulated 45,000+ IPs which routinely try dictionary and > 12345678 password attempts. The file is too big to create firewall > drops [...] The inherent assumption here is that dovecot, using a

On 03/01/2015 04:25 AM, Reindl Harald wrote: >> I wonder if there is an easy way to provide dovecot a flat text >> file of ipv4 #'s which should be ignored or dropped? >> >> I have accumulated 45,000+ IPs which routinely try dictionary >> and 12345678 password attempts. The file is too big to create >> firewall drops, and I don't want to compile with

On 25.04.24 17:15, openssh-unix-dev-request at mindrot.org digested: > Subject: how to block brute force attacks on reverse tunnels? > From: Steve Newcomb <srn at coolheads.com> > Date: 25.04.24, 17:14 > > For many years I've been running ssh reverse tunnels on portable Linux, > OpenWRT, Android etc. hosts so they can be accessed from a server whose > IP is stable

Can anyone share the proper config to get wrappers working in dovecot on FreeBSD? The dovecot examples do not seem to work, and I thought perhaps FBSD needs slightly different configs. I've compiled with: -DHAVE_LIBWRAP which I presume is the first step. The example for dovecot.conf in uncommenting: login_access_sockets = tcpwrap merely causes a log error of "imap-login: Error:

Does IMAP create much additional system load vs. POP3?

Am 02.03.2015 um 18:56 schrieb Robert Schetterer: > perhaps and i mean really "perhaps" go this way > > https://sys4.de/de/blog/2014/03/27/fighting-smtp-auth-brute-force-attacks/ > > https://sys4.de/de/blog/2012/12/28/botnets-mit-rsyslog-und-iptables-recent-modul-abwehren/ > > 45K+ IPs will work in a recent table > i have them too but for smtp only like > >

after having my own dnsbl feeded by a honeypot and even mod_security supports it for webservers i think dovecot sould support the same to prevent dictionary attacks from known bad hosts, in our case that blacklist is 100% trustable and blocks before SMTP-Auth while normal RBL's are after SASL i admit that i am not a C/C++-programmer, but i think doing the DNS request and in case it has a

Estimados usarios de R: Tengo una base de datos madre en formato .sav de SPSS y la quiero modificar usando datos de otras base de datos .sav y otra en .csv a las que llamare hijos. No tengo problema en convertirlas en data.frame. Todos los archivos tienen en común una variable que es única. En aquellos casos que les falta un valor a una variable en el archivo madre lo relleno con el valor del

On Fri, Mar 15, 2019 at 09:10:26AM +0000, Jochen Bern wrote: > Imagine sysadminning a boatload of VMs getting IPs from a dynamic pool, a la > > $ for ADDR in $CUSTOMER_1_RANGE $CUSTOMER_2_RANGE... ; do > > ping -c 1 -w 2 $ADDR >/dev/null 2>&1 && ssh root@$ADDR do_urgent_fix > > done > > , and it mightn't be that much of a niche anymore ... And

Hi Jochen, On Wed, 12 Feb 2020 at 00:16, Jochen Bern <Jochen.Bern at binect.de> wrote: > > On 02/11/2020 07:07 PM, Cl?ment P?ron wrote: > > - I have X devices (around 30) and one SSH server > > - Each of them have a unique public key and create one dynamic reverse > > port forwarding on the server > > - All of them connect with the same UNIX user (I don't

Hello everyone, my workplace has gotten the idea of centrally maintaining a file in ssh_config syntax so that employees do not need to discover every new machine and configure it on their own. Since it's a case of "let's get started now, and properly think it through later", right now, a typical entry might look like > Host [product]-[Customer] > Hostname

Hello: We have a TDM2433E Digium Card (12 FXS, 12 FXO) and Asterisk 1.8.7.0 running. Everything seems to be ok but call transfers. This is the issue: *A, B, C and D are in FXS ports*. 1) A calls B. B anwers. 2) B tries to transfer the call to C dialing *2 (code for attended transfer). 3) A hears MOH. B dials number C. 4) Asterisk says the dialed number is incorrect or non existing. We tried

Contact info * Author: Timo Sirainen, tss at iki.fi <mailto:tss at iki.fi>. * Please use the Dovecot mailing list <http://www.dovecot.org/mailinglists.html> for questions about Dovecot. You don't have to subscribe to it. * Depending on your needs, commercial support may be available. Send a mail if you're interested. according to the above (from

I have just come to the realization that password encryption using the crypt function in linux, ONLY USES THE FIRST 8 CHARS. I have written routines using crypt allowing 16+ chars, and find that anything past 8 is ignored. Wow. Is there a way around this that can be used in dovecot, as well as encryption routines for an email front end? (not system users). It's the integration with