I will look into it. Thanks for the help.
On 6/15/2012 3:20 PM, Eric Shubert wrote:
On 06/15/2012 11:28 AM, Mike Tirpak wrote:
The thing I'm worried about is our mail server is used by our customers
that want to send pages through our system. There are hundreds of emails
that get processed everyday and I can't get all of them into the
whitelist. The pages are very important to emergency services. I don't
want to inadvertently block a doctor from getting a page.
I was able to unblock the ip address and I am getting qmailtoaster
emails now. I had to just block around it.
On 6/15/2012 1:07 PM, Eric Shubert wrote:
It's better to use spamdyke to do this (block and whitelist).
Spamdyke has much more flexibility.
If you don't have spamdyke installed yet, you should do so. It will be
included in the stock QMT at some point.
---------------------------------------------------------------------
Like I said, spamdyke is very flexible. You can activate its rules a
little at a time (gradually), and selectively as well. You can have
separate rules by domain or even by user if need be.
Once size often does not fit all. You might want to whitelist
recipient addresses that are for emergency services. There will most
likely be very few if any cases beyond that which you would need to
whitelist, providing you implement rules appropriate to your
situation. The default configuration file is a good starting point,
which will produce very few false positives.
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
