Hi,
There is just too much spam. Especially the ones that forge email addresses.
I am thinking of setting up a reverse dns checking.
An alternative to spamdyke is by setting the following in the run file.
-p: Paranoid. After looking up the remote host name in DNS, look up the
IP addresses in
I believe that spamdyke does this, and a lot more, including graylisting.
Are you using spamdyke yet? If so, what's your configuration?
P.V.Anthony wrote:
Hi,
There is just too much spam. Especially the ones that forge email
addresses.
I am thinking of setting up a reverse dns checking.
On 5-Mar-09, at 3:59 PM, Eric Shubert wrote:
I believe that spamdyke does this, and a lot more, including
graylisting.
Are you using spamdyke yet? If so, what's your configuration?
P.V.Anthony wrote:
Hi,
There is just too much spam. Especially the ones that forge email
addresses.
I am
On Thu, Mar 5, 2009 at 6:59 PM, Eric Shubert e...@shubes.net wrote:
I believe that spamdyke does this, and a lot more, including graylisting.
Are you using spamdyke yet? If so, what's your configuration?
Here is mine (i do not use qtp-plus):
log-target=stderr
log-level=info
On 06-Mar-09 7:59 AM, Eric Shubert wrote:
I believe that spamdyke does this, and a lot more, including graylisting.
Are you using spamdyke yet? If so, what's your configuration?
Currently not using spamdyke and I already am using graylisting. From
this email I see that I better just go with
On 06-Mar-09 8:09 AM, dnk wrote:
Throwing on Spamdyke and using a combination of RBL's, DNS checks and
graylisting have helped IMMENSELY at my primary employment.
I would just cut to the chase and install spamdyke - it is easy to do
with the qtp-menu option, and you can enable and disable
P.V.Anthony wrote:
On 06-Mar-09 7:59 AM, Eric Shubert wrote:
I believe that spamdyke does this, and a lot more, including graylisting.
Are you using spamdyke yet? If so, what's your configuration?
Currently not using spamdyke and I already am using graylisting. From
this email I see that I
