Good morning everyone - As you may remember, I had a major problem with the decludeproc service crashing on my server over the weekend. I posted yesterday that, with Linda's help, we figured out the problem. I had a request off-list that I reveal the solution in case others came across the same thing.
It turned out that one of my filters was causing the issue. With Linda's help, we went through the global.cfg file and commented out most of "my" filters until decludeproc wouldn't crash anymore (for the rookies out there like me, the \imail\proc\review folder started to fill up when the service crashed). We had an idea of which filter it was, so once we had the service running ok, we would uncomment the filter in the global.cfg file. Sure enough, it crashed again. With it "out of the picture", decludeproc would run fine. I then went through and slowly uncommented the filters we thought were ok, checking the service each time. Linda thought the problem might be the result of my novice attempts at using regular expressions (PCRE) in my filters. After I had confirmed it was the filter we suspected, I went through and commented out the last several PCRE lines I had added. With that, I could once again turn the filter on and decludeproc would run fine. So I have narrowed it down to a few possible PCRE entries that were causing the issue. When I have some time in the next few days, I will probably work with each entry to figure out exactly which one it is. I thought I was starting to get the hang of the PCRE expressions. However, the decludeproc service has "slapped" me back to reality. At least now I realize that I need to be more careful when adding these entries, and what the result is if I'm not! Todd --- 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.
