Firetrust Support Forums

It seems like as the blacklist grows just a bit, the program runs quite slowly.

Is this better in newer versions?
Is there a solution for it?

It depends just how large we're talking. But under Tools >> Spam Tools >> My Blacklist >> List Options >> you can set addresses that haven't matched/been added lately to expire >> you could try around 30-60 days, I think the default is 90 which could grow quite large over time.

docb wrote:It seems like as the blacklist grows just a bit, the program runs quite slowly.

Unfortunately, that is an inevitable doctrine that holds true for all types of blocking programs (not limited to MailWasher.)

docb wrote:Is this better in newer versions?

Better . . . . . . . . yes — to a certain point (the doctrine does kick into play in the longer run, though.)

docb wrote:Is there a solution for it?

Was forced to use a whitelist policy (instead of the more commonly used blacklist) after earning the wrath of spammers — the blacklist policy does not cope up with my kind of mail upsurge (not even on the latest V7.)

Needless to mention, I prefer to employ the whitelist doctrine even in other walks of computing, such as firewalling, ad. blocking, etc., etc.


ps:—

• If your inbounds are just about average, you might want to persist with your present blacklist implementation.