Dear Alex et al
> Did you happen to have this working? Could you share how?
So far it's not working yet. We are currently exploring more recent
dovecot versions (2.2.9 AFAIR) but had to do some other work to keep the
mailsystem running. Now we have more time to work on migration and will
post a
Hello Jogi,
Did you happen to have this working? Could you share how?
Thanks,
Alex
--
View this message in context:
http://dovecot.2317879.n4.nabble.com/proxy-userdb-and-passdb-tp44860p45200.html
Sent from the Dovecot mailing list archive at Nabble.com.
On 22.10.2013, at 13.13, Jogi Hofmüller wrote:
> Hi Steffen,
>
> Am 2013-10-22 10:05, schrieb Steffen Kaiser:
>
>> see http://wiki2.dovecot.org/PasswordDatabase/ExtraFields
>
> Did, thanks. The errors I mentioned in my previous post are gone. Still,
> proxying does not work as expected. Ins
Hi Steffen,
Am 2013-10-22 10:05, schrieb Steffen Kaiser:
see http://wiki2.dovecot.org/PasswordDatabase/ExtraFields
Did, thanks. The errors I mentioned in my previous post are gone.
Still, proxying does not work as expected. Instead I get strange warnings:
Oct 22 12:06:51 server dovecot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 18 Oct 2013, Jogi Hofmüller wrote:
We are getting closer to the migration of our mailsystem. Now I have a
special question. We are successfully using
passdb {
driver = pam
}
and that is good. Now, how would I tell dovecot to proxy cert
Dear all,
We are getting closer to the migration of our mailsystem. Now I have a
special question. We are successfully using
passdb {
driver = pam
}
and that is good. Now, how would I tell dovecot to proxy certain users
(the ones not yet migrated) to the old server? My attempts to configur
