date:20081022

Re: [spamdyke-users] spamdyke +ip-in-rdns - per domain basis

2008-10-22 Thread Sam Clippinger

Yes, this can be done using configuration directories.  Simply follow 
David's example below, but change the configuration files 
(.../domain_setups/_recipient_/tld/firstdomain) to contain one or more 
of the following options as appropriate:
ip-in-rdns-keyword-blacklist-file=!!!
reject-missing-rdns=0
reject-unresolvable-rdns=0

-- Sam Clippinger

Erald Troja wrote:
> David/Linto,
>
> This is very interesting setup.
>
> I would like to push it a bit further and try to find out if it's 
> possible to have a  IP_IN_RDNS_KEYWORDS restriction in place
> server wide, while allowing a few handpicked domains to have it fully
> turned off.  We would like to maintain for RDNS existance and 
> RNDS_RESOLVE existance serverwide as well.
>
> As of now I realize it's possible to simply whitelist a few handpicked
> Reverse DNS's
>
> Is this setup possible?
>
> Thanks.
>
> 
> Erald Troja
>
>
> David Stiller wrote:
>   
>> Hi Linto,
>>
>> the per-domain basis you can create by using the config-dir option,
>> wich is well documented in the documentation:
>>
>> http://www.spamdyke.org/documentation/README.html#CONFIGURATION_DIR
>>
>> Nearly any combination of sender and recipient can be configured
>> with this option. This way i configure black- and whitelists for
>> my customers.
>>
>> My structure looks like the following.
>>
>> In /etc/spamdyke.conf i set:
>> config-dir=/var/qmail/spamdyke/domain_setups
>>
>> The directories contain:
>>
>> domain_setups/
>> `-- _recipient_
>> |-- tld
>> |   `-- firstdomain (file)
>> `-- tld2
>> `-- seconddomain (file)
>>
>>
>> domain_configs/
>> |-- firstdomain.tld
>> |   |-- customer_blacklist_ip
>> |   |-- customer_blacklist_rdns
>> |   |-- customer_whitelist_ip
>> |   `-- customer_whitelist_rdns
>> `-- seconddomain.tld2
>> |-- customer_blacklist_ip
>> |-- customer_blacklist_rdns
>> |-- customer_whitelist_ip
>> `-- customer_whitelist_rdns
>>
>> In the file "firstdomain" you can setup the configuration
>> for the domain and also the IP_IN_RDNS_KEYWORDS of course.
>>
>> In my case these are:
>>
>> ip-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_ip
>> rdns-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_rdns
>> ip-whitelist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_whitelist_ip
>> rdns-whitelist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_whitelist_rdns
>> sender-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_sender
>>
>> I hope this helps! ;)
>>  
>> David
>>
>>
>> Linto Paul schrieb:
>> 
>>> Greetings,
>>>
>>> Could please let me know if there is a way to whitelist a domain on 
>>> the IP_IN_RDNS_KEYWORDS on a per domain basis.
>>>
>>> Say we get user complaining about a domain called example.com 
>>> , and they say, I am the owner of example.com 
>>>  and want this feature not used onto our domain 
>>> even though you host it for us.
>>>
>>> ~~~
>>> Oct 21 11:46:44 mail01 spamdyke[24348]: DENIED_IP_IN_RDNS from: 
>>> [EMAIL PROTECTED]  to: 
>>> [EMAIL PROTECTED]  origin_ip: 66.49.15.190 
>>>  origin_rdns: 66.49.15.190.nw.nuvox.net 
>>>  auth: (unknown)
>>> 
>>>
>>> We have the RDNS blocked in our server via keyword:-
>>>
>>> .nuvox.net 
>>>
>>> Is it possible to just put a whitelist for example.com 
>>>  and deny all others matching this keyword.
>>>
>>> Thanks,
>>> Linto Paul
>>>  
>>>
>>> On Thu, Oct 16, 2008 at 10:30 PM, <[EMAIL PROTECTED] 
>>> > wrote:
>>>
>>> Send spamdyke-users mailing list submissions to
>>>spamdyke-users@spamdyke.org
>>> 
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>>> or, via email, send a message with subject or body 'help' to
>>>[EMAIL PROTECTED]
>>> 
>>>
>>> You can reach the person managing the list at
>>>[EMAIL PROTECTED]
>>> 
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of spamdyke-users digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>>   1. Regular-Expression Support (Felix Buenemann)
>>>   2. Re: spamdyke  +ip-in-rdns-keyword-blacklist-entry option
>>>  (Arthur Girardi)
>>>   3. Re: spamdyke +ip-in-rdns-keyword-blacklist-entry  option
>>>  (Felix Buenemann)
>>>   4. Re: spamdyke  +ip-in-rdns-keyword-blacklist-entryoption
>>>  (Tim Mancour)
>>>
>>>
>>> --
>>>
>

Re: [spamdyke-users] spamdyke +ip-in-rdns - per domain basis

2008-10-22 Thread Erald Troja

David/Linto,

This is very interesting setup.

I would like to push it a bit further and try to find out if it's 
possible to have a  IP_IN_RDNS_KEYWORDS restriction in place
server wide, while allowing a few handpicked domains to have it fully
turned off.  We would like to maintain for RDNS existance and 
RNDS_RESOLVE existance serverwide as well.

As of now I realize it's possible to simply whitelist a few handpicked
Reverse DNS's

Is this setup possible?

Thanks.


Erald Troja


David Stiller wrote:
> Hi Linto,
> 
> the per-domain basis you can create by using the config-dir option,
> wich is well documented in the documentation:
> 
> http://www.spamdyke.org/documentation/README.html#CONFIGURATION_DIR
> 
> Nearly any combination of sender and recipient can be configured
> with this option. This way i configure black- and whitelists for
> my customers.
> 
> My structure looks like the following.
> 
> In /etc/spamdyke.conf i set:
> config-dir=/var/qmail/spamdyke/domain_setups
> 
> The directories contain:
> 
> domain_setups/
> `-- _recipient_
> |-- tld
> |   `-- firstdomain (file)
> `-- tld2
> `-- seconddomain (file)
> 
> 
> domain_configs/
> |-- firstdomain.tld
> |   |-- customer_blacklist_ip
> |   |-- customer_blacklist_rdns
> |   |-- customer_whitelist_ip
> |   `-- customer_whitelist_rdns
> `-- seconddomain.tld2
> |-- customer_blacklist_ip
> |-- customer_blacklist_rdns
> |-- customer_whitelist_ip
> `-- customer_whitelist_rdns
> 
> In the file "firstdomain" you can setup the configuration
> for the domain and also the IP_IN_RDNS_KEYWORDS of course.
> 
> In my case these are:
> 
> ip-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_ip
> rdns-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_rdns
> ip-whitelist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_whitelist_ip
> rdns-whitelist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_whitelist_rdns
> sender-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_sender
> 
> I hope this helps! ;)
>  
> David
> 
> 
> Linto Paul schrieb:
>> Greetings,
>>
>> Could please let me know if there is a way to whitelist a domain on 
>> the IP_IN_RDNS_KEYWORDS on a per domain basis.
>>
>> Say we get user complaining about a domain called example.com 
>> , and they say, I am the owner of example.com 
>>  and want this feature not used onto our domain 
>> even though you host it for us.
>>
>> ~~~
>> Oct 21 11:46:44 mail01 spamdyke[24348]: DENIED_IP_IN_RDNS from: 
>> [EMAIL PROTECTED]  to: 
>> [EMAIL PROTECTED]  origin_ip: 66.49.15.190 
>>  origin_rdns: 66.49.15.190.nw.nuvox.net 
>>  auth: (unknown)
>> 
>>
>> We have the RDNS blocked in our server via keyword:-
>>
>> .nuvox.net 
>>
>> Is it possible to just put a whitelist for example.com 
>>  and deny all others matching this keyword.
>>
>> Thanks,
>> Linto Paul
>>  
>>
>> On Thu, Oct 16, 2008 at 10:30 PM, <[EMAIL PROTECTED] 
>> > wrote:
>>
>> Send spamdyke-users mailing list submissions to
>>spamdyke-users@spamdyke.org
>> 
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>> or, via email, send a message with subject or body 'help' to
>>[EMAIL PROTECTED]
>> 
>>
>> You can reach the person managing the list at
>>[EMAIL PROTECTED]
>> 
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of spamdyke-users digest..."
>>
>>
>> Today's Topics:
>>
>>   1. Regular-Expression Support (Felix Buenemann)
>>   2. Re: spamdyke  +ip-in-rdns-keyword-blacklist-entry option
>>  (Arthur Girardi)
>>   3. Re: spamdyke +ip-in-rdns-keyword-blacklist-entry  option
>>  (Felix Buenemann)
>>   4. Re: spamdyke  +ip-in-rdns-keyword-blacklist-entryoption
>>  (Tim Mancour)
>>
>>
>> --
>>
>> Message: 1
>> Date: Thu, 16 Oct 2008 17:07:56 +0200
>> From: Felix Buenemann <[EMAIL PROTECTED]
>> >
>> Subject: [spamdyke-users] Regular-Expression Support
>> To: spamdyke-users@spamdyke.org 
>> Message-ID: <[EMAIL PROTECTED] >
>> Content-Type: text/plain; charset=ISO-8859-15
>>
>> Hi Sam,
>>
>> I wonder wether there is a specific reason not to use regular
>> expressions via the PCRE lib to matc

