WCSMTP runs two WCX,

WCSAP to check the envelope

SMTPFILTER if installed, to run the optional smtpfilter-checkworks.wcx.

If you are getting an ASSERTION with WCDNS.DLL, then it has to be with
WCSAP.WCX.

I can't help anyone if I don't get a session log (the sender information)
causing this.  That information would in the WCSAP*.log files.  You have to
sort of match the time it happen to get the right session information.

Also, the only other reason I can see is a FIREWALL DNS client proxy that is
providing "bad" or unexpected information to WCDNS.DLL.

If you have such a FIREWALL with DNS client/server proxy, try turning off to
see of the problem goes away.


-- Hector


On 10/2/05 3:47 PM, BOBBY TODD wrote to HECTOR SANTOS:

> 
> -> 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.
> 
> Hector, I get this when wcSMTP looks like it trying to connect to one of
> the spam filter servers.
> 
> 

 
--- Platinum Xpress/Win/WINServer v3.1