Re: [qmailtoaster] spamdyke and tcpserver

2008-11-04 Thread Philip Nix Guru 

Thx
but we are using simscan in qtoaster and it is patched to provide smtp auth
brings memories, I did use qmail scanner in some old days :)

I will play tomorrow with different combos in the tcp.smtp file to 
really see what triggers it

I ll let you know
Cheers
-P

||
Sam Clippinger wrote:

I'm not sure if this applies or not but it might solve your problem:
   http://www.spamdyke.org/documentation/FAQ.html#TROUBLE5

-- Sam Clippinger

Philip Nix Guru wrote:

From my testing
adding those 2 lines in spamdyke.conf
local-domains-file=/var/qmail/control/rcpthosts
local-domains-file=/var/qmail/control/morercpthosts

didnt change anything, all is still working fine on this "busy" test 
server


But
adding
access-file=/etc/tcprules.d/tcp.smtp  (using different tcp.smtp files 
for testing purpose)
I dont have any mail parsed through spamassassin anymore, as soon as 
I remove that configuration

it have activity again ...

cant explain yet why :)

Sam Clippinger wrote:
I wouldn't add them unconditionally, because spamdyke will generate 
errors if it can't open a nonexistent file.  What you're doing now 
is probably best.


I'm not very familiar with QMT's admin tools -- how does 
/var/qmail/control/morercpthosts get created in the first place?  
Does one of the admin tools automatically create the file when 
/var/qmail/control/rcpthosts gets too big?


-- Sam Clippinger

Eric Shubert wrote:

Sam Clippinger wrote:
That's probably all that needs to happen.  I don't have a copy of 
the QTP spamdyke configuration file handy, but it should also 
contain "local-domains-file" lines to load 
/var/qmail/control/rcpthosts and /var/qmail/control/morercpthosts 
if spamdyke is going to correctly handle relaying.


The local-domains-file parameter is added by the script for each of 
rcpthosts and morercpthosts, but only when they exist. Would it 
perhaps be better to always add them whether they exist or not?



-- Sam Clippinger

Eric Shubert wrote:

Looks like I missed this one, Philip. Thanks for pointing it out.

From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would 
change in
the run.spamdyke file. I guess the parameter could be added to 
either
place, but I'm trying to keep the configuration as cohesive as 
possible.


Sam, does this look right to you? If so I'll get in in the next 
QT-Plus

release.

Philip wrote:
 

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus 
should

maybe add the |access-file| option
and use the /etc/tcprules.d/tcp.smtp as parameters in the 
run.spamdyke file
If ppl had local ips or other ips to prevent rbl checking or 
allowing

relaying
it has no effect anymore.

Or those ips should be  under some conditions  added to the 
whitelist_ip

file of spamdyke

-P


Sam Clippinger wrote:
 
spamdyke cannot read CDB files but it can read the 
/etc/tcp.smtp file

(text version) and use some of the values, mostly for controlling
relaying.  For example, if the incoming IP address matches a 
line that

sets the RELAYCLIENT variable, spamdyke will allow the client to
relay.  See the documentation here:
   http://www.spamdyke.org/documentation/README.html#RELAYING

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no 
effect. spamdyke's configuration is set through its 
configuration file(s), not

the environment.

-- Sam Clippinger

Philip Nix Guru wrote:
 

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:
   

Philip wrote:
 
 

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1" 


in tcp.smtp file
or you better add your c-class or any subnet to the 
whitelist_ip file

from spandyke ?

Thx for the info


I don't know of anything like the former. qmail (and thus 
spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if 
this were

available.

I'd look toward the whitelist_ip file. I'm not sure how to 
specify and

IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us 
further. ;)


--
-Eric 'shubes'


- 


 QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]

For additional commands, e-mail:
[EMAIL PROTECTED]


- 


QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]



--

Re: [qmailtoaster] spamdyke and tcpserver

2008-11-04 Thread Sam Clippinger 

I'm not sure if this applies or not but it might solve your problem:
   http://www.spamdyke.org/documentation/FAQ.html#TROUBLE5

-- Sam Clippinger

Philip Nix Guru wrote:

