On Mon, Dec 20, 2010 at 10:58 PM, Eray Aslan wrote:
> On 2010-12-20 10:58 PM, Paul Lesniewski wrote:
>> If there is demand for such a feature, I could try to push it up
>> higher on my TODO list
>
> It would provide a nice interface to dovecot's masterusers setting which
> will probably be use
On 2010-12-20 10:58 PM, Paul Lesniewski wrote:
> If there is demand for such a feature, I could try to push it up
> higher on my TODO list
It would provide a nice interface to dovecot's masterusers setting which
will probably be used more and more. So it would be nice to have.
Having said th
On Mon, Dec 20, 2010 at 12:15 PM, Ralf Hildebrandt
wrote:
> * Paul Lesniewski :
>> On Mon, Dec 20, 2010 at 2:27 AM, Ralf Hildebrandt
>> wrote:
>> > Dovecot has a "masteruser" login feature, meaning an admin can log in
>> > as the user "loginname" using this username:
>> >
>> > loginname*masteruse
* Paul Lesniewski :
> On Mon, Dec 20, 2010 at 2:27 AM, Ralf Hildebrandt
> wrote:
> > Dovecot has a "masteruser" login feature, meaning an admin can log in
> > as the user "loginname" using this username:
> >
> > loginname*masteruser
> >
> > This works really well, but SquirrelMail is using a prefe
On Mon, Dec 20, 2010 at 2:27 AM, Ralf Hildebrandt
wrote:
> Dovecot has a "masteruser" login feature, meaning an admin can log in
> as the user "loginname" using this username:
>
> loginname*masteruser
>
> This works really well, but SquirrelMail is using a preferences file
> called "loginname*mast
Dovecot has a "masteruser" login feature, meaning an admin can log in
as the user "loginname" using this username:
loginname*masteruser
This works really well, but SquirrelMail is using a preferences file
called "loginname*masteruser.pref" instead of "loginname.pref"
How can I work around this?