Re: [qmailtoaster] Problems with SPAMDYKE
I've just released version 3.1.5, which fixes this bug. Thanks again for reporting it! http://www.spamdyke.org/ -- Sam Clippinger Sam Clippinger wrote: OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger Ronnie Tartar wrote: Yes, Spamdyke version 3.1.3 downloaded today. Tried default configure, then the --disable-tls, failed both ways. The remote machine is a centos5 64 bit, running the default sendmail sendmail-8.13.8-2.el5 courier-authlib-toaster-0.59.2-1.3.6 maildrop-toaster-2.0.3-1.3.5 libsrs2-toaster-1.0.18-1.3.3 ezmlm-cgi-toaster-0.53.324-1.3.3 ucspi-tcp-toaster-0.88-1.3.5 qmail-toaster-1.03-1.3.15 autorespond-toaster-2.0.4-1.3.3 isoqlog-toaster-2.1-1.3.4 clamav-toaster-0.92-1.3.16 vpopmail-toaster-5.4.17-1.3.4 qmail-pop3d-toaster-1.03-1.3.15 control-panel-toaster-0.5-1.3.4 qmailmrtg-toaster-4.2-1.3.3 vqadmin-toaster-2.3.4-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 spamassassin-toaster-3.2.3-1.3.12 libdomainkeys-toaster-0.68-1.3.3 ezmlm-toaster-0.53.324-1.3.3 squirrelmail-toaster-1.4.9a-1.3.6 daemontools-toaster-0.76-1.3.3 courier-imap-toaster-4.1.2-1.3.7 maildrop-toaster-devel-2.0.3-1.3.5 simscan-toaster-1.3.1-1.3.6 Are the packages, bone stock except for spambox being enabled and per use settings for spamassassin. - Original Message - From: Phil Leinhauser [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 4:09 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Well Ronnie, you just can't get any better service than the author himself!! Looks like you're in good hands. Phil -Original message- From: Sam Clippinger [EMAIL PROTECTED] Date: Wed, 09 Jan 2008 16:43:29 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE Looking at the configuration file you posted, it doesn't look like you're using spamdyke's TLS at all (so my previous comment about the TLS certificate doesn't apply). spamdyke should be passing the TLS traffic through, untouched, to qmail. Are you using the latest version of spamdyke? Can you post the OS and MTA versions of both your qmail server and the remote server? If this is a bug in spamdyke, I'd like to reproduce it and fix it. -- Sam Clippinger Ronnie Tartar wrote: Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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
Re: [qmailtoaster] Problems with SPAMDYKE
Sam, et. al. I would say that to get the best results out of SPAMDYKE, you DEFINITELY want *IT* to handle the TLS. My reasoning is 2-fold: 1) I have an average of 15% of incoming SPAM that is attaching with TLS (I thought this was odd, but apparently not) 2) I require TLS for my outbound mail (from my clients) and THEY TOO can be sources of SPAM. I'd like SPAMDYKE to equally fight inbound AND outbound SPAM! Just my thoughts. They were free to you, so take them at their face value. Daniel McAllister, President IT4SOHO, LLC Take my advice... I won't be using it today! Sam Clippinger wrote: Actually, enabling TLS in spamdyke is the best solution. When spamdyke handles the TLS, the remote server can't tell the difference -- if it was using TLS before, it should continue to do so. However, because spamdyke decrypts the traffic, it can enable all of its filters (including graylisting, recipient blacklisting, etc). If spamdyke simply passes TLS traffic through without decrypting it, most of its filters cannot operate. -- Sam Clippinger Davide Bozzelli wrote: Sam Clippinger ha scritto: OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger I can confirm this bug, i've have the exact problems with a qmail patched with jms combined patch that sends mail to a qmailtoaster with spamdyke enabled without tls. By enabling tls in spamdyke the problem went down, but it's not the correct way of work, cause the source mta don't do any tls handshake. Have fun, Davide - 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] Problems with SPAMDYKE
I agree spamdyke should handle the TLS so all of its filters can be used (including graylisting). However, spamdyke can't filter outbound mail. Anything that's generated on your server (e.g. webmail users) will bypass spamdyke entirely. Anything that's sent through your server (e.g. your users' MUAs using your server as their SMTP host) will/should be whitelisted or authenticated. Granted, you _can_ setup spamdyke to filter mail generated by your users' MUAs but you won't like it -- you'll get a lot of angry phone calls. -- Sam Clippinger Dan McAllister wrote: Sam, et. al. I would say that to get the best results out of SPAMDYKE, you DEFINITELY want *IT* to handle the TLS. My reasoning is 2-fold: 1) I have an average of 15% of incoming SPAM that is attaching with TLS (I thought this was odd, but apparently not) 2) I require TLS for my outbound mail (from my clients) and THEY TOO can be sources of SPAM. I'd like SPAMDYKE to equally fight inbound AND outbound SPAM! Just my thoughts. They were free to you, so take them at their face value. Daniel McAllister, President IT4SOHO, LLC Take my advice... I won't be using it today! Sam Clippinger wrote: Actually, enabling TLS in spamdyke is the best solution. When spamdyke handles the TLS, the remote server can't tell the difference -- if it was using TLS before, it should continue to do so. However, because spamdyke decrypts the traffic, it can enable all of its filters (including graylisting, recipient blacklisting, etc). If spamdyke simply passes TLS traffic through without decrypting it, most of its filters cannot operate. -- Sam Clippinger Davide Bozzelli wrote: Sam Clippinger ha scritto: OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger I can confirm this bug, i've have the exact problems with a qmail patched with jms combined patch that sends mail to a qmailtoaster with spamdyke enabled without tls. By enabling tls in spamdyke the problem went down, but it's not the correct way of work, cause the source mta don't do any tls handshake. Have fun, Davide - 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] Problems with SPAMDYKE
Dan, Did you get your backup server problem worked out? If so, what did you find? Phil -Original message- From: Dan McAllister [EMAIL PROTECTED] Date: Mon, 14 Jan 2008 14:11:03 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE Sam, et. al. I would say that to get the best results out of SPAMDYKE, you DEFINITELY want *IT* to handle the TLS. My reasoning is 2-fold: 1) I have an average of 15% of incoming SPAM that is attaching with TLS (I thought this was odd, but apparently not) 2) I require TLS for my outbound mail (from my clients) and THEY TOO can be sources of SPAM. I'd like SPAMDYKE to equally fight inbound AND outbound SPAM! Just my thoughts. They were free to you, so take them at their face value. Daniel McAllister, President IT4SOHO, LLC Take my advice... I won't be using it today! Sam Clippinger wrote: Actually, enabling TLS in spamdyke is the best solution. When spamdyke handles the TLS, the remote server can't tell the difference -- if it was using TLS before, it should continue to do so. However, because spamdyke decrypts the traffic, it can enable all of its filters (including graylisting, recipient blacklisting, etc). If spamdyke simply passes TLS traffic through without decrypting it, most of its filters cannot operate. -- Sam Clippinger Davide Bozzelli wrote: Sam Clippinger ha scritto: OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger I can confirm this bug, i've have the exact problems with a qmail patched with jms combined patch that sends mail to a qmailtoaster with spamdyke enabled without tls. By enabling tls in spamdyke the problem went down, but it's not the correct way of work, cause the source mta don't do any tls handshake. Have fun, Davide - 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] Problems with SPAMDYKE
My two favorite words now are: DENIED_RDNS_MISSING DENIED_OTHER That is what my logs have as 95% plus of the emails coming in. I'm just wondering when they will realize that it isn't making it in. It's starting to slow down a bit. -Original Message- From: Sam Clippinger [mailto:[EMAIL PROTECTED] Sent: Monday, January 14, 2008 3:03 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE I agree spamdyke should handle the TLS so all of its filters can be used (including graylisting). However, spamdyke can't filter outbound mail. Anything that's generated on your server (e.g. webmail users) will bypass spamdyke entirely. Anything that's sent through your server (e.g. your users' MUAs using your server as their SMTP host) will/should be whitelisted or authenticated. Granted, you _can_ setup spamdyke to filter mail generated by your users' MUAs but you won't like it -- you'll get a lot of angry phone calls. -- Sam Clippinger Dan McAllister wrote: Sam, et. al. I would say that to get the best results out of SPAMDYKE, you DEFINITELY want *IT* to handle the TLS. My reasoning is 2-fold: 1) I have an average of 15% of incoming SPAM that is attaching with TLS (I thought this was odd, but apparently not) 2) I require TLS for my outbound mail (from my clients) and THEY TOO can be sources of SPAM. I'd like SPAMDYKE to equally fight inbound AND outbound SPAM! Just my thoughts. They were free to you, so take them at their face value. Daniel McAllister, President IT4SOHO, LLC Take my advice... I won't be using it today! Sam Clippinger wrote: Actually, enabling TLS in spamdyke is the best solution. When spamdyke handles the TLS, the remote server can't tell the difference -- if it was using TLS before, it should continue to do so. However, because spamdyke decrypts the traffic, it can enable all of its filters (including graylisting, recipient blacklisting, etc). If spamdyke simply passes TLS traffic through without decrypting it, most of its filters cannot operate. -- Sam Clippinger Davide Bozzelli wrote: Sam Clippinger ha scritto: OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger I can confirm this bug, i've have the exact problems with a qmail patched with jms combined patch that sends mail to a qmailtoaster with spamdyke enabled without tls. By enabling tls in spamdyke the problem went down, but it's not the correct way of work, cause the source mta don't do any tls handshake. Have fun, Davide - 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] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Problems with SPAMDYKE
Actually, enabling TLS in spamdyke is the best solution. When spamdyke handles the TLS, the remote server can't tell the difference -- if it was using TLS before, it should continue to do so. However, because spamdyke decrypts the traffic, it can enable all of its filters (including graylisting, recipient blacklisting, etc). If spamdyke simply passes TLS traffic through without decrypting it, most of its filters cannot operate. -- Sam Clippinger Davide Bozzelli wrote: Sam Clippinger ha scritto: OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger I can confirm this bug, i've have the exact problems with a qmail patched with jms combined patch that sends mail to a qmailtoaster with spamdyke enabled without tls. By enabling tls in spamdyke the problem went down, but it's not the correct way of work, cause the source mta don't do any tls handshake. Have fun, Davide - 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] Problems with SPAMDYKE
When is the spamdyke.conf file place in /etc/ I ran ./configure, make, then copied spamdyke to /usr/local/bin and changed the qmail script. But I'm looking for /etc/spamdyke.conf like you guys reference and it's not there. Jacob Billingsley MCR Technologies, Inc. 2674 Kraft Ave SE Grand Rapids, MI 49546 Office: 616-942-7244 ext: 205 Fax: 616-942-5988 The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, please note that any dissemination, distribution, or copying of this communication is strictly prohibited. -Original Message- From: Sam Clippinger [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 09, 2008 5:00 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger Ronnie Tartar wrote: Yes, Spamdyke version 3.1.3 downloaded today. Tried default configure, then the --disable-tls, failed both ways. The remote machine is a centos5 64 bit, running the default sendmail sendmail-8.13.8-2.el5 courier-authlib-toaster-0.59.2-1.3.6 maildrop-toaster-2.0.3-1.3.5 libsrs2-toaster-1.0.18-1.3.3 ezmlm-cgi-toaster-0.53.324-1.3.3 ucspi-tcp-toaster-0.88-1.3.5 qmail-toaster-1.03-1.3.15 autorespond-toaster-2.0.4-1.3.3 isoqlog-toaster-2.1-1.3.4 clamav-toaster-0.92-1.3.16 vpopmail-toaster-5.4.17-1.3.4 qmail-pop3d-toaster-1.03-1.3.15 control-panel-toaster-0.5-1.3.4 qmailmrtg-toaster-4.2-1.3.3 vqadmin-toaster-2.3.4-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 spamassassin-toaster-3.2.3-1.3.12 libdomainkeys-toaster-0.68-1.3.3 ezmlm-toaster-0.53.324-1.3.3 squirrelmail-toaster-1.4.9a-1.3.6 daemontools-toaster-0.76-1.3.3 courier-imap-toaster-4.1.2-1.3.7 maildrop-toaster-devel-2.0.3-1.3.5 simscan-toaster-1.3.1-1.3.6 Are the packages, bone stock except for spambox being enabled and per use settings for spamassassin. - Original Message - From: Phil Leinhauser [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 4:09 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Well Ronnie, you just can't get any better service than the author himself!! Looks like you're in good hands. Phil -Original message- From: Sam Clippinger [EMAIL PROTECTED] Date: Wed, 09 Jan 2008 16:43:29 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE Looking at the configuration file you posted, it doesn't look like you're using spamdyke's TLS at all (so my previous comment about the TLS certificate doesn't apply). spamdyke should be passing the TLS traffic through, untouched, to qmail. Are you using the latest version of spamdyke? Can you post the OS and MTA versions of both your qmail server and the remote server? If this is a bug in spamdyke, I'd like to reproduce it and fix it. -- Sam Clippinger Ronnie Tartar wrote: Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
Re: [qmailtoaster] Problems with SPAMDYKE
I may have lost a few messages, some servers were not able to get to me with my config. I had to remove. my spamdyke.conf file is: log-level=2 local-domains-file=/var/qmail/control/rcpthosts idle-timeout-secs=60 reject-empty-rdns greeting-delay-secs=5 reject-missing-sender-mx reject-ip-in-cc-rdns I also tried recompiling with --disable-tls parameter, still had problems? Thanks - Original Message - From: Ronnie Tartar [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 2:55 PM Subject: [qmailtoaster] Problems with SPAMDYKE Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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] Problems with SPAMDYKE
I'm not running Spamdyke but It looks like you have it set to only accept TLS (ssl) connections. If the sender doesn't do TLS it should fall back to normal. Phil -Original message- From: Ronnie Tartar [EMAIL PROTECTED] Date: Wed, 09 Jan 2008 15:54:27 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] Problems with SPAMDYKE Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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] Problems with SPAMDYKE
Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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] Problems with SPAMDYKE
Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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] Problems with SPAMDYKE
Looking at the configuration file you posted, it doesn't look like you're using spamdyke's TLS at all (so my previous comment about the TLS certificate doesn't apply). spamdyke should be passing the TLS traffic through, untouched, to qmail. Are you using the latest version of spamdyke? Can you post the OS and MTA versions of both your qmail server and the remote server? If this is a bug in spamdyke, I'd like to reproduce it and fix it. -- Sam Clippinger Ronnie Tartar wrote: Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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] Problems with SPAMDYKE
Well Ronnie, you just can't get any better service than the author himself!! Looks like you're in good hands. Phil -Original message- From: Sam Clippinger [EMAIL PROTECTED] Date: Wed, 09 Jan 2008 16:43:29 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE Looking at the configuration file you posted, it doesn't look like you're using spamdyke's TLS at all (so my previous comment about the TLS certificate doesn't apply). spamdyke should be passing the TLS traffic through, untouched, to qmail. Are you using the latest version of spamdyke? Can you post the OS and MTA versions of both your qmail server and the remote server? If this is a bug in spamdyke, I'd like to reproduce it and fix it. -- Sam Clippinger Ronnie Tartar wrote: Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Problems with SPAMDYKE
Yes, Spamdyke version 3.1.3 downloaded today. Tried default configure, then the --disable-tls, failed both ways. The remote machine is a centos5 64 bit, running the default sendmail sendmail-8.13.8-2.el5 courier-authlib-toaster-0.59.2-1.3.6 maildrop-toaster-2.0.3-1.3.5 libsrs2-toaster-1.0.18-1.3.3 ezmlm-cgi-toaster-0.53.324-1.3.3 ucspi-tcp-toaster-0.88-1.3.5 qmail-toaster-1.03-1.3.15 autorespond-toaster-2.0.4-1.3.3 isoqlog-toaster-2.1-1.3.4 clamav-toaster-0.92-1.3.16 vpopmail-toaster-5.4.17-1.3.4 qmail-pop3d-toaster-1.03-1.3.15 control-panel-toaster-0.5-1.3.4 qmailmrtg-toaster-4.2-1.3.3 vqadmin-toaster-2.3.4-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 spamassassin-toaster-3.2.3-1.3.12 libdomainkeys-toaster-0.68-1.3.3 ezmlm-toaster-0.53.324-1.3.3 squirrelmail-toaster-1.4.9a-1.3.6 daemontools-toaster-0.76-1.3.3 courier-imap-toaster-4.1.2-1.3.7 maildrop-toaster-devel-2.0.3-1.3.5 simscan-toaster-1.3.1-1.3.6 Are the packages, bone stock except for spambox being enabled and per use settings for spamassassin. - Original Message - From: Phil Leinhauser [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 4:09 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Well Ronnie, you just can't get any better service than the author himself!! Looks like you're in good hands. Phil -Original message- From: Sam Clippinger [EMAIL PROTECTED] Date: Wed, 09 Jan 2008 16:43:29 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE Looking at the configuration file you posted, it doesn't look like you're using spamdyke's TLS at all (so my previous comment about the TLS certificate doesn't apply). spamdyke should be passing the TLS traffic through, untouched, to qmail. Are you using the latest version of spamdyke? Can you post the OS and MTA versions of both your qmail server and the remote server? If this is a bug in spamdyke, I'd like to reproduce it and fix it. -- Sam Clippinger Ronnie Tartar wrote: Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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] - 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] Problems with SPAMDYKE
Additionally, I was not able to get any emails from the qmail toaster list either. - Original Message - From: Ronnie Tartar [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 4:15 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Yes, Spamdyke version 3.1.3 downloaded today. Tried default configure, then the --disable-tls, failed both ways. The remote machine is a centos5 64 bit, running the default sendmail sendmail-8.13.8-2.el5 courier-authlib-toaster-0.59.2-1.3.6 maildrop-toaster-2.0.3-1.3.5 libsrs2-toaster-1.0.18-1.3.3 ezmlm-cgi-toaster-0.53.324-1.3.3 ucspi-tcp-toaster-0.88-1.3.5 qmail-toaster-1.03-1.3.15 autorespond-toaster-2.0.4-1.3.3 isoqlog-toaster-2.1-1.3.4 clamav-toaster-0.92-1.3.16 vpopmail-toaster-5.4.17-1.3.4 qmail-pop3d-toaster-1.03-1.3.15 control-panel-toaster-0.5-1.3.4 qmailmrtg-toaster-4.2-1.3.3 vqadmin-toaster-2.3.4-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 spamassassin-toaster-3.2.3-1.3.12 libdomainkeys-toaster-0.68-1.3.3 ezmlm-toaster-0.53.324-1.3.3 squirrelmail-toaster-1.4.9a-1.3.6 daemontools-toaster-0.76-1.3.3 courier-imap-toaster-4.1.2-1.3.7 maildrop-toaster-devel-2.0.3-1.3.5 simscan-toaster-1.3.1-1.3.6 Are the packages, bone stock except for spambox being enabled and per use settings for spamassassin. - Original Message - From: Phil Leinhauser [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 4:09 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Well Ronnie, you just can't get any better service than the author himself!! Looks like you're in good hands. Phil -Original message- From: Sam Clippinger [EMAIL PROTECTED] Date: Wed, 09 Jan 2008 16:43:29 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE Looking at the configuration file you posted, it doesn't look like you're using spamdyke's TLS at all (so my previous comment about the TLS certificate doesn't apply). spamdyke should be passing the TLS traffic through, untouched, to qmail. Are you using the latest version of spamdyke? Can you post the OS and MTA versions of both your qmail server and the remote server? If this is a bug in spamdyke, I'd like to reproduce it and fix it. -- Sam Clippinger Ronnie Tartar wrote: Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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] - 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] Problems with SPAMDYKE
OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger Ronnie Tartar wrote: Yes, Spamdyke version 3.1.3 downloaded today. Tried default configure, then the --disable-tls, failed both ways. The remote machine is a centos5 64 bit, running the default sendmail sendmail-8.13.8-2.el5 courier-authlib-toaster-0.59.2-1.3.6 maildrop-toaster-2.0.3-1.3.5 libsrs2-toaster-1.0.18-1.3.3 ezmlm-cgi-toaster-0.53.324-1.3.3 ucspi-tcp-toaster-0.88-1.3.5 qmail-toaster-1.03-1.3.15 autorespond-toaster-2.0.4-1.3.3 isoqlog-toaster-2.1-1.3.4 clamav-toaster-0.92-1.3.16 vpopmail-toaster-5.4.17-1.3.4 qmail-pop3d-toaster-1.03-1.3.15 control-panel-toaster-0.5-1.3.4 qmailmrtg-toaster-4.2-1.3.3 vqadmin-toaster-2.3.4-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 spamassassin-toaster-3.2.3-1.3.12 libdomainkeys-toaster-0.68-1.3.3 ezmlm-toaster-0.53.324-1.3.3 squirrelmail-toaster-1.4.9a-1.3.6 daemontools-toaster-0.76-1.3.3 courier-imap-toaster-4.1.2-1.3.7 maildrop-toaster-devel-2.0.3-1.3.5 simscan-toaster-1.3.1-1.3.6 Are the packages, bone stock except for spambox being enabled and per use settings for spamassassin. - Original Message - From: Phil Leinhauser [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 4:09 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Well Ronnie, you just can't get any better service than the author himself!! Looks like you're in good hands. Phil -Original message- From: Sam Clippinger [EMAIL PROTECTED] Date: Wed, 09 Jan 2008 16:43:29 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE Looking at the configuration file you posted, it doesn't look like you're using spamdyke's TLS at all (so my previous comment about the TLS certificate doesn't apply). spamdyke should be passing the TLS traffic through, untouched, to qmail. Are you using the latest version of spamdyke? Can you post the OS and MTA versions of both your qmail server and the remote server? If this is a bug in spamdyke, I'd like to reproduce it and fix it. -- Sam Clippinger Ronnie Tartar wrote: Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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] - QmailToaster hosted by: VR Hosted http://www.vr.org
Re: [qmailtoaster] Problems with SPAMDYKE
I will give this a shot tonight then send update. Thanks - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 4:59 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger Ronnie Tartar wrote: Yes, Spamdyke version 3.1.3 downloaded today. Tried default configure, then the --disable-tls, failed both ways. The remote machine is a centos5 64 bit, running the default sendmail sendmail-8.13.8-2.el5 courier-authlib-toaster-0.59.2-1.3.6 maildrop-toaster-2.0.3-1.3.5 libsrs2-toaster-1.0.18-1.3.3 ezmlm-cgi-toaster-0.53.324-1.3.3 ucspi-tcp-toaster-0.88-1.3.5 qmail-toaster-1.03-1.3.15 autorespond-toaster-2.0.4-1.3.3 isoqlog-toaster-2.1-1.3.4 clamav-toaster-0.92-1.3.16 vpopmail-toaster-5.4.17-1.3.4 qmail-pop3d-toaster-1.03-1.3.15 control-panel-toaster-0.5-1.3.4 qmailmrtg-toaster-4.2-1.3.3 vqadmin-toaster-2.3.4-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 spamassassin-toaster-3.2.3-1.3.12 libdomainkeys-toaster-0.68-1.3.3 ezmlm-toaster-0.53.324-1.3.3 squirrelmail-toaster-1.4.9a-1.3.6 daemontools-toaster-0.76-1.3.3 courier-imap-toaster-4.1.2-1.3.7 maildrop-toaster-devel-2.0.3-1.3.5 simscan-toaster-1.3.1-1.3.6 Are the packages, bone stock except for spambox being enabled and per use settings for spamassassin. - Original Message - From: Phil Leinhauser [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 4:09 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Well Ronnie, you just can't get any better service than the author himself!! Looks like you're in good hands. Phil -Original message- From: Sam Clippinger [EMAIL PROTECTED] Date: Wed, 09 Jan 2008 16:43:29 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE Looking at the configuration file you posted, it doesn't look like you're using spamdyke's TLS at all (so my previous comment about the TLS certificate doesn't apply). spamdyke should be passing the TLS traffic through, untouched, to qmail. Are you using the latest version of spamdyke? Can you post the OS and MTA versions of both your qmail server and the remote server? If this is a bug in spamdyke, I'd like to reproduce it and fix it. -- Sam Clippinger Ronnie Tartar wrote: Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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
RE: [qmailtoaster] Problems with SPAMDYKE
Ok, compiling without the --disable-tls, default configure, make, install. Works no problem with the tls-certificate-file parameter in the conf file. Just will not work without it. Thanks for the fix. -Original Message- From: Sam Clippinger [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 09, 2008 5:00 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger Ronnie Tartar wrote: Yes, Spamdyke version 3.1.3 downloaded today. Tried default configure, then the --disable-tls, failed both ways. The remote machine is a centos5 64 bit, running the default sendmail sendmail-8.13.8-2.el5 courier-authlib-toaster-0.59.2-1.3.6 maildrop-toaster-2.0.3-1.3.5 libsrs2-toaster-1.0.18-1.3.3 ezmlm-cgi-toaster-0.53.324-1.3.3 ucspi-tcp-toaster-0.88-1.3.5 qmail-toaster-1.03-1.3.15 autorespond-toaster-2.0.4-1.3.3 isoqlog-toaster-2.1-1.3.4 clamav-toaster-0.92-1.3.16 vpopmail-toaster-5.4.17-1.3.4 qmail-pop3d-toaster-1.03-1.3.15 control-panel-toaster-0.5-1.3.4 qmailmrtg-toaster-4.2-1.3.3 vqadmin-toaster-2.3.4-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 spamassassin-toaster-3.2.3-1.3.12 libdomainkeys-toaster-0.68-1.3.3 ezmlm-toaster-0.53.324-1.3.3 squirrelmail-toaster-1.4.9a-1.3.6 daemontools-toaster-0.76-1.3.3 courier-imap-toaster-4.1.2-1.3.7 maildrop-toaster-devel-2.0.3-1.3.5 simscan-toaster-1.3.1-1.3.6 Are the packages, bone stock except for spambox being enabled and per use settings for spamassassin. - Original Message - From: Phil Leinhauser [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 4:09 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Well Ronnie, you just can't get any better service than the author himself!! Looks like you're in good hands. Phil -Original message- From: Sam Clippinger [EMAIL PROTECTED] Date: Wed, 09 Jan 2008 16:43:29 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE Looking at the configuration file you posted, it doesn't look like you're using spamdyke's TLS at all (so my previous comment about the TLS certificate doesn't apply). spamdyke should be passing the TLS traffic through, untouched, to qmail. Are you using the latest version of spamdyke? Can you post the OS and MTA versions of both your qmail server and the remote server? If this is a bug in spamdyke, I'd like to reproduce it and fix it. -- Sam Clippinger Ronnie Tartar wrote: Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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
RE: [qmailtoaster] Problems with SPAMDYKE
BTW, this is a great program, thanks it is really keeping the spammers @ bay -Original Message- From: Sam Clippinger [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 09, 2008 5:00 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE OK, I should be able to duplicate that setup to see if I can reproduce your error. It may be a little while before I have the time, however. In the meantime, can you try enabling TLS support in spamdyke to see if this error persists? Inside spamdyke, TLS passthrough is handled differently than TLS decoding. If this is a spamdyke bug, you may be able to work around it. Enabling TLS support will also allow all of spamdyke's filters to function, including graylisting. To enable TLS, you'll need to compile spamdyke with TLS support and use the tls-certificate-file directive in the configuration file. Your TLS certificate is probably located at: /var/qmail/control/servercert.pem -- Sam Clippinger Ronnie Tartar wrote: Yes, Spamdyke version 3.1.3 downloaded today. Tried default configure, then the --disable-tls, failed both ways. The remote machine is a centos5 64 bit, running the default sendmail sendmail-8.13.8-2.el5 courier-authlib-toaster-0.59.2-1.3.6 maildrop-toaster-2.0.3-1.3.5 libsrs2-toaster-1.0.18-1.3.3 ezmlm-cgi-toaster-0.53.324-1.3.3 ucspi-tcp-toaster-0.88-1.3.5 qmail-toaster-1.03-1.3.15 autorespond-toaster-2.0.4-1.3.3 isoqlog-toaster-2.1-1.3.4 clamav-toaster-0.92-1.3.16 vpopmail-toaster-5.4.17-1.3.4 qmail-pop3d-toaster-1.03-1.3.15 control-panel-toaster-0.5-1.3.4 qmailmrtg-toaster-4.2-1.3.3 vqadmin-toaster-2.3.4-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 spamassassin-toaster-3.2.3-1.3.12 libdomainkeys-toaster-0.68-1.3.3 ezmlm-toaster-0.53.324-1.3.3 squirrelmail-toaster-1.4.9a-1.3.6 daemontools-toaster-0.76-1.3.3 courier-imap-toaster-4.1.2-1.3.7 maildrop-toaster-devel-2.0.3-1.3.5 simscan-toaster-1.3.1-1.3.6 Are the packages, bone stock except for spambox being enabled and per use settings for spamassassin. - Original Message - From: Phil Leinhauser [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 4:09 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Well Ronnie, you just can't get any better service than the author himself!! Looks like you're in good hands. Phil -Original message- From: Sam Clippinger [EMAIL PROTECTED] Date: Wed, 09 Jan 2008 16:43:29 -0500 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Problems with SPAMDYKE Looking at the configuration file you posted, it doesn't look like you're using spamdyke's TLS at all (so my previous comment about the TLS certificate doesn't apply). spamdyke should be passing the TLS traffic through, untouched, to qmail. Are you using the latest version of spamdyke? Can you post the OS and MTA versions of both your qmail server and the remote server? If this is a bug in spamdyke, I'd like to reproduce it and fix it. -- Sam Clippinger Ronnie Tartar wrote: Strange, those errors are on other machines. Not on the qmail toaster machine. I ran the configtest, no errors. - Original Message - From: Sam Clippinger [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, January 09, 2008 3:26 PM Subject: Re: [qmailtoaster] Problems with SPAMDYKE Most likely, spamdyke doesn't have permission to read your TLS certificate. Are you seeing any errors in the maillog on your qmail server? You can also try running spamdyke with the --config-test flag to check for configuration errors. -- Sam Clippinger Ronnie Tartar wrote: Having trouble from some places getting email to my server, they get tls errors? lnt.c:567: Jan 9 14:56:15 cp sendmail[32112]: ruleset=tls_server, arg1=SOFTWARE, relay=mx1.host2max.com, reject=403 4.7.0 TLS handshake failed Any ideas? - 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