From my testing
adding those 2 lines in spamdyke.conf
local-domains-file=/var/qmail/control/rcpthosts
local-domains-file=/var/qmail/control/morercpthosts

didnt change anything, all is still working fine on this "busy" test 
server


But
adding
access-file=/etc/tcprules.d/tcp.smtp  (using different tcp.smtp files 
for testing purpose)
I dont have any mail parsed through spamassassin anymore, as soon as I 
remove that configuration

it have activity again ...

cant explain yet why :)

Sam Clippinger wrote:
I wouldn't add them unconditionally, because spamdyke will generate 
errors if it can't open a nonexistent file.  What you're doing now is 
probably best.


I'm not very familiar with QMT's admin tools -- how does 
/var/qmail/control/morercpthosts get created in the first place?  
Does one of the admin tools automatically create the file when 
/var/qmail/control/rcpthosts gets too big?


-- Sam Clippinger

Eric Shubert wrote:

Sam Clippinger wrote:
That's probably all that needs to happen.  I don't have a copy of 
the QTP spamdyke configuration file handy, but it should also 
contain "local-domains-file" lines to load 
/var/qmail/control/rcpthosts and /var/qmail/control/morercpthosts 
if spamdyke is going to correctly handle relaying.


The local-domains-file parameter is added by the script for each of 
rcpthosts and morercpthosts, but only when they exist. Would it 
perhaps be better to always add them whether they exist or not?



-- Sam Clippinger

Eric Shubert wrote:

Looks like I missed this one, Philip. Thanks for pointing it out.

From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would 
change in

the run.spamdyke file. I guess the parameter could be added to either
place, but I'm trying to keep the configuration as cohesive as 
possible.


Sam, does this look right to you? If so I'll get in in the next 
QT-Plus

release.

Philip wrote:
 

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus 
should

maybe add the |access-file| option
and use the /etc/tcprules.d/tcp.smtp as parameters in the 
run.spamdyke file
If ppl had local ips or other ips to prevent rbl checking or 
allowing

relaying
it has no effect anymore.

Or those ips should be  under some conditions  added to the 
whitelist_ip

file of spamdyke

-P


Sam Clippinger wrote:
 
spamdyke cannot read CDB files but it can read the /etc/tcp.smtp 
file

(text version) and use some of the values, mostly for controlling
relaying.  For example, if the incoming IP address matches a 
line that

sets the RELAYCLIENT variable, spamdyke will allow the client to
relay.  See the documentation here:
   http://www.spamdyke.org/documentation/README.html#RELAYING

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no 
effect. spamdyke's configuration is set through its 
configuration file(s), not

the environment.

-- Sam Clippinger

Philip Nix Guru wrote:
  

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:


Philip wrote:
 
  

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1" 


in tcp.smtp file
or you better add your c-class or any subnet to the 
whitelist_ip file

from spandyke ?

Thx for the info


I don't know of anything like the former. qmail (and thus 
spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this 
were

available.

I'd look toward the whitelist_ip file. I'm not sure how to 
specify and

IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us 
further. ;)


--
-Eric 'shubes'


- 


 QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]

For additional commands, e-mail:
[EMAIL PROTECTED]


- 


QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]



- 


QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-11-04 Thread Philip Nix Guru 

From my testing
adding those 2 lines in spamdyke.conf
local-domains-file=/var/qmail/control/rcpthosts
local-domains-file=/var/qmail/control/morercpthosts

didnt change anything, all is still working fine on this "busy" test server

But
adding
access-file=/etc/tcprules.d/tcp.smtp  (using different tcp.smtp files 
for testing purpose)
I dont have any mail parsed through spamassassin anymore, as soon as I 
remove that configuration

it have activity again ...

cant explain yet why :)

Sam Clippinger wrote:
I wouldn't add them unconditionally, because spamdyke will generate 
errors if it can't open a nonexistent file.  What you're doing now is 
probably best.


I'm not very familiar with QMT's admin tools -- how does 
/var/qmail/control/morercpthosts get created in the first place?  Does 
one of the admin tools automatically create the file when 
/var/qmail/control/rcpthosts gets too big?


-- Sam Clippinger

Eric Shubert wrote:

