why require APOP for virtual domains?

[Jonathan Walther]

-----BEGIN PGP SIGNED MESSAGE-----

Ohhhh, ok. Phew.  Thanks for clarifying that.  Maybe this would
be a good patch to the documentation to clarify that?

Like this:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Users cannot authenticate using the USER/PASS, APOP, or SASL
methods if the corresponding password or secret is empty.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- --
I am working to subvert from within ...
umm ...  by writing shoddy code ... and
charging too much.

On Thu, 23 Aug 2001, [iso-8859-1] Jerzy Ba=B3amut wrote:
> On Wed, Aug 22, 2001 at 11:13:12AM -0700, Jonathan Walther wrote:
> > User can't authenticate through USER/PASS (APOP/SASL) mechanism
> > if his/her password (APOP/SASL secret) is empty.
>
> Well. It's mean that:
>
> User can't authenticate through USER/PASS mechanism if his/her password
> is empty.
>
> User can't authentiate through APOP mechanism if his/her APOP
> secret is empty.
>
> User can't authenticate through SASL mechanism if his/her SASL
> secret is empty.


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBO4QcccK9HT/YfGeBAQEyVgP9EzLHVmgsKHBByMyvXXFf+T7wblGEI0yn
8RRlcZPL/vmmlgFapEUrqzh7ZuG2WBYCwpUw3DjOpb3kzmKFxVhMIkob9qyH9xmH
AlO2/hng3J1kEbTgNngRk9h3kXknN0mfpQ8baCqdW2X2iCkxfyK+VIOqbHA58mbY
HvENevOVqnE=3D
=3Du1Lf
-----END PGP SIGNATURE-----