Hi All,
I spent some quality time yesterday, tuning dovecot on a server which serves as
an imap-proxy in front of a zimbra setup
the imap proxy does ldap client-cert authentication and works well.
BUT
I found that the imap-login processes seem to gain 100 MB per connection they
are accepti
On 8/24/21 6:46 PM, William Edwards wrote:
I think the general concensus is that containerisation isn't always
better than 'normal' VMs. 'Easy deployment & scaling' is also perfectly
possible without containers.
Without a doubt VMs are a good solution. Containers use some of the same
techn
https://doc.dovecot.org/configuration_manual/dict/#dict-sql
https://doc.dovecot.org/configuration_manual/dict/#dict-proxy
https://doc.dovecot.org/configuration_manual/dict/proxy/
I can't get the complete picture from these pages how to implement proxy
with sql. I have direct sql setup now, how d
For the record, we also use 554 for Over Quota, but it is an interesting
topic for conversation, eg why do we even indicate a permanent failure,
when of course the person might make room in the next couple of hours.
It MIGHT be preferred to let the sender know as soon as possible, so he
can ad
Hi Vincent,
thanks for your investigations!
Il 01/09/21 11:27, Vincent Brillault ha scritto:
Dear all,
Just a status update, in case this can help others.
We went forward and disabled the position information indexing and the
re-indexed of our mail data (over a couple of days to avoid
overl
https://doc.dovecot.org/configuration_manual/lastlogin_plugin/
Is there any documentation about how to get the "Last Login" info into the
PostfixAdmin database ?
Hello,
thanks for the reply.
On Thu, 2 Sep 2021 12:47:43 +0300 (EEST) Aki Tuomi wrote:
> Would it be possible to workaround this with:
>
> mail_location = maildir:~/Mail/
>
Maybe, but that is not feasible in our deployment, which is LDAP driven
and thus looks like this:
mail_location = maild
Would it be possible to workaround this with:
mail_location = maildir:~/Mail/
Aki
> On 02/09/2021 11:21 Christian Balzer wrote:
>
>
> Hello,
>
> it is now nearly 2 years later and we are running 2.3.13 with this bug
> still present.
> Would be nice if it were acknowledged at least if not ev
Hello,
it is now nearly 2 years later and we are running 2.3.13 with this bug
still present.
Would be nice if it were acknowledged at least if not even fixed.
And it was confirmed by other people who contacted me directly after
seeing the original report here.
Regards,
Christian
On Wed, 5 Feb