Sam Clippinger wrote:
That's probably all that needs to happen.  I don't have a copy of 
the QTP spamdyke configuration file handy, but it should also 
contain "local-domains-file" lines to load 
/var/qmail/control/rcpthosts and /var/qmail/control/morercpthosts if 
spamdyke is going to correctly handle relaying.


The local-domains-file parameter is added by the script for each of 
rcpthosts and morercpthosts, but only when they exist. Would it 
perhaps be better to always add them whether they exist or not?



-- Sam Clippinger

Eric Shubert wrote:

Looks like I missed this one, Philip. Thanks for pointing it out.

From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would 
change in

the run.spamdyke file. I guess the parameter could be added to either
place, but I'm trying to keep the configuration as cohesive as 
possible.


Sam, does this look right to you? If so I'll get in in the next 
QT-Plus

release.

Philip wrote:
 

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus should
maybe add the |access-file| option
and use the /etc/tcprules.d/tcp.smtp as parameters in the 
run.spamdyke file

If ppl had local ips or other ips to prevent rbl checking or allowing
relaying
it has no effect anymore.

Or those ips should be  under some conditions  added to the 
whitelist_ip

file of spamdyke

-P


Sam Clippinger wrote:
 
spamdyke cannot read CDB files but it can read the /etc/tcp.smtp 
file

(text version) and use some of the values, mostly for controlling
relaying.  For example, if the incoming IP address matches a line 
that

sets the RELAYCLIENT variable, spamdyke will allow the client to
relay.  See the documentation here:
   http://www.spamdyke.org/documentation/README.html#RELAYING

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no 
effect. spamdyke's configuration is set through its configuration 
file(s), not

the environment.

-- Sam Clippinger

Philip Nix Guru wrote:
   

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:
 

Philip wrote:
 
   

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1" 


in tcp.smtp file
or you better add your c-class or any subnet to the 
whitelist_ip file

from spandyke ?

Thx for the info


I don't know of anything like the former. qmail (and thus 
spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this 
were

available.

I'd look toward the whitelist_ip file. I'm not sure how to 
specify and

IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us 
further. ;)


--
-Eric 'shubes'


- 


 QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]

For additional commands, e-mail:
[EMAIL PROTECTED]


- 


QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]



- 


QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]



  

-
QmailToaster hosted by: VR Hosted 




--

Re: [qmailtoaster] spamdyke and tcpserver

2008-11-04 Thread Sam Clippinger 
I wouldn't add them unconditionally, because spamdyke will generate 
errors if it can't open a nonexistent file.  What you're doing now is 
probably best.


I'm not very familiar with QMT's admin tools -- how does 
/var/qmail/control/morercpthosts get created in the first place?  Does 
one of the admin tools automatically create the file when 
/var/qmail/control/rcpthosts gets too big?


-- Sam Clippinger

Eric Shubert wrote:

Sam Clippinger wrote:
That's probably all that needs to happen.  I don't have a copy of the 
QTP spamdyke configuration file handy, but it should also contain 
"local-domains-file" lines to load /var/qmail/control/rcpthosts and 
/var/qmail/control/morercpthosts if spamdyke is going to correctly 
handle relaying.


The local-domains-file parameter is added by the script for each of 
rcpthosts and morercpthosts, but only when they exist. Would it 
perhaps be better to always add them whether they exist or not?



-- Sam Clippinger

Eric Shubert wrote:

Looks like I missed this one, Philip. Thanks for pointing it out.

From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would change in
the run.spamdyke file. I guess the parameter could be added to either
place, but I'm trying to keep the configuration as cohesive as 
possible.


Sam, does this look right to you? If so I'll get in in the next QT-Plus
release.

Philip wrote:
 

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus should
maybe add the |access-file| option
and use the /etc/tcprules.d/tcp.smtp as parameters in the 
run.spamdyke file

If ppl had local ips or other ips to prevent rbl checking or allowing
relaying
it has no effect anymore.

Or those ips should be  under some conditions  added to the 
whitelist_ip

file of spamdyke

-P


Sam Clippinger wrote:
  

spamdyke cannot read CDB files but it can read the /etc/tcp.smtp file
(text version) and use some of the values, mostly for controlling
relaying.  For example, if the incoming IP address matches a line 
that

