On 07/08/2019 11:19, James via dovecot wrote:
My more simplistic policy does not need both. I perform whitelist,
blacklist, geo and greylist
...and DNSBL which where I started with the policyserver, "Can dovecot
do DNSBL?", only indirectly via a policyserver. This is better as most
pass
On 07/08/2019 11:02, Aki Tuomi via dovecot wrote:
before and after auth? roundcube webmail reports an error with only
auth_policy_check_before_auth. I cannot see why. The simple and lazy
solution is to use double auth_policy_check_!
...
The double-check is for places which want to
On 7.8.2019 11.51, James via dovecot wrote:
> On 06/08/2019 06:46, Aki Tuomi via dovecot wrote:
>>
>> On 2.8.2019 13.45, James via dovecot wrote:
>>> My auth process is dumping core. This happens several times per day
> ...
>
>> There is an easy fix for this, attached.
>
> Patch applied; no
On 06/08/2019 06:46, Aki Tuomi via dovecot wrote:
On 2.8.2019 13.45, James via dovecot wrote:
My auth process is dumping core. This happens several times per day
...
There is an easy fix for this, attached.
Patch applied; no core dump in 24 hours.
This appears to have fixed the problem.
On 2.8.2019 13.45, James via dovecot wrote:
> My auth process is dumping core. This happens several times per day
> but dovecot can operate normally for hours between errors.
>
> The crash occurs in src/auth/auth-policy.c, line 356:
>
> t@1 (l@1) program terminated by signal SEGV (no mapping at
On 02/08/2019 11:45, James via dovecot wrote:
My auth process is dumping core. This happens several times per day but
dovecot can operate normally for hours between errors.
The crash occurs in src/auth/auth-policy.c, line 356:
t@1 (l@1) program terminated by signal SEGV (no mapping at the