Why don't you capture some WCSMTPTRACE or WCSAP logs to find out who were
the last sessions that is causing this.  It has to be a certain DOMAIN.

Having the assertion is not the main problem because EVERYONE has WCDNS.DLL
for the past 2 years and we never got this reported even though the
assertions were in there.  You are the first.

So you are getting something that is making it POP up and I want to know why
it pops up.

All I did before was tell you WHY it was popping up and even though it was
not suppose to be there, it doesn't MEAN it didn't do its job if was a
DEBUGGING project where we had a TEST case that would cause it to occur.

So I need to see some data before releasing a new one.

Thanks


 wrote in message news:1128003055.40.0@winserver.com...
> Hector!
> it is still poping up and I have to close many windows as a result of
> the popups.  I think you will need to recompile wcDNS.dll.  I removed
> wcdns and my e-mail was rejected by the server, so I downloaded it from
> the AUP and it is doing the same thing.
>
> Louis
>
--- Platinum Xpress/Win/WINServer v3.1