sets the RELAYCLIENT variable, spamdyke will allow the client to
relay.  See the documentation here:
   http://www.spamdyke.org/documentation/README.html#RELAYING

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no 
effect. spamdyke's configuration is set through its configuration 
file(s), not

the environment.

-- Sam Clippinger

Philip Nix Guru wrote:


Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:
  

Philip wrote:
 


Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the 
whitelist_ip file

from spandyke ?

Thx for the info



I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to 
specify and

IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


- 


 QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]

For additional commands, e-mail:
[EMAIL PROTECTED]


- 


QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]



  

-
QmailToaster hosted by: VR Hosted 




-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]


  


-
QmailToaster hosted by: VR Hosted 





-
QmailToaster hosted by: VR Hosted

Re: [qmailtoaster] spamdyke and tcpserver

2008-11-01 Thread Eric Shubert 

Sam Clippinger wrote:
That's probably all that needs to happen.  I don't have a copy of the 
QTP spamdyke configuration file handy, but it should also contain 
"local-domains-file" lines to load /var/qmail/control/rcpthosts and 
/var/qmail/control/morercpthosts if spamdyke is going to correctly 
handle relaying.


The local-domains-file parameter is added by the script for each of 
rcpthosts and morercpthosts, but only when they exist. Would it perhaps 
be better to always add them whether they exist or not?



-- Sam Clippinger

Eric Shubert wrote:

Looks like I missed this one, Philip. Thanks for pointing it out.

From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would change in
the run.spamdyke file. I guess the parameter could be added to either
place, but I'm trying to keep the configuration as cohesive as possible.

Sam, does this look right to you? If so I'll get in in the next QT-Plus
release.

Philip wrote:
 

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus should
maybe add the |access-file| option
and use the /etc/tcprules.d/tcp.smtp as parameters in the 
run.spamdyke file

If ppl had local ips or other ips to prevent rbl checking or allowing
relaying
it has no effect anymore.

Or those ips should be  under some conditions  added to the whitelist_ip
file of spamdyke

-P


Sam Clippinger wrote:
   

spamdyke cannot read CDB files but it can read the /etc/tcp.smtp file
(text version) and use some of the values, mostly for controlling
relaying.  For example, if the incoming IP address matches a line that
sets the RELAYCLIENT variable, spamdyke will allow the client to
relay.  See the documentation here:
   http://www.spamdyke.org/documentation/README.html#RELAYING

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no effect. 
spamdyke's configuration is set through its configuration file(s), not

the environment.

-- Sam Clippinger

Philip Nix Guru wrote:
 

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:
   

Philip wrote:
 
 

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip 
file

from spandyke ?

Thx for the info



I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to specify 
and

IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: 
[EMAIL PROTECTED]

For additional commands, e-mail:
[EMAIL PROTECTED]



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]



  

-
QmailToaster hosted by: VR Hosted 




-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


-
QmailToaster hosted by: VR Hosted 



--
-Eric 'shubes'


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-30 Thread Philip Nix Guru 

I added 2 lines and it seems to eb accpeted
local-domains-file=/var/qmail/control/rcpthosts
local-domains-file=/var/qmail/control/morercpthosts

not that I see much differece. was workign without
but the tcp.smtp file is definatly blocking something

I have a few diff ones
but what is stopping spamassassint to pass email looks like this

127.:allow,RELAYCLIENT="",RBLSMTPD="",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1"
192.168.66.:allow,RELAYCLIENT="",RBLSMTPD="",NOP0FCHECK="1",SENDER_NOCHECK="1"
y.z.a.x:allow,RELAYCLIENT="",RBLSMTPD="",NOP0FCHECK="1",MAXCONNIP="10"
x.y.z.a:allow,RELAYCLIENT="",RBLSMTPD="",SENDER_NOCHECK="1"
2
:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="30",DKVERIFY="DEfhIJK",QMAILQUEUE="/var/qmail/bin/simscan",DKQUEUE="/var/qmail/bin/qmail-queue.orig",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1",MAXCONNIP="5",RBLTIMEOUT="15",SENDER_NOCHECK="1"

If you have an idea ?
Or I ll just put basic things and slowly add the env variables


