[qmailtoaster] Enabling TLS for send

[Vincent Deschênes]

We need to enable TLS for sending mail to servers supporting TLS.

I think that TLS is supported for receiving by the default toaster install but 
not for sending.

Am I right ?

 

Then, could some one point me to a procedure to enable TLS for send.

 

Thanks !

 

 

Vincent Deschenes

 

RE: [qmailtoaster] Enabling TLS for send

[Vincent Deschênes]

This is strange I sent thei mail only once and received it 3 time from the list.

 

Anyway, I think I have found my problem. I am using ASSP and I realized that I 
do not get the same response to ehlo if I pass by
ASSP

 

Port 25 (ASSP) I get :

 

220 mail.qa.shipdecisionmail.com - Welcome to Qmail Toaster Ver. 1.3 SMTP 
Server ESMTP 
ehlo 
250-mail.qa.shipdecisionmail.com - Welcome to Qmail Toaster Ver. 1.3 SMTP 
Server 
250-8BITMIME 
250-SIZE 80971520 
250 AUTH LOGIN PLAIN CRAM-MD5 
quit

221 Closing connection. Good bye.

 

 

Port 125 (direct to qmail) I get:

 

220 mail.qa.shipdecisionmail.com - Welcome to Qmail Toaster Ver. 1.3 SMTP 
Server ESMTP 
ehlo 
250-mail.qa.shipdecisionmail.com - Welcome to Qmail Toaster Ver. 1.3 SMTP 
Server 
250-STARTTLS 
250-PIPELINING 
250-8BITMIME 
250-SIZE 80971520 
250 AUTH LOGIN PLAIN CRAM-MD5

quit

221 Closing connection. Good bye.

 

 

VD

 

From: Vincent Deschênes [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 04, 2008 10:38 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] Enabling TLS for send

 

We need to enable TLS for sending mail to servers supporting TLS.

I think that TLS is supported for receiving by the default toaster install but 
not for sending.

Am I right ?

 

Then, could some one point me to a procedure to enable TLS for send.

 

Thanks !

 

 

Vincent Deschenes

 

Re: [qmailtoaster] spamdyke smtp logging bugs

[Eric Shubert]

Philip Nix Guru wrote:

Hello
I was playing with a spamdyke-stats.pl script I saw, trying to update it 
to work with the qtoaster setup

and I was getting some strange results .. so I checked the logs
and found that that I had a few spamdyke[###]:spamdyke[] in my smtp 
log file


example : (I converted TAI64N timestamps for better readings)

2008-11-03 23:51:28.405450500 spamdyke[26362]: DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.446391500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] to: 
[EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: 
(unknown)DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.488134500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] to: 
[EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: 
(unknown)DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.536631500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] to: 
[EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)


It seems to happen when you have multiple emails reaching different 
users on the same domain




That appears to be odd all right. I scanned my logs and couldn't find 
such a thing (what appears to be a spamdyke within a spamdyke), fwiw. 
It'll be interesting to see what Sam has to say about this.


--
-Eric 'shubes'


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

Re: [qmailtoaster] Email lost from one outside domain after qmail-scan

[Eric Shubert]

Thomas M. Jaeger wrote:
Sorry Eric (Shubert).  Your response must have gotten filtered by that 
“wonderful” MS Outlook 2003 Junk filter then absent mindedly deleted by me…


I actually discovered my answer not too long after emailing the list.  
It had all to do with the SPF filter.  The email was coming from a 
legitimate company domain (and person) but SPF is not finding it to be 
valid.  I had to change the /var/qmail/control/spfbehavior from 3 to 0 
(could have used 1 or 2 but, to me, off is off…).  It was set when I 
re-built the server; either I selected the suggested “#” or it set 3 at 
default… dunno.  Sorry for any hassle.


Thank you, again, for all that you are doing!

Thomas M. Jaeger
Computer Technician, A.A.S.
[EMAIL PROTECTED]
[EMAIL PROTECTED]



