For now, please try setting your MX Cache to 0.  We're working on this and should have 
a fix soon.

Regards,

Howie

----- Original Message ----- 
From: "Vishal Narayan" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, August 01, 2002 7:22 AM
Subject: [iMS] Access violation errors in POST log


> 
> I am running IMS-SE version 2.2 on my production server. Suddenly we have 
> started getting access violation errors in our post logs. Here's a snippet 
> from the log files -
> 
> 08/01/2002 05:12:02 PM [024] WARNING: Error resolving MX from server 
> dns1.ilink.net for sina.com: Access violation at address 00428668 in module 
> 'inFusionPOST.exe'. Read of address 4589575B
> 08/01/2002 05:12:02 PM [024] WARNING: Error resolving MX from server 
> dns2.ilink.net for sina.com: Access violation at address 00428668 in module 
> 'inFusionPOST.exe'. Read of address 4589575B
> 08/01/2002 05:12:02 PM [024] WARNING: Error resolving MX from server 
> dns3.ilink.net for sina.com: Access violation at address 00428668 in module 
> 'inFusionPOST.exe'. Read of address 4589575B
> 
> 
> We tried disabling MX caching by setting the max records to 0, and this 
> seems to have temporarily resolved the problem, though the performance 
> seems slower than before.
> 
> I would like to know whether this problem has been resolved completely in 
> version 2.3. Or is anyone still getting the same access violation errors 
> after upgrading ?
> 
> Vishal.
> 
==^=======================================================
     This list server is Powered by iMS
   "The Swiss Army Knife of Mail Servers"
   --------------------------------------
To leave this list please complete the form at 
http://www.coolfusion.com/iMSSupport.cfm
Need an iMS Developer license?  Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [email protected]
==^=======================================================


Reply via email to