Philip Nix Guru wrote:
Oh that's bad then coz it definatly doesnt include rcphosts nor 
morercpthosts

Sam how can you add 2 files ?

local-domains-file=/var/qmail/control/rcpthosts then a , a space .. 
/var/qmail/control/morercpthosts ?

in spamdyke.conf


Thx for the info

Sam Clippinger wrote:
That's probably all that needs to happen.  I don't have a copy of the 
QTP spamdyke configuration file handy, but it should also contain 
"local-domains-file" lines to load /var/qmail/control/rcpthosts and 
/var/qmail/control/morercpthosts if spamdyke is going to correctly 
handle relaying.


-- Sam Clippinger

Eric Shubert wrote:

Looks like I missed this one, Philip. Thanks for pointing it out.

From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would change in
the run.spamdyke file. I guess the parameter could be added to either
place, but I'm trying to keep the configuration as cohesive as 
possible.


Sam, does this look right to you? If so I'll get in in the next QT-Plus
release.

Philip wrote:
 

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus should
maybe add the |access-file| option
and use the /etc/tcprules.d/tcp.smtp as parameters in the 
run.spamdyke file

If ppl had local ips or other ips to prevent rbl checking or allowing
relaying
it has no effect anymore.

Or those ips should be  under some conditions  added to the 
whitelist_ip

file of spamdyke

-P


Sam Clippinger wrote:
  

spamdyke cannot read CDB files but it can read the /etc/tcp.smtp file
(text version) and use some of the values, mostly for controlling
relaying.  For example, if the incoming IP address matches a line 
that

sets the RELAYCLIENT variable, spamdyke will allow the client to
relay.  See the documentation here:
   http://www.spamdyke.org/documentation/README.html#RELAYING

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no 
effect. spamdyke's configuration is set through its configuration 
file(s), not

the environment.

-- Sam Clippinger

Philip Nix Guru wrote:


Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:
  

Philip wrote:
 


Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the 
whitelist_ip file

from spandyke ?

Thx for the info



I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to 
specify and

IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


- 


 QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]

For additional commands, e-mail:
[EMAIL PROTECTED]


- 


QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-30 Thread Philip Nix Guru 

spamdyke.conf installed via qtp-plus

#dns-blacklist-entry=zombie.dnsbl.sorbs.net
#dns-blacklist-entry=dul.dnsbl.sorbs.net
#dns-blacklist-entry=bogons.cymru.com
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=bl.spamcop.net
graylist-dir=/var/spamdyke/graylist
graylist-level=always
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=5
idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
local-domains-file=/var/qmail/control/rcpthosts
local-domains-file=/var/qmail/control/morercpthosts
log-level=info
log-target=stderr
max-recipients=50
#policy-url=http://my.policy.explanation.url/
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
reject-empty-rdns
#reject-ip-in-cc-rdns
reject-missing-sender-mx
reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem


Sam Clippinger wrote:
That's probably all that needs to happen.  I don't have a copy of the 
QTP spamdyke configuration file handy, but it should also contain 
"local-domains-file" lines to load /var/qmail/control/rcpthosts and 
/var/qmail/control/morercpthosts if spamdyke is going to correctly 
handle relaying.


-- Sam Clippinger

Eric Shubert wrote:

Looks like I missed this one, Philip. Thanks for pointing it out.

From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would change in
the run.spamdyke file. I guess the parameter could be added to either
place, but I'm trying to keep the configuration as cohesive as possible.

Sam, does this look right to you? If so I'll get in in the next QT-Plus
release.

Philip wrote:
 

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus should
maybe add the |access-file| option
and use the /etc/tcprules.d/tcp.smtp as parameters in the 
run.spamdyke file

If ppl had local ips or other ips to prevent rbl checking or allowing
relaying
it has no effect anymore.

Or those ips should be  under some conditions  added to the 
whitelist_ip

file of spamdyke

-P


Sam Clippinger wrote:
   

spamdyke cannot read CDB files but it can read the /etc/tcp.smtp file
(text version) and use some of the values, mostly for controlling
relaying.  For example, if the incoming IP address matches a line that
sets the RELAYCLIENT variable, spamdyke will allow the client to
relay.  See the documentation here:
   http://www.spamdyke.org/documentation/README.html#RELAYING

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no 
effect. spamdyke's configuration is set through its configuration 
file(s), not

