[Dovecot] NULL for password and proxy fields

[Timo Sirainen]

On Mon, 2008-02-04 at 09:48 -0800, WJCarpenter 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.)

Yes. It's even documented (somewhere) that NULL value means the same as
if the field wasn't even selected by the query.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20080204/02b04903/attachment.bin