Re: [qmailtoaster] spamdyke and tcpserver
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 http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] spamdyke and tcpserver
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 http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] spamdyke and tcpserver
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 http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[qmailtoaster] Authenticate over 587
Hi I need authenticate over 587 ports, because using this port I cant send outgoing mails to another domains only the internal, How Do That? Example Error Your message did not reach some or all of the intended recipients. Subject:test Sent: 30/10/2008 10:36 a.m. The following recipient(s) cannot be reached: '[EMAIL PROTECTED]' on 30/10/2008 10:36 a.m. 511 sorry, can't find a valid MX for rcpt domain (#5.1.1 - chkuser) Este correo electronico puede conteneder informacion confindencial y protegida legalmente bajo secreto profesional. La informacion esta dirigida solamente a la persona o entidad indicada como destinatario y su acceso por cualquier otra persona no esta autorizado. si ud recibio este mensaje electronico por error, informeselo al remitente y borrelo. Aclaramos que los conceptos y opiniones comprendidos en este correo electronico, deben atribuirse exclusivamente a su auntor y no deben entenderse como necesariamente coincidentes con las de AIMAR, S.A. y en consecuencia, absolutamente ajenos a la responsabilidad de sus directores y ejecutivos. en tanto no hayan participado de su confension y/o emision y quede esta participacion expresamente consignada en el mensaje La divulgacion publica de este correo electronico, como asi su copia, reproduccion total o parcial queda prohibida, dando lugar en caso de inobservancia de estas y todas las acciones legales que pudiesen corresponder.
[qmailtoaster] ERROR URGENT
I cant receive email everything say CHKUSER rejected sender: from [EMAIL PROTECTED]:: remote rcpt : invalid sender MX domain Este correo electronico puede conteneder informacion confindencial y protegida legalmente bajo secreto profesional. La informacion esta dirigida solamente a la persona o entidad indicada como destinatario y su acceso por cualquier otra persona no esta autorizado. si ud recibio este mensaje electronico por error, informeselo al remitente y borrelo. Aclaramos que los conceptos y opiniones comprendidos en este correo electronico, deben atribuirse exclusivamente a su auntor y no deben entenderse como necesariamente coincidentes con las de AIMAR, S.A. y en consecuencia, absolutamente ajenos a la responsabilidad de sus directores y ejecutivos. en tanto no hayan participado de su confension y/o emision y quede esta participacion expresamente consignada en el mensaje La divulgacion publica de este correo electronico, como asi su copia, reproduccion total o parcial queda prohibida, dando lugar en caso de inobservancia de estas y todas las acciones legales que pudiesen corresponder.
Re: [qmailtoaster] ERROR URGENT
Robin W. Sanchez C. wrote: I cant receive email everything say CHKUSER rejected sender: from [EMAIL PROTECTED]:: remote rcpt : invalid sender MX domain You have a DNS problem. The QMT server cannot lookup domain names in DNS, and/or your records are incorrect.
[qmailtoaster] FW: Email Senting Problems
From: Robin W. Sanchez C. [mailto:[EMAIL PROTECTED] Sent: jueves, 30 de octubre de 2008 01:06 p.m. To: 'qmailtoaster-list@qmailtoaster.com' Subject: Email Senting Problems All outgoing emails that i send using smtp port 587 cant be delivery Show this error Your message did not reach some or all of the intended recipients. Subject:test Sent: 30/10/2008 10:36 a.m. The following recipient(s) cannot be reached: '[EMAIL PROTECTED]' on 30/10/2008 10:36 a.m. 511 sorry, can't find a valid MX for rcpt domain (#5.1.1 - chkuser) Este correo electronico puede conteneder informacion confindencial y protegida legalmente bajo secreto profesional. La informacion esta dirigida solamente a la persona o entidad indicada como destinatario y su acceso por cualquier otra persona no esta autorizado. si ud recibio este mensaje electronico por error, informeselo al remitente y borrelo. Aclaramos que los conceptos y opiniones comprendidos en este correo electronico, deben atribuirse exclusivamente a su auntor y no deben entenderse como necesariamente coincidentes con las de AIMAR, S.A. y en consecuencia, absolutamente ajenos a la responsabilidad de sus directores y ejecutivos. en tanto no hayan participado de su confension y/o emision y quede esta participacion expresamente consignada en el mensaje La divulgacion publica de este correo electronico, como asi su copia, reproduccion total o parcial queda prohibida, dando lugar en caso de inobservancia de estas y todas las acciones legales que pudiesen corresponder.
Re: [qmailtoaster] FW: Email Senting Problems
Robin -- As Jake mentioned in response to one of your other messages, this appears to be a DNS problem. I'd suggest checking - using dig, etc. - the DNS server(s) for your toaster mail server. Firewall may also be an issue. On Oct 30, 2008, at 03:09 PM, Robin W. Sanchez C. wrote: From: Robin W. Sanchez C. [mailto:[EMAIL PROTECTED] Sent: jueves, 30 de octubre de 2008 01:06 p.m. To: 'qmailtoaster-list@qmailtoaster.com' Subject: Email Senting Problems All outgoing emails that i send using smtp port 587 cant be delivery Show this error Your message did not reach some or all of the intended recipients. Subject:test Sent: 30/10/2008 10:36 a.m. The following recipient(s) cannot be reached: '[EMAIL PROTECTED]' on 30/10/2008 10:36 a.m. 511 sorry, can't find a valid MX for rcpt domain (#5.1.1 - chkuser) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] spamdyke and tcpserver
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 http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] FW: Email Senting Problems
Ok thnas, but exists any option to disable this MX validation into the QMT, only for make test because my domains look well Regards -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: jueves, 30 de octubre de 2008 01:35 p.m. To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] FW: Email Senting Problems Robin -- As Jake mentioned in response to one of your other messages, this appears to be a DNS problem. I'd suggest checking - using dig, etc. - the DNS server(s) for your toaster mail server. Firewall may also be an issue. On Oct 30, 2008, at 03:09 PM, Robin W. Sanchez C. wrote: From: Robin W. Sanchez C. [mailto:[EMAIL PROTECTED] Sent: jueves, 30 de octubre de 2008 01:06 p.m. To: 'qmailtoaster-list@qmailtoaster.com' Subject: Email Senting Problems All outgoing emails that i send using smtp port 587 cant be delivery Show this error Your message did not reach some or all of the intended recipients. Subject:test Sent: 30/10/2008 10:36 a.m. The following recipient(s) cannot be reached: '[EMAIL PROTECTED]' on 30/10/2008 10:36 a.m. 511 sorry, can't find a valid MX for rcpt domain (#5.1.1 - chkuser) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Este correo electronico puede conteneder informacion confindencial y protegida legalmente bajo secreto profesional. La informacion esta dirigida solamente a la persona o entidad indicada como destinatario y su acceso por cualquier otra persona no esta autorizado. si ud recibio este mensaje electronico por error, informeselo al remitente y borrelo. Aclaramos que los conceptos y opiniones comprendidos en este correo electronico, deben atribuirse exclusivamente a su auntor y no deben entenderse como necesariamente coincidentes con las de AIMAR, S.A. y en consecuencia, absolutamente ajenos a la responsabilidad de sus directores y ejecutivos. en tanto no hayan participado de su confension y/o emision y quede esta participacion expresamente consignada en el mensaje La divulgacion publica de este correo electronico, como asi su copia, reproduccion total o parcial queda prohibida, dando lugar en caso de inobservancia de estas y todas las acciones legales que pudiesen corresponder. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] FW: Email Senting Problems
this is a quote fron the list: rpm -Uvh qmail-toaster*.src.rpm cd /usr/src/redhat/SPECS (assuming you are using CentOS 4) edit qmail-toaster.spec find 'sleep 5' (should be line 606) change 5 to 300 (5 seconds to 300 seconds) rpmbuild -bb --with cnt40 qmail-toaster.spec When the build process pauses, make your changes. You have 5 minutes. edit /usr/src/redhat/BUILD/qmail-1.03/chkuser_settings.h as you wish something like this /* #define CHKUSER_RCPT_MX */ /* #define CHKUSER_RCPT_MX */ Save your changes and wait for the 300 seconds to expire and watch it build. cd ../RPMS/i386/ qmailctl stop rpm -Uvh --replacefiles --replacepkgs qmail-*.rpm qmailctl start Robin W. Sanchez C. wrote: Ok thnas, but exists any option to disable this MX validation into the QMT, only for make test because my domains look well Regards -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: jueves, 30 de octubre de 2008 01:35 p.m. To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] FW: Email Senting Problems Robin -- As Jake mentioned in response to one of your other messages, this appears to be a DNS problem. I'd suggest checking - using dig, etc. - the DNS server(s) for your toaster mail server. Firewall may also be an issue. On Oct 30, 2008, at 03:09 PM, Robin W. Sanchez C. wrote: From: Robin W. Sanchez C. [mailto:[EMAIL PROTECTED] Sent: jueves, 30 de octubre de 2008 01:06 p.m. To: 'qmailtoaster-list@qmailtoaster.com' Subject: Email Senting Problems All outgoing emails that i send using smtp port 587 cant be delivery Show this error Your message did not reach some or all of the intended recipients. Subject:test Sent: 30/10/2008 10:36 a.m. The following recipient(s) cannot be reached: '[EMAIL PROTECTED]' on 30/10/2008 10:36 a.m. 511 sorry, can't find a valid MX for rcpt domain (#5.1.1 - chkuser) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Este correo electronico puede conteneder informacion confindencial y protegida legalmente bajo secreto profesional. La informacion esta dirigida solamente a la persona o entidad indicada como destinatario y su acceso por cualquier otra persona no esta autorizado. si ud recibio este mensaje electronico por error, informeselo al remitente y borrelo. Aclaramos que los conceptos y opiniones comprendidos en este correo electronico, deben atribuirse exclusivamente a su auntor y no deben entenderse como necesariamente coincidentes con las de AIMAR, S.A. y en consecuencia, absolutamente ajenos a la responsabilidad de sus directores y ejecutivos. en tanto no hayan participado de su confension y/o emision y quede esta participacion expresamente consignada en el mensaje La divulgacion publica de este correo electronico, como asi su copia, reproduccion total o parcial queda prohibida, dando lugar en caso de inobservancia de estas y todas las acciones legales que pudiesen corresponder. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] spamdyke and tcpserver
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 http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] spamdyke and tcpserver
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 http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] spamdyke and tcpserver
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 http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] spamdyke and tcpserver
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 http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] FW: Email Senting Problems
Robin W. Sanchez C. wrote: Ok thnas, but exists any option to disable this MX validation into the QMT, only for make test because my domains look well Not be be condescending, but you don't expect a mail server to work with broken DNS do you? - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] FW: Email Senting Problems
No I dont I only try to make several test, tryng to determine how is working it, because my DNS appearly looks well but I don't understand what is the specific reason of that warning 4000490a58ef0ad06114 CHKUSER rejected rcpt: from [EMAIL PROTECTED]:[EMAIL PROTECTED]: remote soporte1:unknown:xxx... rcpt [EMAIL PROTECTED] : invalid rcpt MX domain -Original Message- From: Jake Vickers [mailto:[EMAIL PROTECTED] Sent: jueves, 30 de octubre de 2008 05:11 p.m. To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] FW: Email Senting Problems Robin W. Sanchez C. wrote: Ok thnas, but exists any option to disable this MX validation into the QMT, only for make test because my domains look well Not be be condescending, but you don't expect a mail server to work with broken DNS do you? - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Este correo electronico puede conteneder informacion confindencial y protegida legalmente bajo secreto profesional. La informacion esta dirigida solamente a la persona o entidad indicada como destinatario y su acceso por cualquier otra persona no esta autorizado. si ud recibio este mensaje electronico por error, informeselo al remitente y borrelo. Aclaramos que los conceptos y opiniones comprendidos en este correo electronico, deben atribuirse exclusivamente a su auntor y no deben entenderse como necesariamente coincidentes con las de AIMAR, S.A. y en consecuencia, absolutamente ajenos a la responsabilidad de sus directores y ejecutivos. en tanto no hayan participado de su confension y/o emision y quede esta participacion expresamente consignada en el mensaje La divulgacion publica de este correo electronico, como asi su copia, reproduccion total o parcial queda prohibida, dando lugar en caso de inobservancia de estas y todas las acciones legales que pudiesen corresponder. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] FW: Email Senting Problems
For addiontal information this issue happened today bloquing every incoming email, and I don't know the server was working around 2 moths without any problem, I added this line inside tcp.smtp SENDER_NOCHECK=1, because without every incoming mail say problem with invalid sender MX domain -Original Message- From: Jake Vickers [mailto:[EMAIL PROTECTED] Sent: jueves, 30 de octubre de 2008 05:11 p.m. To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] FW: Email Senting Problems Robin W. Sanchez C. wrote: Ok thnas, but exists any option to disable this MX validation into the QMT, only for make test because my domains look well Not be be condescending, but you don't expect a mail server to work with broken DNS do you? - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Este correo electronico puede conteneder informacion confindencial y protegida legalmente bajo secreto profesional. La informacion esta dirigida solamente a la persona o entidad indicada como destinatario y su acceso por cualquier otra persona no esta autorizado. si ud recibio este mensaje electronico por error, informeselo al remitente y borrelo. Aclaramos que los conceptos y opiniones comprendidos en este correo electronico, deben atribuirse exclusivamente a su auntor y no deben entenderse como necesariamente coincidentes con las de AIMAR, S.A. y en consecuencia, absolutamente ajenos a la responsabilidad de sus directores y ejecutivos. en tanto no hayan participado de su confension y/o emision y quede esta participacion expresamente consignada en el mensaje La divulgacion publica de este correo electronico, como asi su copia, reproduccion total o parcial queda prohibida, dando lugar en caso de inobservancia de estas y todas las acciones legales que pudiesen corresponder. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
