I figured out why it was looking like it was using the global.cfg file instead of $default$.JunkMail It had to do with the way our email server is set up - we needed to put the global.cfg file under a different directory to work on our domain. You can disregaurd the problem below. Thanks
----- Original Message ----- > >Also I posted a question earlier about why Declude is using Global.cfg > >instead of $default$.JunkMail file settings on incoming email - do you > >have any ideas why? > > To get a better idea of what is happening, you can use the Declude debug > mode. To do this, change the "LOGLEVEL LOW" line in > \IMail\Declude\global.cfg to "LOGLEVEL DEBUG". Then, after an E-mail has > come through that used the global.cfg settings instead of the > $default$.JunkMail settings, you can switch it back to "LOGLEVEL LOW" (the > debug mode adds huge amounts of information to the log file). You can then > send me the \IMail\Declude\vir####.log file, letting me know which E-mail > was using the wrong settings, and I can take a look at it to see what the > problem may be. > -Scott > > --- > > 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". You can E-mail > [EMAIL PROTECTED] for assistance. You can visit our web > site at http://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". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
