Hi
I'm setting up a Dovecot Proxy Server to access Gmail.
But It doesn’t work.
I tried to configure Dovecot without proxy authentication.
passdb {
driver = static
args = nopasssword=y proxy=y proxy_mech=xoauth2 ...
}
It works fine. So far so good.
But with proxy authentication It does not
* Stuart Henderson:
> you could perhaps use "auth_bind = yes" to have Dovecot attempt a bind
> with the user-supplied password [...]
Thanks, that sounds like an approach worth investigating to me. Current
access control settings for the LDAP server do not permit this method of
binding, but I
On 2021-11-07, Ralph Seichter wrote:
> * Alexander Dalloz:
>
>> Don't know about Ubuntu specifics [...]
>
> Thank you for the pointers. Am I right to interpret the Dovecot docs as
> stating that SSHA384 is not supported by the official packages, and that
> my only recourse might be building from
Hello again,
I've found out that some mailboxes are actually duplicated. Doveadm
replicator status on the production server gives this:
~# doveadm replicator status 'dummy-c-1*'
username priority fast sync full sync
success sync failed
dummy-c-1
* Alexander Dalloz:
> Don't know about Ubuntu specifics [...]
Thank you for the pointers. Am I right to interpret the Dovecot docs as
stating that SSHA384 is not supported by the official packages, and that
my only recourse might be building from the source code and adding some
external code in
Am 07.11.2021 um 14:35 schrieb Ralph Seichter:
While using LDAP-based authentication, I have come across the message
auth: Error: [...] Unknown scheme SSHA384
Based on the docs at [1] I use the dovecot.org packages provided for
Ubuntu 20.04 LTS which, as you can see, are not yet documented
While using LDAP-based authentication, I have come across the message
auth: Error: [...] Unknown scheme SSHA384
Based on the docs at [1] I use the dovecot.org packages provided for
Ubuntu 20.04 LTS which, as you can see, are not yet documented in the
HTML page, put are available via [2].
Przemysław Kwiatkowski schreef op 2021-11-07 11:31:
Hello,
As far as I understand - auth cache it stored in memory, isn't it? Is
there a way for it to survive Dovecot restart?
A second-level cache next to SHM would require the data to be dumped on
and read from disk at start time. I'm not
Am 07.11.2021 um 12:45 schrieb Przemysław Kwiatkowski:
Hello,
It updates automatically on password mismatch. It's quite clear
described here: https://wiki.dovecot.org/Authentication/Caching
What's not described is if the cache could survive restart... :-(
Unless it is possible to
Hello,
It updates automatically on password mismatch. It's quite clear
described here: https://wiki.dovecot.org/Authentication/Caching
What's not described is if the cache could survive restart... :-(
--
Przemyslaw Kwiatkowski
If users change their password how does the cache continue to
If users change their password how does the cache continue to work? Thanks
> Hello,
>
> It's Submission only. It authenticates users with ldap, but I want to make
> sure it will work also on ldap connection failure. (And it works - auth
> cache does its job until Dovecot restart.)
>
>
> --
>
Hello,
It's Submission only. It authenticates users with ldap, but I want to
make sure it will work also on ldap connection failure. (And it works -
auth cache does its job until Dovecot restart.)
--
Przemyslaw Kwiatkowski
W dniu 07.11.2021 o 11:45, Walt Pang pisze:
Is it not in LDA?
Is it not in LDA?
> Hello,
>
> As far as I understand - auth cache it stored in memory, isn't it? Is
> there a way for it to survive Dovecot restart?
>
> --
> Przemyslaw Kwiatkowski
>
>
>
Hello,
As far as I understand - auth cache it stored in memory, isn't it? Is
there a way for it to survive Dovecot restart?
--
Przemyslaw Kwiatkowski
14 matches
Mail list logo