the environment.

-- Sam Clippinger

Philip Nix Guru wrote:
 

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:
   

Philip wrote:
 
 

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip 
file

from spandyke ?

Thx for the info



I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to 
specify and

IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


- 


 QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]

For additional commands, e-mail:
[EMAIL PROTECTED]



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-30 Thread Philip Nix Guru 
Oh that's bad then coz it definatly doesnt include rcphosts nor 
morercpthosts

Sam how can you add 2 files ?

local-domains-file=/var/qmail/control/rcpthosts then a , a space .. 
/var/qmail/control/morercpthosts ?
in spamdyke.conf


Thx for the info

Sam Clippinger wrote:
That's probably all that needs to happen.  I don't have a copy of the 
QTP spamdyke configuration file handy, but it should also contain 
"local-domains-file" lines to load /var/qmail/control/rcpthosts and 
/var/qmail/control/morercpthosts if spamdyke is going to correctly 
handle relaying.


-- Sam Clippinger

Eric Shubert wrote:

Looks like I missed this one, Philip. Thanks for pointing it out.

From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would change in
the run.spamdyke file. I guess the parameter could be added to either
place, but I'm trying to keep the configuration as cohesive as possible.

Sam, does this look right to you? If so I'll get in in the next QT-Plus
release.

Philip wrote:
 

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus should
maybe add the |access-file| option
and use the /etc/tcprules.d/tcp.smtp as parameters in the 
run.spamdyke file

If ppl had local ips or other ips to prevent rbl checking or allowing
relaying
it has no effect anymore.

Or those ips should be  under some conditions  added to the 
whitelist_ip

file of spamdyke

-P


Sam Clippinger wrote:
   

spamdyke cannot read CDB files but it can read the /etc/tcp.smtp file
(text version) and use some of the values, mostly for controlling
relaying.  For example, if the incoming IP address matches a line that
sets the RELAYCLIENT variable, spamdyke will allow the client to
relay.  See the documentation here:
   http://www.spamdyke.org/documentation/README.html#RELAYING

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no 
effect. spamdyke's configuration is set through its configuration 
file(s), not

the environment.

-- Sam Clippinger

Philip Nix Guru wrote:
 

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:
   

Philip wrote:
 
 

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip 
file

from spandyke ?

Thx for the info



I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to 
specify and

IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


- 


 QmailToaster hosted by: VR Hosted 
- 

To unsubscribe, e-mail: 
[EMAIL PROTECTED]

For additional commands, e-mail:
[EMAIL PROTECTED]



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: 
[EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]



  

-
QmailToaster hosted by: VR Hosted 




-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-30 Thread Sam Clippinger 
That's probably all that needs to happen.  I don't have a copy of the 
QTP spamdyke configuration file handy, but it should also contain 
"local-domains-file" lines to load /var/qmail/control/rcpthosts and 
/var/qmail/control/morercpthosts if spamdyke is going to correctly 
handle relaying.


-- Sam Clippinger

Eric Shubert wrote:

Looks like I missed this one, Philip. Thanks for pointing it out.

From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would change in
the run.spamdyke file. I guess the parameter could be added to either
place, but I'm trying to keep the configuration as cohesive as possible.

Sam, does this look right to you? If so I'll get in in the next QT-Plus
release.

Philip wrote:
  

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus should
maybe add the |access-file| option
and use the /etc/tcprules.d/tcp.smtp as parameters in the run.spamdyke file
If ppl had local ips or other ips to prevent rbl checking or allowing
relaying
it has no effect anymore.

Or those ips should be  under some conditions  added to the whitelist_ip
file of spamdyke

-P


Sam Clippinger wrote:


spamdyke cannot read CDB files but it can read the /etc/tcp.smtp file
(text version) and use some of the values, mostly for controlling
relaying.  For example, if the incoming IP address matches a line that
sets the RELAYCLIENT variable, spamdyke will allow the client to
relay.  See the documentation here:
   http://www.spamdyke.org/documentation/README.html#RELAYING

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no effect. 
spamdyke's configuration is set through its configuration file(s), not

