RE: [Declude.JunkMail] Declude Crashes

[Goran Jovanovic]

Matt,   I agree with your comments regarding AUTOREVIEW and its potential problems. I originally started out manually checking an moving but that got too time consuming and seeming to no effect. Therefore I made a calculated risk that I would turn it on and take the chance of a killer message being looped. If that happens my proc directory will backup and Queuemon will notify me of a problem. So not elegant but it seems to work for me.   Goran Jovanovic Omega Network Solutions   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Monday, August 28, 2006 10:33 PM To: declude.junkmail@declude.com Subject: Re: [Declude.JunkMail] Declude Crashes   Goran, That worked great for me until I experienced a killer message last week that AUTOREVIEW was throwing back into the proc directory after every restart which in turn caused Declude to crash every time.  They said that this was fixed in the most recent version, but there are more bugs with their own killer messages out there certainly.  AUTOREVIEW ON therefore should not be used for that reason.  Keep in mind that not all messages that caused a crash will be repeatable causes of a crash. What I would like to see (and I'm not holding my breath) is something that didn't move all the proc contents into the review directory, but instead just the message that was there when it crashed.  My GP1 file that was created by the crash as well as the logs clearly showed the problematic message.  If Declude can create the GP1 file, it can also be made to only move that one problematic message over to review.  I'm afraid that they are casting the net too widely.  The protective measure of moving killer messages out of proc is wise, but designing a process that requires constant attention and maintenance to move messages back causes people to disable these protective measures.  So the process should be changed to be more granular. With that said, I still would rather see the long known outstanding bugs addressed first.  Clearly there has been a decision to ignore our concerns about these bugs and work on the gateway.  That's an unfortunate way to deal with ones customers. Matt Goran Jovanovic wrote: I had this problem a while ago and never really got an answer on it. I too had a script that would check the review directory and then let me know if there were files there. I reprocessed them manually to check for “killer” messages (just like Darrell) and never found one. I finally resorted to   # Email in the \review directory is automatically moved to the \proc directory when the service # starts or when the proc directory is empty  AUTOREVIEW       ON    In my DECLUDE.CFG file. That way I could stop checking the messages. Never did find the problem.     Goran Jovanovic Omega Network Solutions   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of John T (Lists) Sent: Monday, August 28, 2006 8:55 PM To: declude.junkmail@declude.com Subject: RE: [Declude.JunkMail] Declude Crashes   Darrell, I have a script that is scheduled to run every 15 minutes to check for any files in the error or review folders.   John T eServices For You   "Seek, and ye shall find!"   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Darrell ([EMAIL PROTECTED]) Sent: Monday, August 28, 2006 5:18 PM To: declude.junkmail@declude.com Subject: Re: [Declude.JunkMail] Declude Crashes   Mark,   I also have those issues.  However, my decludeproc is set to auto restart.  On several occasions I have tested the files in the review folder to see if they are the culprit (i.e killer message) and never made any headway on it.  It has not been too much of an issue since it restarts itself.  The only downside is that you run the risk of legit mail ending up in the review folder.   Darrell   ------------------------------------------------------------------------ Check out http://www.invariantsystems.com for utilities for Declude And Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. ----- Original Message ----- From: Mark Strother To: declude.junkmail@declude.com Sent: Monday, August 28, 2006 7:47 PM Subject: [Declude.JunkMail] Declude Crashes   Does anyone else have problems with Declude ‘crashing’? Several times each day I see the following in our application event logs:   Reporting queued error: faulting application decludeproc.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.1830, fault address 0x00032335.   Followed by this in the system logs:   The Decludeproc service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 1 milliseconds: Restart the service.   It seems as though Declude restarts fine and we don’t seem to suffer any ill effects but I’d like to see it resolved. We’re processing a fair volume of mail, 100,000+ messages per day. We’re running Declude 4.3.7 with Sniffer but I can rule out Sniffer as being the issue as I disabled it temporarily and still saw these errors.  Mark Strother  Pacific Online  Phone: 604-638-6010 ext. 222  Fax: 604-638-6020  Toll Free: 1-877-503-9870  http://www.pacificonline.com From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Craig Edmonds Sent: Monday, August 28, 2006 2:41 PM To: declude.junkmail@declude.com Subject: RE: [Declude.JunkMail] some emails being marked with **spam** despite being authenticated Importance: High Sensitivity: Confidential   Thanks John,   I had the log mode set to high, debug seems to show a lot more detail.   Anything in particular I should look out for? (in debug mode the log can chuck out more than 300 lines!!!)   Kindest Regards Craig Edmonds 123 Marbella Internet W: www.123marbella.com E : [EMAIL PROTECTED]   LEGAL DISCLAIMER - This message may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby informed that you must not use, disseminate, copy it in any form or take any action in reliance on it. If you have received this message in error please delete it and any copies of it and notify it to the sender.   AVISO LEGAL - Este mensaje puede contener informacion confidencial, en propiedad o legalmente protegida y esta dirigida unicamente para el uso de la persona destinataria. Si usted no es la persona destinataria de este mensaje, por la presente se le comunica que no debe usar, difundir, copiar de ninguna forma, ni emprender ninguna accion en relacion con ella.     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of John T (Lists) Sent: Monday, August 28, 2006 7:25 PM To: declude.junkmail@declude.com Subject: RE: [Declude.JunkMail] some emails being marked with **spam** despite being authenticated Sensitivity: Confidential You need to review the log lines of a message that was marked, not one that shows Whitelisted.   Preferably, the log should be in debug mode.   John T eServices For You   "Seek, and ye shall find!"   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Craig Edmonds Sent: Monday, August 28, 2006 9:45 AM To: declude.junkmail@declude.com Subject: [Declude.JunkMail] some emails being marked with **spam** despite being authenticated Importance: High Sensitivity: Confidential   Hi All,   I have a strange problem with a client who has complained that **spam** is being put in the subject line of his outgoing emails.   A quick check on the server logs (the declude logs) confirms that some of his emails are being passed through the spam tests and others are being whitelisted becasue he is an authenticated user.   example (Skipping E-mail from authenticated user [EMAIL PROTECTED]@mydomain.com; whitelisted)   I have checked his machine and he has everything set up perfectly including smtp authentication etc.   Why would some email be run through declude and other not?   I am using IMAIL 8.11, Declude 4 (security suite)   Kindest Regards Craig Edmonds 123 Marbella Internet W: www.123marbella.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 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 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 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 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 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 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 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 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.