If your users could handle going to the web interface and adding people they would like whitelisted to their address book there, all you would need do then is add AUTOWHITELIST ON to your one global config file. This way they could whitelist anyone's e-mail address that they wished. Next maybe you can have a whitelist word or phrase in your global config file; WHITELIST ANYWHERE whitelistphrase, tell your users that that they could add this phrase to their signature so that all replies to them or to whom they give the pass phrase would be whitelisted as well. I think you are asking for trouble if you let them FTP their own files. I have played with the idea of creating separate junkmail files and allowing users to select levels of control:
Severe (only people who are whitelisted can get through) Strict hold on 10, delete on 20 Moderate hold on 20 delete on 30 Permissive hold on 30 delete on 40 Open nothing held or deleted. This is still a heavy amount of admin and asking for a bit of trouble (I think, unless you can automate the ftp process to create the separate folders and appropriately named junkmail file) If you try to let them manually create a junkmail file I think it gets to involved, IMHO. The tests and the actions would get too confusing and god help you if they all discover how to bounce messages. Marc -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brent Brashear Sent: Monday, January 19, 2004 02:28 PM To: [EMAIL PROTECTED] Subject: RE: [Declude.JunkMail] Enabling control to customers Scott, Thank you VERY much for your reply. From what I understand (in your message), I'm wasting my time by making the $default$.JunkMail file available (FTP was just the method I was using to access the file) -since the Global.CFG file overwrites it anyway. The file structure is IMail\Declude\mail.customerdomain.com\$default$.JunkMail (the Global.CFG file is in the Declude folder). My impression was that the customer settings would point to $default$.JunkMail file and they could have their settings different from the Global.CFG ones. What method would you recommend to let the customers edit their individual e-mail domains? Or would you even attempt this at all? Best Regards, Brent -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of R. Scott Perry Sent: Monday, January 19, 2004 1:45 PM To: [EMAIL PROTECTED] Subject: RE: [Declude.JunkMail] Enabling control to customers >I'd like to setup an FTP site with individual '$default$.JunkMail' files >accessible for each domain that's setup with AntiSpam.... Will this >overwrite some of the settings from Global.CFG? -If so, that's okay. No, it would not overwrite the global.cfg file (assuming that the FTP site doesn't allow access to the global.cfg file). >One of the requests I frequently get is WHITELISTING. I've done a test on my >end (to no success) by typing WHITELIST FROM [EMAIL PROTECTED] Whenever I send >an e-mail out with a particiliar word (a certain male body part) in the >subject line, it still goes into the spam mailbox.... -BUT when I put the >word "porn" in the subject line (which is set to send the message to the >spam mailbox) I do receive it. Note that the WHITELIST command only works in the \IMail\Declude\global.cfg file. If you want per-domain whitelisting, you would need to set it up using the WHITELISTFILE option. The configuration file for the user/domain can have a line in the format "WHITELISTFILE C:\IMail\Declude\example.com\whitelistfile.txt", which instructs Declude JunkMail to use a whitelist file. The whitelist file (whitelistfile.txt in this case) can then have 1 E-mail address or domain per line. >I was under the impression that if something is 'WHITELISTED', it'll go >through (even if it's BLACKLISTED somewhere in another setting). That is correct. Any E-mail that is whitelisted should be delivered as if it did not fail any spam tests. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [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". The archives can be found at http://www.mail-archive.com. --- [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". The archives can be found at http://www.mail-archive.com. --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail scanned for viruses by Declude Virus] --- [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". The archives can be found at http://www.mail-archive.com.