NP Thomas. FWIW, I'm running with spfbehavior  "1". The wiki indicates 
that "3" is the default toaster value. It'd be nice if someone came up 
with a fix that made the toaster's SPF processing work correctly. :(


--
-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

[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 smtp logging bugs

[Sam Clippinger]

It looks like spamdyke is being run multiple times for each connection 
-- the two spamdyke PIDs in the logs are different.  What does your 
"run" file look like?


I have no idea where the asterisks came from.  Did you insert those 
manually to highlight the duplicated text?


-- Sam Clippinger

Philip Nix Guru wrote:

Hello
I was playing with a spamdyke-stats.pl script I saw, trying to update 
it to work with the qtoaster setup

and I was getting some strange results .. so I checked the logs
and found that that I had a few spamdyke[###]:spamdyke[] in my 
smtp log file


example : (I converted TAI64N timestamps for better readings)

2008-11-03 23:51:28.405450500 spamdyke[26362]: DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.446391500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] to: 
[EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: 
(unknown)DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.488134500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] to: 
[EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: 
(unknown)DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.536631500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] 
to: [EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)


It seems to happen when you have multiple emails reaching different 
users on the same domain





-
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] Enabling TLS for send

[Eric Shubert]

Yeah, looks like ASSP isn't handling TLS.

AFAIK, the stock toaster by default uses TLS for sending if the receiver 
allows it, and allows for TLS if the sender requests it (I don't think 
that a receiving server can initiate TLS, but I could be wrong on that).


I'd be interested to know if ASSP does any better handling spam than the 
stock toaster with spamdyke installed. My guess is that you wouldn't see 
a noticeable improvement. Configuration might be a bit easier though if 
you had some elaborate requirements. Of course, I could be wrong (again!).


Please keep us posted regarding your ASSP experiences.

Vincent Deschênes wrote:
This is strange I sent thei mail only once and received it 3 time from 
the list.


Anyway, I think I have found my problem. I am using ASSP and I realized 
that I do not get the same response to ehlo if I pass by ASSP


Port 25 (ASSP) I get :

220 mail.qa.shipdecisionmail.com - Welcome to Qmail Toaster Ver. 1.3 
SMTP Server ESMTP

ehlo
250-mail.qa.shipdecisionmail.com - Welcome to Qmail Toaster Ver. 1.3 
SMTP Server

250-8BITMIME
250-SIZE 80971520
250 AUTH LOGIN PLAIN CRAM-MD5
quit

221 Closing connection. Good bye.

Port 125 (direct to qmail) I get:

220 mail.qa.shipdecisionmail.com - Welcome to Qmail Toaster Ver. 1.3 
SMTP Server ESMTP

ehlo
250-mail.qa.shipdecisionmail.com - Welcome to Qmail Toaster Ver. 1.3 
SMTP Server

250-STARTTLS
250-PIPELINING
250-8BITMIME
250-SIZE 80971520
250 AUTH LOGIN PLAIN CRAM-MD5

quit

221 Closing connection. Good bye.

 

 


VD

 


