Our current way of blocking a spam address is by editing access_sender & access_recipient & then reload postmap.
>From time to time we're given addresses that should never be blocked but due to staff turnover & documentation not up-to-date, an address that should never be blocked was somehow blocked. Pardon me if this has been discussed before, what's the best way to go about preventing such mistakes? Is there a whitelist file that we can enter addresses that should never blocked so that even if this address is manually added into access_sender & access_recipient, they will still not be blocked (& possibly will be automatically removed from the two files access_sender/recipient). If there's such a whitelist file, presumably there should be 2 of them, one for sending & receiving. Let me know the full directory path & filename of the whitelist files Thanks Sun