Re: [spamdyke-users] spamdyke +ip-in-rdns - per domain basis

2008-10-22 Thread Sam Clippinger

Whitelists always override blacklists, no matter where they are found or 
what order they are listed in.

-- Sam Clippinger

David Stiller wrote:
> As an answer to this:
> "Is it possible to just put a whitelist for example.com 
>  and deny all others matching this keyword."
>
> Sure. I would just whitelist 66.49.15.190 and blacklist .nuvox.net 
> . Don't know wich one catches
> first. I would try.
>
> Regards,
> David
>
> 
>
> David Stiller schrieb:
>   
>> Hi Linto,
>>
>> the per-domain basis you can create by using the config-dir option,
>> wich is well documented in the documentation:
>>
>> http://www.spamdyke.org/documentation/README.html#CONFIGURATION_DIR
>>
>> Nearly any combination of sender and recipient can be configured
>> with this option. This way i configure black- and whitelists for
>> my customers.
>>
>> My structure looks like the following.
>>
>> In /etc/spamdyke.conf i set:
>> config-dir=/var/qmail/spamdyke/domain_setups
>>
>> The directories contain:
>>
>> domain_setups/
>> `-- _recipient_
>> |-- tld
>> |   `-- firstdomain (file)
>> `-- tld2
>> `-- seconddomain (file)
>>
>>
>> domain_configs/
>> |-- firstdomain.tld
>> |   |-- customer_blacklist_ip
>> |   |-- customer_blacklist_rdns
>> |   |-- customer_whitelist_ip
>> |   `-- customer_whitelist_rdns
>> `-- seconddomain.tld2
>> |-- customer_blacklist_ip
>> |-- customer_blacklist_rdns
>> |-- customer_whitelist_ip
>> `-- customer_whitelist_rdns
>>
>> In the file "firstdomain" you can setup the configuration
>> for the domain and also the IP_IN_RDNS_KEYWORDS of course.
>>
>> In my case these are:
>>
>> ip-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_ip
>> rdns-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_rdns
>> ip-whitelist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_whitelist_ip
>> rdns-whitelist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_whitelist_rdns
>> sender-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_sender
>>
>> I hope this helps! ;)
>>  
>> David
>>
>>
>> Linto Paul schrieb:
>> 
>>> Greetings,
>>>
>>> Could please let me know if there is a way to whitelist a domain on 
>>> the IP_IN_RDNS_KEYWORDS on a per domain basis.
>>>
>>> Say we get user complaining about a domain called example.com 
>>> , and they say, I am the owner of example.com 
>>>  and want this feature not used onto our domain 
>>> even though you host it for us.
>>>
>>> ~~~
>>> Oct 21 11:46:44 mail01 spamdyke[24348]: DENIED_IP_IN_RDNS from: 
>>> [EMAIL PROTECTED]  to: 
>>> [EMAIL PROTECTED]  origin_ip: 66.49.15.190 
>>>  origin_rdns: 66.49.15.190.nw.nuvox.net 
>>>  auth: (unknown)
>>> 
>>>
>>> We have the RDNS blocked in our server via keyword:-
>>>
>>> .nuvox.net 
>>>
>>> Is it possible to just put a whitelist for example.com 
>>>  and deny all others matching this keyword.
>>>
>>> Thanks,
>>> Linto Paul
>>>  
>>>
>>> On Thu, Oct 16, 2008 at 10:30 PM, 
>>> <[EMAIL PROTECTED] 
>>> > wrote:
>>>
>>> Send spamdyke-users mailing list submissions to
>>>spamdyke-users@spamdyke.org
>>> 
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>>> or, via email, send a message with subject or body 'help' to
>>>[EMAIL PROTECTED]
>>> 
>>>
>>> You can reach the person managing the list at
>>>[EMAIL PROTECTED]
>>> 
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of spamdyke-users digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>>   1. Regular-Expression Support (Felix Buenemann)
>>>   2. Re: spamdyke  +ip-in-rdns-keyword-blacklist-entry option
>>>  (Arthur Girardi)
>>>   3. Re: spamdyke +ip-in-rdns-keyword-blacklist-entry  option
>>>  (Felix Buenemann)
>>>   4. Re: spamdyke  +ip-in-rdns-keyword-blacklist-entryoption
>>>  (Tim Mancour)
>>>
>>>
>>> --
>>>
>>> Message: 1
>>> Date: Thu, 16 Oct 2008 17:07:56 +0200
>>> From: Felix Buenemann <[EMAIL PROTECTED]
>>> >
>>> Subject: [spamdyke-users] Regular-Expression Support
>>> To: spamdyke-users@spamdyke.org 
>>> Message-ID: <[EMAIL PROTECTED] >
>>> Content-Type: text/plain; charset=ISO-8859-15
>>>
>>> Hi Sam,
>>

Re: [spamdyke-users] spamdyke +ip-in-rdns - per domain basis

2008-10-22 Thread David Stiller

As an answer to this:
"Is it possible to just put a whitelist for example.com 
 and deny all others matching this keyword."

Sure. I would just whitelist 66.49.15.190 and blacklist .nuvox.net 
. Don't know wich one catches
first. I would try.

Regards,
David



David Stiller schrieb:
> Hi Linto,
>
> the per-domain basis you can create by using the config-dir option,
> wich is well documented in the documentation:
>
> http://www.spamdyke.org/documentation/README.html#CONFIGURATION_DIR
>
> Nearly any combination of sender and recipient can be configured
> with this option. This way i configure black- and whitelists for
> my customers.
>
> My structure looks like the following.
>
> In /etc/spamdyke.conf i set:
> config-dir=/var/qmail/spamdyke/domain_setups
>
> The directories contain:
>
> domain_setups/
> `-- _recipient_
> |-- tld
> |   `-- firstdomain (file)
> `-- tld2
> `-- seconddomain (file)
>
>
> domain_configs/
> |-- firstdomain.tld
> |   |-- customer_blacklist_ip
> |   |-- customer_blacklist_rdns
> |   |-- customer_whitelist_ip
> |   `-- customer_whitelist_rdns
> `-- seconddomain.tld2
> |-- customer_blacklist_ip
> |-- customer_blacklist_rdns
> |-- customer_whitelist_ip
> `-- customer_whitelist_rdns
>
> In the file "firstdomain" you can setup the configuration
> for the domain and also the IP_IN_RDNS_KEYWORDS of course.
>
> In my case these are:
>
> ip-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_ip
> rdns-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_rdns
> ip-whitelist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_whitelist_ip
> rdns-whitelist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_whitelist_rdns
> sender-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_sender
>
> I hope this helps! ;)
>  
> David
>
>
> Linto Paul schrieb:
>> Greetings,
>>
>> Could please let me know if there is a way to whitelist a domain on 
>> the IP_IN_RDNS_KEYWORDS on a per domain basis.
>>
>> Say we get user complaining about a domain called example.com 
>> , and they say, I am the owner of example.com 
>>  and want this feature not used onto our domain 
>> even though you host it for us.
>>
>> ~~~
>> Oct 21 11:46:44 mail01 spamdyke[24348]: DENIED_IP_IN_RDNS from: 
>> [EMAIL PROTECTED]  to: 
>> [EMAIL PROTECTED]  origin_ip: 66.49.15.190 
>>  origin_rdns: 66.49.15.190.nw.nuvox.net 
>>  auth: (unknown)
>> 
>>
>> We have the RDNS blocked in our server via keyword:-
>>
>> .nuvox.net 
>>
>> Is it possible to just put a whitelist for example.com 
>>  and deny all others matching this keyword.
>>
>> Thanks,
>> Linto Paul
>>  
>>
>> On Thu, Oct 16, 2008 at 10:30 PM, 
>> <[EMAIL PROTECTED] 
>> > wrote:
>>
>> Send spamdyke-users mailing list submissions to
>>spamdyke-users@spamdyke.org
>> 
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>> or, via email, send a message with subject or body 'help' to
>>[EMAIL PROTECTED]
>> 
>>
>> You can reach the person managing the list at
>>[EMAIL PROTECTED]
>> 
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of spamdyke-users digest..."
>>
>>
>> Today's Topics:
>>
>>   1. Regular-Expression Support (Felix Buenemann)
>>   2. Re: spamdyke  +ip-in-rdns-keyword-blacklist-entry option
>>  (Arthur Girardi)
>>   3. Re: spamdyke +ip-in-rdns-keyword-blacklist-entry  option
>>  (Felix Buenemann)
>>   4. Re: spamdyke  +ip-in-rdns-keyword-blacklist-entryoption
>>  (Tim Mancour)
>>
>>
>> --
>>
>> Message: 1
>> Date: Thu, 16 Oct 2008 17:07:56 +0200
>> From: Felix Buenemann <[EMAIL PROTECTED]
>> >
>> Subject: [spamdyke-users] Regular-Expression Support
>> To: spamdyke-users@spamdyke.org 
>> Message-ID: <[EMAIL PROTECTED] >
>> Content-Type: text/plain; charset=ISO-8859-15
>>
>> Hi Sam,
>>
>> I wonder wether there is a specific reason not to use regular
>> expressions via the PCRE lib to match patterns in blacklist files
>> etc.
>>
>> Has this been avoided for performance reasons?
>>
>> -- Felix Buenemann
>>
>>
>>
>> --
>>
>> Message: 2
>>

