I think maybe I missed something. I HAD:
Declude/DomainName.com directories for each customer we are JunkMail'ing for. and no $default$.JunkMail file in the Declude directory (which was generating errors in the Declude log). BUT The Global.cfg only defines the tests, does not have any actions associated with them. $default$.JunkMail defines the actions associated with the tests. SO I put an empty file in the Declude directory and named it $default$.JunkMail. I have $default$.JunkMail files with tests / actions specified in each of the Declude/DomainName.com directories for the customers subscribing to the service. This should result in no logging, no warnings, nothing, UNLESS the receiver's domain name is one of the Declude/DomainName.com domains. Correct? (I'll know shortly.) [EMAIL PROTECTED] > > The warnings are only added to the headers if the WARN action is used for > the domain/user receiving the E-mail. So if you change the > \IMail\Declude\global.cfg file to use the LOG action instead of the WARN > action, then your users who aren't paying won't be able to use > IMail rules > to detect the warning headers. > -Scott --- [This E-mail was scanned for viruses by Declude Virus (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 .
