Re: [qmailtoaster] Forwarding Mails to another server (smtproutes)
I have checked the sources and the qmail-remote-auth patch is definitely included. It can be found in qmailtoaster-1.3.1.patch.bz2 which patches qmail-1.03 to netqmail-1.05. I'll see to find time to test with recordio. Johannes Eric Shubert schrieb: Hmmm, that's interesting. I use smtproutes with authentication quite a bit with dyndns.org's outbound mailhop relay, which uses authentication. I've used this toaster feature for about 2 years now. So I'm pretty sure the patch is in there. What's maybe not working is when the toaster is on the relay (receiving) end. That I haven't done. Dan, can you put recordio on either end of your test and see what's going on? Dan McAllister wrote: I have done some testing... I don't know if the QMail-Remote-Auth patch is a part of QMT, but if so - then it is not working. What this patch is /supposed /to do is to allow the addition of username password info in the smtproutes file. The idea being, if I place in my smtproutes file a line like: *:mail.myserver.com [EMAIL PROTECTED] mypassword * which is actually 2 fields longer than a normal smtproutes line (the extra 2 lines being a username (which, in the case of QMT is an email address) and a password, then all my outbound emails should be routed to the server *mail.myserver.com* and when the connection is made, SMTP_AUTH is supposed to be used, using the credentials provided. Any chance someone better at this than I am could figure out how to add the QMail-Remote-Auth patch??? (Or figure out why it isn't working?) I [personally] think that this patch should be a permanent part of the Toaster... any comments? BTW: I tested this by adding a valid username/password entry to a server, then sending a test message, then checking the send log -- which indicates that the connection is still proceeding without the authentication (exact snippet from the log file is: *delivery 29: failure: User_and_password_not_set,_continuing_without_authentication.*) Cheers! Dan Daniel McAllister, President IT4SOHO, LLC 224 - 13th Avenue N St. Petersburg, FL 33701 877-IT4SOHO: Toll Free 727-647-7646 In Pinellas 813-464-2093 In Hillsborough 727-507-9435 Fax Only When did you do your last backup? Ask me about unattended offsite backup solutions... to protect your business, not just your data! Eric Shubert wrote: You got me, then. Maybe a TLS issue? I'd try turning on recordio to see what's happening. You can find instructions on using recordio in the list archives. It'd be nice to have a wiki page on that, but I don't recall anyone writing one yet. Johannes Weberhofer, Weberhofer GmbH wrote: Yes, the user/password is valid on the receiving server. Johannes Eric Shubert schrieb: Is that user/pw an account on the sending or receiving server? It needs to be an account on the receiving server. Johannes Weberhofer, Weberhofer GmbH wrote: Yes, it has (the line is: weberhofer.at:mail.weberhofer.at:587 [EMAIL PROTECTED] password). Johannes Eric Shubert schrieb: Does his machine's smtproutes record include a username and password? It needs that in order to authenticate. I believe the wiki has details. Johannes Weberhofer, Weberhofer GmbH wrote: Hello everyone! I have a question related to the smtproutes. I want to force one of my customers to route external mails through my server, internal mails should stay within his office. I have set up an qmail-toaster within the office which operates perfectly. My server works perfectly, too. When I modify the smptroutes to forward all mails to my server's submission port the customer always gets an error message like this: - returning mail's content [EMAIL PROTECTED]: Connected to 80.237.247.145 but sender was rejected. Remote host said: 503 AUTH first (#5.5.1) - Do you have any ideas how this could be done? Unfortunately the sender does not have a fixed IP address, so he must send authenticated only. Also sending via port 25 does not work. Do you have any ideas? Below you see all the relevant settings and log-files. Best regards, Johannes Weberhofer - /var/qmail/control/smtproutes at my customer's server weberhofer.at:mail.weberhofer.at:587 [EMAIL PROTECTED] password - submission/current in my relaying mail server: @40004817317702ef9834 CHKUSER accepted sender: from [EMAIL PROTECTED]:: remote server.office.mycustomer.domain:unknown:YYY.YYY.YYY.YYY rcpt : sender accepted - smtp/current at my customer's server: @4000481731762d9096c4 status: local 0/10 remote 1/60 @40004817317701c5b27c delivery 83: failure: Connected_to_XXX.XXX.XXX.XXX_but_sender_was_rejected./Remote_host_said:_503_AUTH_first_(#5.5.1)/ @40004817317701c5c21c status: local 0/10 remote 0/60 -- trying to send via port 25 results in the following smtp/current at my customer's server: @40004817350e1c560d1c delivery 87: deferral:
[qmailtoaster] Spamassassin Headers Problem
I've just discovered that on or around the 20th-20st of April, my Toaster stopped including some of the Spamassassin headers on messages. Specifically, the X-Spam-Level and X-Spam-Status headers. The X-Spam-Checker-Version header is still present. This would have been during the time when the upgraded ClamAV came out that required that we uninstall the previous version and then install the new version. Is there a configuration file, or more than one, that I should check and/or modify to correct this? Or am I going to have to uninstall several dependent packages and then re-install them to get everything working together properly? Has anyone else seen this? Roxanne - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Spamassassin Headers Problem
Roxanne Sandesara wrote: I've just discovered that on or around the 20th-20st of April, my Toaster stopped including some of the Spamassassin headers on messages. Specifically, the X-Spam-Level and X-Spam-Status headers. The X-Spam-Checker-Version header is still present. This would have been during the time when the upgraded ClamAV came out that required that we uninstall the previous version and then install the new version. Is there a configuration file, or more than one, that I should check and/or modify to correct this? Or am I going to have to uninstall several dependent packages and then re-install them to get everything working together properly? Has anyone else seen this? You probably just need to let simscan know there's a new version: /var/qmail/bin/simscanmk -g That should put the headers back in. If not, let us know what versions of the packages you're running. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Spamassassin Headers Problem
Roxanne Sandesara wrote: I've just discovered that on or around the 20th-20st of April, my Toaster stopped including some of the Spamassassin headers on messages. Specifically, the X-Spam-Level and X-Spam-Status headers. The X-Spam-Checker-Version header is still present. This would have been during the time when the upgraded ClamAV came out that required that we uninstall the previous version and then install the new version. Is there a configuration file, or more than one, that I should check and/or modify to correct this? Or am I going to have to uninstall several dependent packages and then re-install them to get everything working together properly? Has anyone else seen this? Roxanne What version of toaster packages are you running? Does what you're running match what the header shows? -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Spamassassin Headers Problem
OK. Ran that. It built without errors. Sent in a test message from outside, the headers still appear to be missing. Tried qmailctl cdb just in case. Headers still missing on another test afterwards. qtp-ami-up2date says there are no new packages. Versions of packages: # rpm -qa | grep toaster ucspi-tcp-toaster-0.88-1.3.5 courier-imap-toaster-4.1.2-1.3.7 qmail-pop3d-toaster-1.03-1.3.15 squirrelmail-toaster-1.4.13-1.3.9 courier-authlib-toaster-0.59.2-1.3.6 isoqlog-toaster-2.1-1.3.4 ezmlm-toaster-0.53.324-1.3.3 qmail-toaster-1.03-1.3.15 ezmlm-cgi-toaster-0.53.324-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 simscan-toaster-1.3.1-1.3.6 vpopmail-toaster-5.4.17-1.3.4 libsrs2-toaster-1.0.18-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 control-panel-toaster-0.5-1.3.4 maildrop-toaster-devel-2.0.3-1.3.5 send-emails-toaster-0.5-1.3.4 vqadmin-toaster-2.3.4-1.3.3 spamassassin-toaster-3.2.4-1.3.14 clamav-toaster-0.93-1.3.18 maildrop-toaster-2.0.3-1.3.5 libdomainkeys-toaster-0.68-1.3.3 qmailtoaster-plus-0.3.0-1.4.2 daemontools-toaster-0.76-1.3.3 autorespond-toaster-2.0.4-1.3.3 qmailmrtg-toaster-4.2-1.3.3 qmailtoaster-plus.repo-0.1-1 On May 1, 2008, at 7:28 AM, Jake Vickers wrote: Roxanne Sandesara wrote: I've just discovered that on or around the 20th-20st of April, my Toaster stopped including some of the Spamassassin headers on messages. Specifically, the X-Spam-Level and X-Spam-Status headers. The X-Spam-Checker-Version header is still present. This would have been during the time when the upgraded ClamAV came out that required that we uninstall the previous version and then install the new version. Is there a configuration file, or more than one, that I should check and/or modify to correct this? Or am I going to have to uninstall several dependent packages and then re-install them to get everything working together properly? Has anyone else seen this? You probably just need to let simscan know there's a new version: /var/qmail/bin/simscanmk -g That should put the headers back in. If not, let us know what versions of the packages you're running. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [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] Spamassassin Headers Problem
It appears to report correctly the version of Spamassassin in the header that /is/ being included: X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on myserver Although, I did check the website, and the date there seems wrong. The date on the package on the website - which is what I have - is 2008-02-04. Would that change? Roxanne On May 1, 2008, at 7:51 AM, Roxanne Sandesara wrote: OK. Ran that. It built without errors. Sent in a test message from outside, the headers still appear to be missing. Tried qmailctl cdb just in case. Headers still missing on another test afterwards. qtp-ami-up2date says there are no new packages. Versions of packages: # rpm -qa | grep toaster ucspi-tcp-toaster-0.88-1.3.5 courier-imap-toaster-4.1.2-1.3.7 qmail-pop3d-toaster-1.03-1.3.15 squirrelmail-toaster-1.4.13-1.3.9 courier-authlib-toaster-0.59.2-1.3.6 isoqlog-toaster-2.1-1.3.4 ezmlm-toaster-0.53.324-1.3.3 qmail-toaster-1.03-1.3.15 ezmlm-cgi-toaster-0.53.324-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 simscan-toaster-1.3.1-1.3.6 vpopmail-toaster-5.4.17-1.3.4 libsrs2-toaster-1.0.18-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 control-panel-toaster-0.5-1.3.4 maildrop-toaster-devel-2.0.3-1.3.5 send-emails-toaster-0.5-1.3.4 vqadmin-toaster-2.3.4-1.3.3 spamassassin-toaster-3.2.4-1.3.14 clamav-toaster-0.93-1.3.18 maildrop-toaster-2.0.3-1.3.5 libdomainkeys-toaster-0.68-1.3.3 qmailtoaster-plus-0.3.0-1.4.2 daemontools-toaster-0.76-1.3.3 autorespond-toaster-2.0.4-1.3.3 qmailmrtg-toaster-4.2-1.3.3 qmailtoaster-plus.repo-0.1-1 On May 1, 2008, at 7:28 AM, Jake Vickers wrote: Roxanne Sandesara wrote: I've just discovered that on or around the 20th-20st of April, my Toaster stopped including some of the Spamassassin headers on messages. Specifically, the X-Spam-Level and X-Spam-Status headers. The X-Spam-Checker-Version header is still present. This would have been during the time when the upgraded ClamAV came out that required that we uninstall the previous version and then install the new version. Is there a configuration file, or more than one, that I should check and/or modify to correct this? Or am I going to have to uninstall several dependent packages and then re-install them to get everything working together properly? Has anyone else seen this? You probably just need to let simscan know there's a new version: /var/qmail/bin/simscanmk -g That should put the headers back in. If not, let us know what versions of the packages you're running. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [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] Spamassassin Headers Problem
Have you tried removing the spamassassin package and rebuilding it? James On 1 May 2008, at 12:51, Roxanne Sandesara wrote: OK. Ran that. It built without errors. Sent in a test message from outside, the headers still appear to be missing. Tried qmailctl cdb just in case. Headers still missing on another test afterwards. qtp-ami-up2date says there are no new packages. Versions of packages: # rpm -qa | grep toaster ucspi-tcp-toaster-0.88-1.3.5 courier-imap-toaster-4.1.2-1.3.7 qmail-pop3d-toaster-1.03-1.3.15 squirrelmail-toaster-1.4.13-1.3.9 courier-authlib-toaster-0.59.2-1.3.6 isoqlog-toaster-2.1-1.3.4 ezmlm-toaster-0.53.324-1.3.3 qmail-toaster-1.03-1.3.15 ezmlm-cgi-toaster-0.53.324-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 simscan-toaster-1.3.1-1.3.6 vpopmail-toaster-5.4.17-1.3.4 libsrs2-toaster-1.0.18-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 control-panel-toaster-0.5-1.3.4 maildrop-toaster-devel-2.0.3-1.3.5 send-emails-toaster-0.5-1.3.4 vqadmin-toaster-2.3.4-1.3.3 spamassassin-toaster-3.2.4-1.3.14 clamav-toaster-0.93-1.3.18 maildrop-toaster-2.0.3-1.3.5 libdomainkeys-toaster-0.68-1.3.3 qmailtoaster-plus-0.3.0-1.4.2 daemontools-toaster-0.76-1.3.3 autorespond-toaster-2.0.4-1.3.3 qmailmrtg-toaster-4.2-1.3.3 qmailtoaster-plus.repo-0.1-1 On May 1, 2008, at 7:28 AM, Jake Vickers wrote: Roxanne Sandesara wrote: I've just discovered that on or around the 20th-20st of April, my Toaster stopped including some of the Spamassassin headers on messages. Specifically, the X-Spam-Level and X-Spam-Status headers. The X-Spam-Checker-Version header is still present. This would have been during the time when the upgraded ClamAV came out that required that we uninstall the previous version and then install the new version. Is there a configuration file, or more than one, that I should check and/or modify to correct this? Or am I going to have to uninstall several dependent packages and then re-install them to get everything working together properly? Has anyone else seen this? You probably just need to let simscan know there's a new version: /var/qmail/bin/simscanmk -g That should put the headers back in. If not, let us know what versions of the packages you're running. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [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] Spamassassin Headers Problem
Or the simscan package even! ;-) On 1 May 2008, at 12:51, Roxanne Sandesara wrote: OK. Ran that. It built without errors. Sent in a test message from outside, the headers still appear to be missing. Tried qmailctl cdb just in case. Headers still missing on another test afterwards. qtp-ami-up2date says there are no new packages. Versions of packages: # rpm -qa | grep toaster ucspi-tcp-toaster-0.88-1.3.5 courier-imap-toaster-4.1.2-1.3.7 qmail-pop3d-toaster-1.03-1.3.15 squirrelmail-toaster-1.4.13-1.3.9 courier-authlib-toaster-0.59.2-1.3.6 isoqlog-toaster-2.1-1.3.4 ezmlm-toaster-0.53.324-1.3.3 qmail-toaster-1.03-1.3.15 ezmlm-cgi-toaster-0.53.324-1.3.3 qmailadmin-toaster-1.2.11-1.3.4 simscan-toaster-1.3.1-1.3.6 vpopmail-toaster-5.4.17-1.3.4 libsrs2-toaster-1.0.18-1.3.3 ripmime-toaster-1.4.0.6-1.3.3 control-panel-toaster-0.5-1.3.4 maildrop-toaster-devel-2.0.3-1.3.5 send-emails-toaster-0.5-1.3.4 vqadmin-toaster-2.3.4-1.3.3 spamassassin-toaster-3.2.4-1.3.14 clamav-toaster-0.93-1.3.18 maildrop-toaster-2.0.3-1.3.5 libdomainkeys-toaster-0.68-1.3.3 qmailtoaster-plus-0.3.0-1.4.2 daemontools-toaster-0.76-1.3.3 autorespond-toaster-2.0.4-1.3.3 qmailmrtg-toaster-4.2-1.3.3 qmailtoaster-plus.repo-0.1-1 On May 1, 2008, at 7:28 AM, Jake Vickers wrote: Roxanne Sandesara wrote: I've just discovered that on or around the 20th-20st of April, my Toaster stopped including some of the Spamassassin headers on messages. Specifically, the X-Spam-Level and X-Spam-Status headers. The X-Spam-Checker-Version header is still present. This would have been during the time when the upgraded ClamAV came out that required that we uninstall the previous version and then install the new version. Is there a configuration file, or more than one, that I should check and/or modify to correct this? Or am I going to have to uninstall several dependent packages and then re-install them to get everything working together properly? Has anyone else seen this? You probably just need to let simscan know there's a new version: /var/qmail/bin/simscanmk -g That should put the headers back in. If not, let us know what versions of the packages you're running. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [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] Spamassassin Headers Problem
Roxanne Sandesara wrote: OK. Ran that. It built without errors. Try: /var/qmail/bin/simscanmk /var/qmail/bin/simscanmk -g (yeah, run both) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Spamassassin Headers Problem
Ran both. Both ran without errors. New test message. Same results. X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mymailserver The other two headers are still missing. On May 1, 2008, at 8:25 AM, Jake Vickers wrote: Roxanne Sandesara wrote: OK. Ran that. It built without errors. Try: /var/qmail/bin/simscanmk /var/qmail/bin/simscanmk -g (yeah, run both) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [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] smtproutes log
Last few questions in regards to smtproutes! I promise! After add a line to smtproutes all I have to do is restart qmail correct? Also, once its live is there a log file that I can tail to make sure its working? Or will it just display in the normal qmail logs? Thanks!
Re: [qmailtoaster] smtproutes log
Yes just qmailctl restart AFAIK its just normal traffic that will display in the relevant log file. On 1 May 2008, at 14:24, Dan Herbon wrote: Last few questions in regards to smtproutes! I promise! After add a line to smtproutes all I have to do is restart qmail correct? Also, once its live is there a log file that I can tail to make sure its working? Or will it just display in the normal qmail logs? Thanks!
Re: [qmailtoaster] Update of ClamAV Solved
I've upgraded my clam clamav-toaster-0.92-1.3.16 which was working fine for the new released version clamav-toaster-0.93-1.3.18. Installation went ok, the package manager reported that it was installed fine. The thing es that mail is not being accepted, here's is an example of an smtp transaction: - 220 qmailserver.example.com - SMTP Server ESMTP - EHLO sender.example.com - 250-hostname.example.com - SMTP Server - 250-STARTTLS - 250-PIPELINING - 250-8BITMIME - 250-SIZE 20971520 - 250 AUTH LOGIN PLAIN CRAM-MD5 - AUTH CRAM-MD5 - 334 ( CRAM MD5 auth ) - (more auth) - 235 ok, go ahead (#2.0.0) - MAIL FROM:[EMAIL PROTECTED] - 250 ok - RCPT TO:[EMAIL PROTECTED] - 250 ok - DATA - 354 go ahead - Date: Thu, 01 May 2008 20:47:10 -0400 - Subject: test Thu, 01 May 2008 20:47:10 -0400 - - This is a test mailing - - . ** 451 mail server temporarily rejected message (#4.3.0) - QUIT - 221 qmailserver.example.com - SMTP Server This stopped working after the upgrade, my tcp.smtp is: 127.:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1 :allow,BADMIMETYPE=,RBLSMTPD=,SENDER_NOCHECK=1,BADLOADERTYPE=M,CHKUSER_RCPTLIMIT=50,CHKUSER_WRONGRCPTLIMIT=10,QMAILQUEUE=/var/qmail/bin/simscan,DKSIGN=/var/qmail/control/domainkeys/%/private,NOP0FCHECK=1 When I remove the QMAILQUEUE=.. part and do a qmailctl cdb, the mail starts being accepted. The only problem is that AV and Spam are not being processed. I am running a regular qmail-toaster with Fedora Core 6 arch i686 The server is now working, but with no scanning, i'd appreciate any suggestions that you may have to fix this. Thanks in advance Pablo Zavalia Ariel escribió: steps taken 1 - qmailctl stop 2 - rpmbuild package clamv* 3 - rpm -e clamav-toaster-0.92.1-1.3.17 --nodeps 4 - rpm -i clamav-toaster-0.93-1.3.18.i386.rpm works OK - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Update of ClamAV Solved
What are the corresponding smtp and spamd log messages when the message is rejected? Pablo Zavalia wrote: I've upgraded my clam clamav-toaster-0.92-1.3.16 which was working fine for the new released version clamav-toaster-0.93-1.3.18. Installation went ok, the package manager reported that it was installed fine. The thing es that mail is not being accepted, here's is an example of an smtp transaction: - 220 qmailserver.example.com - SMTP Server ESMTP - EHLO sender.example.com - 250-hostname.example.com - SMTP Server - 250-STARTTLS - 250-PIPELINING - 250-8BITMIME - 250-SIZE 20971520 - 250 AUTH LOGIN PLAIN CRAM-MD5 - AUTH CRAM-MD5 - 334 ( CRAM MD5 auth ) - (more auth) - 235 ok, go ahead (#2.0.0) - MAIL FROM:[EMAIL PROTECTED] - 250 ok - RCPT TO:[EMAIL PROTECTED] - 250 ok - DATA - 354 go ahead - Date: Thu, 01 May 2008 20:47:10 -0400 - Subject: test Thu, 01 May 2008 20:47:10 -0400 - - This is a test mailing - - . ** 451 mail server temporarily rejected message (#4.3.0) - QUIT - 221 qmailserver.example.com - SMTP Server This stopped working after the upgrade, my tcp.smtp is: 127.:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1 :allow,BADMIMETYPE=,RBLSMTPD=,SENDER_NOCHECK=1,BADLOADERTYPE=M,CHKUSER_RCPTLIMIT=50,CHKUSER_WRONGRCPTLIMIT=10,QMAILQUEUE=/var/qmail/bin/simscan,DKSIGN=/var/qmail/control/domainkeys/%/private,NOP0FCHECK=1 When I remove the QMAILQUEUE=.. part and do a qmailctl cdb, the mail starts being accepted. The only problem is that AV and Spam are not being processed. I am running a regular qmail-toaster with Fedora Core 6 arch i686 The server is now working, but with no scanning, i'd appreciate any suggestions that you may have to fix this. Thanks in advance Pablo Zavalia Ariel escribió: steps taken 1 - qmailctl stop 2 - rpmbuild package clamv* 3 - rpm -e clamav-toaster-0.92.1-1.3.17 --nodeps 4 - rpm -i clamav-toaster-0.93-1.3.18.i386.rpm works OK -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Update of ClamAV Solved
Thanks for the reply Eric, that was quick! Smtp logs this: @4000481a6504112f8364 tcpserver: pid 7772 from MY-DESKTOP-IP @4000481a6504112f8b34 tcpserver: ok 7772 qmailserver.example.com:server-ip:25 :MY-DESKTOP-IP::25380 @4000481a650420c9c6a4 tcpserver: status: 11/100 @4000481a650421d03e0c CHKUSER relaying rcpt: from [EMAIL PROTECTED]:[EMAIL PROTECTED]: remote desktop:unknown:desktop-ip rcpt [EMAIL PROTECTED] : client allowed to relay @4000481a650503bfb974 qmail-smtpd: qq soft reject (mail server temporarily rejected message (#4.3.0)): MAILFROM:[EMAIL PROTECTED] RCPTTO:[EMAIL PROTECTED] @4000481a650503e1dfa4 tcpserver: end 7772 status 0 Nothing comes up in spamd log. I wonder why. Moreover I tried to run the simscan binary and i got this: $ /var/qmail/bin/simscan Segmentation fault I'm puzzled... Pablo Eric Shubert escribió: What are the corresponding smtp and spamd log messages when the message is rejected? Pablo Zavalia wrote: I've upgraded my clam clamav-toaster-0.92-1.3.16 which was working fine for the new released version clamav-toaster-0.93-1.3.18. Installation went ok, the package manager reported that it was installed fine. The thing es that mail is not being accepted, here's is an example of an smtp transaction: - 220 qmailserver.example.com - SMTP Server ESMTP - EHLO sender.example.com - 250-hostname.example.com - SMTP Server - 250-STARTTLS - 250-PIPELINING - 250-8BITMIME - 250-SIZE 20971520 - 250 AUTH LOGIN PLAIN CRAM-MD5 - AUTH CRAM-MD5 - 334 ( CRAM MD5 auth ) - (more auth) - 235 ok, go ahead (#2.0.0) - MAIL FROM:[EMAIL PROTECTED] - 250 ok - RCPT TO:[EMAIL PROTECTED] - 250 ok - DATA - 354 go ahead - Date: Thu, 01 May 2008 20:47:10 -0400 - Subject: test Thu, 01 May 2008 20:47:10 -0400 - - This is a test mailing - - . ** 451 mail server temporarily rejected message (#4.3.0) - QUIT - 221 qmailserver.example.com - SMTP Server This stopped working after the upgrade, my tcp.smtp is: 127.:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1 :allow,BADMIMETYPE=,RBLSMTPD=,SENDER_NOCHECK=1,BADLOADERTYPE=M,CHKUSER_RCPTLIMIT=50,CHKUSER_WRONGRCPTLIMIT=10,QMAILQUEUE=/var/qmail/bin/simscan,DKSIGN=/var/qmail/control/domainkeys/%/private,NOP0FCHECK=1 When I remove the QMAILQUEUE=.. part and do a qmailctl cdb, the mail starts being accepted. The only problem is that AV and Spam are not being processed. I am running a regular qmail-toaster with Fedora Core 6 arch i686 The server is now working, but with no scanning, i'd appreciate any suggestions that you may have to fix this. Thanks in advance Pablo Zavalia Ariel escribió: steps taken 1 - qmailctl stop 2 - rpmbuild package clamv* 3 - rpm -e clamav-toaster-0.92.1-1.3.17 --nodeps 4 - rpm -i clamav-toaster-0.93-1.3.18.i386.rpm works OK
Re: [qmailtoaster] SpamDyke downside?
what about a spec file? :-) On Wed, Apr 30, 2008 at 2:23 PM, Eric Shubert [EMAIL PROTECTED] wrote: Just for the record, I agree with everything Sam says here. (Not that it matters much ;) ) Sam Clippinger wrote: spamdyke has no flaws, I thought everyone knew that. :) Perhaps I should update the FAQ. To answer your questions: Once enabled, spamdyke's graylist filter will block anything that isn't explicitly whitelisted, including newsletters, mailing lists, etc. Some mailing lists (depending on the mailing list software) use tagged senders, which means that every message appears to come from a different sender. This is done so that bounced messages can be more easily matched with a specific mailing list and recipient. (Ezmlm and Yahoo lists both use tagged senders. Mailman does not. I'm not sure about Listserv and Majordomo.) For those kinds of lists, every message is graylisted. This isn't really a problem however, as the remote server will simply retry delivery and the message will be received. The QMT list uses tagged senders and I receive its messages just fine. Some users may complain about the (small) delay, however. I'll probably incorporate some heuristics in a future version of spamdyke to allow mailing lists with tagged senders to bypass graylisting (but it may be a while before that's done). Online ticket orders, receipts, password verifications and other automated messages should pass the graylist filter as long as they are being sent from a real mail server. In other words, as long as the remote server attempts to redeliver the message, it will be received. Graylisting works fine with all of the major email hosts and every mail server I've ever encountered. An SSL certificate is only needed for using TLS (an encryption protocol that allows email to be sent securely). Only one certificate can be installed on a server (one per domain is not possible) but you don't have to pay for it -- a self-signed certificate works just fine. The sender and recipient blacklists are just text files, so editing them is very easy. The graylist system uses a directory structure that contains files named after the senders and recipients. It's not as easy to edit manually (nor is it difficult) but you shouldn't ever need to. spamdyke has no mechanism for saving rejected messages. It works by rejecting the message before the remote server even sends it, so spamdyke never sees its content. For that reason, it is not possible to recover rejected messages. However, spamdyke does log the sender and recipient addresses for every message (accepted or rejected), along with the reason the message was rejected. This does make it possible to determine if a delivery was attempted and why it failed. Obviously, I've been using spamdyke for years now with no problems. spamdyke has an active mailing list (subscribe at www.spamdyke.org) with many helpful and responsive people. You should probably pose these questions there to see what they have to say. -- Sam Clippinger Kent Busbee wrote: I've heard so many good things about spamdyke, I am wondering what flaws it might have. From my understanding greylisting is the key to its success. -Will it block wanted newsletters, email lists, email subscriptions? Or will it greylist the first attempt and then deliver the next a day, week, or month later. -Will it unintentionally prevent things like online tickets orders, receipts from online orders, password verifications, etc. -Does it work well with the major online email systems accepting emails from gmail, yahoo, hotmail, etc. -Do you need an Certificate SSL for your site? For each site hosted? -Is it easy to tweek the lists? Move an address/domain from greylist to whitelist or blacklist? -If a message is lost/rejected/greylisted, is it possible to pull it back and deliver it? -What other problems/unexpected results did you get from installing? -- -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]
