Hi @Kurt I think For machines without IPv4, the behavior might be similar but
for IPv6 addresses. Dovecot generally tries to bind to all specified addresses
& if an address is not available or not configured correctly it can cause
issue;. I have a few suggestions to handle this you can check
Co
Thank you John for that hint, it looks promising. I will try to check that out
and report back.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
On 12/08/2024 19:06, skraw--- via dovecot wrote:
As I already said, this setup is way too complex to think about an update.
The cause of this problem cannot be a problem of the same size. If somebody
(probably you or Stephan) already found the cause I could concentrate on
backporting a soluti
As I already said, this setup is way too complex to think about an update.
The cause of this problem cannot be a problem of the same size. If somebody
(probably you or Stephan) already found the cause I could concentrate on
backporting a solution.
And future readers of the thread may be interest
2.1.17 is way older than 2.3.2.1
Please try with 2.3.21 (latest version).
Aki
> On 12/08/2024 17:11 EEST skraw--- via dovecot wrote:
>
>
> I see it happening with dovecot 2.1.17 in a setup that is complex to update.
> So I am interested in the cause and possible solutions to bring them into
I see it happening with dovecot 2.1.17 in a setup that is complex to update. So
I am interested in the cause and possible solutions to bring them into this old
setup.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to doveco
Have you verified that it happens with dovecot 2.3.21 and pigeonhole 0.5.21?
Aki
> On 12/08/2024 16:39 EEST skraw--- via dovecot wrote:
>
>
> And what was the proposed solution to this?
> ___
> dovecot mailing list -- dovecot@dovecot.org
> To unsubs
And what was the proposed solution to this?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