*From:* Vincent Deschênes [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, November 04, 2008 10:38 AM
*To:* qmailtoaster-list@qmailtoaster.com
*Subject:* [qmailtoaster] Enabling TLS for send

 


We need to enable TLS for sending mail to servers supporting TLS.

I think that TLS is supported for receiving by the default toaster 
install but not for sending.


Am I right ?

 


Then, could some one point me to a procedure to enable TLS for send.

 


Thanks !

 

 


Vincent Deschenes

 




--
-Eric 'shubes'


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

Re: [qmailtoaster] spamdyke smtp logging bugs

[Philip Nix Guru]

Yes the * were added  manually
sorry for the confusion

# cat /var/qmail/supervise/smtp/run
#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SPAMDYKE="/usr/local/bin/spamdyke"
SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
REQUIRE_AUTH=0

exec /usr/bin/softlimit -m 1200 \
/usr/bin/tcpserver -v -R -h -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
-u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
$SPAMDYKE --config-file $SPAMDYKE_CONF \
$SMTPD $VCHKPW /bin/true 2>&1

-P

Sam Clippinger wrote:
It looks like spamdyke is being run multiple times for each connection 
-- the two spamdyke PIDs in the logs are different.  What does your 
"run" file look like?


I have no idea where the asterisks came from.  Did you insert those 
manually to highlight the duplicated text?


-- Sam Clippinger

Philip Nix Guru wrote:

Hello
I was playing with a spamdyke-stats.pl script I saw, trying to update 
it to work with the qtoaster setup

and I was getting some strange results .. so I checked the logs
and found that that I had a few spamdyke[###]:spamdyke[] in my 
smtp log file


example : (I converted TAI64N timestamps for better readings)

2008-11-03 23:51:28.405450500 spamdyke[26362]: DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.446391500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] to: 
[EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: 
(unknown)DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.488134500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] to: 
[EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: 
(unknown)DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.536631500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] 
to: [EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)


It seems to happen when you have multiple emails reaching different 
users on the same domain





-
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

[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 




--

[qmailtoaster] script clean

[Ariel]

Hola lista , necesito correr el siguiente comando en un qmail. que esta
lleno de correos muy viejos, la idea es que elimine de todos los dominios
correos mayores a 180 dias.
No se cual sera el problema pero , al correr este script me dice que la
lista es demasioado larga.



find /home/vpopmail/domains/*/*/Maildir/new/* -type f -mtime +180 -print
-exec rm -f /home/vpopmail/domains/*/*/Maildir/new/* {} \$


esta bien la sintaxis ?

Re: [qmailtoaster] spamdyke and tcpserver

[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

[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 smtp logging bugs

[Sam Clippinger]

I don't see anything obviously wrong with your "run" file, but it 
certainly looks like two spamdyke log lines are overlapping for some reason.


After going through some source code, I see this is a problem with the 
basic design of DJB's multilog program.  When spamdyke prints logging 
output to stderr, it actually uses three function calls to do it.  The 
first prints "spamdyke[PID]:", the second prints the rest of the log 
text and the third prints a newline character.  If two different 
spamdyke processes print messages at the same time, those three calls 
can become intermixed (a classic race condition).  Because multilog only 
uses one pipe for input, it can't separate input from two different 
processes to keep the messages intact.  It just prints what it sees 
which, in this case, is garbage.


I'll update spamdyke to print its log messages using a single function 
call; that should work around this problem.  This is just one more 
reason not to use multilog, I guess.


Thanks for reporting this!

-- Sam Clippinger

Philip Nix Guru wrote:

Yes the * were added  manually
sorry for the confusion

# cat /var/qmail/supervise/smtp/run
#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SPAMDYKE="/usr/local/bin/spamdyke"
SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
REQUIRE_AUTH=0

exec /usr/bin/softlimit -m 1200 \
/usr/bin/tcpserver -v -R -h -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
-u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
$SPAMDYKE --config-file $SPAMDYKE_CONF \
$SMTPD $VCHKPW /bin/true 2>&1

-P

Sam Clippinger wrote:
It looks like spamdyke is being run multiple times for each 
connection -- the two spamdyke PIDs in the logs are different.  What 
does your "run" file look like?


I have no idea where the asterisks came from.  Did you insert those 
manually to highlight the duplicated text?


-- Sam Clippinger

Philip Nix Guru wrote:

Hello
I was playing with a spamdyke-stats.pl script I saw, trying to 
update it to work with the qtoaster setup

and I was getting some strange results .. so I checked the logs
and found that that I had a few spamdyke[###]:spamdyke[] in my 
smtp log file


example : (I converted TAI64N timestamps for better readings)

2008-11-03 23:51:28.405450500 spamdyke[26362]: DENIED_RBL_MATCH 
from: [EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.446391500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] to: 
[EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: 
(unknown)DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.488134500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] to: 
[EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: 
(unknown)DENIED_RBL_MATCH from: 
[EMAIL PROTECTED] to: [EMAIL PROTECTED] 
origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)
2008-11-03 23:51:28.536631500 *spamdyke[26365]: spamdyke[26362]*: 
DENIED_RBL_MATCH from: [EMAIL PROTECTED] 
to: [EMAIL PROTECTED] origin_ip: 86.2.231.197 origin_rdns: 
cpc2-hudd10-0-0-cust964.hudd.cable.ntl.com auth: (unknown)


It seems to happen when you have multiple emails reaching different 
users on the same domain





-
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]

[qmailtoaster] 5.5.3 chkuser rcpthosts

[Josh Hopkins]

I just started to get this today on one of my domains.  I have about 12
domains listed in the rcpthosts file.  They all worked until yesterday.
I looked though the smtp logs and could not find the test message below.
I am not sure what to look at.  Thanks,
-Josh

 


This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

[EMAIL PROTECTED]

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the
recipient domain. We recommend contacting the other email provider for
further information about the cause of this error. The error that the
other server returned was: 553 553 sorry, that domain isn't in my list
of allowed rcpthosts (#5.5.3 - chkuser) (state 14).

  - Original message -

Received: by 10.181.57.7 with SMTP id j7mr46717bkk.77.1225839200062;
   Tue, 04 Nov 2008 14:53:20 -0800 (PST)
Received: by 10.181.33.1 with HTTP; Tue, 4 Nov 2008 14:53:20 -0800 (PST)
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 4 Nov 2008 15:53:20 -0700
From: "Josh Hopkins" <[EMAIL PROTECTED]>
To: "Josh Hopkins" <[EMAIL PROTECTED]>
Subject: testing for qmail
MIME-Version: 1.0
Content-Type: multipart/alternative;
   boundary="=_Part_101899_7606574.1225839200047"

--=_Part_101899_7606574.1225839200047
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

this is qmail testing

--=_Part_101899_7606574.1225839200047
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

  - Message truncated -

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

Re: [qmailtoaster] 5.5.3 chkuser rcpthosts

[Eric Shubert]

Is gmail possibly connecting to some other server? Check DNS MX 
record(s), routing.


Josh Hopkins wrote:

I just started to get this today on one of my domains.  I have about 12
domains listed in the rcpthosts file.  They all worked until yesterday.
I looked though the smtp logs and could not find the test message below.
I am not sure what to look at.  Thanks,
-Josh

 



This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

[EMAIL PROTECTED]

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the
recipient domain. We recommend contacting the other email provider for
further information about the cause of this error. The error that the
other server returned was: 553 553 sorry, that domain isn't in my list
of allowed rcpthosts (#5.5.3 - chkuser) (state 14).

  - Original message -

Received: by 10.181.57.7 with SMTP id j7mr46717bkk.77.1225839200062;
   Tue, 04 Nov 2008 14:53:20 -0800 (PST)
Received: by 10.181.33.1 with HTTP; Tue, 4 Nov 2008 14:53:20 -0800 (PST)
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 4 Nov 2008 15:53:20 -0700
From: "Josh Hopkins" <[EMAIL PROTECTED]>
To: "Josh Hopkins" <[EMAIL PROTECTED]>
Subject: testing for qmail
MIME-Version: 1.0
Content-Type: multipart/alternative;
   boundary="=_Part_101899_7606574.1225839200047"

--=_Part_101899_7606574.1225839200047
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

this is qmail testing

--=_Part_101899_7606574.1225839200047
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

  - Message truncated -

-
 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]

[qmailtoaster] SpamAssassin whitelist_from is bypassed sometime

[Kaven Gagnon]

Hi,

I got email addresses listed in whitelist_from still rejected as spam.
This is like a intermittent problem...

The spam reject do not come from blocking lists.

Any idea?

Thanks,
Kaven G.


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