new authentication format coming; please read and comment

> That was a lot of new information, and that's my first

> attempt to document it.
> It also just helped me get my mind around what all the 
> changes are, so thanks
> for letting me sound off  y'all.  Does that
make sense?  
> Any questions, comments?

1)  Am I right in reading that if you have multiple domains
and use
internal auth for all, the fall through auth will ultimately
catch it?
In other words, will a server with a bunch of domains need
major
reconfiguration to set all domains to internal or will it
"Just work".

2)  I suggest cutting a release prior to adding this code. 
Lots of nice
stuff went in recently and it would be good to cut it there
before
opening this potential can-o-worms ;).

-steve
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

SRH-Lists wrote:
>> That was a lot of new information, and that's my
first 
>> attempt to document it.
>> It also just helped me get my mind around what all
the 
>> changes are, so thanks
>> for letting me sound off  y'all.  Does that
make sense?  
>> Any questions, comments?
> 
> 1)  Am I right in reading that if you have multiple
domains and use
> internal auth for all, the fall through auth will
ultimately catch it?
> In other words, will a server with a bunch of domains
need major
> reconfiguration to set all domains to internal or will
it "Just work".

Yeah, simple case, just add the proper settings to the . domain,
and everyone
will fall through to it.  All domains will fall through to
.,
unless a specific
domain mechanism specifies a fail result of REJECT.


> 2)  I suggest cutting a release prior to adding this
code.  Lots of nice
> stuff went in recently and it would be good to cut it
there before
> opening this potential can-o-worms ;).

Possibly.  I'm going to do this in another branch first to
get it stable, and
I'll try to keep it current with trunk at the same time. 
Having said that,
Jacob is using the stats branch with these change in
production, and the reason
I'm working on it now is I have another site that needs it
in production ASAP.
So I think it will be a safe can of worms.   The only
drawback is the need to
reconfigure the authentication mechs.  (I'm thinking about
whether an upgrade
script can do it)



- --
David Morton
Maia Mailguard                        - http://www.maiamailguard
.com
Morton Software Design and Consulting - http://www.dgrmm.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFEmEFXUy30ODPkzl0RAvXFAKCPgVG0kCC5xoe/oTkjONJTzgXmpgCf
YG9X
CQQpG59exn9eAdXHb9vV4mE=
=zY4A
-----END PGP SIGNATURE-----
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

SRH-Lists wrote:

> 1)  Am I right in reading that if you have multiple
domains and use
> internal auth for all, the fall through auth will
ultimately catch it?
> In other words, will a server with a bunch of domains
need major
> reconfiguration to set all domains to internal or will
it "Just work".
> 
> 2)  I suggest cutting a release prior to adding this
code.  Lots of nice
> stuff went in recently and it would be good to cut it
there before
> opening this potential can-o-worms ;).


Seconded, we want that last release before the per-domain
auth.

J
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users