Will high whitelist row count adversely affect performance?

Glenn Steen glenn.steen at gmail.com
Fri Sep 22 01:43:03 IST 2006

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:-).

-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se

More information about the MailScanner mailing list