the environment.

-- Sam Clippinger

Philip Nix Guru wrote:
  

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:


Philip wrote:
 
  

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip file
from spandyke ?

Thx for the info




I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to specify and
IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]

  
  

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
QmailToaster hosted by: VR Hosted 




-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-30 Thread Philip Nix Guru 

Hi Eric
just wait a bit I ll check a few things this weekend
coz when I added it, suddenly nothing went through spamassassin anymore
dont have much time today to figure out what line triggered it
so stay tuned :)


Eric Shubert wrote:

Looks like I missed this one, Philip. Thanks for pointing it out.

From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would change in
the run.spamdyke file. I guess the parameter could be added to either
place, but I'm trying to keep the configuration as cohesive as possible.

Sam, does this look right to you? If so I'll get in in the next QT-Plus
release.

Philip wrote:
  

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus should
maybe add the |access-file| option
and use the /etc/tcprules.d/tcp.smtp as parameters in the run.spamdyke file
If ppl had local ips or other ips to prevent rbl checking or allowing
relaying
it has no effect anymore.

Or those ips should be  under some conditions  added to the whitelist_ip
file of spamdyke

-P


Sam Clippinger wrote:


spamdyke cannot read CDB files but it can read the /etc/tcp.smtp file
(text version) and use some of the values, mostly for controlling
relaying.  For example, if the incoming IP address matches a line that
sets the RELAYCLIENT variable, spamdyke will allow the client to
relay.  See the documentation here:
   http://www.spamdyke.org/documentation/README.html#RELAYING

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no effect. 
spamdyke's configuration is set through its configuration file(s), not

the environment.

-- Sam Clippinger

Philip Nix Guru wrote:
  

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:


Philip wrote:
 
  

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip file
from spandyke ?

Thx for the info




I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to specify and
IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]

  
  

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
QmailToaster hosted by: VR Hosted 




-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-30 Thread Eric Shubert 
Looks like I missed this one, Philip. Thanks for pointing it out.

>From what I'm seeing, I simply need to add:
access-file=/etc/tcprules.d/tcp.smtp
to the configuration file. I'm not seeing anything that would change in
the run.spamdyke file. I guess the parameter could be added to either
place, but I'm trying to keep the configuration as cohesive as possible.

Sam, does this look right to you? If so I'll get in in the next QT-Plus
release.

Philip wrote:
> Thx Sam for clearing up a few things
> 
> In that case the spamdyke installation script used by qtp-plus should
> maybe add the |access-file| option
> and use the /etc/tcprules.d/tcp.smtp as parameters in the run.spamdyke file
> If ppl had local ips or other ips to prevent rbl checking or allowing
> relaying
> it has no effect anymore.
> 
> Or those ips should be  under some conditions  added to the whitelist_ip
> file of spamdyke
> 
> -P
> 
> 
> Sam Clippinger wrote:
>> spamdyke cannot read CDB files but it can read the /etc/tcp.smtp file
>> (text version) and use some of the values, mostly for controlling
>> relaying.  For example, if the incoming IP address matches a line that
>> sets the RELAYCLIENT variable, spamdyke will allow the client to
>> relay.  See the documentation here:
>>http://www.spamdyke.org/documentation/README.html#RELAYING
>>
>> However, setting a SPAMDYKE variable in /etc/tcp.smtp has no effect. 
>> spamdyke's configuration is set through its configuration file(s), not
>> the environment.
>>
>> -- Sam Clippinger
>>
>> Philip Nix Guru wrote:
>>> Heheh
>>> Yes I am using the
>>>
>>> whitelist_ip file
>>>
>>> you can either enter x.y.z or x.y.z. for a c-class
>>> I was just curious about the tcp.smtp file :)
>>> I know that spamdyke cant use cdb files
>>>
>>> -P
>>>
>>>
>>> Eric Shubert wrote:
 Philip wrote:
  
