On 04.08.2017 23:10, Daniel Miller wrote:
> On 8/4/2017 12:48 PM, Daniel Miller wrote:
>> On 8/3/2017 6:11 AM, Teemu Huovila wrote:
>>>
>>> On 02.08.2017 23:35, Daniel Miller wrote:
Is there explicit documentation available for the (probably trivial)
configuration needed for Dovecot an
On 8/4/2017 12:48 PM, Daniel Miller wrote:
On 8/3/2017 6:11 AM, Teemu Huovila wrote:
On 02.08.2017 23:35, Daniel Miller wrote:
Is there explicit documentation available for the (probably trivial)
configuration needed for Dovecot and Wforce? I'm probably missing
something that should be perfe
On 8/3/2017 6:11 AM, Teemu Huovila wrote:
On 02.08.2017 23:35, Daniel Miller wrote:
Is there explicit documentation available for the (probably trivial)
configuration needed for Dovecot and Wforce? I'm probably missing something
that should be perfectly obvious...
Wforce appears to start wi
On 02.08.2017 23:35, Daniel Miller wrote:
> Is there explicit documentation available for the (probably trivial)
> configuration needed for Dovecot and Wforce? I'm probably missing something
> that should be perfectly obvious...
>
> Wforce appears to start without errors. I added a file to d
Is there explicit documentation available for the (probably trivial)
configuration needed for Dovecot and Wforce? I'm probably missing
something that should be perfectly obvious...
Wforce appears to start without errors. I added a file to dovecot's conf.d:
95-policy.conf:
auth_policy_server_
> On June 30, 2017 at 10:24 PM Daniel Miller wrote:
>
>
> On 6/30/2017 12:05 PM, Aki Tuomi wrote:
> >> On June 30, 2017 at 9:49 PM Daniel Miller wrote:
> >>
> >>
> >> I've made a preliminary auth policy server in Perl - and it sort of
On 6/30/2017 12:05 PM, Aki Tuomi wrote:
On June 30, 2017 at 9:49 PM Daniel Miller wrote:
I've made a preliminary auth policy server in Perl - and it sort of
works (mostly) - but I've got some questions on "proper" implementation.
Hi!
First of all, which version are
> On June 30, 2017 at 9:49 PM Daniel Miller wrote:
>
>
> I've made a preliminary auth policy server in Perl - and it sort of
> works (mostly) - but I've got some questions on "proper" implementation.
>
> It appears the communication is HTTP base
I've made a preliminary auth policy server in Perl - and it sort of
works (mostly) - but I've got some questions on "proper" implementation.
It appears the communication is HTTP based - is the intent to talk to a
"proper" webserver, or is a simple dedicated daemon
