Creating a commercial version to reward the developers and fund future
> development is fine; I applaud it.
>
> But it really smells like the current move with Director is crossing a line.
>
> Those in charge of making this decision would do well to pay very close
> attention
I think the only thing they will gain is a community that is angry and will in
the end leave the product / fork the complete product.
Jan Hugo
On November 2, 2022 5:39:53 PM GMT+01:00, Brad Schuetz wrote:
>On 11/2/22 03:54, Aki Tuomi wrote:
>>> On 02/11/2022 11:55 EET Frank Wall wrote:
>>>
>>
Even more easy, start by examining the mail headers to see where the mail was
blocked.
Jhp
On October 23, 2022 4:05:51 PM GMT+02:00, Aki Tuomi
wrote:
>Hi!
>
>This is very unlikely to be a dovecot issue itself. There is nothing inside
>dovecot that would horde your emails for 2 hours before "d
f2b-sasl tcp -- * * 0.0.0.0/0
0.0.0.0/0 multiport dports 25,465
9691K 2788M ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0
134M 257G ACCEPT all -- * * 0.0.0.0/0
0.0.0.0/0 state RELATED,ESTABLISHED
Jan Hugo Prins
On 5/23/22 23:16
Look at fail2ban.
Should be able to do that for you.
Jan Hugo
On 5/23/22 21:11, Lloyd Zusman wrote:
I'm running dovecot 2.2.13 under Debian 8.
I'd like to force an immediate TCP socket disconnect after any imap
login attempt that fails.
Right now, if invalid credentials are supplied during
lot easier if we could do the migration without this.
Jan Hugo Prins
On 3/20/22 21:36, Chris Hoogendyk wrote:
I'm posting to the list, but not on the list. I presume that means a
reply-all to get to me as well as the list?
We have two servers (dovecot --version: 2.2.22 (fe789d2)) t
