Just a suggestion...
I really think that we should keep any dynamic entries out of the Global statement. Global should be a file that changes only when one wants to make changes to the engine or adding functionality. It is simply like a .ini file that controls the engine.
Currently there is one that I am confused as to why it belong to Global.cfg.
WHITELIST HELO
The idea here is that the WHITELIST command was originally added as a last resort. The "WHITELIST HELO" option isn't commonly used, and we did not foresee it being something that would be changed frequently.
If this was like a filter file one could make the changes in a database and simply update these files dynamically. Right now these entries being in the Global makes it real hard.
Is it a possibility to move any such action and make them a filter type entry so simply the address of the file is located in the global.
That is something that we are moving towards; the WHITELISTFILE option (which doesn't work in the global.cfg file, and won't look at the HELO) was the first step towards this.
-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 have been missing: Ask for a 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.
