Will high whitelist row count adversely affect performance?

[Scott Silva]

Glenn Steen spake the following on 9/21/2006 5:43 PM:
> On 22/09/06, Dennis Willson <taz at taz-mania.com> wrote:
>> Actually if you do "default" whitelisting you can certainly create
>> holes. I mostly do (there are only a few exceptions) IP whitelists and
>> Specific from and to whitelists. Meaning the whitelist must have a
>> specific fully qualified to address to accompany the from address or
>> domain. That way only one user can get slamed by their request.
>> External peoples (not my users) cannot request (actually gets ignored)
>> any whitelisting.
>>
>> By using mailwatch and allowing the users to manage their own
>> whitelists, it (mailwatch) forces the To: address to be theis and they
>> can't change that. So a single user and mess themselves up, but not
>> others.
>>
> Letting the users have enough rope, eh? I suppose that is a viable
> compromise:-). At least for you ISP types... Me, I'm more for
> ...dictatorship... when it comes to this (at least as long as it is
> _me_ dictating:-).
> 
That is the thing about a dictatorship ..
 The dictator is usually the only one happy all the time.

-- 

MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!