On 8/16/2010 2:24 PM, Timo Sirainen wrote:
On 16.8.2010, at 22.01, Marc Perkel wrote:
But the %{login_domain} evaluates to an empty string as you can see from the
results of the debug.
What about %{login_user} or %{username}?
Hi Timo,
Apparently I'm getting different results that you
On 8/16/2010 2:24 PM, Timo Sirainen wrote:
On 16.8.2010, at 22.01, Marc Perkel wrote:
But the %{login_domain} evaluates to an empty string as you can see from the
results of the debug.
What about %{login_user} or %{username}?
Actually - spoke too soon. %{username} returned the wrong val
On 8/16/2010 2:24 PM, Timo Sirainen wrote:
On 16.8.2010, at 22.01, Marc Perkel wrote:
But the %{login_domain} evaluates to an empty string as you can see from the
results of the debug.
What about %{login_user} or %{username}?
Interestingly %{login_user} doesn't work either returning an
On 16.8.2010, at 22.01, Marc Perkel wrote:
> But the %{login_domain} evaluates to an empty string as you can see from the
> results of the debug.
What about %{login_user} or %{username}?
On 8/16/2010 11:26 AM, Timo Sirainen wrote:
On Mon, 2010-08-16 at 11:17 -0700, Marc Perkel wrote:
Odd - wonder what I'm doing wrong then? My result:
Aug 16 10:44:43 auth: Debug: sql(supp...@junkemailfilter.com,127.0.0.1):
query: SELECT user_name, domain_name, password FROM users WHERE
user_n
On Mon, 2010-08-16 at 11:17 -0700, Marc Perkel wrote:
> Odd - wonder what I'm doing wrong then? My result:
>
> Aug 16 10:44:43 auth: Debug: sql(supp...@junkemailfilter.com,127.0.0.1):
> query: SELECT user_name, domain_name, password FROM users WHERE
> user_name = 'support' AND domain_name = 'ju
On 8/16/2010 11:04 AM, Timo Sirainen wrote:
On Mon, 2010-08-16 at 10:49 -0700, Marc Perkel wrote:
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Hi Timo,
I just tried the 2.0 of
You can use checkpassword:
http://wiki.dovecot.org/AuthDatabase/CheckPassword
Works fine for me for master user authentication.
Emerson Pinter
On 15-08-2010 18:46, Marc Perkel wrote:
Here's what I'd like. Limited master users, where someone can be a
master users for some domains but not o
On Mon, 2010-08-16 at 10:49 -0700, Marc Perkel wrote:
>
> On 8/15/2010 3:06 PM, Timo Sirainen wrote:
> >
> > These are available in v2.0:
> >
> > %{login_user}
> > %{login_username}
> > %{login_domain}
> >
> > I guess they should be added to wiki..
>
> Hi Timo,
>
> I just tried the 2.0 official
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Hi Timo,
I just tried the 2.0 official release and these variables return an
empty string.
On 8/15/2010 5:07 PM, Bradley Giesbrecht wrote:
On Aug 15, 2010, at 4:56 PM, Marc Perkel wrote:
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
On 15.8.2010, at 22.46, Marc Perkel wrote:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
..
I
On Aug 15, 2010, at 4:56 PM, Marc Perkel wrote:
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
On 15.8.2010, at 22.46, Marc Perkel wrote:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
..
I'm assuming that the masteruser and masterpass is p
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
On 15.8.2010, at 22.46, Marc Perkel wrote:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
..
I'm assuming that the masteruser and masterpass is passed to the master passdb
and when doing so
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
On 15.8.2010, at 22.46, Marc Perkel wrote:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
..
I'm assuming that the masteruser and masterpass is passed to the master passdb
and when doing so
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
On 15.8.2010, at 22.46, Marc Perkel wrote:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
..
I'm assuming that the masteruser and masterpass is passed to the master passdb
and when doing so
On 15.8.2010, at 22.46, Marc Perkel wrote:
> passdb {
> driver = sql
> args = /etc/dovecot/dovecot-sql-master.conf.ext
> master = yes
> pass = yes
> }
..
> I'm assuming that the masteruser and masterpass is passed to the master
> passdb and when doing so the variable %u is the master user. I
On 8/15/2010 5:46 PM, Marc Perkel wrote:
Here's what I'd like. Limited master users, where someone can be a
master users for some domains but not others. I think I could do what
I want with the right kinds of variable passing that doesn't yet
exist. Let me see if I can explain clearly.
From
Here's what I'd like. Limited master users, where someone can be a
master users for some domains but not others. I think I could do what I
want with the right kinds of variable passing that doesn't yet exist.
Let me see if I can explain clearly.
From the example in the wiki:
auth_master_user
18 matches
Mail list logo
