On 8 Aug 2019, at 13:03, Amir Caspi wrote:
> IMHO the setting should apply regardless of protocol, but is that actually
> the case in practice?
It seems to be broken.
I have
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
autoexpunge = 14 days
I’m not familiar with dovecot code, but as I’m using ldap, so I know that the
ldap authdb support is not part of dovecot-core package, and is provided as a
plugin in an extra package.
And a quick look at the libauthdb_ldap.so file (installed by the dovecot-ldap
package) shows me these symbols:
> On Aug 9, 2019, at 3:45 PM, Aki Tuomi wrote:
>
>
>> On 09/08/2019 22:16 Coy Hile via dovecot wrote:
>>
>>
>> Hi all,
>>
>> In an earlier thread,
>> https://dovecot.org/pipermail/dovecot/2019-August/116694.html I got a lot of
>> useful help about migration. On my older host,
> On 09/08/2019 22:16 Coy Hile via dovecot wrote:
>
>
> Hi all,
>
> In an earlier thread,
> https://dovecot.org/pipermail/dovecot/2019-August/116694.html I got a lot of
> useful help about migration. On my older host, everything was static; on the
> newer host, I’m storing user
Hi all,
In an earlier thread,
https://dovecot.org/pipermail/dovecot/2019-August/116694.html I got a lot of
useful help about migration. On my older host, everything was static; on the
newer host, I’m storing user information in Postgres. usernames are of the form
, say ‘h...@coyhile.com’ as
I am looking at replacing our creaky old courier-imap server, which takes
authentication and user info from an LDAP database, with dovecot imap. Any
comments on the wisdom of this choice of action, or anything I should know
about the setting up before starting to work on it?
Should dovecot not be using different severity levels like auth.warn? On
my system everything goes to loglevel info:
lev_info:Aug 9 16:18:24 mail03 dovecot: imap-login: Aborted login (auth
failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=x.x.x.x,
lip=x.x.x.x, TLS, session=
(resending to the list; I apologize, I'm not using my usual email client)
Hello,
That's actually great news. The perspective of working in-tree didn't make me
particularly happy.
Could you point me to any documentation or examples? While I can find many
plugins in the repo and around the
On 9.8.2019 14.51, Riccardo Paolo Bestetti via dovecot wrote:
> Greetings!
>
> I'm planning to implement a new auth driver. It's going to be, in concept,
> similar to the Lua and CheckPassword drivers, in that it allows an user
> program to carry out the authentication and user enumeration
Greetings!
I'm planning to implement a new auth driver. It's going to be, in concept,
similar to the Lua and CheckPassword drivers, in that it allows an user program
to carry out the authentication and user enumeration steps.
The rationale is that such a solution would provide better decoupling
On 8.8.2019 21.31, Hauke Fath via dovecot wrote:
> On Wed, 7 Aug 2019 20:24:13 +0300 (EEST), Aki Tuomi via dovecot wrote:
>>> i thought ssl_ca is where to put the intermediate cert?
> Well, it surely worked that way until v2.3...
>
>> (Sorry for duplicate mail, keyboard acted up...)
>>
>> No,
11 matches
Mail list logo
