-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 23 Nov 2017, Evgeniy Korneechev wrote:
We have userdb=passwd.
userdb {
driver = passwd #server was entered domain Active Directory
override_fields = home=/var/vmail/glu_vrem/%u
}
If I disable in AD user's account, he can not sign in.
But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 21 Nov 2017, A. Schulze wrote:
in /etc/dovecot/ldap.conf
user_attrs = ...
=lmtp_save_to_detail_mailbox=%{ldap:lmtp-save-to-detail-mailbox:no},
=...
Unfortunately messages to user+extension@domain
Hi
I got dovecot 2.2.26 on a Centos7 with latest updates. Dovecot is
configured to act as director and delivers to my two backend servers.
I enabled lmtp proxy on director to listen on port 24.
Now I see in msg headers that the connection to the lmtp proxy uses
STARTTLS but the connection from
Hello!
We have userdb=passwd.
userdb {
driver = passwd #server was entered domain Active Directory
override_fields = home=/var/vmail/glu_vrem/%u
}
If I disable in AD user's account, he can not sign in.
But he can and will receive letters, which of course is not correct.
How can I exclude
Am 23.11.2017 um 14:40 schrieb Sami Ketola:
> can you verify if the value is correctly formed in userdb. Ie. is it visible
> in output:
>
> doveadm -o service=lmtp user
# doveadm -o service=lmtp user us...@example.org
field value
uid 8
gid 8
home/mail/user1
mail
Steffen Kaiser:
Is the detail delived to Dovecot by the MTA at all?
sure!
have to say: I faked that example. In reality I tested the inverse way:
My lab setup actually *do* deliver to folders and
I saw, setting lmtp_save_to_detail_mailbox to 'no' still deliver to folder
while INBOX was
> On 23 Nov 2017, at 15.32, A. Schulze wrote:
>
>
> Steffen Kaiser:
>
>> Is the detail delived to Dovecot by the MTA at all?
> sure!
>
> have to say: I faked that example. In reality I tested the inverse way:
> My lab setup actually *do* deliver to folders and
> I
Hi
thanks for the link. Read that page before but somehow missed the
comment about ssl+lmtp proxy :-)
Are there any plans to implement that to dovecot in future?
Regards
tobi
Am 23.11.2017 um 18:38 schrieb Carsten Rosenberg:
> NOTE: LMTP/doveadm proxying doesn't support SSL/TLS currently -