similar to: Mail account brute force / harassment

Marc, There is a strategy loosely referred to as "choose your battles well" :-) Let the others bother with their own problems. If you can, hack the server and dump the 500GB - you'll be using resources transferring the 500GB as the other server receives it. Two servers wasting resources because you think you are punishing an offender! On Thu, 11 Apr 2019 at 13:43, Marc Roos

> Am 11.04.2019 um 12:43 schrieb Marc Roos via dovecot <dovecot at dovecot.org>: > > Please do not assume anything other than what is written, it is a > hypothetical situation > > > A. With the fail2ban solution > - you 'solve' that the current ip is not able to access you > - it will continue bothering other servers and admins > - you get the

Please do not assume anything other than what is written, it is a hypothetical situation A. With the fail2ban solution - you 'solve' that the current ip is not able to access you - it will continue bothering other servers and admins - you get the next abuse host to give a try. B. With 500GB dump - the owner of the attacking server (probably hacked) will notice it will be

On Thu, 11 Apr 2019 at 13:24, Marc Roos via dovecot <dovecot at dovecot.org> wrote: > > > Say for instance you have some one trying to constantly access an > account > > > Has any of you made something creative like this: > > * configure that account to allow to login with any password > * link that account to something like /dev/zero that generates infinite

Say for instance you have some one trying to constantly access an account Has any of you made something creative like this: * configure that account to allow to login with any password * link that account to something like /dev/zero that generates infinite amount of messages (maybe send an archive of virusses?) * transferring TB's of data to this harassing client. I think it would be

Bump! On Fri, 16 Oct 2020 at 13:26, Odhiambo Washington <odhiambo at gmail.com> wrote: > > > On Fri, 16 Oct 2020 at 13:15, Aki Tuomi <aki.tuomi at open-xchange.com> > wrote: > >> >> > On 16/10/2020 13:11 Odhiambo Washington <odhiambo at gmail.com> wrote: >> > >> > >> > >> > >> > >> > On Fri, 16

On 11 Apr 2019, at 04:43, Marc Roos via dovecot <dovecot at dovecot.org> wrote: > B. With 500GB dump > - the owner of the attacking server (probably hacked) will notice it > will be forced to take action. Unlikely. What is very likely is that your ISP shuts you don for network abuse. > If abuse clouds are smart (most are) they would notice that attacking my > servers, will

On Fri, 16 Oct 2020 at 13:15, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 16/10/2020 13:11 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > > > > > On Fri, 16 Oct 2020 at 08:19, Aki Tuomi <aki.tuomi at open-xchange.com> > wrote: > > > > On 15/10/2020 18:14 Odhiambo Washington <odhiambo

Yes indeed, we have already own dnsbl's for smtp and ssh/ftp access. How do you have one setup for dovecot connections? -----Original Message----- From: James via dovecot [mailto:dovecot at dovecot.org] Sent: donderdag 11 april 2019 13:25 To: dovecot at dovecot.org Subject: Re: Mail account brute force / harassment On 11/04/2019 11:43, Marc Roos via dovecot wrote: > A. With the

On Mon, 19 Oct 2020 at 09:27, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 19/10/2020 09:16 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > Bump! > > > > > > On Fri, 16 Oct 2020 at 13:26, Odhiambo Washington <odhiambo at gmail.com> > wrote: > > > > > > > > > > > > On

On Fri, 16 Oct 2020 at 08:19, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > On 15/10/2020 18:14 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > Here is what I see on the error.log: > > > > Oct 15 17:37:58 imap(technical at mydomain.name)<62260><9ucgmLax7s3F6FH2>: > Error: Mailbox INBOX: Cache /var/spool/virtual/

On 29 March 2018 at 13:26, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On 29.03.2018 13:14, Odhiambo Washington wrote: > > > > On 29 March 2018 at 13:04, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> >> >> On 29.03.2018 10:36, Odhiambo Washington wrote: >> >> >> >> On 29 March 2018 at 09:43, Aki Tuomi

> On 19/10/2020 09:48 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > On Mon, 19 Oct 2020 at 09:27, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > On 19/10/2020 09:16 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > > Bump! > > > > > > >

Bueno. I don't even remember well. Wasn't that issue about mysql-8.0.12 to 8.0.13?? On Tue, 5 Feb 2019 at 23:46, Larry Rosenman <larryrtx at gmail.com> wrote: > 2.3.4 had the same compile issues.... > > > On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington <odhiambo at gmail.com> > wrote: > >> Noted. >> >> I will wait for dovecot-2.3.4.2

> On 16/10/2020 13:11 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > On Fri, 16 Oct 2020 at 08:19, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 15/10/2020 18:14 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > > Here is what I see on the error.log: > > >

On Mon, 17 Jun 2019 at 21:03, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 17 June 2019 20:55 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > > > > > On Mon, 17 Jun 2019 at 20:45, Aki Tuomi via dovecot <dovecot at dovecot.org> > wrote: > > > > > > > On 17 June 2019 18:59

> On 19/10/2020 09:16 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > Bump! > > > On Fri, 16 Oct 2020 at 13:26, Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > On Fri, 16 Oct 2020 at 13:15, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > > > On 16/10/2020 13:11

On Thu, 20 Dec 2018 at 15:54, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > On 20 December 2018 at 14:33 Odhiambo Washington < odhiambo at gmail.com> > wrote: > > > On Thu, 20 Dec 2018 at 15:23, Aki Tuomi < aki.tuomi at open-xchange.com> > wrote: > > > > > On 20 December 2018 at 14:10 Odhiambo Washington < odhiambo at gmail.com>

On 29 March 2018 at 13:04, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On 29.03.2018 10:36, Odhiambo Washington wrote: > > > > On 29 March 2018 at 09:43, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> >> >> On 28.03.2018 22:14, Odhiambo Washington wrote: >> >> >> >> On 27 March 2018 at 20:06, <aki.tuomi at

Noted. I will wait for dovecot-2.3.4.2 tarball then. In all the servers I listed (+2 more), I never use the mail/dovecot port. I rely on mail/dovecot port on my own prototype (FreeBSD 12) which I have built in preparation for the upgrade of all the servers I currently have (except the 11.2). So for now, they have to run with 2.3.4, because of that reason - I am not using the port. And yes, I