[Dovecot] NULL for password and proxy fields
Eric Hester
eric.hester at gmail.com
Mon Feb 4 19:56:51 EET 2008
also just as a note, when you go to 1.1 make sure to return
nopassword='Y' if you return a NULL password or dovecot will complain
and will fail auth.
On Feb 4, 2008 12:48 PM, WJCarpenter <bill-dovecot at carpenter.org> wrote:
>
> >> 2. It looks like any value at all for the "proxy" field in the passdb
> >> lookup turns proxying on. The one exception is a value of NULL for
> >> "proxy", in which case proxying is not turned on and proxy-related
> >> other fields are ignored. Is that how it's intended to work?
> >>
> >
> > Yes. It might change in some future release, but currently I'm not
> > planning on changing it. 'Y' would anyway be a future-safe choice.
> >
> >
>
> Thanks for the information. I was actually asking about the other side
> of the coin ... is it safe to assume that "proxy=NULL" will disable the
> proxying, at least for the 1.0 series? (I saw the "proxy_maybe" for
> 1.1, which is also OK for me when I get to that release.)
>
More information about the dovecot
mailing list