Interesting, but this means that we need to have one tree with all users
(where each user have additional attribute containing local ip), instead we
now have two separate trees because we use this for other authentication
purposes.
Thank you for sharing your thoughts Steffen
On Mon, Apr 8, 201
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 7 Apr 2013, Pavel Dimow wrote:
Just to be clear my goal is to have multiple domains on multiple addresses
but use one dovecot instance and to let users logging without @domain part.
If %l is expanded in the LDAP query, you could add an att
Am 08.04.2013 13:18, schrieb Benny Pedersen:
> On 2013-04-07 22:51, Pavel Dimow wrote:
>
>> Why does dovecot does not expand %l to local ip address?
>
> what it it does not contain an ip address ?, like "rm -f /"
what is your f**ing problem?
signature.asc
Description: OpenPGP digital signat
On 2013-04-07 22:51, Pavel Dimow wrote:
Why does dovecot does not expand %l to local ip address?
what it it does not contain an ip address ?, like "rm -f /"
--
senders that put my email into body content will deliver it to my own
trashcan, so if you like to get reply, dont do it
Thank you Timo, then I guess I will runing two instances of dovecot one for
each domain until
local 1.2.3.4 {
userdb {
..
}
}
becomes ready :)
On Mon, Apr 8, 2013 at 12:14 PM, Timo Sirainen wrote:
> You could put (%l=1.2.3.4) in the ldap filter. But I guess it still gets
> sent to the
You could put (%l=1.2.3.4) in the ldap filter. But I guess it still gets sent
to the LDAP server. The best solution would be:
local 1.2.3.4 {
userdb {
..
}
}
But that doesn't work yet.
With v2.2 you can do multiple queries. So you could have one query to translate
IP address to the dom
Well that is not very scalable as we always ask first database no matter
what. What if I have the same user in both databases (ldap)?
On Mon, Apr 8, 2013 at 12:36 AM, Daniel Parthey <
daniel.part...@informatik.tu-chemnitz.de> wrote:
> Pavel Dimow wrote:
> > Just to be clear my goal is to have mu
Pavel Dimow wrote:
> Just to be clear my goal is to have multiple domains on multiple addresses
> but use one dovecot instance and to let users logging without @domain part.
You might try to use several passdb/userdb sections with driver ldap,
one for each domain:
http://wiki2.dovecot.org/Authent
Just to be clear my goal is to have multiple domains on multiple addresses
but use one dovecot instance and to let users logging without @domain part.
On Sun, Apr 7, 2013 at 11:51 PM, Pavel Dimow wrote:
> Thank you Timo, can you please correct me if I am wrong, but this means
> that only way t
Thank you Timo, can you please correct me if I am wrong, but this means
that only way to have one dovecot server authenticating users from ldap
without domain part is to use %l in ldap query? That imply to have tree
like ou=people,o=x.x.x.x.o=mail,dc=acme,dc=com
Or there is a better way to do it?
On 7.4.2013, at 23.51, Pavel Dimow wrote:
> I am trying to use separate configurations for ldap authentication thus
> providing users
> with the ability to only use username without domain part. Now according to
> documentation this should be possible
> http://wiki2.dovecot.org/AuthDatabase/Passw
Hi,
I am trying to use separate configurations for ldap authentication thus
providing users
with the ability to only use username without domain part. Now according to
documentation this should be possible
http://wiki2.dovecot.org/AuthDatabase/PasswdFile
but I keep getting error in my dovecot.log
12 matches
Mail list logo