* Aki Tuomi 2017.07.20 05:40:
> Should be fixed with
>
> commit 81e832796cdc6af790ed7be8a6c150889f03171c
> Author: Timo Sirainen
> Date: Wed Jul 19 23:19:12 2017 +0300
>
> virtual: Optimize mailbox_notify_changes() when there's only a single
> backend mailbox
>
> commit 2044eb7652b864a
> On July 19, 2017 at 9:16 PM Thomas Leuxner wrote:
>
>
> * Thomas Leuxner 2017.07.19 14:29:
>
> It seems to have a new side effect which I haven't noticed upfront as it does
> not produce logging in Dovecot:
>
Should be fixed with
commit 81e832796cdc6af790ed7be8a6c150889f03171c
Author: T
mj writes:
However, it seems almost all IPs are different, and I don't think I can
keep the above settings permanently.
Why not? Limited by firewall rules overload? You could probably use
a persistent DB, can't you?
I meant: keep the "block after the first failed attempt" setting. People
Hello there Larry !
No it is not a client issue... Because i have tried many clients and all the
same issue ! Actually the 1st client that refreshes the new email appear all
others not !
I have tried RoundCube/Outlook/Thunderbird/Android Email... etc All have the
same issue ..?
-Original
Hello there !
Is there anything wrong in the config i have sent earlier ..?
__ Information from ESET Endpoint Antivirus, version of detection
engine 15774 (20170719) __
The message was checked by ESET Endpoint Antivirus.
Email message - is OK
http://www.eset.com
* Thomas Leuxner 2017.07.19 14:29:
It seems to have a new side effect which I haven't noticed upfront as it does
not produce logging in Dovecot:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 io_loop_extract_notify_fd (ioloop=0x563456973540) at
ioloop-notify-inotify.c:224
224
* Aki Tuomi 2017.07.19 11:43:
> Should be fixed with
>
> commit 2f691d6dd1b98f605043744846534b828a43994d
> Author: Aki Tuomi
> Date: Wed Jul 19 12:03:58 2017 +0300
>
> virtual: Stop watching notification on backend box close
>
> Fixes Panic: file mail-index.c: line 662
> (mail_in
Hi everybody,
Thanks very much for the kind advises given yesterday and today.
I have now implemented the blocklist on
* http://list.blocklist.de/lists/all.txt
using the scripts here:
* https://forum.blocklist.de/viewtopic.php?f=11&t=84#
(a combi of bash and php)
For now, my server appears to
On 19/07/2017 11:23, mj wrote:
> Hi Robert,
>
> On 07/18/2017 11:43 PM, Robert Schetterer wrote:
>> i guess not, but typical bots arent using ssl, check it
>>
>> however fail2ban sometimes is to slow
>
> I have configured dovecot with
> auth_failure_delay = 10 secs
>
> I hope that before the 10
Hi Joseph,
On 07/18/2017 11:10 PM, Joseph Tam wrote:
However, it seems almost all IPs are different, and I don't think I can
keep the above settings permanently.
Why not? Limited by firewall rules overload? You could probably use
a persistent DB, can't you?
I meant: keep the "block after the
Hi Robert,
On 07/18/2017 11:43 PM, Robert Schetterer wrote:
i guess not, but typical bots arent using ssl, check it
however fail2ban sometimes is to slow
I have configured dovecot with
auth_failure_delay = 10 secs
I hope that before the 10 sec are over, dovecot will have logged about
the fa
On 19.07.2017 09:39, Aki Tuomi wrote:
>
> On 19.07.2017 09:36, Thomas Leuxner wrote:
>> * Aki Tuomi 2017.07.19 08:31:
>>
>>> oh and any idea which one of these crashes?
>> This one does:
>>
>> # cat Flagged/dovecot-virtual
>> *
>> :public/*
>> -Trash
>> -Trash/*
>> flagged
> Thanks, we'll look
om
>
>
>
>
> __ Information from ESET Endpoint Antivirus, version of detection
> engine 15767 (20170718) __
>
> The message was checked by ESET Endpoint Antivirus.
>
> Email message - is OK
>
> http://www.eset.com
>
>
> __ Information from
__
The message was checked by ESET Endpoint Antivirus.
Email message - is OK
http://www.eset.com
__ Information from ESET Endpoint Antivirus, version of detection
engine 15768 (20170718) __
The message was checked by ESET Endpoint Antivirus.
Email message - is OK
http://www
14 matches
Mail list logo
