> anyone see any problems with this? I didn't want Yet Another
> Password, and it seems to me an authentification scheme that ties
> into the subscriber database is the easiest way to close off access
> without significantly raising complexity for the end user. Anyone see
> any real flaws here?
Well, if your user base is like mine, users THINK their e-mail address
is [EMAIL PROTECTED] when it is really [EMAIL PROTECTED] If
you're extracting the subscriber address from headers and then they're
hand-typing in their e-mail address as a verification step, a goodly portion
of them aren't gonna get in.
--
Mike Nolan