Re: [spamdyke-users] spamdyke +ip-in-rdns - per domain basis

2008-10-22 Thread David Stiller

Hi Linto,

the per-domain basis you can create by using the config-dir option,
wich is well documented in the documentation:

http://www.spamdyke.org/documentation/README.html#CONFIGURATION_DIR

Nearly any combination of sender and recipient can be configured
with this option. This way i configure black- and whitelists for
my customers.

My structure looks like the following.

In /etc/spamdyke.conf i set:
config-dir=/var/qmail/spamdyke/domain_setups

The directories contain:

domain_setups/
`-- _recipient_
   |-- tld
   |   `-- firstdomain (file)
   `-- tld2
   `-- seconddomain (file)

domain_configs/
|-- firstdomain.tld
|   |-- customer_blacklist_ip
|   |-- customer_blacklist_rdns
|   |-- customer_whitelist_ip
|   `-- customer_whitelist_rdns
`-- seconddomain.tld2
   |-- customer_blacklist_ip
   |-- customer_blacklist_rdns
   |-- customer_whitelist_ip
   `-- customer_whitelist_rdns

In the file "firstdomain" you can setup the configuration
for the domain and also the IP_IN_RDNS_KEYWORDS of course.

In my case these are:

ip-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_ip
rdns-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_rdns
ip-whitelist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_whitelist_ip
rdns-whitelist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_whitelist_rdns
sender-blacklist-file=/var/qmail/spamdyke/domain_configs/firstdomain.tld/customer_blacklist_sender

I hope this helps! ;)

David

Linto Paul schrieb:

Greetings,

Could please let me know if there is a way to whitelist a domain on 
the IP_IN_RDNS_KEYWORDS on a per domain basis.

Say we get user complaining about a domain called example.com 
, and they say, I am the owner of example.com 
 and want this feature not used onto our domain 
even though you host it for us.

~~~
Oct 21 11:46:44 mail01 spamdyke[24348]: DENIED_IP_IN_RDNS from: 
[EMAIL PROTECTED]  to: 
[EMAIL PROTECTED]  origin_ip: 66.49.15.190 
 origin_rdns: 66.49.15.190.nw.nuvox.net 
 auth: (unknown)

We have the RDNS blocked in our server via keyword:-

.nuvox.net 

Is it possible to just put a whitelist for example.com 
 and deny all others matching this keyword.

Thanks,
Linto Paul

On Thu, Oct 16, 2008 at 10:30 PM, <[EMAIL PROTECTED] 
> wrote:

Send spamdyke-users mailing list submissions to
   spamdyke-users@spamdyke.org

To subscribe or unsubscribe via the World Wide Web, visit
   http://www.spamdyke.org/mailman/listinfo/spamdyke-users
or, via email, send a message with subject or body 'help' to
   [EMAIL PROTECTED]

You can reach the person managing the list at
   [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of spamdyke-users digest..."

Today's Topics:

  1. Regular-Expression Support (Felix Buenemann)
  2. Re: spamdyke  +ip-in-rdns-keyword-blacklist-entry option
 (Arthur Girardi)
  3. Re: spamdyke +ip-in-rdns-keyword-blacklist-entry  option
 (Felix Buenemann)
  4. Re: spamdyke  +ip-in-rdns-keyword-blacklist-entryoption
 (Tim Mancour)

--

Message: 1
Date: Thu, 16 Oct 2008 17:07:56 +0200
From: Felix Buenemann <[EMAIL PROTECTED]
>
Subject: [spamdyke-users] Regular-Expression Support
To: spamdyke-users@spamdyke.org 
Message-ID: <[EMAIL PROTECTED] >
Content-Type: text/plain; charset=ISO-8859-15

Hi Sam,

I wonder wether there is a specific reason not to use regular
expressions via the PCRE lib to match patterns in blacklist files etc.

Has this been avoided for performance reasons?

-- Felix Buenemann

--

Message: 2
Date: Thu, 16 Oct 2008 12:12:58 -0300
From: Arthur Girardi <[EMAIL PROTECTED]
>
Subject: Re: [spamdyke-users] spamdyke
   +ip-in-rdns-keyword-blacklist-entry option
To: spamdyke-users@spamdyke.org 
Message-ID: <[EMAIL PROTECTED]
>
Content-Type: text/plain;   charset=ISO-8859-1; DelSp="Yes";
   format="flowed"

For me it looks as if the message is being blocked because it contains
the country code and ip in the rdns and his setup has
reject-ip-in-cc-rdns enabled.

In the FAQ it says it will check reject-ip-in-cc-rdns b

Re: [spamdyke-users] spamdyke +ip-in-rdns - per domain basis

Re: [spamdyke-users] spamdyke +ip-in-rdns - per domain basis

Re: [spamdyke-users] spamdyke +ip-in-rdns - per domain basis

Re: [spamdyke-users] spamdyke +ip-in-rdns - per domain basis

Re: [spamdyke-users] spamdyke +ip-in-rdns - per domain basis

5 matches

Site Navigation

Mail list logo

Footer information