> Hello
> I was wondering about how to disable spamdyke by ip range
> can we do something like :
>
> 1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
> in tcp.smtp file
> or you better add your c-class or any subnet to the whitelist_ip file
> from spandyke ?
>
> Thx for the info
>
> 

 I don't know of anything like the former. qmail (and thus spamdyke)
 doesn't necessarily use tcpserver, so I'd be surprised if this were
 available.

 I'd look toward the whitelist_ip file. I'm not sure how to specify and
 IP range there though. Check the documentation.

 I'm expect that Sam will chime in here and enlighten us further. ;)

 -- 
 -Eric 'shubes'


 -
  QmailToaster hosted by: VR Hosted 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail:
 [EMAIL PROTECTED]

   
>>>
>>> -
>>> QmailToaster hosted by: VR Hosted 
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>
>> -
>> QmailToaster hosted by: VR Hosted 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> -
> QmailToaster hosted by: VR Hosted 


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-30 Thread Philip 

Thx Sam for clearing up a few things

In that case the spamdyke installation script used by qtp-plus should 
maybe add the |access-file| option

and use the /etc/tcprules.d/tcp.smtp as parameters in the run.spamdyke file
If ppl had local ips or other ips to prevent rbl checking or allowing 
relaying

it has no effect anymore.

Or those ips should be  under some conditions  added to the whitelist_ip 
file of spamdyke


-P


Sam Clippinger wrote:
spamdyke cannot read CDB files but it can read the /etc/tcp.smtp file 
(text version) and use some of the values, mostly for controlling 
relaying.  For example, if the incoming IP address matches a line that 
sets the RELAYCLIENT variable, spamdyke will allow the client to 
relay.  See the documentation here:

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

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no effect.  
spamdyke's configuration is set through its configuration file(s), not 
the environment.


-- Sam Clippinger

Philip Nix Guru wrote:

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:

Philip wrote:
 

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip file
from spandyke ?

Thx for the info




I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to specify and
IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: 
[EMAIL PROTECTED]


  


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-30 Thread Sam Clippinger 
spamdyke cannot read CDB files but it can read the /etc/tcp.smtp file 
(text version) and use some of the values, mostly for controlling 
relaying.  For example, if the incoming IP address matches a line that 
sets the RELAYCLIENT variable, spamdyke will allow the client to relay.  
See the documentation here:

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

However, setting a SPAMDYKE variable in /etc/tcp.smtp has no effect.  
spamdyke's configuration is set through its configuration file(s), not 
the environment.


-- Sam Clippinger

Philip Nix Guru wrote:

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:

Philip wrote:
 

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip file
from spandyke ?

Thx for the info




I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to specify and
IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-29 Thread Dan McAllister 
You would want to use the tcprules.d folder only if you were trying to 
alter the "general" processing of inbound messages. As it appears you're 
trying to limit only the spamdyke functions, I suggest you look in the 
spamdyke config folder (its location is configurable -- I put mine in 
/var/qmail/control/spamdyke). Within that folder, create a whitelist_ip 
file. Messages received from those IP addresses will be skipped by 
spamdyke (e.g. they'll ALWAYS pass).


I hope this helps...

Dan

"When did you do your last backup?"

Ask me about unattended offsite backup solutions...
to protect your business, not just your data!



Philip Nix Guru wrote:

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:

Philip wrote:
 

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip file
from spandyke ?

Thx for the info




I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to specify and
IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-29 Thread Philip Nix Guru 

Heheh
Yes I am using the

whitelist_ip file

you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files

-P


Eric Shubert wrote:

Philip wrote:
  

Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :

1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip file
from spandyke ?

Thx for the info




I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to specify and
IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] spamdyke and tcpserver

2008-10-29 Thread Eric Shubert 
Philip wrote:
> Hello
> I was wondering about how to disable spamdyke by ip range
> can we do something like :
> 
> 1.2.3.:allow,RELAYCLIENT="",RBLSMTPD="",SPAMDYKE="",NOP0FCHECK="1"
> in tcp.smtp file
> or you better add your c-class or any subnet to the whitelist_ip file
> from spandyke ?
> 
> Thx for the info
> 

I don't know of anything like the former. qmail (and thus spamdyke)
doesn't necessarily use tcpserver, so I'd be surprised if this were
available.

I'd look toward the whitelist_ip file. I'm not sure how to specify and
IP range there though. Check the documentation.

I'm expect that Sam will chime in here and enlighten us further. ;)

--
-Eric 'shubes'


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]