> > Curiously, what happens when you specify this:
> >
> > auth_username_format=%n
> > passdb passwd-file {
> > args = username_format=%u /etc/imap.passwd
> > }
> >
> > In my attempt to implement something like this, I didn't find any
> > straightforward way to have "username_format=%u" use the o
On 17.9.2007, at 18.59, Alan Ferrency wrote:
Curiously, what happens when you specify this:
auth_username_format=%n
passdb passwd-file {
args = username_format=%u /etc/imap.passwd
}
In my attempt to implement something like this, I didn't find any
straightforward way to have "username_format
> I implemented this to v1.1:
Great, thanks!
Yes, my initial digging did lead me to conclude it would be a pain to
add new settings into the passdb block. But the format you provided is
equivalent, which works fine for me.
Curiously, what happens when you specify this:
auth_username_format=%n
On Fri, 2007-09-14 at 13:33 -0400, Alan Ferrency wrote:
> An example configuration would look like this:
>
> passdb passwd-file {
> args = /path/%l.passwd
> username_format = %n
> }
That would be nice configuration, but currently it's too difficult to
add more settings inside passdb block
On Fri, 14 Sep 2007, Alan Ferrency wrote:
> I have a likely unusual request regarding IP based virtual
> dovecot users.
>
> When you specify a passdb passwd-file name containing "%d", then the
> domain portion is stripped from the login username, before the user is
> checked in the passwd-file. Ho
Hello.
I have a likely unusual request regarding IP based virtual
dovecot users.
When you specify a passdb passwd-file name containing "%d", then the
domain portion is stripped from the login username, before the user is
checked in the passwd-file. However, if you specify a passwd-file name
conta
