Will, Thanks for your post. I will arrange for one of our engineers to take a further look at this issue.
David B www.declude.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Will Sent: Tuesday, January 17, 2006 10:06 AM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] decludeproc causing dns queries to fail Thank you for the feedback. There is no firewall between my mail server and my DNS server. The DNS server is running without issue and resolves names just fine on all other workstations and servers even when the issues on my mail server arise. When the issue presents itself, the mail server alone is unable to establish a connection to the DNS. During the first instance, I verified multiple times that the DNS server was resolving properly and noted that the mail server could not establish a connection with any of the five DNS servers I tried. After the decludeproc service was restarted, I could once again establish the connection for DNS and mail processing started again. However, with 500k messages in queue it took less than a half hour for the problem to happen again. My solution at the time, which I am not happy with, was to purge the proc folder. Without such overhead it ran fine for weeks. The second time this happened a few days ago, I verified all my pervious findings. I can guarantee with absolute certainty that there are no DNS issues at the root of this problem. The sole cause and solution lie with the decludeproc service and its consumption of resources on my mail server. I just wrote a program to monitor the number of files in the proc folder and restart the decludeproc service if it exceeds 2000. This will be enough to ensure that this doesn't happen again, but I do wish to make this issue known so it can be avoided or diagnosed in the future. I am currently running Win2003/sp1, Imail 8.12 with declude pro 3.0.5.22 running spam and antivirus with f-prot. Will -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Barker Sent: Tuesday, January 17, 2006 9:40 AM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] decludeproc causing dns queries to fail Will, If Decludeproc was usurping network resources we should be aware of this issue. However currently you are the only report of this incident. Please make sure you are running the latest version of declude 3.0.5.23 Declude has sent out DNS requests and did not recieve responses from the DNS server, this is an indication of a DNS issues with your Network.. 1. Check your firewall and ensure Port 53 is open. 2. Check your Firewall/Router logs to make sure incoming DNS packets are not being blocked 3. Check for potential Network problems 4. Check that you DNS is working correctly. If you find it to be one of these reasons listed above it is a DNS issue and not a Declude issue. BTW this is posted in our Knowledge base. David B www.declude.com ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Will Sent: Tuesday, January 17, 2006 9:22 AM To: Declude.JunkMail@declude.com Subject: [Declude.JunkMail] decludeproc causing dns queries to fail For the second time in a month I have come to work to find over 500,000 messages in my proc folder. The cause is declude's inability to perform dns queries, thus mail backlogs. The reason declude cannot perform DNS queries is that no outgoing traffic is being permitted on port 53. The reason no outgoing traffic is being permitted on port 53 is that decludeproc has consumed the resources allocated to my network interface. The fix for this is relatively simple. I stop the decludeproc service and restart it and all is well. After the first occurrence, it was suggested that I enable winsockcleanup documented as the following at declude.com: WINSOCKCLEANUP ON Located in Declude.cfg. Some customers had issues related to their network stack causing loss of functionality for basic network operations. The default for this directive is OFF Now I've been fooled twice, so I guess shame on me. Does anyone have a suggestion that would help resolve this? In the meantime I will be writing a script to monitor the number of message in the proc folder and if it reaches a certain threshold, will restart the decludeproc service. I really don't care for workarounds such as this, but I've gained a bad image over these two occurrences and I cannot allow it to happen again. Declude.cfg: THREADS 100 WAITFORMAIL 5000 WINSOCKCLEANUP ON --- [This E-mail was scanned for viruses by Declude EVA www.declude.com] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude EVA www.declude.com] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude EVA www.declude.com] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
