Just to clarify something here, IMHO, Rockliffe didn't implement the
multi-domain support correctly. Even though the stored proc returns
several records, only the ones for the specific domain in question
should be looked at. For example, if this is a pop connection
comes in on a virtual IP associated with domain isp.com, then
only those records for isp.com should be looked at. That is one of
the reasons why the domain is included with each record.
Our EmerAuth DLL handles this correctly for multi-domain situations,
and most likely this was just an oversight on Rockliffe's part when
they were adding support for the Emerald database.
By not forcing the domain associations, the DLL or mail system
has maximum flexibility for things like domain aliasing and
such in future versions.
Also note that the more complex you make this query, the slower
it runs and has exponential performance issues on the mail
system.
--Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com