Just got off the phone with IPSwitch; all they could come up with was my Queuemgr threads being too high (was 120 and retry 100;  they reset to 75 and 30). 
 
I had no application errors, etc.  Declude was not the issue here...
 
I'll be watching this closely thru-out the nite...
 
 


Sincerely,

Support Department
Global Web Solutions®, Inc.
804-346-5300 x112
877-800-GLOBAL (4562) x112
http://globalweb.net

 

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alvaro Dioni
Sent: Tuesday, December 27, 2005 4:42 PM
To: [email protected]
Subject: RE:[Declude.JunkMail] recurrance of delayed message processing

This morning I had the same problem, but after restarting the services (SMTP and decludeproc) the mail was finally delivered. Later, the operating system gave me these errors about Decludeproc: there were about three of them, at different times:

 

 

szAppName : decludeproc.exe     szAppVer : 0.0.0.0    

szModName : decludeproc.exe     szModVer : 0.0.0.0     offset : 000060fd    

 

 

I have two gateway servers; the other didn’t crash, but was using 180MB of RAM… after restarting the service, memory was back to “normal” (34MB max).

 

I upgraded to declude 3.X on dec. 20, today was the first problem, also using (IMail 8.15hf2)…

Any ideas?

 

Al Dioni

 

 

 

 


De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de randy armbrecht
Enviado el: Martes, 27 de Diciembre de 2005 12:15 p.m.
Para: [email protected]
Asunto: X-I1-POSIBLE-SPAM-sr [Declude.JunkMail] recurrance of delayed message processing

 

I am on hold with IPSwitch checking on this issue again - (IMail 8.15hf2, declude 3.x latest) -  it started about 12.30pm; email comes into the server, handled by Declude, processed back in Spool, but is not delivered past this point....DNS checks out OK; even tried switching DNS servers and stop/starting all IMail services and the Declide proc service.

Declude logs show normal processing activity; IMail logs simply show message coming in and that's it.  nothing unuasul in logs at all...

(I replied back to a post this morning using my regular list address, but since the server that handles that address is not working, I am sending this out via our gateway server...we had this happen on Xmas eve night as well....)

Randy Armbrecht

Reply via email to