| | This is what we are thinking of. | | [1] Keep the BANEXT option the way it is (banning specified | extensions). | [2] Add an "ALLOWEXT" option (banning all extensions | except the | ones listed). | [3] If both BANEXT and ALLOWEXT exist, allow all | extensions, and | generate an error in the logs. | | -Scott
OK... I think in case of a collision [3] it would be safer to ban all extensions and generate an error in logs. In case the log isn't reviewed quickly enough a: the sysop would likely be prompted by a user, b: nothing ugly would suddenly get through in case of a configuration mishap. my $.02. _M | | --- | [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.Virus mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.Virus". 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.Virus mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.Virus". The archives can be found at http://www.mail-archive.com.
